SOLVED: Calls cutting off after 30 seconds - Intermittently

General Help
1

Can anyone help with this, I have installed the new system over the weekend and now calls are cutting off after 30 seconds. I have checked the logs and it appears that my system is hanging up.

All are outbound calls.

There have been about 300 outbound calls today and about 20 of them have failed with this issue.

see extract…

[Dec 6 13:55:41] VERBOSE[9164] pbx.c: – Executing [h@macro-dialout-trunk:1] Macro(“SIP/6002-000000bd”, “hangupcall,”) in new stack
[Dec 6 13:55:41] VERBOSE[9164] pbx.c: – Executing [s@macro-hangupcall:1] GotoIf(“SIP/6002-000000bd”, “1?skiprg”) in new stack
[Dec 6 13:55:41] VERBOSE[9164] pbx.c: – Goto (macro-hangupcall,s,4)
[Dec 6 13:55:41] VERBOSE[9164] pbx.c: – Executing [s@macro-hangupcall:4] GotoIf(“SIP/6002-000000bd”, “1?skipblkvm”) in new stack
[Dec 6 13:55:41] VERBOSE[9164] pbx.c: – Goto (macro-hangupcall,s,7)
[Dec 6 13:55:41] VERBOSE[9164] pbx.c: – Executing [s@macro-hangupcall:7] GotoIf(“SIP/6002-000000bd”, “1?theend”) in new stack
[Dec 6 13:55:41] VERBOSE[9164] pbx.c: – Goto (macro-hangupcall,s,9)
[Dec 6 13:55:41] VERBOSE[9164] pbx.c: – Executing [s@macro-hangupcall:9] Hangup(“SIP/6002-000000bd”, “”) in new stack
[Dec 6 13:55:41] VERBOSE[9164] app_macro.c: == Spawn extension (macro-hangupcall, s, 9) exited non-zero on ‘SIP/6002-000000bd’ in macro ‘hangupcall’
[Dec 6 13:55:41] VERBOSE[9164] app_macro.c: == Spawn extension (macro-dialout-trunk, s, 19) exited non-zero on ‘SIP/6002-000000bd’ in macro ‘dialout-trunk’
[Dec 6 13:55:41] VERBOSE[9164] pbx.c: == Spawn extension (from-internal, 01274815207, 7) exited non-zero on ‘SIP/6002-000000bd’
[Dec 6 13:55:41] VERBOSE[9165] app_mixmonitor.c: == MixMonitor close filestream
[Dec 6 13:55:41] VERBOSE[9165] app_mixmonitor.c: == End MixMonitor Recording SIP/6002-000000bd

Can anyone offer advice?

2

Any chance each of the failed 20 calls were traversing a firewall that the other calls weren’t? Many firewalls timeout state entries for UDP at 30 seconds.

3

They are all going over the same trunk so I don’t think so.

My trunk providers IP is set on the firewall to forward all traffic to the ip of the voip server also.

I believe they may all be local numbers and mobile numbers may not be affected, but my users can’t confirm this yet. Mobiles and Local numbers are on different outbout calling rules, but both rules point to the same trunk.

Do you need any different logs?

Thanks

Mark

4

I got to the bottom of the problem. I am using soft phones (eyebeam) as well as some Atcom IP phones. Only the soft phones were failing and only on local numbers.

I have found a setting on the soft phone which said " In times of network disruption automatically hang up phones after RTCP has been inactive for xx seconds". xx was set to 30!

Unselecting the box has fixed the issue.

Hopefully it wont cause a different one!

Regards

Mark.

1 Like