Hi Paul & Brett, Thanks for your detailed clarification. Just final doubt if
in the INVITE request will have "Request-Disposition: no-fork" then Call
forwarding will not happen for that request ?
Thanks,Sourav
On Tuesday, 5 May 2015 6:53 PM, Paul Kyzivat wrote:
On 5/5/15 4:21 AM
On 5/5/15 4:21 AM, Sourav Dhar Chaudhuri wrote:
Hi Paul,
Thanks for your response. So it means the Call Forwarding always
need minimum requirement that Caller [UAC] must have support for
handling forking response in case SBC does not have the "fix" you mentioned.
Also my second doubt wh
> Also my second doubt why this thing not been properly
> highlighted in RFC 5359.
Section 1 indicates the following.
"These call flows are based on the current version 2.0 of SIP in RFC
3261 [RFC3261] with Session Description Protocol (SDP) usage
described in RFC 3264 [RFC3264]. Other RFCs also
Hi Paul, Thanks for your response. So it means the Call Forwarding always
need minimum requirement that Caller [UAC] must have support for handling
forking response in case SBC does not have the "fix" you mentioned.
Also my second doubt why this thing not been properly highlighted in RFC
5
