Call not being answered by extension when being picked up

I have some odd behavior on one of my 20 extensions.

When an external call rings the extension and the extension is answered the call seems to be cancelled. The caller either goes to that extension’s voicemail or hangup. BUT, it oddly doesn’t happen when I test the extension with my cell phone.

Here is the CEL from the call that worked and that didn’t.

THIS CALL DID NOT WORK

Time Event Type UniqueID LinkedID Cid num Extension Context Channel Name
Tue, Apr 5, 2022 12:31 PM APP_END 1649179755 1649179755 15154087682 dovm macro-vm SIP/fpbx-1-nxivK8e5bb4a-00000095
Tue, Apr 5, 2022 12:31 PM HANGUP 1649179755 1649179755 15154087682 h ext-local SIP/fpbx-1-nxivK8e5bb4a-00000095
Tue, Apr 5, 2022 12:31 PM CHAN_END 1649179755 1649179755 15154087682 h ext-local SIP/fpbx-1-nxivK8e5bb4a-00000095
Tue, Apr 5, 2022 12:31 PM LINKEDID_END 1649179755 1649179755 15154087682 h ext-local SIP/fpbx-1-nxivK8e5bb4a-00000095
Tue, Apr 5, 2022 12:29 PM APP_START 1649179755 1649179755 15154087682 dovm macro-vm SIP/fpbx-1-nxivK8e5bb4a-00000095
Tue, Apr 5, 2022 12:29 PM HANGUP 1649179761 1649179755 9008 9008 from-internal PJSIP/9008-000000dd
Tue, Apr 5, 2022 12:29 PM CHAN_END 1649179761 1649179755 9008 9008 from-internal PJSIP/9008-000000dd
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179761 1649179755 9008 s from-internal PJSIP/9008-000000dc
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179761 1649179755 9008 s from-internal PJSIP/9008-000000dd
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179761 1649179755 909008 zulu-call Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179761 1649179755 909008 zulu-call Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179761 1649179755 909008 zulu-desktop-phone Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179761 1649179755 909008 zulu-desktop-phone Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179761 1649179755 909008 zulu-mobile-phone-push Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179761 1649179755 909008 zulu-mobile-phone-push Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM HANGUP 1649179761 1649179755 15154087682 909008 zulu-desktop-phone Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM CHAN_END 1649179761 1649179755 15154087682 909008 zulu-desktop-phone Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM HANGUP 1649179761 1649179755 15154087682 909008 zulu-mobile-phone-push Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM CHAN_END 1649179761 1649179755 15154087682 909008 zulu-mobile-phone-push Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM HANGUP 1649179761 1649179755 909008 909008 zulu-mobile-phone-push Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM CHAN_END 1649179761 1649179755 909008 909008 zulu-mobile-phone-push Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM HANGUP 1649179761 1649179755 909008 909008 zulu-desktop-phone Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM CHAN_END 1649179761 1649179755 909008 909008 zulu-desktop-phone Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM HANGUP 1649179761 1649179755 15154087682 909008 zulu-call Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM CHAN_END 1649179761 1649179755 15154087682 909008 zulu-call Local/[email protected];2
Tue, Apr 5, 2022 12:29 PM HANGUP 1649179761 1649179755 9008 9008 zulu-call Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM CHAN_END 1649179761 1649179755 9008 9008 zulu-call Local/[email protected];1
Tue, Apr 5, 2022 12:29 PM HANGUP 1649179761 1649179755 9008 9008 from-internal PJSIP/9008-000000dc
Tue, Apr 5, 2022 12:29 PM CHAN_END 1649179761 1649179755 9008 9008 from-internal PJSIP/9008-000000dc
Tue, Apr 5, 2022 12:29 PM ANSWER 1649179755 1649179755 15154087682 5159789008 from-pstn SIP/fpbx-1-nxivK8e5bb4a-00000095
Tue, Apr 5, 2022 12:29 PM CHAN_START 1649179755 1649179755 15154087682 5159789008 from-pstn SIP/fpbx-1-nxivK8e5bb4a-00000095
Tue, Apr 5, 2022 12:29 PM APP_START 1649179755 1649179755 15154087682 recordcheck sub-record-check SIP/fpbx-1-nxivK8e5bb4a-00000095
Tue, Apr 5, 2022 12:29 PM APP_END 1649179755 1649179755 15154087682 recordcheck sub-record-check SIP/fpbx-1-nxivK8e5bb4a-00000095

THIS CALL WORKED FINE

