Hi
There was no provisional response to the ReINVITE, simple case of the UAS
(Nortel switch) misbehaving. No other signalling.
Regards
Tarun Gupta
On Fri, Dec 5, 2014 at 9:42 pm, Paul Kyzivat wrote:
On 12/5/14 7:47 AM, ankur bansal wrote:
> Hi
> Reinvite acting as session modification request
On 12/5/14 7:47 AM, ankur bansal wrote:
Hi
Reinvite acting as session modification request here so its behavior
should be atomic.
And reinvite failed in the end reason could be any error response or
offer answer failure.but uac should try to restore session state sending
update request to get ses
Tarun2 Gupta writes:
>
> Our implementation is clearing the call on receiving no SDP (answer)
> in 200 OK for a ReINVITE with SDP (offer) sent. Is this (call
> clearing) the recommended behavior?
It's certainly a difficult situation. OTOH, I've never heard of it
happening in the real world, so i
Hi
Reinvite acting as session modification request here so its behavior should
be atomic.
And reinvite failed in the end reason could be any error response or offer
answer failure.but uac should try to restore session state sending update
request to get session back in sync as recommended in rfc 63
On 12/4/14 2:20 AM, Tarun2 Gupta wrote:
Hi
Our implementation is clearing the call on receiving no SDP (answer) in 200 OK
for a ReINVITE with SDP (offer) sent. Is this (call clearing) the recommended
behavior?
I am not able to find any normative RFC references to support this. Can you
please
-Original Message-
>> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:
>> sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Vivek Batra
>> Sent: Thursday, December 04, 2014 2:47 PM
>> To: Alok Tiwari
>> Cc: sip-implementors
>> Subjec
2:47 PM
> To: Alok Tiwari
> Cc: sip-implementors
> Subject: Re: [Sip-implementors] ReINVITE offer answer failure
>
> Hi all,
>
> Just thinking widely if it's violating the SDP offer/answer in ReINVITE,
> then why to terminate the complete dialog instead of clearing only
-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Banda,
Srinivas (Srinivas)
Sent: Thursday, December 04, 2014 2:50 PM
To: Vivek Batra; Alok Tiwari
Cc: sip-implementors
Subject: Re: [Sip-implementors] ReINVITE offer answer failure
Hi
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Vivek Batra
Sent: Thursday, December 04, 2014 2:47 PM
To: Alok Tiwari
Cc: sip-implementors
Subject: Re: [Sip-implementors] ReINVITE offer answer
Hi all,
Just thinking widely if it's violating the SDP offer/answer in ReINVITE,
then why to terminate the complete dialog instead of clearing only specific
transaction...
Best Regards,
Vivek Batra
On Thu, Dec 4, 2014 at 2:42 PM, Alok Tiwari wrote:
> Hi Tarun,
>
> IMO, this behavior is correc
Hi Tarun,
IMO, this behavior is correct as it violates the offer-answer model. The
answer must have overlapped SDP. But in mentioned scenario, the media at
UAC and UAS is not in sync and therefore UAC should terminate the dialog in
such scenario.
Thanks,
Alok Tiwari
On Thu, Dec 4, 2014 at 12:50
Hi
Our implementation is clearing the call on receiving no SDP (answer) in 200 OK
for a ReINVITE with SDP (offer) sent. Is this (call clearing) the recommended
behavior?
I am not able to find any normative RFC references to support this. Can you
please help here?
Regards
Tarun Gupta
"DISCLAIM
12 matches
Mail list logo
