< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
Yes – that would be a good idea. : ) From: Byron Campen
[mailto:bcampen@xxxxxxxxxxxx] I assume we
should backport this to the 1.1 release branch, yes? Best regards, Byron Campen
Thanks
Matt – I just committed this fix. Scott From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx]
On Behalf Of Matt Porter This
is definitely something to be aware of when using the Dum. Always
have a ClientSubscriptionHandler for refer. Even
if you never issue a REFER, if the far side sends you a NOTIFY with no
event in it at all…blammo! See….
Dialog.cxx ( around line 496 )
if (mInviteSession != 0 && (!msg.exists(h_Event) ||
msg.header(h_Event).value() == "refer")) It’s
a 1 line fix to Dialog.cxx… change it to this code, and you wont have to worry
about it. if (mInviteSession
!= 0 && (!msg.exists(h_Event) || msg.header(h_Event).value() == "refer") &&
mDum.getClientSubscriptionHandler("refer")!=0
) From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx]
On Behalf Of 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@xxxxxxxxxxxxxxxxxxxx
on behalf of maodonghu resip _______________________________________________ resiprocate-devel mailing list |