This documentation reflects the implementation details for Diversion header support in Sippy.
The header contains the originally called number, and is useful in case the CLD has gotten completely rewritten before sending the call to vendor.
Developed in order to comply with Turkish Telecommunication Board requirements, could be installed on any Sippy version above 4.5.
For implementation details/cost please contact our Sales/Billing department
Areas of use:
- Call to Account that has Follow-Me enabled
- Call to Registered account via DID
- Call to Registered account forwarded to another Account
- Call to Account Trunk via DID
- Call to Calling Card and Call-back application
For extra details see RFC5806
The main place for Diversion to be configured is Connection preferences interface:
After setting Enable Diversion checkbox the translated incoming CLD would be sent in Diversion header to Vendor for one of the following events:
- Follow Me was triggered for this call
- Call came to the Callback/Calling Card IVR application
Switch operator can also set the Diversion Header Tr. Rule in order to change the Diversion number according to the Vendor requirements.
Example:
Incoming Diversion:
Diversion: <sip:[email protected]>;reason=follow-me
Outgoing Diversion:
Diversion: <sip:[email protected]>;reason=follow-me
Sippy will pass the incoming Diversion header to vendor in case neither of the events mentioned above were triggered, otherwise the incoming Diversion number would be substituted by the one generated by Sippy.
Please note, the Diversion Header Tr. Rule is applicable only to username part in Diversion header. It doesn't support the replacement of extra parameters or the actual IP/domain.
For the replacement of parameters in Diversion header you may use the external translator script:
https://support.sippysoft.com/a/solutions/articles/77914
Detailed example of the scenario with Follow Me:
Call comes to Sippy with CLD = B92071234567, authentication is done to the DID 92071234567 via Incoming DID = B92071234567. CLD Tr. Rule is applied, cutting the tech prefix B.
DID is assigned to Account diversion_test, with Onnet = Default on Routing Group, and Follow Me configured to forward all calls to 12061234567 number unconditionally (always).
Incoming Routing for Account diversion_test has Trunk = Registered Account
The call would be sent to the Follow Me leg through the Routing Group of Account diversion_test to the Test Vendor-Test connection with CLD=12061234567.
Case Diversion is enabled on connection, 92071234567 number would be sent in Diversion header, so that the vendor can do the reconfiguration based on this parameter.
Detailed example of the scenario with DID-Registered Account/Trunk:
Call comes to Sippy with CLD = B92071234567, authentication is done to the DID 92071234567 via Incoming DID = B92071234567. CLD Tr. Rule is applied, cutting the tech prefix B.
DID is assigned to Account diversion_test, with Onnet = Default on Routing Group
Incoming Routing for Account diversion_test has Trunk = Registered Account, and Fwd DID Mode = Diversion Header
The call would be sent to the Registered Account with Diversion header containing the DID call came to Sippy Softswitch, To and URI headers would have account's name.
Connected documentation links:
External Translator documentation