The Cause map profiles provide customized tables on the SBC to map cause codes between internal, SIP and Q850 cause codes. The custom mappings can be selected on a per-route basis, on egress trunks, as well as on a per call basis, on ingress trunks, through the IP Signaling Profile. Four preconfigured base profiles are available to either use as-is, or to build upon for SIP to CPC mapping:
DefaultSipCpc
– recommended to achieve backwards compatibility. Index is 1DefaultQ1912SipCpc
– based on Q1912.5. Index is 2DefaultRFC3398SipCpc
– based on RFC 3398. Index is 3DefaultTS29163SipCpc
– based on 3GPP TS 29.163. Index is 4The four corresponding preconfigured profiles for CPC to SIP mapping are:
DefaultCpcSip
– recommended to achieve backwards compatibility. Index is 1DefaultQ1912CpcSip
– based on Q1912.5. Index is 2DefaultRFC3398CpcSip
– based on RFC 3398. Index is 3DefaultTS29163CpcSip
– based on 3GPP TS 29.163. Index is 4In the case of both SIP to CPC and CPC to SIP there is an additional mapping corresponding to index = 0. Each corresponds to a fixed mapping implemented directly in the SBC software. Profiles corresponding to indices 0 – 4 may not be altered under any circumstances. However, when you create a new profile, it is populated using a preconfigured profile that you specify and thereafter you may add, delete, and modify entries. Each profile has a unique index (an integer in the range 5-16) associated with it. The base profiles take indices 1-4. The index of the desired profile is configured on the SBC on the ingress and egress IP Signaling profiles. After creating a new profile:
The SBC Core supports up to 64 SIP-to-CPC and 64 CPC-to-SIP cause code mapping profiles.
The following special case handling is performed for cause codes that are not present in the active Causemap profiles:
DefaultRFC3398SipCpc
because cause code 22 is absent from that profile.DefaultQ1912SipCpc
because cause code 34 is absent from that profile.This behavior is achieved by deleting the relevant cause code from the new profile.