Template:SIP TEST FACT DESCRIPTION TEST REDIR DIVHDR FAILS: Difference between revisions
Jump to navigation
Jump to search
(New page: The PBX is configured to send a SIP ''Diversion:'' header along with a redirected call. An incoming call from the PSTN is redirected to an external destination. At the final destination,...) |
No edit summary |
||
| Line 1: | Line 1: | ||
The PBX is configured to send a SIP ''Diversion:'' header along with a redirected call. An incoming call from the PSTN is redirected to an external destination. At the final destination, the proper (original) ''calling line did (CLI)'' is verified. This is done both for CFU and CFNR. | The PBX is configured to send a SIP ''Diversion:'' header along with a redirected call. An incoming call from the PSTN is redirected to an external destination. At the final destination, the proper (original) ''calling line did (CLI)'' is verified. This is done both for CFU and CFNR. | ||
Note that this test less meaningful if the provider supports straight ''clip no screening (CLNS)''. In this case, the CLI at receiving end will be correct even if the ''Diversion:'' header is not evaluated by the provider at all. However, if CLNS is not supported and the test still succeeds, a redirected call will carry a correct CLI due to the header information. | Note that this test is less meaningful if the provider supports straight ''clip no screening (CLNS)''. In this case, the CLI at receiving end will be correct even if the ''Diversion:'' header is not evaluated by the provider at all. However, if CLNS is not supported and the test still succeeds, a redirected call will carry a correct CLI due to the header information. | ||
Latest revision as of 12:34, 28 December 2017
The PBX is configured to send a SIP Diversion: header along with a redirected call. An incoming call from the PSTN is redirected to an external destination. At the final destination, the proper (original) calling line did (CLI) is verified. This is done both for CFU and CFNR.
Note that this test is less meaningful if the provider supports straight clip no screening (CLNS). In this case, the CLI at receiving end will be correct even if the Diversion: header is not evaluated by the provider at all. However, if CLNS is not supported and the test still succeeds, a redirected call will carry a correct CLI due to the header information.