On 5/5/15 10:46 AM, Sourav Dhar Chaudhuri wrote:
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 ?
Yes, *IF* the proxy honored that. But the calle
Hi,
Concerning RFC 7118, "wss" was not defined as transport for SIP-URI. If
dialog setup with "transport=ws" as a SIP-URI parameter within Contact or
Record-Route entry when the connection is actually secured using wss (such
as within RFC 7118 section 8.2 example), should wss continue to be used?
There is a revision underway on SDP. The a=quality attribute has always
been underspecified. We would like to tighten up the specification, but
do so in a backward compatible way with existing usage if possible. So
far we have not identified any usage of it. If not, we will probably
leave the s
> Just final doubt if in the INVITE request will have
> "Request-Disposition: no-fork" then Call forwarding
> will not happen for that request ?
As far I know, the UAC doesn't know what will happen.
For instance, RFC 3841 section 9.1 indicates should instead of must.
"When the caller specifies a
