Custom Query (2195 matches)

Currently UAC transaction does not set any timeout timer after a provisional response has been received. If the server crashes after it sends provisional response, then the client will get stucked forefer (for example, for client registration).

This behavior is compliant with RFC 3261, but nevertheless it's not robust, so the stack should better provide a mechanism for setting up such timer.

This ticket supersedes ticket #89 since it solves the problem in more generic manner.

Break point:

PJ_DEF(pj_status_t) pjsip_evsub_terminate( pjsip_evsub *sub,
					   pj_bool_t notify )
{
    PJ_ASSERT_RETURN(sub, PJ_EINVAL);



Call stack:

	htmlview.exe!_wassert(const wchar_t * expr=0x006f93c4, const wchar_t * filename=0x0071b380, unsigned int lineno=878)  Line 384

        htmlview.exe!pjsip_evsub_terminate(pjsip_evsub * sub=0x00000000, int notify=0)  Line 878 + 0x1e bytes	C
 	htmlview.exe!pjsip_pres_terminate(pjsip_evsub * sub=0x00000000, int notify=0)  Line 332 + 0xd bytes	C
 	htmlview.exe!unsubscribe_buddy_presence(unsigned int index=0) Line 1050 + 0xe bytes	
 	htmlview.exe!refresh_client_subscriptions()  Line 1072 + 0x9 bytes	C
 	htmlview.exe!pjsua_pres_refresh()  Line 1120	C
 	htmlview.exe!pjsua_pres_shutdown()  Line 1145	C
 	htmlview.exe!pjsua_destroy()  Line 666	C

Thanks Edward Tian for reporting this.

When port is zero, PJSIP transport will use any available port when creating SIP transports. This works fine, except that in PJSUA-API the published address of the transport is not updated with the actual port number where the transport listens to after the transport is created.