...
| borderColor | green |
|---|
| bgColor | transparent |
|---|
| borderWidth | 2 |
|---|
Back to Table of Contents
Back to SBC SIP Transparency Implementation Guide
...
...
...
...
...
...
...
...
Overview
The
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 . The 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
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.
| Include Page |
|---|
| Transparency_Profile_Note |
|---|
| Transparency_Profile_Note |
|---|
|
SBC ERE Configuration
...
...
...
...
...
| Create IP Signaling Profile |
|---|
|
...
| Create IP Signaling Profile |
|---|
|
...
Create IP Signaling Profile
To create the IP Signaling Profile, execute the following command:
| Code Block |
|---|
% set profiles signaling ipSignalingProfile |
...
...
| Create Cause Code Mapping Profile |
|---|
|
...
| Create Cause Code Mapping Profile |
|---|
|
...
Create Cause Code Mapping Profile
To create the Cause Coding Mapping Profile, execute the following command:
| Code Block |
|---|
% set profiles signaling ipSignalingProfile IPSP1 egressIpAttributes sipCauseMapping |
| Code Block |
|---|
% set profiles signaling ipSignalingProfile |
...
IPSP1 egressIpAttributes sipCauseMapping internalToSipCauseMappingProfileName ERE_CPC2SIP |
| Code Block |
|---|
% set profiles signaling ipSignalingProfile |
...
IPSP1 egressIpAttributes sipCauseMapping sipToInternalCauseMappingProfileName ERE_SIP2CPC |
...
| Create Profile to Map CPC and SIP |
|---|
|
...
| Create Profile to Map CPC and SIP |
|---|
|
...
Create Profile to Map CPC and SIP
| Code Block |
|---|
% set profiles signaling sipCauseCodeMapping sipToCpcCauseMapProfile ERE_SIP2CPC baseProfile defaultSipCpc causeMap 482 cpcCause 70 |
| Code Block |
|---|
% set profiles signaling sipCauseCodeMapping cpcToSipCauseMapProfile ERE_CPC2SIP baseProfile defaultCpcSip causeMap 70 sipCause 405 |
...
| Attach Cause Code Mapping Profile to Trunk Groups |
|---|
|
...
| Attach Cause Code Mapping Profile to Trunk Groups |
|---|
|
...
Attach Cause Code Mapping Profile to Trunk Groups
To 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 ERE_SIP2CPC |
| Code Block |
|---|
% set addressContext default zone Zone1 sipTrunkGroup SIPTG_2 signaling causeCodeMapping cpcSipCauseMappingProfile ERE_CPC2SIP |
Egress
| Code Block |
|---|
% set addressContext default zone Zone2 sipTrunkGroup SIPTG_1 signaling causeCodeMapping sipCpcCauseMappingProfile ERE_SIP2CPC |
| Code Block |
|---|
% set addressContext default zone Zone2 sipTrunkGroup SIPTG_1 signaling causeCodeMapping cpcSipCauseMappingProfile ERE_CPC2SIP |
External PSX
...
Configuration
Create 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 |
|---|
| Create Cause Code Mapping Profile_psx |
|---|
| Create Cause Code Mapping Profile_psx |
|---|
|
Create 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 |
|---|
| Create Profile to Map CPC and SIP_psx |
|---|
| Create Profile to Map CPC and SIP_psx |
|---|
|
Create 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 |
|---|
| Attach Cause Code Mapping Profile to Trunk Groups_psx |
|---|
| Attach Cause Code Mapping Profile to Trunk Groups_psx |
|---|
|
Attach 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 |
...