Treating 1pcc calls via trunks as external
A new application-level options enforce-1pcc-inbound and internal-call-domains introduced to instruct SIP Server to treat 1PCC calls from external callers as inbound call.
Previously if username in the header "From:" of initial INVITE request can be matched with the name of existing DN in SIP Switch that call was treated as internal by SIP Server,
Such behavior may lead to situation when inbound call treated as internal mistakenly.
New behavior with enforce-1pcc-inbound=true will be as following: if username in the header "From:" of initial INVITE request can be matched with the name of existing DN in CME and address in the first header "Via:" is matched address mentioned in the internal-call-domains than this call will be treated as internal, otherwise it will be treated as inbound.
Option 'enforce-extenal-domains' has higher priority over the new option 'enforce-1pcc-inbound'. If call is received from address mentioned in the option 'enforce-external-domain', then feature described in this document will not be applied to it. Configuration Options These options will be developed as 'semihidden' and should not be described in Deployment Guide, because they are intended only for Pure Engage Cloud deployments.
Option Name enforce-1pcc-inbound Default Value false Changes take effect For the next call Valid Values true, false Description If set to false, behaviour of SIP Server is default. If set to true, SIP Server treats 1pcc calls from external callers as inbound. Caller is considered as internal if both conditions are satisfied: 1) username in "From:" matches with Extension DN configured in the SIP Switch; 2) Network address of caller in the first "Via:" header matches with on of IPv4 CIDR blocks or FQDN listed in the option 'internal-call-domains'.
If option 'internal-call-domains' is empty, all received 1pcc calls will be treated as inbound.