In this section:

Related articles:

Use this window to work with CPC-to-SIP cause mapping profiles on the node. These profiles can be assigned to SIP trunk groups and map internal CPC (Call Processing Component) cause codes to SIP status codes.The SBC provides four mapping profiles by default that you can assign to trunk groups. The default profiles cannot be modified or deleted. However, you can create custom mapping profiles which you can assign to trunk groups.

Note

The SBC supports SIP Cause Code Mapping for CPC to SIP for trunk groups regardless of the signaling zone. For more information, refer to SIP Profiles.


SBC Core supports up to 64 SIP-to-CPC and 64 CPC-to-SIP cause code mapping profiles.

To View CPC To SIP Cause Map Profiles

On the SBC main screen, go to Configuration > Profile Management > Category: Signaling Profiles > SIP Cause Code Mapping > CPC To SIP Cause Map Profile or
All > Profiles > Signaling > SIP Cause Code Mapping > CPC To SIP Cause Map Profile

The CPC To SIP Cause Map Profile window opens.

Profile Management - Signaling Profiles - CPC To SIP Cause Map Profile

 

To Create a CPC To SIP Cause Map Profile

To create a new CPC To SIP cause map profile:

  1. Click New CPC To SIP Cause Map Profile. The Create New CPC To SIP Cause Map Profile window opens.

    Create New CPC To SIP Cause Map Profile Window

  2. Use the following table to enter general parameters for the profile and click Save.

CPC To SIP Cause Map Profile Parameters

Parameter

Description

Name

The name for the new CPC to SIP cause map profile. This name cannot start with the string "default."

Base Profile

The name of one of the four default cause map profiles to base the new profile on. These CPC-to-SIP base profiles are:

  • Default CPC SIP – current default mappings
  • Default Q1912 CPC SIP – based on Q1912.5
  • Default RFC3398 CPC SIP – based on RFC 3398
  • Default TS29163 CPC SIP – based on 3GPP TS 29.163

The cause maps from the base profile that you select are applied to the profile that you create. You can then create additional cause maps for the custom profile that override what is specified in the base profile. Specifying a base profile is optional.

Unrec Action

Specifies the SIP cause value to use when an unrecognized ISUP cause value is received a value that is not mapped in the profile:

  • Q1912Procedure – Use the default value for the ISUP class of the unrecognized cause code and map that value to the SIP cause value, the default in DefaultQ1912CpcSip.
  • RFC3398Procedure – Use a SIP 500 message (SERVER INTERNAL ERROR), the default in DefaultRFC3398CpcSip.

Include Q850Reason

Specifies whether SIP error messages associated with this profile will include a Reason header Q.850 value taken from the Q850REASON parameter.

  • Disabled (default) – the SIP error message does not include a Q850 REASON value
  • Enabled – SIP error messages associated with this profile will include a Reason header Q.850 value taken from the Q850REASON parameter.
Note:

The specific CPC to SIP code mappings within the profile are created on the Cause Map window. Refer to CPC To SIP Cause Map Profile - Cause Map.

To Edit a CPC To SIP Cause Map Profile

The default profiles cannot be edited. To edit a CPC To SIP cause map profile you added:

  1. Click the radio button next to the name of the profile you want to edit. The Edit Selected CPC To SIP Cause Map Profile window opens.
  2. Make the required changes and click Save.

To Delete a CPC To SIP Cause Map Profile

The default profiles cannot be deleted. To delete any of the CPC To SIP cause map profile you added:

  1.  Click the radio button next to the specific CPC To SIP cause map profile you want to delete.
  2. Click the X at the end of the row to delete.
  3. Confirm the deletion when prompted.

 

  • No labels