reSIProcate

Mailing Lists

Source Code

Google Search:



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

Re: [reSIProcate] refer with refSub = false still causeClientSubscriptionHandler be used

Title: [reSIProcate] refer with refSub = false still causeClientSubscriptionHandler be used
I agree that behaviour would be nice.  In the meantime, you can always add a ClientSubscriptionHandler and have your application reject the NOTIFY with rejectUpdate().
 
Scott

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx on behalf of maodonghu
Sent: Tue 2/6/2007 11:52 PM
To: resip
Subject: [reSIProcate] refer with refSub = false still causeClientSubscriptionHandler be used

resip
                       

I call refer with refSub = false, but if the the other party still send NOTIFY, the dum will assert(ClientSubscriptionHandler),
I think if refSub = false, the NOTIFY should be reject by dum, not go to try get a ClientSubscriptionHandler

　　　　　　　　maodonghu
　　　　　　　　hhmmdd@xxxxxxx
　　　　　　　　　　2007-02-07

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