Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: move workflow

Add_workflow_for_techpubs
AUTH1jdavy
JIRAIDAUTHSBX-88802
REV5ghoppe
REV6ghoppe
REV3rramaiah
REV4gkansal
REV1prjain
REV2mshankar

...

borderColorgreen
bgColortransparent
borderWidth2

Additional section:

...

Panel

In this section:

Table of Contents
maxLevel2

...

Info
iconfalse

Related articles:

Children Display

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.

Info
titleNote

The

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


Info

Spacevars
0series4
 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

The Cpc To Sip Cause Map Profile window is displayed.

Caption
0Figure
1Profile Management - Signaling Profiles - Cpc To Sip Cause Map Profile
 

 Image Removed

To Edit Cpc To Sip Cause Map Profile

To edit any of the Cpc To Sip Cause Map Profile in the list, click the radio button next to the specific Cpc To Sip Cause Map Profile name.

Caption
0Figure
1Profile Management - Signaling Profiles - Cpc To Sip Cause Map ProfileProfile Management - Signaling Profiles - Cpc To Sip Cause Map Profile Highlighted
 

 Image Removed

...

.

Caption
0Figure
1Profile Management - Signaling Profiles -

...

CPC To

...

SIP Cause Map Profile

...

 Image Removed

...

...

Image Added 

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

Caption
0Figure
1Profile Management - Signaling Profiles - Cpc To Sip Cause Map Profile Fields
 

 Image Removed

...

  1. .

    Caption
    0Figure
    1

...

  1. Create New CPC To SIP Cause Map Profile

...

  1. Window

...

...

  1. Image Modified

...

  1. Use the following table to enter general parameters for the profile and click Save.
Caption
0Table
1CPC 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.

...

Specifies the SIP-to-CPC cause mapping values. Enter cause map value between 1-255 and specify the following reasons:

...

sipCause – SIP Cause value for a given CPC cause value. (range: 300-606).

Note

This parameter applies to Cpc To Sip CauseMap Profile only.

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.

...

Info
titleNote:

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

To Delete Cpc To Sip Cause Map Profile

...

  1. the radio button next to the

...

  1. name of the profile you want to edit. The Edit Selected CPC To SIP Cause Map Profile

...

Caption
0Figure
1Profile Management - Signaling Profiles - Cpc To Sip Cause Map Profile Highlighted
 

 Image Removed

...

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

...

  1. row

...

  1. to delete.
  2. Confirm the deletion when prompted.

 

Pagebreak

Caption
0Figure
1Profile Management - Signaling Profiles - Cpc To Sip Cause Map Profile Delete Confirmation
 

 Image Removed

Click Yes to remove the specific Cpc To Sip Cause Map Profile from the list.

...