[reSIProcate] Handling of 200 ok response with out Contacts Field
Scott Godin
slgodin at icescape.com
Thu Nov 17 07:35:09 CST 2005
Patel,
This is the 3rd time you've posted this problem. Jason has responded
already with some food for thought, but no conclusions on a final
solution have been made yet.
>From Jason:
>What do people think we should do in this case? I'm not sure what is
the >right thing to do here. Certainly, we should catch the exception
and not >leak any state. If there is no Contact, how can we refresh the
>subscription? I guess we could do something if the expires=0 on the
>subscription.
I suggest that if you need an immediate solution, then you should
implement something in your local copy of resiprocate.
Scott
> -----Original Message-----
> From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-
> devel-bounces at list.sipfoundry.org] On Behalf Of Patel Parag
> Sent: Thursday, November 17, 2005 2:06 AM
> To: resiprocate-devel at list.sipfoundry.org
> Subject: [reSIProcate] Handling of 200 ok response with out Contacts
Field
>
> hi scott,
> I am facing one problem during handling of 200 ok response(with
out
> contacts field) of SUBSCRIBE Request. I try to explain flow of
response
> handling for SUBSCRIBE response.
>
> 1)DialogUsageManager::processResponce()
> 2)DialogSet::dispatch()
> there is Dialog not found so, DUM create new Dialog for
> Subscription
>
> if (dialog == 0)
> {
> dialog = new Dialog(mDum, msg, *this);
> }
>
> but, problem is, response doesn't contain contact field
so
> throw
> exception.
>
> if (response.exists(h_Contacts) &&
> response.header(h_Contacts).size() ==
> 1)
> {
> }
> else
> {
> // control will come here ... and throw
exception.
> }
> please any buddy give me right direction...
>
> According to RFC 3842.. response to SUBSCRIBE may come without
> contacts
> field.
>
> regards,
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
More information about the resiprocate-devel
mailing list