[asterisk-users] Loss of devices registration (pjsip)

[Dmitriy Serov]

Thanks, George Joseph!

Now a lot clearer the reasons for this behavior.
It turns out that in the case of devices there are two ways to 
understand that they are "alive":
1. Registration from device to server
2. qualify from the server to the client
And the second way does not seems superfluous. Since calling to the 
device this way will be used. if qualify doesn't working, then this call 
will not take place.

Most likely the problem is that the device is behind two NAT (from your 
ISP and your own router).
Can you advise how to configure the client in this case? Is it necessary 
to use a stun (did not seem to help, and it only works in the case of 
RTP) or proxy?

Thanks.

21.03.2016 23:32, George Joseph пишет:
>
>
> On Mon, Mar 21, 2016 at 11:58 AM, Dmitriy Serov <serov.d.p at gmail.com 
> <mailto:serov.d.p at gmail.com>> wrote:
>
>     Good day.
>
>     Asterisk 13.7.2, res_pjsip.
>     There is a problem of loss of registration of several devices.
>     This happens not on all devices, but problem devices a lot.
>     Below is the log of registration of a contact of one device.
>
>     Is suspect two things:
>     1. delete a contact after the contact is added. But, like, it's a
>     feature of code that may already be fixed.
>     2. deleting a contact much earlier than the 90 seconds specified
>     during the registration
>
>     Would be grateful for any clues.
>
>     Dmitriy Serov.
>
>     expiration settings:
>     [common-aor](!)
>     type=aor
>     qualify_frequency=60
>     default_expiration=120
>     maximum_expiration=600
>     minimum_expiration=90
>
>     log:
>     [2016-03-21 20:39:58] VERBOSE[30251] res_pjsip_registrar.c: Added
>     contact 'sip:17367 at 46.39.229.18:37910
>     <http://sip:17367@46.39.229.18:37910>' to AOR '17367' with
>     expiration of 90 seconds
>
> ​The client just registered​
>
>     [2016-03-21 20:39:58] VERBOSE[28019]
>     res_pjsip/pjsip_configuration.c: Contact
>     17367/sip:17367 at 46.39.229.18:37910
>     <http://sip:17367@46.39.229.18:37910> has been created
>
> ​We added a new contact​
>
>     [2016-03-21 20:39:58] VERBOSE[28019]
>     res_pjsip/pjsip_configuration.c: Contact
>     17367/sip:17367 at 46.39.229.18:27143
>     <http://sip:17367@46.39.229.18:27143> has been deleted
>
> ​We deleted the old contact​
>
>     [2016-03-21 20:39:58] VERBOSE[28019]
>     res_pjsip/pjsip_configuration.c: Contact
>     17367/sip:17367 at 46.39.229.18:37910
>     <http://sip:17367@46.39.229.18:37910> is now Reachable.  RTT:
>     41.882 msec
>
> ​We qualified the contact successfully​
>
>     [2016-03-21 20:41:01] VERBOSE[28019]
>     res_pjsip/pjsip_configuration.c: Contact
>     17367/sip:17367 at 46.39.229.18:37910
>     <http://sip:17367@46.39.229.18:37910> is now Unreachable.  RTT:
>     0.000 msec
>
> ​At the next qualify, we couldn't reach the contact
>
>     [2016-03-21 20:41:06] VERBOSE[3827] res_pjsip_registrar.c: Added
>     contact 'sip:17367 at 46.39.229.18:60105
>     <http://sip:17367@46.39.229.18:60105>' to AOR '17367' with
>     expiration of 90 seconds
>
> ​The client just registered​
> ​(again)​
>
>     [2016-03-21 20:41:06] VERBOSE[28019]
>     res_pjsip/pjsip_configuration.c: Contact
>     17367/sip:17367 at 46.39.229.18:60105
>     <http://sip:17367@46.39.229.18:60105> has been created
>
> ​We added a new contact​
>  [2016-03-21 20:41:06] VERBOSE[28019] res_pjsip/pjsip_configuration.c: 
> Contact 17367/sip:17367 at 46.39.229.18:37910 
> <http://sip:17367@46.39.229.18:37910> has been deleted
> ​We deleted the old contact​
>
>     [2016-03-21 20:41:06] VERBOSE[28019]
>     res_pjsip/pjsip_configuration.c: Contact
>     17367/sip:17367 at 46.39.229.18:60105
>     <http://sip:17367@46.39.229.18:60105> is now Reachable.  RTT:
>     44.031 msec
>
> ​We qualified the contact successfully​
>
>     [2016-03-21 20:42:09] VERBOSE[28019]
>     res_pjsip/pjsip_configuration.c: Contact
>     17367/sip:17367 at 46.39.229.18:60105
>     <http://sip:17367@46.39.229.18:60105> is now Unreachable.  RTT:
>     0.000 msec
>
> ​At the next qualify, we couldn't reach the contact
>
> ​This looks like a client that's going to sleep or a firewall that's 
> timing out connections.  Asterisk is only deleting the contact on the 
> next successful register because it's replacing it. You need to figure 
> out why the qualify is failing and why the client keeps registering.
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20160322/62be3706/attachment.html>