Was configuring a SIP trunk to a grandstream gateway and I am now getting this constantly:chan_sip.c:4263 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
I unplugged the grandstream and removed the trunks, still I am getting those CLI messages. What’s wrong?
I have created extension, trunk, and user in User management.
I tried to configure one of the extension 6001 in softphone and it works. incoming and outgoing (International call) works fine.
So now tried to login through UCP and all I get is this error in cli:
== WebSocket connection from ‘192.168.1.100:62380’ for protocol ‘sip’ accepted using version ‘13’
– Registered SIP ‘996003’ at 192.168.1.100:62380
[2017-05-31 16:52:48] ERROR[14963]: chan_sip.c:4273 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
The moment I logout of the UCP I dont get this error
I did a quick Google search and found several threads that hinted at the problem being in the SIP Trunk configuration. Only one offered any suggestions:
Basically, his theory is that one of the options in the trunk configuration is wrong and is causing an error when the trunk is instantiated. Most of the suggestions include posting your Trunk configuration so that we can look for deprecated options.
If this is a bidirectional trunk (inbound and outbound) then the type is correct.
It is also reasonably possible that there is a problem with the device connected to the trunk or a problem in the network (a “SIP helper” in a router, for example).
It seems to be an uncommon problem and is at the Asterisk level (not specifically a FreePBX question). Most of what I found implies that the problem is in your configuration, but I don’t really see much wrong with your config.
Examples, but notice the different part at the end:
> 2017-06-01 17:18:50] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b920bb40 (len 453) to 172.15.253.114:45204 returned -2: No such file or directory
> [2017-06-01 17:18:50] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
> [2017-06-01 17:18:50] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b868a050 (len 457) to 192.168.80.191:41975 returned -2: No such file or directory
> [2017-06-01 17:18:50] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
> [2017-06-01 17:18:50] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b8920eb0 (len 455) to 192.168.80.101:62879 returned -2: No such file or directory
> [2017-06-01 17:18:50] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:00] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b920bb40 (len 455) to 192.168.80.104:32907 returned -2: Interrupted system call
[2017-06-01 17:19:00] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:00] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b9431370 (len 450) to 192.168.6.75:44045 returned -2: Interrupted system call
[2017-06-01 17:19:00] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:00] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b8498250 (len 456) to 96.81.178.217:20648 returned -2: Interrupted system call
[2017-06-01 17:19:00] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:11] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b8ebac60 (len 449) to 192.168.40.54:38802 returned -2: Broken pipe
[2017-06-01 17:19:11] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:11] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b8233120 (len 455) to 209.222.118.34:29097 returned -2: Broken pipe
[2017-06-01 17:19:11] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:11] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b89eb470 (len 449) to 10.20.23.131:61422 returned -2: Broken pipe
[2017-06-01 17:19:11] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:49] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b8f0efb0 (len 454) to 96.81.178.217:23705 returned -2: Network is unreachable
[2017-06-01 17:19:49] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:49] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b9431370 (len 458) to 192.168.80.104:38966 returned -2: Network is unreachable
[2017-06-01 17:19:49] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-06-01 17:19:49] WARNING[2345] chan_sip.c: sip_xmit of 0x7f91b89eb470 (len 449) to 192.168.10.100:42700 returned -2: Network is unreachable
[2017-06-01 17:19:49] ERROR[2345] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
These type of log errors and warnings went away after a server restart. That said, if it is a Web RTC issue, we probably won’t see the issue until the morning when the users are using it again.
I have restarted the server couple of times and still the same. I now have no clue whats to be done next.
Now I am thinking whether I should continue with this new version or stick to the old existing one. And the reason I want to switch to this new version is the Firewall.
Just because this is the first google response when you see the error i wanted to drop my fix in.
I had this problem on a brand new install of FPBX 6.21.20.21
FreePBX 15.0.17.34
Asterisk 16.17.0
I was getting the same error and my trunk was unreachable.
I disabled my trunk and the network trouble error went away.
I found this forum post and got to the end of it and well.
Still failing.
So I ran asterisk-version-switch and used option 4
Press 4 for Asterisk 16 (LTS)
After it reinstalled and restarted all services my error has been cleared up.