Page History
| Noprint | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
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.
| Caption | ||||
|---|---|---|---|---|
| ||||
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.
...
| 0 | Figure |
|---|---|
| 1 | 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.
...
| Include Page | ||
|---|---|---|
|
...
...
The Edit Selected Cause Map window is displayed below.
| Caption | ||||
|---|---|---|---|---|
| ||||
|
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.
| Caption | ||||
|---|---|---|---|---|
| ||||
The Create New Cause Map window is displayed.
...
|
...
The following fields are displayed:
...
| 0 | Table |
|---|---|
| 1 | Trunk Provisioning - Trunk Provisioning - SIP Trunk Group |
...
Parameter
...
Description
...
Specifies the option to configure custom SIP cause response codes. Options are:
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 sipTrunkGroup congestionHandling - CLI to configure these parameters.
Other Req Rate Policing– Cause code when a message rate other than REGISTER or SUBSCRIBE exceeds IP trunk group's maximum configured value.Register Rate Policing– Cause code when REGISTER message rate exceeds IP trunk group's maximum configured value.Register TGLimit– Cause code when current REGISTRATION exceeds IP trunk group's maximum registration limit.Register Timeout– Cause code from REGISTER request timeout.Subscription Rate Policing– Cause code when SUBSCRIBE message rate exceeds IP trunk group's maximum configured value.Subscription TGLimit– Cause code when current Subscription on IP trunk group exceeds maximum configuration limit.
...
Sip Cause
...
|
...
|
...
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.
| Caption | ||||
|---|---|---|---|---|
| ||||
|
Click Copy Cause Map tab on the Cause Maps List panel.
| Caption | ||||
|---|---|---|---|---|
| ||||
|
The Copy Selected Cause Map window is displayed along with the field details which can be edited.
| Caption | ||||
|---|---|---|---|---|
| ||||
|
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.
| Caption | ||||
|---|---|---|---|---|
| ||||
|
Click Delete at the end of the highlighted row. A delete confirmation message appears seeking your decision.
...
|
...
...
Click OK to remove the specific Cause Map from the list.
Overview
Content Tools