DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
Use this window to specify for SIP trunk groups which cause map profiles control the mapping of CPC (Call Processing Component) cause codes to/from SIP status codes, and which profile controls mapping between internal cause codes and SIP status codes. The SBC provides default cause map profiles you can assign or you can assign custom profiles you created.
To View and Edit Cause Code Mapping
On the SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Trunk Group > Sip Trunk Group > Signaling > Cause Code Mapping. The Cause Code Mapping window opens.
Use the drop-down lists to select the Address Context, Zone and SIP Trunk Group. The Edit Cause Code Mapping options open.
Sip Trunk Group - Signaling - Cause Code Mapping
Use the following table to specify parameters and click Save.
Cause Code Mapping Parameters
Parameter | Description |
|---|---|
CPC SIP Cause Mapping Profile | Specify the name of cause mapping profile to use for CPC to SIP status code mapping. Select one of the default profiles: defaultCpcSip, defaultQ1912CpcSip, defaultRfc3398CpcSip, or defaultTs29163CpcSip, or specify the name of a custom profile. |
SIP CPC Cause Mapping Profile | Specify the name of cause mapping profile to use for SIP status code to CPC mapping. Select one of the default profiles: defaultQ1912SipCpc, defaultRfc3398SipCpc, defaultSipCpc, defaultTs29163SipCpc, or specify the name of a custom profile. |
Use Non Default Cause Codefor ARSBlack List | Enable this option to use cause code 168 for route rejection due to ARS blacklisting.
|
SIP Internal Cause Mapping Profile | Specify the name of cause mapping profile to use for internal cause code to SIP status code mapping. |
Overview
Content Tools