Template:SIP Profile Test CLNS no clns 302 not recommended: Difference between revisions
Jump to navigation
Jump to search
m (New page: Call redirection using the SIP ''302 Redirect'' header is supported by the provider. {{Template:SIP_Profile_how_to_enable_reroute}} : However, during our test other interop problems wer...) |
No edit summary |
||
Line 1: | Line 1: | ||
Call redirection using the SIP ''302 Redirect'' header is supported by the provider. {{Template:SIP_Profile_how_to_enable_reroute}} | Call redirection using the SIP ''302 Redirect'' header is supported by the provider. {{Template:SIP_Profile_how_to_enable_reroute}} | ||
: However, during our test other interop problems were discovered when the ''Interworking'' Flag is enabled. Therefore it is not recommended to use the call redirection via SIP ''302 Redirect'' header. | : However, during our test other interop problems were discovered when the ''Interworking'' Flag is enabled. Therefore it is not recommended to use the call redirection via SIP ''302 Redirect'' header. | ||
: We recommend to set the ''Set Calling = Diverting No'' check-mark in the PBX ''Trunk'' object. This way, the calls will at least carry the user's own extension as calling party number (CGPN/CLI) when alerting at the mobile device/forwarding destination. |
Revision as of 16:53, 23 August 2016
Call redirection using the SIP 302 Redirect header is supported by the provider. Rerouting can be enabled by setting the Reroute supported check-mark in the corresponding Trunk object configuration. Also, the Interworking check-mark must be set in the route used for calls from and to the SIP provider.
- However, during our test other interop problems were discovered when the Interworking Flag is enabled. Therefore it is not recommended to use the call redirection via SIP 302 Redirect header.
- We recommend to set the Set Calling = Diverting No check-mark in the PBX Trunk object. This way, the calls will at least carry the user's own extension as calling party number (CGPN/CLI) when alerting at the mobile device/forwarding destination.