Template:SIP Profile Test CLNS clns 302 optional: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This provider supports call redirection using the SIP ''302 Redirect'' header. | This provider supports call redirection using the SIP ''302 Redirect'' header. {{Template:SIP_Profile_how_to_enable_reroute}} | ||
: However, this configuration is not strictly required, as the provider supports ''clip no screening'' so that redirected calls (i.e. call forwards to external numbers) will show a proper calling line id (CLI) at the receiving party anyway. However, it may be useful anyhow to get rid of externally forwarded calls on the SBC entirely. | : However, this configuration is not strictly required, as the provider supports ''clip no screening'' so that redirected calls (i.e. call forwards to external numbers) will show a proper calling line id (CLI) at the receiving party anyway. However, it may be useful anyhow to get rid of externally forwarded calls on the SBC entirely. | ||
Latest revision as of 17:33, 29 July 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, this configuration is not strictly required, as the provider supports clip no screening so that redirected calls (i.e. call forwards to external numbers) will show a proper calling line id (CLI) at the receiving party anyway. However, it may be useful anyhow to get rid of externally forwarded calls on the SBC entirely.