Oracle Session Border controller : Reason explained for Multiple to-tags within same dialog to caller. Specially in case of serial forking
(Doc ID 2373936.1)
Last updated on OCTOBER 09, 2020
Applies to:Acme Packet 6300 - Version S-Cz7.2.0 to S-Cz8.0.0 [Release S-Cz7.0 to S-Cz8.0]
Information in this document applies to any platform.
Does SBC allow multiple to-tags within same SIP call flow to caller when call forking?
In case of sip recursion call flow, kind of a serial forking on core side of SBC. After SBC receives provisional response (180/183) from outbound session-agent, followed by 503 which triggers SBC to go to next hop agent in a Session-agent group.
SBC changes the `TO' tag in dialog between itself and the caller whenever it forwards provisioning responses (180/183) to the caller from each SA.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document