< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] 200OK with Offer in UAC "EarlyWithAnswer" state


Duh - right!  Disregard my email.  I'll let the PRACK developers field that
question.  : )

Scott

-----Original Message-----
From: Michael Trank [mailto:mike@xxxxxxxxxx] 
Sent: August 31, 2007 2:14 PM
To: Scott Godin
Cc: resiprocate-users@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate-users] 200OK with Offer in UAC "EarlyWithAnswer"
state


Hi Scott:

I had read that PRACK support is only completed for the client side, but I 
thought that DUM is the client in the scenario that I layed out.


On Fri, 31 Aug 2007, Scott Godin wrote:

> PRACK support in dum is only completed for the client side (ie.
> responding to a PRACK request).  Support for sending a PRACK via dum has
> not yet been completed.
>
> Scott
>
>> -----Original Message-----
>> From: resiprocate-users-bounces@xxxxxxxxxxxxxxxxxxxx
>> [mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of
>> Michael Trank
>> Sent: Friday, August 31, 2007 10:34 AM
>> To: resiprocate-users@xxxxxxxxxxxxxxxxxxxx
>> Subject: [reSIProcate-users] 200OK with Offer in UAC "EarlyWithAnswer"
>> state
>>
>>
>>
>> Friends:
>>
>> I am having a problem with sessions using DUM connecting to a gateway
>> manufactured by Sonus. Not sure of the model number, but the SDP
>> packets
>> say "Sonus_UAC".
>>
>> My sessions look like the following:
>>
>>                DUM                                       GATEWAY
>>          INVITE ( no sdp, Supported: 100rel )            ------->>
>>          100 Trying                                      <<-------
>>          180 Ringing ( with sdp offer, Requires 100rel ) <<-------
>>          PRACK ( with sdp answer )                       ------->>
>>          200 OK ( for the prack, no sdp )                <<-------
>>
>> At this point i hear the ringback from the telephone network through
>> the
>> gateway.
>>
>> But the next thing that happens is the remote telephone gets answered.
>>
>>          200 OK (for the invite, *with* sdp offer )      <<-------
>>
>> When the GW sends this 200 OK with a new offer, DUM shuts everything
>> down,
>> and the onFailure callback gets called.
>>
>>          ACK ( no sdp )                                  -------->>
>>          BYE                                             -------->>
>>
>>
>> I looked at the state machine, and I think the relevant state
>> transition
>> for that 200 OK with the offer  is the following:
>>
>> EarlyWithAnswer -> Terminated           [ label =
>> "on2XX-sdp/send::ACK,send::BYE,app::onFailure,app::onTerminated" ];
>>
>> So, DUM is doing what is documented. DUM seems to think that what the
>> gateway is doing is *bad* SIP. But it seems to me that DUM could
>> transition to
>> the "Answered" state, and send a new answer in the ACK with
>> provideAnswer(),
>> and all would be well. Does anyone have any idea why
>> DUM shuts down for on2XX-sdp in the EarlyWithAnswer state?
>>
>>
>>
>>
>> _______________________________________________
>> resiprocate-users mailing list
>> resiprocate-users@xxxxxxxxxxxxxxxxxxxx
>> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>
>