On 6/11/13 9:52 AM, Johan DE CLERCQ wrote:
> Scenario :
>
> uas registers to generic proxy (next hop).
>
> As we all know, when the uas sends a register to a proxy the register request
> will have a contact header.
> Upon the proxy returning 200 OK, does this 200 OK needs to have the same
> cont
Scenario :
uas registers to generic proxy (next hop).
As we all know, when the uas sends a register to a proxy the register request
will have a contact header.
Upon the proxy returning 200 OK, does this 200 OK needs to have the same
contact header ?
Cheers, Johan.
Hi all,
I 'd like to know if ports can be renegotiated (with a new INVITE for
example) while RTP flows are already established ... !
If it is possible, in which case we can face with this situation ?
(multicast ? other ?)
Thanks for your help
___
Sip-i
I agree; the CANCEL can be sent after receiving a 100 response.
The following are some additional snippets which define "provisional response"
and why RFC 3261 introduced delaying CANCEL until 1xx received.
Section 6:
"Provisional Response: A response used by the server to indicate
progress,
