Treating 1pcc calls via trunks as external

FDS: https://intranet.genesys.com/pages/viewpage.action?spaceKey=RDSIPS&title=%5BFDS%5D+Treat+1pcc+calls+via+trunks+as+external

For Genesys Engage cloud deployments only. Keep it internally. Starting with version 8.1.103.32, SIP Server can treat 1pcc calls from external callers (agents behind SIP trunks) as inbound calls. Previously, if the username in the From header of the initial INVITE request matched the name of the existing DN in the SIP Switch, SIP Server treated that inbound call as an internal call.

Feature Configuration

To enable this feature:

1. Set the enforce-1pcc-inbound option to true.
2. Set the internal-call-domains option to a list of IPv4 CIDR blocks or FQDN separated by semicolons (;).

Important

Genesys recommends that you do not interchange the enforce-1pcc-inbound and enforce-external-domains options.

The enforce-external-domains option has higher priority over the enforce-1pcc-inbound option. If configuration options of the both approaches are applied, SIP Server verifies each call against the value of enforce-external-domains, as follows:

• If a match is found in enforce-external-domains, SIP Server treats a call as inbound.
• If a match is not found in enforce-external-domains and enforce-1pcc-inbound is set to true, SIP Server verifies a call against the value of the internal-call-domains option.
• If a match is found in the internal-call-domains option, and the From header value matches an Extension DN, SIP Server treats a call as internal.
• If a match is not found in the internal-call-domains option, SIP Server treats a call as inbound.

In existing deployments, consider gradual transition from the enforce-external-domains option to the enforce-1pcc-inbound option set to true/internal-call-domains to replace the use of enforce-external-domains.

Configuration Options

enforce-1pcc-inbound

Setting: TServer section, Application level
Default Value: false
Valid Values: true, false
Changes Take Effect: For the next call

When set to true, SIP Server treats 1pcc calls from external callers as inbound calls. A caller is considered internal if both conditions are met:

1. A username in the From header matches the Extension DN configured in the SIP Switch.
2. A network address of the caller in the first Via header matches the IPv4 CIDR blocks or FQDN listed in the internal-call-domains option.

If the internal-call-domains option is empty, all received 1pcc calls are treated as inbound calls.

Note: The enforce-external-domains option has higher priority over the enforce-1pcc-inbound option. If a call is received from the address specified in the enforce-external-domains option, this feature is not applied.

internal-call-domains

Setting: TServer section, Application level
Default Value: An empty string
Valid Values: A list of IPv4 CIDR blocks or FQDN separated by semicolons (;). The IP address without a wildcard means the host address—for example, "1.2.3.0" means "1.2.3.0/32".
Changes Take Effect: For the next call

If the enforce-1pcc-inbound option is set to true and the internal-call-domains option is set to a list of IP addresses, SIP Server treats 1pcc calls arriving from the addresses that match the specified list as internal calls. All other 1pcc calls are treated as inbound calls. If the option is empty, all 1pcc calls are treated as inbound calls.

Feature Limitations

• IPv6 addresses are not supported in the list of the internal-call-domains option.