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

[Scott Godin]

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 at list.resiprocate.org 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 at tom.com
??????????2007-02-07

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel at list.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/20070207/834c7cb7/attachment.htm>