logan wrote:
> Oh, I forgot to mention that the crash happens inside SipUserAgent.cpp
> at line 1851:
>
> if (!mbShuttingDown)
> {
> responseQ->send(eventMsg); //<--Crashes here
> }
>
> This is what the call stack shows:
>
> sipXtapid.dll!SipUserAgent::dispatch(SipMessage * message=0x01c72ed0,
> int messageType=2, SIPX_TRANSPORT_DATA * pTransport=0x00000000) Line
> 1851 + 0x1c C++
> sipXtapid.dll!SipClient::run(void * runArg=0x00000000) Line 468 +
> 0x27 C++
> sipXtapid.dll!OsTaskWnt::threadEntry(void * arg=0x01bc08b8) Line 587
> + 0x22 C++
> Thanks,
> Hitesh
What kind of crash is it? Ilegal memory access? BTW I also found
sipxtapi and sipxtacklib generally quite buggy (can't even shutdown
cleanly).
It's a pitty sipxtapi is built on such a buggy sip stack.I think more
effort should be done to fix various bugs reported in jira to get it to
a usable state rather than add lots of new experimental features.
Jaro
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