Time Event Type UniqueID LinkedID Cid num Extension Context Channel Name
Tue, Apr 5, 2022 12:38 PM BRIDGE_EXIT 1649180294 1649180289 9008 s macro-dial PJSIP/9008-000000e0
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180294 1649180289 9008 s macro-dial PJSIP/9008-000000e0
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180294 1649180289 9008 s macro-dial PJSIP/9008-000000e0
Tue, Apr 5, 2022 12:38 PM BRIDGE_EXIT 1649180289 1649180289 15158682015 s macro-dial SIP/fpbx-1-nxivK8e5bb4a-00000097
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180289 1649180289 15158682015 9008 followme-sub SIP/fpbx-1-nxivK8e5bb4a-00000097
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180289 1649180289 15158682015 9008 followme-sub SIP/fpbx-1-nxivK8e5bb4a-00000097
Tue, Apr 5, 2022 12:38 PM LINKEDID_END 1649180289 1649180289 15158682015 9008 followme-sub SIP/fpbx-1-nxivK8e5bb4a-00000097
Tue, Apr 5, 2022 12:38 PM ANSWER 1649180294 1649180289 9008 9008 from-internal PJSIP/9008-000000e0
Tue, Apr 5, 2022 12:38 PM BRIDGE_ENTER 1649180294 1649180289 9008 s macro-dial PJSIP/9008-000000e0
Tue, Apr 5, 2022 12:38 PM BRIDGE_ENTER 1649180289 1649180289 15158682015 s macro-dial SIP/fpbx-1-nxivK8e5bb4a-00000097
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180294 1649180289 9008 s from-internal PJSIP/9008-000000df
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180294 1649180289 9008 s from-internal PJSIP/9008-000000e0
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180294 1649180289 909008 zulu-call Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180294 1649180289 909008 zulu-call Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180294 1649180289 909008 zulu-desktop-phone Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180294 1649180289 909008 zulu-desktop-phone Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180294 1649180289 909008 zulu-mobile-phone-push Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180294 1649180289 909008 zulu-mobile-phone-push Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180294 1649180289 15158682015 909008 zulu-desktop-phone Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180294 1649180289 15158682015 909008 zulu-desktop-phone Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180294 1649180289 15158682015 909008 zulu-mobile-phone-push Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180294 1649180289 15158682015 909008 zulu-mobile-phone-push Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180294 1649180289 909008 909008 zulu-mobile-phone-push Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180294 1649180289 909008 909008 zulu-mobile-phone-push Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180294 1649180289 909008 909008 zulu-desktop-phone Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180294 1649180289 909008 909008 zulu-desktop-phone Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180294 1649180289 15158682015 909008 zulu-call Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180294 1649180289 15158682015 909008 zulu-call Local/[email protected];2
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180294 1649180289 9008 9008 zulu-call Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180294 1649180289 9008 9008 zulu-call Local/[email protected];1
Tue, Apr 5, 2022 12:38 PM HANGUP 1649180294 1649180289 9008 9008 from-internal PJSIP/9008-000000df
Tue, Apr 5, 2022 12:38 PM CHAN_END 1649180294 1649180289 9008 9008 from-internal PJSIP/9008-000000df
Tue, Apr 5, 2022 12:38 PM CHAN_START 1649180289 1649180289 15158682015 5159789008 from-pstn SIP/fpbx-1-nxivK8e5bb4a-00000097
Tue, Apr 5, 2022 12:38 PM APP_START 1649180289 1649180289 15158682015 recordcheck sub-record-check SIP/fpbx-1-nxivK8e5bb4a-00000097
Tue, Apr 5, 2022 12:38 PM APP_END 1649180289 1649180289 15158682015 recordcheck sub-record-check SIP/fpbx-1-nxivK8e5bb4a-00000097
Tue, Apr 5, 2022 12:38 PM ANSWER 1649180289 1649180289 15158682015 5159789008 from-pstn SIP/fpbx-1-nxivK8e5bb4a-00000097

Please provide an actual call trace via pastebin Providing Great Debug - Support Services - Documentation

Here are the pastebin URLs.

Call that did not work
https://pastebin.freepbx.org/view/36b8f3fb

Call that worked
https://pastebin.freepbx.org/view/3d774e34

I just had another call that didn’t work, but this time it was an internal extension to extension. That call has two uniqueIDs

https://pastebin.freepbx.org/view/e376b9aa
https://pastebin.freepbx.org/view/a2325068

If it helps, the problem is only happening on phones that are on the same LAN as the PBX. Phones at remote locations dont have the issue.

I’ve done some more troubleshooting, this seems to be tied to find me/follow me, specifically the ring time.

If I have the ring time set to 30 seconds, if the inbound caller (tested with my cell phone) rings in for more than 20 seconds before the extension picks up then the call skips the extension and goes to VM. If I set ring time to 50 seconds then the inbound caller needs to ring for about 40 seconds before it skips the extension.

Those last two calls are 7 minutes apart. They are not related.

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