RE: [reSIProcate] Has anyone expericened that latest resip doesn' t send response after received NOTIFY
Hi Scott,
I rolled back using revision 3914, and it worked. Do you have any clue when
is this changed?
On Fri, 4 Mar 2005 14:18:05 -0500 , Scott Godin wrote
> I think the API was changed so that your application must accept
> each Notify now. Check out the comments in the SusbscriptionHandler
> header file for onUpdatePending. You must call acceptUpdate or
rejectUpdate.
>
> -----Original Message-----
> From: Nash Tsai [mailto:nash@xxxxxxxxxx]
> Sent: Friday, March 04, 2005 12:41 PM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] Has anyone expericened that latest resip
> doesn't send response after received NOTIFY
>
> Hi,
>
> Has anyone expericened that latest resip doesn't send response after
> received NOTIFY?
>
> --
> Nash Tsai
> Senior Engineer
>
> TeLTeL.COM
> 4F, No. 41&43, Lane 76, Rui Guang Road, Taipei 114, Taiwan
> Phone: +886 2 27923998 Fax: +886 2 87918740
> Mobile: +886 952 252658
> EMail: nash@xxxxxxxxxx
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
--
Nash Tsai
Senior Engineer
TeLTeL.COM
4F, No. 41&43, Lane 76, Rui Guang Road, Taipei 114, Taiwan
Phone: +886 2 27923998 Fax: +886 2 87918740
Mobile: +886 952 252658
EMail: nash@xxxxxxxxxx