[reSIProcate] Receiving notify after re-register results in 481 Call/Transaction does not exist

[Scott Godin]

481 means that resiprocate does not have a matching
dialog/subscription for the notify request.  It seems that freeswitch
is sending a notify that is not in the context of your existing
subscription.  A wireshark trace, and examination of the resip logs
should help you track this down.

Scott

On Tue, Dec 30, 2008 at 6:20 AM, Richard Stellingwerff
<remenic at gmail.com> wrote:
> Hi there,
>
> My SIP application subscribes for dialog events, in order to implement BLF.
> This works fine, at least until the registration period expires.
>
> reSIProcate re-registers succesfully, but when the PBX (freeswitch in this
> case) sends me a NOTIFY for a new dialog event, reSIProcate replies with
> "481 Call/Transaction Does Not Exist".
>
> Does anyone know how to handle this case?
>
> Kind regards,
> Richard.
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>