[reSIProcate] ReceivedProvisional state in client registration'sDialogSet

[Scott Godin]

Getting a 100 to any request is possible.  The problem is that (App)Dialogset::end is currently only meant for Invite sessions - since they are the only client transactions that you can use a sip message to try to end (cancel).  I suppose we could modify end()  to just set the DialogSet state to something appropriate and wait for the final response before deleting for non-invite requests.  But for now applications need to wait for the final response then use the appropriate usage (ClientRegistration::end) api to end.

Scott

----- Original Message -----
From: resiprocate-devel-bounces at resiprocate.org <resiprocate-devel-bounces at resiprocate.org>
To: resiprocate-devel at resiprocate.org <resiprocate-devel at resiprocate.org>
Sent: Tue May 27 06:20:01 2008
Subject: [reSIProcate] ReceivedProvisional state in client registration'sDialogSet

Hi,

I have following problem. One VoIP provider responds
with 100 Trying to my REGISTER request before answer
with 401 or 200 replies. This leads to
ReceivedProvisional state of DialogSet, which has two
bad results:
1) it asserts if I try to end() DialogSet before final
answer received;
2) it sends CANCEL in the same case.

I suppose it is not allowed to send 100 Trying in
response to REGISTER, but still we have to deal with
it somehow.

Currently, I'm trying to skip setting DialogSet.mState
to ReceivedProvisional for registration dialog sets,
but I'm not sure if it is proper approach.

Best regards,
Arthur Moroz
3CX Ltd.



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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20080528/8ecc2db8/attachment.htm>