, Jan Thiemo Fricke wrote:
> From: Jan Thiemo Fricke
> Subject: Re: [sipxtapi-dev] Presence problem second notify answered with 481
> To: dpet...@sipez.com
> Cc: sipxtapi-dev@list.sipfoundry.org
> Date: Wednesday, January 6, 2010, 12:19 PM
> Hi Dan,
> I had a further look into
Hi Dan,
I had a further look into the code of sipxtapi the last days.
Some things I figured out:
- The 481 just occurs in SipXtapi 3.3 (in 3.2 everything works fine)
- The problem just occurs if Subscription needs authentication
(subscribe, 401, subscribe, 202; If I subscribe reg-event I don't nee
manager handles this case.
Cheers,
Dan
--- On Wed, 12/23/09, Jan Fricke wrote:
> From: Jan Fricke
> Subject: Re: [sipxtapi-dev] Presence problem second notify answered with 481
> To: sipxtapi-dev@list.sipfoundry.org
> Date: Wednesday, December 23, 2009, 3:33 AM
> Hello again,
Hello again,
I figured out that sipxtapi does not find the dialog on second notify
because it seems the remote-tag of the stored dialog is empty.
I debugged SipSubscribeClient::handleNotifyRequest.
The SipDialogMgr should store the dialog (including callId, from-tag,
to-tag) on first notify. It s
