Termination cause codes
(Moved information from https://docs.telcobridges.com/tbwiki/Toolpack:Protocol_Stack_Settings_A#Redirection here) |
(Added the process to create reason cause codes following our standard way of working) |
||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | ==General | + | ==General Configuration== |
| Line 28: | Line 28: | ||
For each redirection cause code, choose '''Process''' to let the routing scripts process the redirection. Choose '''Stop''' to drop calls when receiving a redirection and use the above table to specify if the redirection contents should be dropped. | For each redirection cause code, choose '''Process''' to let the routing scripts process the redirection. Choose '''Stop''' to drop calls when receiving a redirection and use the above table to specify if the redirection contents should be dropped. | ||
| − | + | ||
| − | + | '''To Modify a reason cause code:''' | |
| − | [[Image: | + | |
| + | |||
| + | 1- Click '''Profiles''' in the navigation panel. | ||
| + | |||
| + | [[Image:Configure_ReasonCause_0.png]] | ||
| + | |||
| + | |||
| + | 2- Select a profile: | ||
| + | |||
| + | [[Image:Configure_ReasonCause_1.png]] | ||
| + | |||
| + | |||
| + | 3- Click '''Edit Reason Cause Mapping''': | ||
| + | |||
| + | [[Image:Configure_ReasonCause_2.png]] | ||
| + | |||
| + | |||
| + | 4- Select the reason cause that you wish to create: | ||
| + | |||
| + | [[Image:Configure_ReasonCause_3.png]] | ||
| + | |||
| + | |||
| + | 5- Configure the reason cause values | ||
| + | *Click '''Create''' | ||
| + | |||
| + | [[Image:Configure_ReasonCause_4.png]] | ||
<br> | <br> | ||
Latest revision as of 08:57, 10 October 2018
General Configuration
When configuring termination cause codes, use the following table as a guide. The Drop column represents codes to use when redirection contents should be dropped and the call should be terminated with the specified code. The Forward column represents codes to use when redirection contents should be forwarded to the incoming leg with the specified code. If the redirection requests must be processed, the codes are not used.
| Code | Drop | Forward | ||
|---|---|---|---|---|
| SS7 | SIP | SS7 | SIP | |
| 14 | 21 | 603 | 14 | 300 |
| 22 | 21 | 410 | 22 | 301 |
| 23 | 21 | 410 | 23 | 302 |
| 300 | 21 | 603 | 23 | 300 |
| 301 | 21 | 410 | 22 | 301 |
| 302 | 21 | 410 | 23 | 302 |
| 305 | 21 | 603 | 23 | 305 |
| 380 | 21 | 603 | 23 | 380 |
For each redirection cause code, choose Process to let the routing scripts process the redirection. Choose Stop to drop calls when receiving a redirection and use the above table to specify if the redirection contents should be dropped.
To Modify a reason cause code:
1- Click Profiles in the navigation panel.
2- Select a profile:
3- Click Edit Reason Cause Mapping:
4- Select the reason cause that you wish to create:
5- Configure the reason cause values
- Click Create
Complete list of Reason Cause mapping between the protocols:
Case for the 603 DECLINE and 200 TOOLPACK NORMAL
The TOOLPACK_NORMAL reason code is mapped to the 603_DECLINE reason code. The reason for this is the following:
A SIP BYE does not include a cause code, so on a normal call terminations, TMedia will send a BYE on SIP, and internally, a 200 TOOLPACK_NORMAL (in the logs and the CDRs). When the call terminates unexpectedly, for example after a ACM, but before a ANM, Tmedia will still send a BYE on SIP, but internally, it will log a 603 Decline (REASON_CODE_603_DECLINE).
