Hi,
In the first scenario, the UAS is NOT behaving according to
RFC3262. It MUST reject the INVITE with 420 (Bad Extension) if it does
NOT support 100rel. If you really want to handle this scenario, I
would suggest silently dropping the non-reliable 180, as you were
expecting a reliable 180.
Hi,
Thanks for the reply, but rfc 3262 does not clearly mention what to do
in these scenarios.
Regards,
Soma
On Tue, 2009-06-30 at 12:43 -0400, Alejandro Orellana wrote:
> Please refer to http://www.ietf.org/rfc/rfc3262.txt
>
> thanks
>
> On Tue, Jun 30, 2009 at 11:48 AM, soma bhargava
> wrot
Please refer to http://www.ietf.org/rfc/rfc3262.txt
thanks
On Tue, Jun 30, 2009 at 11:48 AM, soma bhargava <
soma.bharg...@globaledgesoft.com> wrote:
> Hi All,
>
> What is the behaviour of UAC in following scenario:
>
> 1. UAC sends INVITE with 100rel in both requires and supported headers.
> UA
Hi All,
What is the behaviour of UAC in following scenario:
1. UAC sends INVITE with 100rel in both requires and supported headers.
UAS sends 180 prov resp without 100rel in both requires and supported
headers. what should the UAC do?
2. Invite is sent without 100rel in both require and support
