Registered Softphones on Mobile roaming in and out of / between WLAN access points

Hallo,

I’m on FPBX-2.8.1, Asterisk PBX 1.8.9.1 (sorry for not upgrading) and I hope to receive some help on how to best to do the following scenario:

I have a few people in a company, and they have a softphone (Zoiper) installed on their mobile phone, which is registered to the PBX, as they wish to walk around a lot on the company grounds and still be reachable internally, and this is working fine.

I have set up a Follow-Me on their usual Extension, which rings their regular office desk phone extension first, next it rings their softphone on mobile extension (still free of charge), and finally (last resort, when there is no answer or when the softphone extension is unreachable), calls a Misc. Destination, which initiates an external call to their mobile number (at a cost). Last step should only occur, whenever the person is out of reach from WLAN, i.e. they have gone somewhere with no access point, or they have driven off the grounds temporarily with their car. So far, so good, and working. When they go home in the evening, they quit the softphone App on the mobile, saving battery life, and turn it back on in the morning.

What I need help with is how to best influence the timing of ‘qualify’, which tells the PBX if the softphone on mobile extension is reachable or unreachable.

Here is what I have done: In etc/asterisk/sip_custom_post.conf (in order to avoid changing general sip settings), I have entries for each of the softphone on mobile extensions (793 being the example) as follows

[793](+)
qualify=3600
qualifyfreq=5

Which is aimed at qualifying a little bit longer than default in order to adjust for WLAN lag, and qualifying very often (every 5 seconds), to find out where the person currently is located (in which WLAN cell, or none at all), while they are walking the grounds.

So what I am getting in the logs is typically looking like this:

[Feb 20 13:49:13] NOTICE[4701] chan_sip.c: Peer '793' is now UNREACHABLE!  Last qualify: 87
[Feb 20 13:49:24] NOTICE[4701] chan_sip.c: Peer '793' is now Reachable. (151ms / 3600ms)
[Feb 20 13:50:20] NOTICE[4701] chan_sip.c: Peer '793' is now UNREACHABLE!  Last qualify: 797
[Feb 20 13:50:30] NOTICE[4701] chan_sip.c: Peer '793' is now Reachable. (619ms / 3600ms)
[Feb 20 13:51:12] NOTICE[4701] chan_sip.c: Peer '793' is now UNREACHABLE!  Last qualify: 157
[Feb 20 13:51:24] NOTICE[4701] chan_sip.c: Peer '793' is now Reachable. (1902ms / 3600ms)
[Feb 20 13:52:03] NOTICE[4701] chan_sip.c: Peer '793' is now UNREACHABLE!  Last qualify: 46
[Feb 20 13:53:12] VERBOSE[4701] chan_sip.c:     -- Registered SIP '793' at 192.168.30.83:43098
[Feb 20 13:53:12] NOTICE[4701] chan_sip.c: Peer '793' is now Reachable. (15ms / 3600ms)
[Feb 20 13:53:12] VERBOSE[4701] chan_sip.c:     -- Unregistered SIP '793'
[Feb 20 13:53:12] VERBOSE[4701] chan_sip.c:     -- Registered SIP '793' at 192.168.30.83:43098
[Feb 20 13:53:12] VERBOSE[4701] chan_sip.c:     -- Unregistered SIP '793'
[Feb 20 13:53:15] VERBOSE[4701] chan_sip.c:     -- Registered SIP '793' at 192.168.30.83:47957
[Feb 20 13:53:24] VERBOSE[4701] chan_sip.c:     -- Unregistered SIP '793'
[Feb 20 13:53:24] VERBOSE[4701] chan_sip.c:     -- Registered SIP '793' at 192.168.30.83:47957
[Feb 20 13:53:46] NOTICE[4701] chan_sip.c: Peer '793' is now UNREACHABLE!  Last qualify: 18
[Feb 20 13:55:16] VERBOSE[4701] chan_sip.c:     -- Registered SIP '793' at 192.168.30.83:47957
[Feb 20 13:55:16] NOTICE[4701] chan_sip.c: Peer '793' is now Reachable. (4ms / 3600ms)
[Feb 20 13:55:37] NOTICE[4701] chan_sip.c: Peer '793' is now Lagged. (5655ms / 3600ms)
[Feb 20 13:55:47] NOTICE[4701] chan_sip.c: Peer '793' is now Reachable. (56ms / 3600ms)
[Feb 20 13:55:59] NOTICE[4701] chan_sip.c: Peer '793' is now UNREACHABLE!  Last qualify: 56

Is there a better way to adjust my settings, as I find there is a lot of coming in and out of reach (during these 6 minutes logged above)? Or is this the price to pay for this scenario?

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.