Re: [Linphone-developers] LinphoneRegistrationCleared no longer callback

[Jehan Monnier]

Hi,

You are right, this behavior slightly changed. The point is that multiple parallel transactions are not supposed to be issued by a UA. So when the done is executed, what should we do with the previous registration transaction (I.E the unregister) ?

The new behavior is if any, to "cancel" the previous transaction in the "done".

To receive the LinphoneRegistrationCleared, you should wait for it before calling done.

linphone_proxy_config_edit(proxyCfg);

int i=0;

while (!linphone_proxy_config_is_registered(proxyCfg) && i++<40 ) {

linphone_core_iterate(theLinphoneCore);

usleep(100000);

}

linphone_proxy_config_enable_register(proxyCfg, false);

linphone_proxy_config_done(proxyCfg);

Cheers

Jehan

www.linphone.org

Le 18 avr. 2014 à 15:19, mcyep <address@hidden> a écrit :

Hi Linphone team,

In the new update of linphone, SIP unregistration (below) no longer receive
state-changed-callback for LinphoneRegistrationCleared.

// SIP unregistration example
linphone_proxy_config_edit(proxyCfg);
linphone_proxy_config_enable_register(proxyCfg, false);
linphone_proxy_config_done(proxyCfg);

Perhaps the adding of sal_op_stop_refreshing in the
linphone_proxy_config_register, may cause execution of
belle_sip_transaction_terminate in belle_sip_refresher_stop_internal
(Pending unregistration transaction terminated before able to receive sip
response)

regards
mcyep

--
View this message in context: http://nongnu.13855.n7.nabble.com/LinphoneRegistrationCleared-no-longer-callback-tp182222.html
Sent from the linphone-developers mailing list archive at Nabble.com.

_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers