Frequent Drops of SIP Trunk

FreePBX Providers
, , ,
1

I have been having an issue on FreePBX where the SIP trunk drops between the server and the SIP provider.

Here is what I see in the logs. Trunk name has been masked.

5928 [2022-10-25 21:00:20] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (71ms / 2000ms)
5929 [2022-10-25 21:07:04] NOTICE[2408] chan_sip.c: Peer ‘40’ is now UNREACHABLE! Last qualify: 71
5930 [2022-10-25 21:07:24] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now UNREACHABLE! Last qualify: 70
5931 [2022-10-25 21:08:38] NOTICE[2408] chan_sip.c: – Registration for '4[email protected]’ timed out, trying again (Attempt #2)
5932 [2022-10-25 21:09:12] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (70ms / 2000ms)
5933 [2022-10-25 21:09:30] NOTICE[2408] chan_sip.c: Peer ‘40’ is now Reachable. (69ms / 3500ms)
5934 [2022-10-25 21:17:17] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now UNREACHABLE! Last qualify: 69
5935 [2022-10-25 21:17:38] NOTICE[2408] chan_sip.c: Peer '40’ is now UNREACHABLE! Last qualify: 70
5936 [2022-10-25 21:19:05] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (69ms / 2000ms)
5937 [2022-10-25 21:19:13] NOTICE[2408] chan_sip.c: Peer ‘40’ is now Reachable. (70ms / 3500ms)
5938 [2022-10-25 21:27:07] NOTICE[2408] chan_sip.c: – Registration for '4[email protected]’ timed out, trying again (Attempt #2)
5939 [2022-10-25 21:27:10] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now UNREACHABLE! Last qualify: 316
5940 [2022-10-25 21:27:20] NOTICE[2408] chan_sip.c: Peer ‘40’ is now UNREACHABLE! Last qualify: 71
5941 [2022-10-25 21:27:27] NOTICE[2408] chan_sip.c: – Registration for '4[email protected]’ timed out, trying again (Attempt #3)
5942 [2022-10-25 21:27:47] NOTICE[2408] chan_sip.c: Peer ‘40’ is now Reachable. (70ms / 3500ms)
5943 [2022-10-25 21:27:47] NOTICE[2408] chan_sip.c: – Registration for '4[email protected]’ timed out, trying again (Attempt #4)
5944 [2022-10-25 21:28:07] NOTICE[2408] chan_sip.c: – Registration for ‘4[email protected]’ timed out, trying again (Attempt #5)
5945 [2022-10-25 21:28:27] NOTICE[2408] chan_sip.c: – Registration for '4[email protected]’ timed out, trying again (Attempt #6)
5946 [2022-10-25 21:28:58] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (69ms / 2000ms)
5947 [2022-10-25 21:36:02] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now UNREACHABLE! Last qualify: 69
5948 [2022-10-25 21:37:33] NOTICE[2408] chan_sip.c: – Registration for ‘4[email protected]’ timed out, trying again (Attempt #2)
5949 [2022-10-25 21:37:53] NOTICE[2408] chan_sip.c: – Registration for '4[email protected]’ timed out, trying again (Attempt #3)
5950 [2022-10-25 21:37:54] NOTICE[2408] chan_sip.c: Peer ‘40’ is now UNREACHABLE! Last qualify: 69
5951 [2022-10-25 21:38:22] NOTICE[2408] chan_sip.c: Peer '40’ is now Reachable. (1069ms / 3500ms)
5952 [2022-10-25 21:38:32] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (69ms / 2000ms)

6228 [2022-10-25 23:31:25] NOTICE[2408] chan_sip.c: Peer ‘40’ is now UNREACHABLE! Last qualify: 71
6229 [2022-10-25 23:31:36] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now UNREACHABLE! Last qualify: 69
6230 [2022-10-25 23:32:43] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (1071ms / 2000ms)
6231 [2022-10-25 23:32:43] NOTICE[2408] chan_sip.c: Peer '40’ is now Reachable. (69ms / 3500ms)
6232 [2022-10-25 23:54:49] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now UNREACHABLE! Last qualify: 141
6233 [2022-10-25 23:54:51] NOTICE[2408] chan_sip.c: Peer ‘40’ is now UNREACHABLE! Last qualify: 71
6234 [2022-10-25 23:55:03] NOTICE[2408] chan_sip.c: Peer '40’ is now Reachable. (2077ms / 3500ms)
6235 [2022-10-25 23:55:13] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (69ms / 2000ms)
6236 [2022-10-25 23:57:10] NOTICE[2408] chan_sip.c: Peer ‘40’ is now UNREACHABLE! Last qualify: 2077
6237 [2022-10-25 23:57:17] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now UNREACHABLE! Last qualify: 71
6238 [2022-10-25 23:58:09] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (69ms / 2000ms)
6239 [2022-10-25 23:58:11] NOTICE[2408] chan_sip.c: Peer '40’ is now Reachable. (70ms / 3500ms)
6693 [2022-10-26 00:05:12] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Lagged. (3070ms / 2000ms)
6694 [2022-10-26 00:05:22] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (70ms / 2000ms)
6695 [2022-10-26 00:06:26] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now UNREACHABLE! Last qualify: 70
6698 [2022-10-26 00:07:04] NOTICE[2408] chan_sip.c: Peer ‘ThinkTel’ is now Reachable. (70ms / 2000ms)

I had a ticket open with the SIP Provider. They validated that the SIP trunk was flapping, but saw no issues on their end.

The PBX is version FreePBX 15.0.24

Currently running as a Virtual Machine on ESXi 6.5.0U3. There are plenty or resources located to the VM with no errors reported.

The Network is running clean with no errors on the Network Switch or Firewall/Router. Network Utilization is very low.

Here is an MTR showing performance of the internet connection. I have spoken with the ISP about a more direct route, but it still falls within the performance specs put out by the SIP Provider.

Host Loss% Snt Last Avg Best Wrst StDev

  1. _gateway 1.7% 59 0.4 0.4 0.3 1.0 0.1
  2. 199.180.170.25 0.0% 59 11.3 11.9 10.7 21.9 1.4
  3. (waiting for reply)
  4. 10.130.17.44 0.0% 59 11.3 13.6 10.8 57.4 8.0
  5. 67.69.37.65 0.0% 59 11.2 11.8 10.9 16.0 0.9
  6. tcore3-calgaryqa_bundle-ether5.n 0.0% 59 25.9 28.9 25.8 89.7 9.1
  7. tcore3-calgary68_hundredgige0-1- 1.7% 59 25.8 29.6 25.8 48.4 3.6
  8. tcore3-vancouver_tengige0-15-0-5 15.5% 59 25.8 26.5 23.4 35.8 1.8
  9. bx6-seattle_et-0\0470\0477_ae0.n 0.0% 59 23.3 27.9 23.1 97.2 11.0
  10. sea-b2-link.ip.twelve99.net 0.0% 59 55.2 59.7 53.2 116.6 11.1
  11. shawbusiness-svc070877-ic357089. 0.0% 59 31.0 31.4 28.0 85.8 7.3
  12. rc2wt-be18-1.wa.shawcable.net 0.0% 59 28.7 31.0 27.9 49.2 4.0
  13. rc3no-be100.cg.shawcable.net 0.0% 59 26.1 27.2 25.5 57.4 4.4
  14. rc2we-be6.ed.shawcable.net 0.0% 59 31.0 31.8 30.4 66.1 4.6
  15. 66.163.70.81 70.7% 59 30.7 30.7 28.6 32.1 1.0
  16. ra1ar-ge3-2-66.ed.bigpipeinc.com 51.7% 59 30.7 31.3 30.7 35.9 0.9
  17. ge-0-2-5-889.ipr01.edtmtds.distr 0.0% 58 67.1 69.4 66.7 121.0 7.8
  18. ThinkTel 0.0% 58 67.1 69.0 66.9 145.0 10.2

If there are any other (preferably free and linux based) VoIP network analyses out there please let me know. What would be the next troubleshooting steps?

Thanks for the support.

2

This seems to be the problem hop in this particular trace, although it is nowhere near the 2 seconds measured here:

IP networks are contended, and modern routers can have far too much buffer space, as so can react to an overload with extreme round trip times.

3

Thank you David55. Have been down this path to try and work with the ISP. They are not open to reviewing their network or doing any optimization. As you can see, the route takes the packet around North America to get 200km across the province. The SIP provider reviews to look at a trace route as it is “Not a proper VoIP diagnosis tool as ICMP is prioritized lower on the network elements”

It brings me back to looking for a network sniffer tool that is optimized for VoIP and perhaps some tuning perimeters for the freePBX system.

4

ICMP is the only way you are going to access intermediate nodes. VoIP diagnostics can only tell you about the behaviour between VoIP components in the network (proxies, registrars, and user agents). That is what the 2.07 seconds figure is telling you about.

The default for Unix/Linux traceroute is to use UDP outbound, it is fundamentally dependent on ICMP for the responses.

5

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