Template:SIP Profile Test CLNS clns 302 not recommended: Difference between revisions
Jump to navigation
Jump to search
(New page: This provider supports call redirection using the SIP ''302 Redirect'' header. {{Template:SIP_Profile_how_to_enable_reroute}} : However, during our test other interop problems were disco...) |
No edit summary |
||
| Line 1: | Line 1: | ||
This provider supports call redirection using the SIP ''302 Redirect'' header. {{Template:SIP_Profile_how_to_enable_reroute}} | This provider supports call redirection using the SIP ''302 Redirect'' header. {{Template:SIP_Profile_how_to_enable_reroute}} | ||
: However, during our test other interop problems were discovered when the | : 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. | ||
Latest revision as of 15:51, 18 August 2016
This provider supports call redirection using the SIP 302 Redirect header. 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.