How to start diagnosing dropped calls

FreePBX
1

Hello,
we are using a FreePBX 14.0.5.25 and are experiencing random dropps of outgoing and incoming calls using different trunks. Below you will find the logs of one of these drops.

[2019-02-04 11:52:41] VERBOSE[28495][C-000003cc] bridge_channel.c: Channel SIP/xxxx-gmbh-00000279 joined 'simple_bridge' basic-bridge <67b59e5c-4d05-4280-a206-f4eb492f8917>
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] bridge_channel.c: Channel SIP/xxxx-gmbh-00000279 left 'simple_bridge' basic-bridge <67b59e5c-4d05-4280-a206-f4eb492f8917>
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] app_macro.c: Spawn extension (macro-dial, s, 22) exited non-zero on 'SIP/xxxx-gmbh-00000279' in macro 'dial'
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] pbx.c: Spawn extension (ext-group, 11, 20) exited non-zero on 'SIP/xxxx-gmbh-00000279'
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] pbx.c: Executing [h@ext-group:1] Macro("SIP/xxxxx-gmbh-00000279", "hangupcall,") in new stack
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] pbx.c: Executing [s@macro-hangupcall:1] GotoIf("SIP/xxxxxx-gmbh-00000279", "1?theend") in new stack
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] pbx_builtins.c: Goto (macro-hangupcall,s,3)
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] pbx.c: Executing [s@macro-hangupcall:3] ExecIf("SIP/xxxxx-gmbh-00000279", "0?Set(CDR(recordingfile)=)") in new stack
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] pbx.c: Executing [s@macro-hangupcall:4] NoOp("SIP/xxxxx-gmbh-00000279", "PJSIP/21-000006df monior file= ") in new stack
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] pbx.c: Executing [s@macro-hangupcall:5] AGI("SIP/xxxx-gmbh-00000279", "attendedtransfer-rec-restart.php,PJSIP/21-000006df,") in new stack
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] res_agi.c: Launched AGI Script /var/lib/asterisk/agi-bin/attendedtransfer-rec-restart.php
[2019-02-04 11:54:44] VERBOSE[28514][C-000003cc] bridge_channel.c: Channel PJSIP/45-000006dd left 'simple_bridge' basic-bridge <67b59e5c-4d05-4280-a206-f4eb492f8917>
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] res_agi.c: <SIP/xxxxx-gmbh-00000279>AGI Script attendedtransfer-rec-restart.php completed, returning 0
[2019-02-04 11:54:44] VERBOSE[28495][C-000003cc] pbx.c: Executing [s@macro-hangupcall:6] Hangup("SIP/xxx-gmbh-00000279", "") in new stack

How do I go about diagnosing these dropped calls. The system has been running for over a year now with almost no dropping calls. About a month ago calls started to drop…

Where should I start to find out what is causing the problem?

Best regards
codec

2

Are there any special logging functionalities to start, which could help diagnosing this?
Looking at the full-log I can only see “left ‘simple_bridge’ basic-bridge”…

But I cannot see why it is leaving the simple bridge, nor which side of the communication is causing it.

Any help appreciated

3

Turning on SIP Debug from the Asterisk CLI would be the next logical step. This should give you lots (perhaps too much) information on where the comm failure is starting from.

4

As @cynjut said use SIP debug. But be aware, you will have a LOT of logs to parse out.

5

@cynjut Thank you, I’ve enabled sip debug now. I’ve also enabled the tcpdump into rotating files with:
tcpdump -s 0 -C 100 -W 10 -w rbuf -Z root &
which I found in another thread.
Now I’ll wait for the next drop of a call, then wade through the information.
I bet I’ll have some more questions then :wink:

Thanks sofar
codec

2 Likes
6

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