Re: [reSIProcate-users] subscribe failed handler

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

Inline...

-----Original Message-----
From: resiprocate-users-bounces@xxxxxxxxxxxxxxx
[mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Vitali
Fomine
Sent: February 20, 2008 6:14 AM
To: resiprocate-users@xxxxxxxxxxxxxxx
Subject: [reSIProcate-users] subscribe failed handler

Hi,

I receive event:
void InstantMessenger::onNewSubscription(ClientSubscriptionHandle handle, 
const SipMessage &notify)

when I made subcribtion:
mDum.send(mDum.makeSubscription(addr, "presence", (UInt32)60));

But how can I catch failed subscription?

I saw these cases:
1. server response 480 on subscribe

[Scott] Looking at code in ClientSubscription::dispatch in SVN head - if 480
has a retry after header then the onRequestRetry callback should be called.
Otherwise onTerminated should be called.

2. response is 200 but notify is absence

[Scott] There are no callbacks for this case.  

3. invalid mime in notify

[Scott] If mime type is not supported then Notify is rejected and there are
no callbacks.  Note:  If profile option validateAcceptEnabled is set to
false, then this will no happened.

[Scott] We could consider call onNewSubscription for either the
200/subscribe or first notify - whichever comes first.  Or perhaps starting
a timer in when ClientSubscription is created, and if no Notifies are
received within X amount of time, then generate a timeout callback.

TIA,
Vitali Fomine 

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/