Based on the callflow diagrams, all SIP carriers between Originating carrier and Terminating carrier must support TCP SIP and allow the extended headers to be forwarded, correct?
Page 1 of 1
Based on the callflow diagrams, all SIP carriers between Originating carrier and Terminating carrier must support TCP SIP and allow the extended headers to be forwarded, correct?
by alan.percy@telcobridges.c Thu Feb 21, 2019 3:45 pm
Use of SIP/TCP is not required, the demon showed SIP/UDP across the open internet.
alan.percy@telcobridges.c- Number of Messages : 60
Point : 176
Registration Date : 2019-01-14
Similar topics» Since this requires token generation on origination and verification on the terminating carrier, do we have stats on how much PDD we expect to be added to a callflow?
» Is it fair to assume that most user-agent devices such as Polycom VVX phones, Yealink Phones currently do NOT support these new protocols? What about support from voice switches (broadworks). Do they know how to process the new headers appropriately?
» How granular do you expect the origid assignments to be (e.g., at the originating interface, at the sbc, at the carrier, or some other level)?
» Does FreeSBC hide the Media's Originating IP?
» ProSBC - Support for "IP-Based" registration for 3CX Phone System
» Is it fair to assume that most user-agent devices such as Polycom VVX phones, Yealink Phones currently do NOT support these new protocols? What about support from voice switches (broadworks). Do they know how to process the new headers appropriately?
» How granular do you expect the origid assignments to be (e.g., at the originating interface, at the sbc, at the carrier, or some other level)?
» Does FreeSBC hide the Media's Originating IP?
» ProSBC - Support for "IP-Based" registration for 3CX Phone System
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum