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.

In this section:

To View Cause Map

On SBC main screen, go to All > Profiles > Signaling > Sip Cause Code Mapping > Internal Sip Cause Map Profile > Cause Map. The Cause Map window is displayed.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map

The Cause Map can be checked for each Internal Sip Cause Map Profile or for all the Internal Sip Cause Map Profiles created. Use the drop-down box to select the desired Internal Sip Cause Map Profile.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map - Main Field

 

To Edit Cause Map

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

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map Highlighted

 

The Edit Selected Cause Map window is displayed below.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map - Edit Window

 

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

To Create Cause Map

To create a new Cause Map, click New Cause Map tab on the Cause Map List panel.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map Fields

The Create New Cause Map window is displayed.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map - Create Window

 

The following fields are displayed:

Trunk Provisioning - Trunk Provisioning - SIP Trunk Group

Parameter

Description

Internal Cause

Specifies the option to configure custom SIP cause response codes. Options are:

  • Peer Bidirectional Blocked - SIP cause used when the peer has the bidirectional blocked.
  • Peer in Disabled State - SIP cause used when the peer is in disabled state.
  • Peer Incoming Blocked - SIP cause used when the peer has the incoming calls blocked.
  • Peer Outgoing Blocked - SIP cause used when the peer has the outgoing calls blocked.
  • Peer Out of Service - SIP cause code used when the peer is out-of-service.
  • Trunk Group Bidirectional Blocked - SIP cause code used when the trunk group has the bidrectional calls blocked.
  • Trunk Group in Disabled - SIP cause code used when the trunk group is in disabled state.
  • Trunk Group Incoming blocked - SIP cause code used when the trunk group has the incoming calls blocked.
  • Trunk Group Outgoing blocked - SIP cause code used when the trunk group has the outgoing calls blocked.
  • Trunk Group Out of Service - SIP cause code used when the trunk group is out-of-service.
     
  • Congestion Policing  – SIP cause code used when an initial SUBSCRIBE request is rejected due to Adaptive Overload Control. This internal cause code is mapped to 503 by default, and a Retry-After header is added to SIP response. The Retry-After value is randomized between 'retryAfterMin' and 'retryAfterMax' values. The 'retryAfterMin' and 'retryAfterMax' values must be configured under Ingress Trunk Group in CLI. Refer to SIP Trunk Group - Congestion Handling - CLI to configure these parameters.
  • DNS Rcode Error – SIP cause code to allow 500 and 503 error code mapping to a configurable response code.
  • Other Req Rate Policing –  SIP cause code when a message rate other than REGISTER or SUBSCRIBE exceeds IP trunk group's maximum configured value.
  • Register Rate Policing  – SIP cause code when REGISTER message rate exceeds IP trunk group's maximum configured value.
  • Register TGLimit – SIP  cause code when current REGISTRATION exceeds IP trunk group's maximum registration limit.
  • Register Timeout – SIP cause code from REGISTER request timeout.
  • Subscription EndPoint Rate Policing  –  SIP cause code to map SUBSCRIBE Endpoint CAC default error response.

  • Subscription Rate Policing – SIP cause code when SUBSCRIBE message rate exceeds IP trunk group's maximum configured value.

  • Subscription TGLimit – SIP cause code when current Subscription on IP trunk group exceeds maximum configuration limit.

Sip Cause

Specifies the response code to use when a received SIP message other than an INVITE or a REGISTER is rejected due to congestion in the SBC. The value ranges from 300 to 606.
Sip Cause TextSpecifies the Internal SIP Cause text that is used in the Reason Header of the error response to reject the SUBSCRIBE Request. The value ranges from 0 -127 characters.

To Copy Cause Map

To copy any of the created Cause Maps and to make any minor changes, click the radio button next to the specific Cause Map to highlight the row.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map Highlighted

 

Click Copy Cause Map tab on the Cause Maps List panel.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map Fields

 

The Copy Selected Cause Map window is displayed along with the field details which can be edited.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map - Copy Window

 

Make the required changes to the required fields and click Save to save the changes. The copied Cause Map is displayed at the bottom of the original Cause Map in the Cause Map List panel.

To Delete Cause Map

To delete any of the created Cause Map, click the radio button next to the specific Cause Map which you want to delete.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map Highlighted

 

Click Delete at the end of the highlighted row. A delete confirmation message appears seeking your decision.

Profiles - Signaling - Internal Sip Cause Map Profile - Cause Map - Delete Confirmation

 

Click Yes to remove the specific Cause Map from the list.