Calls on our FXO ring but do not connect when answered. The call side continues to ring. Upon hanging up, phones ring again showing “Unknown” and still does not connect while the call side continues to ring.
Have log text but is too large to include.
. DAHDI Version: 2.11.1
the endpoint that takes the call from a DAHDI FXO/analog channel must immediately “give answer”, make sure your pseudo did is pointed at such an endpoint.
Dicko, as lovingly as I can say it… Huh?
By the way, this is a change from a working setup.
Logs?
What changes?
Definitely need the logs, but the change is the failure. He’s saying he hasn’t changed anything.
Only images can be attached and when I tried to add the log to the post it said it was too large,
Share logs via pastebin. If you’re running the distro there is native support as described on this page:
https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII
.
.
.
[2019-10-24 17:17:07] VERBOSE[2234][C-00000005] chan_iax2.c: Call accepted by
148.75.124.245:55141 (format ulaw)
[2019-10-24 17:17:07] VERBOSE[2234][C-00000005] chan_iax2.c: Format for call is (ulaw)
[2019-10-24 17:17:07] VERBOSE[4534][C-00000005] app_dial.c: IAX2/349-735 is ringing
[2019-10-24 17:17:12] VERBOSE[4534][C-00000005] app_dial.c: IAX2/349-735 answered DAHDI/1-1
[2019-10-24 17:17:20] VERBOSE[4599][C-00000005] bridge_channel.c: Channel IAX2/349-735 left 'simple_bridge' basic-bridge <653b09a4-c996-4485-addb-faf656fb3abc>
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] app_macro.c: Spawn extension (macro-dial, s, 22) exited non-zero on 'DAHDI/1-1' in macro 'dial'
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx.c: Spawn extension (ext-group, 601, 19) exited non-zero on 'DAHDI/1-1'
[2019-10-24 17:17:20] VERBOSE[4599][C-00000005] chan_iax2.c: Hungup 'IAX2/349-735'
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx.c: Executing [h@ext-group:1] Macro("DAHDI/1-1", "hangupcall,") in new stack
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx.c: Executing [s@macro-hangupcall:1] GotoIf("DAHDI/1-1", "1?theend") in new stack
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx_builtins.c: Goto (macro-hangupcall,s,3)
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx.c: Executing [s@macro-hangupcall:3] ExecIf("DAHDI/1-1", "0?Set(CDR(recordingfile)=)") in new stack
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx.c: Executing [s@macro-hangupcall:4] NoOp("DAHDI/1-1", "IAX2/349-735 montior file= ") in new stack
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx.c: Executing [s@macro-hangupcall:5] GotoIf("DAHDI/1-1", "1?skipagi") in new stack
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx_builtins.c: Goto (macro-hangupcall,s,7)
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx.c: Executing [s@macro-hangupcall:7] Hangup("DAHDI/1-1", "") in new stack
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] app_macro.c: Spawn extension (macro-hangupcall, s, 7) exited non-zero on 'DAHDI/1-1' in macro 'hangupcall'
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] pbx.c: Spawn extension (ext-group, h, 1) exited non-zero on 'DAHDI/1-1'
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] sig_analog.c: Hanging up on 'DAHDI/1-1'
[2019-10-24 17:17:20] VERBOSE[4534][C-00000005] chan_dahdi.c: Hungup 'DAHDI/1-1'
The incoming call was sent to a ring-group of which there were a few available extensions,
The call was answered by the laptop’s zoiper client and hangup 8 seconds later.
This call doesn’t reflect your original observations as after the IAX2 extension answered all the sip phones where informed to stop ringing
Of note is that your laptop answers on 148.75.124.245, is that expected? How about
SIP/300&SIP/301&SIP/302&SIP/99310&SIP/310&SIP/315&SIP/316
? . please describe your network along with and routers and firewalls between the FXO and the ringing phones.
Yes, during testing, the example in the log was answered on my laptop rather than the physical phones. The ringing mentioned was the incoming caller continued to hear ringing (me from my cell phone). Answering did not result in picking up the call.
This is identical to the symptoms we have experienced on out physical extensions.
VOIP incoming routes do not have a problem. In fact, I have forwarded the FXO line to a VOIP DID to make sure we get calls.
Yet
I suggest you record the audio of the call using dahdi_monitor
https://support.digium.com/community/s/article/How-do-I-record-calls-using-dahdi-monitor
to isolate whether it is the dahdi channel driver misbehaving or asterisk misreporting the dahdi state.
is there an edge version of DAHDI to try to update?
No, you are thinking FreePBX modules, but FreePBX is used to manage Asterisk and DAHDI is not actually part of Asterisk, it is a channel driver separate from Asterisk , albeit from Digium which was acquired recently by Sangoma.
Did you listen to your dahdi_monitor recordings yet, If you compare the TX and RX channels in the stereo result , they should generally agree as to channel signal events, the existence of audio before and after the announced answer event on RX/TX is pretty definitive as to what problems you need to fix.
Thanks. I will have to postpone that testing until I have some time to set it up.
If the first link was too complicated
https://support.digium.com/community/s/article/How-do-you-run-DAHDI-monitor
It should take you about 5 seconds to set it all up ,(in your case <channel> is 1)
Yes, but the PBX is in business and I have to wait until after hours to remove the forward to VOIP… Last night I was too tired to continue. Thanks.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.