[reSIProcate] Question for how to handle 491 message from SIP server

[Wenwei Xu]

If this is the case, then if two UAC's hold the call(send Invite message)
exactly at the same time the call will be disconnected involuntarily. Should
this be allowed?

Thanks,
Wenwei Xu

-----Original Message-----
From: Scott Godin [mailto:slgodin at icescape.com] 
Sent: Thursday, March 30, 2006 3:11 PM
To: Wenwei Xu; resiprocate-devel at list.sipfoundry.org
Subject: RE: [reSIProcate] Question for how to handle 491 message from SIP
server

Here is a comment directly from the code.
// RFC3261 section 14.1
// If a UAC receives a 491 response to a re-INVITE, it SHOULD start a
timer with
// a value T chosen as follows:
//  1. If the UAC is the owner of the Call-ID of the dialog ID, T has a
randomly
//  chosen value between 2.1 and 4 seconds in units of 10 ms.
//  2. If the UAC is not the owner of the Call-ID of the dialog ID, T
has a
//  randomly chosen value of between 0 and 2 seconds in units of 10 ms.

Scott

-----Original Message-----
From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
Wenwei Xu
Sent: Thursday, March 30, 2006 2:38 PM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] Question for how to handle 491 message from SIP
server

When two calling parties try to hold the call (send an Invite message)
simultaneously, the SIP server will send 491 message (pending request)
to
both parties. Then InviteSession::start491Timer() will get called. After
that, the two UA's can't hold/unhold anymore but wait till timeout by
the
SIP server (a 481 message). Is this the right way or shall we implement
a
491 message handler in the reciprocate stack library such that the UA
can
have some control when this happens?

Thanks a lot.

Wenwei Xu


_______________________________________________
resiprocate-devel mailing list
resiprocate-devel at list.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel