Hi Klaus, Basically, it is application responsibility to update the registration state in network up/down events, as currently network state monitoring should be done in application level and it sounds useless for pjsip to re-register when network is down. Just FYI, ticket #1032 has added TCP/TLS transport state notification feature, so when SIP transport TCP/TLS reports network disconnection (based on transport failure in sending keep-alive or any SIP messages), application can try to initiate/monitor network reconnection, and application may start re-register once network is up. BR, nanang On Fri, Mar 12, 2010 at 4:26 PM, Klaus Darilion <klaus.mailinglists at pernau.at> wrote: > Hi! > > QjSimple client stops registering if one REGISTER times out (e.g. network > was down). > > ?02:34:04.239 ? ?pjsua_acc.c ?sip:user2 at sip.nxdomain.at: registration > success, status=200 (OK), will re-register in 60 seconds > QjSimple: Info: on_reg_state_slot called > QjSimple: Info: on_reg_state_slot: status=200 > QjSimple: Info: on_reg_state_slot: statustext=OK > ?02:34:59.458 ? ?pjsua_acc.c ?sip:user2 at sip.nxdomain.at: registration > success, status=200 (OK), will re-register in 60 seconds > QjSimple: Info: on_reg_state_slot called > QjSimple: Info: on_reg_state_slot: status=200 > QjSimple: Info: on_reg_state_slot: statustext=OK > ?02:36:26.458 ? ?pjsua_acc.c ?SIP registration failed, status=408 (Request > Timeout) > QjSimple: Info: on_reg_state_slot called > QjSimple: Info: on_reg_state_slot: status=408 > QjSimple: Info: on_reg_state_slot: statustext=Request Timeout > > Now, it does not REGISTER again (I waited several hours). > > Shouldn't pjsip recover itself and try to REGISTER after a few minutes? > > Or is this something I have to handle in the application? > > thanks > Klaus > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
