You need this for several reasons. Mobile devices may change their ip quite frequently and this re-register updates your connection to the server. You control that in the account config structure. AccountConfig.GetRegConfig().set… there you have the flags for registertimeout, and the intervals
that control the sip engine. 300 is the default of pjsip. Our mobile apps run at 90 seconds while active and switch to 900 (15 minutes) when in background/sleep. mit freundlichen Grüßen | kind regards Michael Barthold Senior Software Architect ---------------------------------------------- T +43 5 06216-5285 ---------------------------------------------- Von: pjsip [mailto:pjsip-bounces@xxxxxxxxxxxxxxx]
Im Auftrag von Rodrigo Pimenta Carvalho This behaviour is a SIP one. This is normal. I don't know how to reconfigure pjsip to change the frequency of SIP REGISTERs. The SIP REGISTER message is necessary to tell to the SIP proxy (SIP server) that the client is still alive. That is, the SIP server has the condition to knows that the client
is still online. If the register expires and there is no more SIP REGISTERS, the SIP server will consider that the client is offline and will delete the client register from the registrar. Is the client that should decide how long a register will be valid.
In the current case, I guess 300 secs is hardcoded somewhere. Best regards. RODRIGO PIMENTA CARVALHO De: pjsip <pjsip-bounces@xxxxxxxxxxxxxxx>
em nome de Oli Kah <mj_fn@xxxxxx> Ah, ok, thank you :) ...didn't know that a SIP connection could expire. That may be the case... I'll have a look! But this auto-reconnect that is performed on expiration would not happen when there is an active call ongoing, right? Currently I am using pjsip only as a kind of notification service and not to actually talk to someone. But I plan to do this, too at some
point. In the log files where I save the status that comes back from pjsua I saw these "200 OK"s which occur periodically and precisely every 5
minutes (=300 sec) - that looked a bit surprising to me. But I'll see if there is an expiration time that might explain this behaviour. Thanks!
Gesendet: Mittwoch, 22. Juni 2016 um 18:45 Uhr Look at the "expire" in the register, i guess it's at 600 seconds (5 minutes). If so, yes, It's completely normal.
On Wed, Jun 22, 2016 at 12:36 PM Harald Radke <harryrat@xxxxxx> wrote:
_______________________________________________ Visit our blog:
http://blog.pjsip.org pjsip mailing list
pjsip@xxxxxxxxxxxxxxx
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org |
_______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@xxxxxxxxxxxxxxx http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org