Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to SBC SIP Transparency Implementation Guide

...

 

...

Panel

In this section:

Table of Contents

...

...

...

...

 

Overview

The 

Spacevars
0product

...

 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

Spacevars
0product
. The 
Spacevars
0product
 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

Spacevars
0product
 applies

...

the Cause Code Mapping profile in the following order:

  1. If a policy response contains a profile name and a locally configured profile exists with the same name, SBC applies the same profile.

  2. 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).

  3. 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 IPSP1

Anchor

...

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

Anchor

...

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

Anchor

...

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

...

...

...

...

...

IPSP

...

IPSP

...

Create IP Signaling Profile

Caption
0Figure
1IP Signaling Profile

Image Modified

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
0Figure
1Cause Code Mapping Profile

Image Modified

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 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 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

Pagebreak