| Add_workflow_for_techpubs |
|---|
|
...
Overview
A new configuration is added to IP Signaling Profile of PSX to specify the Cause Code Mapping profile names. PSX returns the Cause Code profile names in the POL responses. SBC uses the Cause Code profile names specified by PSX.
SBC applies the Cause Code Mapping profile in the following order:
If a policy response contains a profile name and a locally configured profile uses the same name, SBC applies the same name.
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 SIP Trunk Group created local profile name (if created).
SBC applies a default profile name if none of the above two cases match.
The following new IPSP configurations are added to PSX under SIP Cause Mapping section:
- Internal to SIP Cause Mapping Profile Name
- SIP to Internal Cause Mapping Profile Name
SBC ERE Configuration
...
| Code Block |
|---|
% set profiles signaling ipSignalingProfile DEFAULT_SIPIPSP1 |
| Anchor |
|---|
| Creating Cause Code Mapping Profile |
|---|
| Creating Cause Code Mapping Profile |
|---|
|
Creating Cause Code Mapping Profile
...
| Code Block |
|---|
% set profiles signaling ipSignalingProfile IPSP1 egressIpAttributes sipCauseMapping |
| Code Block |
|---|
% set profiles signaling ipSignalingProfile IPSP1DEFAULT_SIP egressIpAttributes sipCauseMapping internalToSipCauseMappingProfileName ERE_CPC2SIP |
| Code Block |
|---|
% set profiles signaling ipSignalingProfile DEFAULT_SIPIPSP1 egressIpAttributes sipCauseMapping sipToInternalCauseMappingProfileName ERE_SIP2CPC |
...
External PSX/ePSX Configuration
...
Creating IP Signaling Profile| Caption |
|---|
| 0 | Figure |
|---|
| 1 | IP Signaling Profile |
|---|
|
 Image Added
|
| Note |
|---|
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. |
| Anchor |
|---|
| Creating Cause Code Mapping Profile_psx |
|---|
| Creating Cause Code Mapping Profile_psx |
|---|
|
Creating Cause Code Mapping Profile| Note |
|---|
The SIP Cause Code Mapping profile names are received from External PSX in the policy response. |
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Cause Code Mapping Profile |
|---|
|
Image Added |
| Anchor |
|---|
| Creating Profile to Map CPC and SIP_psx |
|---|
| Creating Profile to Map CPC and SIP_psx |
|---|
|
Creating Profile to Map CPC and SIP| Code Block |
|---|
% set profiles signaling sipCauseCodeMapping sipToCpcCauseMapProfile PSX_SIP2CPC baseProfile defaultSipCpc causeMap 482 cpcCause 70 |
| Code Block |
|---|
% set profiles signaling sipCauseCodeMapping cpcToSipCauseMapProfile PSX_CPC2SIP baseProfile defaultCpcSip causeMap 70 sipCause 405 |
| Anchor |
|---|
| Attaching Cause Code Mapping Profile to Trunk Groups_psx |
|---|
| Attaching Cause Code Mapping Profile to Trunk Groups_psx |
|---|
|
Attaching Cause Code Mapping Profile to Trunk GroupsTo associate the created profiles with Ingress and Egress Trunk Groups, execute the following commands:
Ingress
| Code Block |
|---|
% set addressContext default zone Zone1 sipTrunkGroup SIPTG_2 signaling causeCodeMapping sipCpcCauseMappingProfile PSX_SIP2CPC |
| Code Block |
|---|
% set addressContext default zone Zone1 sipTrunkGroup SIPTG_2 signaling causeCodeMapping cpcSipCauseMappingProfile PSX_CPC2SIP |
Egress
| Code Block |
|---|
% set addressContext default zone Zone2 sipTrunkGroup SIPTG_1 signaling causeCodeMapping sipCpcCauseMappingProfile PSX_SIP2CPC |
| Code Block |
|---|
% set addressContext default zone Zone2 sipTrunkGroup SIPTG_1 signaling causeCodeMapping cpcSipCauseMappingProfile PSX_CPC2SIP |