In this section:
Overview
The SBC supports configuring and applying Cause Mapping profiles locally during call processing. Additionally, the PSX supports configuring its IP Signaling Profile (IPSP) to specify the Cause Code Mapping profile names and return the Cause Code profile names in the Policy response to SBC. The SBC then uses these Cause Code profile names specified by PSX.
The following IPSP configurations are included in the PSX's SIP Cause Mapping section:
- Internal to SIP Cause Mapping Profile Name
- SIP to Internal Cause Mapping Profile Name
The SBC applies the Cause Code Mapping profile in the following order:
If a policy response contains a profile name and a locally configured profile exists with the same name, SBC applies the same profile.
If a policy response does not contain a profile name or if the profile name does not match with any local profile, SBC applies the local Cause Mapping profile attached to the SIP Trunk Group (if configured).
SBC applies a default profile name if none of the above two cases match.
IMPORTANT
The Transparency Profile is the recommended method of configuring transparency on the SBC Core for new deployments as well as when applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.
Refer to the SBC SIP Transparency Implementation Guide for additional information.
SBC ERE Configuration
- Create IP Signaling Profile
- Create Cause Code Mapping Profile
- Create Profile to Map CPC and SIP
- Attach Cause Code Mapping Profile to Trunk Groups
Create IP Signaling Profile
To create the IP Signaling Profile, execute the following command:
% set profiles signaling ipSignalingProfile IPSP1
Create Cause Code Mapping Profile
To create the Cause Coding Mapping Profile, execute the following command:
% set profiles signaling ipSignalingProfile IPSP1 egressIpAttributes sipCauseMapping
% set profiles signaling ipSignalingProfile IPSP1 egressIpAttributes sipCauseMapping internalToSipCauseMappingProfileName ERE_CPC2SIP
% set profiles signaling ipSignalingProfile IPSP1 egressIpAttributes sipCauseMapping sipToInternalCauseMappingProfileName ERE_SIP2CPC
Create Profile to Map CPC and SIP
% set profiles signaling sipCauseCodeMapping sipToCpcCauseMapProfile ERE_SIP2CPC baseProfile defaultSipCpc causeMap 482 cpcCause 70
% set profiles signaling sipCauseCodeMapping cpcToSipCauseMapProfile ERE_CPC2SIP baseProfile defaultCpcSip causeMap 70 sipCause 405
Attach Cause Code Mapping Profile to Trunk Groups
To associate the created profiles with Ingress and Egress Trunk Groups, execute the following commands:
Ingress
% set addressContext default zone Zone1 sipTrunkGroup SIPTG_2 signaling causeCodeMapping sipCpcCauseMappingProfile ERE_SIP2CPC
% set addressContext default zone Zone1 sipTrunkGroup SIPTG_2 signaling causeCodeMapping cpcSipCauseMappingProfile ERE_CPC2SIP
Egress
% set addressContext default zone Zone2 sipTrunkGroup SIPTG_1 signaling causeCodeMapping sipCpcCauseMappingProfile ERE_SIP2CPC
% set addressContext default zone Zone2 sipTrunkGroup SIPTG_1 signaling causeCodeMapping cpcSipCauseMappingProfile ERE_CPC2SIP
External PSX Configuration
- Create IP Signaling Profile
- Create Cause Code Mapping Profile
- Create Profile to Map CPC and SIP
- Attach Cause Code Mapping Profile to Trunk Groups
Create IP Signaling Profile
IP Signaling Profile
For “SIP in Core” SBC deployments, if the cause code received at egress SBC requires to be passed on to ingress SBC, either “Include Reason Header” flag in IP Signaling Profile needs to be enabled or a “Sip Cause Code Mapping Profile” need to be attached to SIP Core Trunk Groups.
Create Cause Code Mapping Profile
The SIP Cause Code Mapping profile names are received from External PSX in the policy response.
Cause Code Mapping Profile
Create Profile to Map CPC and SIP
% set profiles signaling sipCauseCodeMapping sipToCpcCauseMapProfile PSX_SIP2CPC baseProfile defaultSipCpc causeMap 482 cpcCause 70
% set profiles signaling sipCauseCodeMapping cpcToSipCauseMapProfile PSX_CPC2SIP baseProfile defaultCpcSip causeMap 70 sipCause 405
Attach Cause Code Mapping Profile to Trunk Groups
To associate the created profiles with Ingress and Egress Trunk Groups, execute the following commands:
Ingress
% set addressContext default zone Zone1 sipTrunkGroup SIPTG_2 signaling causeCodeMapping sipCpcCauseMappingProfile PSX_SIP2CPC
% set addressContext default zone Zone1 sipTrunkGroup SIPTG_2 signaling causeCodeMapping cpcSipCauseMappingProfile PSX_CPC2SIP
Egress
% set addressContext default zone Zone2 sipTrunkGroup SIPTG_1 signaling causeCodeMapping sipCpcCauseMappingProfile PSX_SIP2CPC
% set addressContext default zone Zone2 sipTrunkGroup SIPTG_1 signaling causeCodeMapping cpcSipCauseMappingProfile PSX_CPC2SIP
Overview
Content Tools