Log files telling me of network delays?

FreePBX Providers
1

I noticed the following in the FreePBX log files :-
54 [2021-10-05 10:23:08] NOTICE[1197] chan_sip.c: Peer ‘SIPGATE’ is now Lagged. (3014ms / 2000ms)
55 [2021-10-05 10:23:18] NOTICE[1197] chan_sip.c: Peer ‘SIPGATE’ is now Reachable. (13ms / 2000ms)
56 [2021-10-05 10:26:20] NOTICE[1197] chan_sip.c: Peer ‘SIPGATE’ is now Lagged. (2014ms / 2000ms)
57 [2021-10-05 10:26:30] NOTICE[1197] chan_sip.c: Peer ‘SIPGATE’ is now Reachable. (13ms / 2000ms)
58 [2021-10-05 10:29:33] NOTICE[1197] chan_sip.c: Peer ‘SIPGATE’ is now Lagged. (2014ms / 2000ms)
59 [2021-10-05 10:29:43] NOTICE[1197] chan_sip.c: Peer ‘SIPGATE’ is now Reachable. (13ms / 2000ms)
60 [2021-10-05 11:09:47] NOTICE[1197] chan_sip.c: Peer ‘SIPGATE’ is now Lagged. (2014ms / 2000ms)
61 [2021-10-05 11:09:57] NOTICE[1197] chan_sip.c: Peer ‘SIPGATE’ is now Reachable. (14ms / 2000ms)

This is a fairly recurrent feature in the logs. We are noticing occaisional jitter / garbled speech on calls, and I’m guessing this might be the cause of it. Our SIP trunk provider is SIPGATE.

We have a 100mb leased line (so 100mb synchronous) which is used for internet and telephony for 12 people. We dont make that many phone calls to be honest. Does this look like a bandwidth issue our end, or is it more likely to be a SIPGATE issue?

Thanks in advance.

2

You mean 100 Mb/s.

I don’t think Sipgate could offer a service with those delays at their end, so I would say it a problem with your ISP, or your link to them.

You may have some buffer bloat, i…e. the network can just cope, but so much traffic gets buffered in the network that it produces unacceptable delays.

3

Yes, 100Mb/s.

Interestingly, whenever I phone Sipgate support I get an inordinate amount of jitter (I call from a landline) which I always put down to the person I am speaking to working from home, and they have a poor internet connection.

But your post made me wonder, so I rang them today, and lo and behold, they have had a lot of reports of this, it’s a known issue, and they have 2 teams of engineers looking into it. (One looking at the carrier side, and one looking at their internal network side.)

So it looks like it is Sipgate after all.

4

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