SOLVED Extension Only Rings Sometimes

[Josh Glenn]

Incoming calls get picked up by the automated attendant. But there is one of my extensions that when dialed only rings sometimes, other times it does not ring.

I have two fixed extensions right now, in two seperate offices, in two seperate locations. Both the main office and the satelite office use Aastra 57i phones. My main office extension is giving the trouble. My satelite office extension and my other extensions seem to be consistent, and ring whenever they are called.

I am using PIAF purple running on RentPBX hosting. Everything works great for the most part. But there is a problem I am having, that I have had for sometime.

I am not sure where to start when diagnosing. Has anyone else had this problem? Any ideas what I should try to get this worked out?

 

[krzykat]

Have you look at the CLI and done sip show peers? Make sure that it is shown there as registered with its latency displayed. If not, it won't get there. Good chance your issue is that the PBX is losing the registration from your phone. Check the "Register Expiration" setting on the phone. Typically they are set to 60. Try changing this to 1, meaning it will re-register every minute so that your PBX knows how to find and ring your phone.

 

[Josh Glenn]

That makes sense. But I am having real trouble finding those settings. I looked in the Adminstration menu on the phone and have yet to find anything that remotely resembles "Register Expiration".

Also I'm wondering if my problem might be the same as this guy's: http://pbxinaflash.com/community/index.php?threads/remote-aastra-unregistering.6673/

His was a phone firmware issue. Looking into that also. Any ideas where I can find that setting on the phone?

 

[Josh Glenn]

Okay. So I have found those settings on the phones web admin interface. I have been experimenting with the Registration Renewal Timer and Registration Period settings. But to no avail. The behavior I am seeing in the log files goes a little something like this:

• The extension registers.
• Exactly 1 minute four seconds later, the peer is now unreachable.
• A certain time passes, then the process repeats itself.

Here's a sample of the log:

[2014-04-18 13:19:27] VERBOSE[1528] chan_sip.c: -- Registered SIP '104' at 6X.40.XX.159:61626
[2014-04-18 13:19:27] NOTICE[1528] chan_sip.c: Peer '104' is now Reachable. (101ms / 2000ms)
[2014-04-18 13:20:31] NOTICE[1528] chan_sip.c: Peer '104' is now UNREACHABLE! Last qualify: 101
[2014-04-18 13:21:12] VERBOSE[1528] chan_sip.c: -- Registered SIP '104' at 6X.40.XX.159:61662
[2014-04-18 13:21:13] NOTICE[1528] chan_sip.c: Peer '104' is now Reachable. (99ms / 2000ms)
[2014-04-18 13:22:17] NOTICE[1528] chan_sip.c: Peer '104' is now UNREACHABLE! Last qualify: 99
[2014-04-18 13:22:58] VERBOSE[1528] chan_sip.c: -- Registered SIP '104' at 6X.40.XX.159:61748
[2014-04-18 13:22:58] NOTICE[1528] chan_sip.c: Peer '104' is now Reachable. (107ms / 2000ms)
[2014-04-18 13:24:02] NOTICE[1528] chan_sip.c: Peer '104' is now UNREACHABLE! Last qualify: 107
[2014-04-18 13:24:43] VERBOSE[1528] chan_sip.c: -- Registered SIP '104' at 6X.40.XX.159:61764
[2014-04-18 13:24:43] NOTICE[1528] chan_sip.c: Peer '104' is now Reachable. (110ms / 2000ms)
[2014-04-18 13:25:47] NOTICE[1528] chan_sip.c: Peer '104' is now UNREACHABLE! Last qualify: 110

Any ideas???

 

[Josh Glenn]

Also, I downgraded the phone's firmware to 2.3.1.26 . But the behavior hasn't changed.

 

[Josh Glenn]

Update: So, it looks like I may have found a solution. I don't know if it is a good solution or not, but in the FreePbx extension settings, I changed the qualifyfreq from 60 down to 30. For the time being, that seems to be working.

What do you think? Is that a good solution? What happens when the PBX qualifies an extension, anyway?