Hello,
please check if calling:
pSipUserAgent->removeMessageObserver(pPimClient->getMessageQueue());
where pSipUserAgent is your SipUserAgent instance and pPimClient is SipPimClient
before you destroy SipPimClient instance helps.
Best Regards,
Andrzej
|
> |
Hi,
Andrzej, thanks a ton for looking into the matter :).
I added the following checks to line number 1821 in SipUserAgent.cpp:
if ( request && (shouldDispatch || delayedDispatchMessage) && delayedResponseCode != 404 && delayedResponseCode != 415 && delayedResponseCode != 407 && delayedResponseCode != -1) { ... }
Sure, it's a pathetic hack :(, but it seems to avoid the crash. And now I'm able to send/receive messages across freeworlddialup.com and other servers (I still have problems when I try this against Brekeke on a LAN). I guess till a proper solution is found I will have to persist with this only.
Thanks, Hitesh ----- Original Message ----- From: Andrzej Ciarkowski To: logan Sent: Wednesday, February 21, 2007 1:30 PM Subject: Re[2]: [sipxtapi-dev] Problems in using SipPimClient (SIPSIMPLE message) Hello, I see is SipPimClient code, that sendPagerMessage() creates its own message queue which is used for receiving the response. It seems that after receiving some response which triggers completion of sendPagerMessage() and destruction of the message queue, SipUserAgent receives some message which it "thinks" is another response to your MESSAGE. I wonder if this is related somehow to the fact that both the sent and received MESSAGE have the same Call-Id? Regards, Andrzej Ciarkowski
|
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
