Chan_sip.c:4263 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data


(Avayax) #1

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?


(James Zhu) #2

Please refer this: http://forums.asterisk.org/viewtopic.php?f=1&t=92474


(Andrew Marba) #3

Hi, I am facing this same problem. Let me explain. I installed the FreePBX 10.13.66-64bit using the iso on Intel machine.
I followed the installation process from wiki.freepbx.org/display/PPS/FreePBX+Distro+First+Steps+After+Installation

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


(Andrew Marba) #4

Update:

I am still getting the error even if not logged in to UCP.


[2017-05-31 19:38:40] ERROR[2567]: chan_sip.c:4273 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
Really destroying SIP dialog ‘76fceccd230bd82f4cedb81c6ff16ef0@192.168.1.15:5160’ Method: OPTIONS
Reliably Transmitting (no NAT) to 192.168.1.100:65107:
OPTIONS sip:jl9hkug8@ohdb8merp4q8.invalid;transport=wss SIP/2.0
Via: SIP/2.0/WS 192.168.1.15:5160;branch=z9hG4bK00784d2b
Max-Forwards: 70
From: “Unknown” sip:Unknown@192.168.1.15:5160;tag=as18cdacc9
To: sip:jl9hkug8@ohdb8merp4q8.invalid;transport=wss
Contact: sip:Unknown@192.168.1.15:5160;transport=ws
Call-ID: 14e0438825e98f5675a98215358dcfd4@192.168.1.15:5160
CSeq: 102 OPTIONS
User-Agent: FPBX-13.0.191.11(13.14.0)
Date: Wed, 31 May 2017 14:08:54 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
Content-Length: 0


PBX IP is 192.168.1.15
My PC is 192.168.1.100


(Dave Burgess) #5

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:

http://forums.asterisk.org/viewtopic.php?f=1&t=92474

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.


(Andrew Marba) #6

I tried disabling all the trunks except for the default which was dahdi and still there was this error. Below is my trunk configuration:

username=1004XXX
type=friend
secret=vgEEXXXXXXXXXX
qualify=yes
nat=force_rport,comedia
insecure=very
host=203.153.53.140
fromuser=1004292
fromdomain=203.153.53.140
dtmfmode=rfc2833
disallow=all
allow=ulaw&alaw


(Dave Burgess) #7

“insecure=very” is deprecated (IIRC).

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.


(Andrew Marba) #8

I tried to reinstall the firewall.

Freepbx ip is in the DMZ in the router.

when I try to login to UCP I get this in cli :slight_smile:

== WebSocket connection from ‘192.168.1.100:51014’ for protocol ‘sip’ accepted using version ‘13’
– Registered SIP ‘996003’ at 192.168.1.100:51014
[2017-05-31 20:43:01] ERROR[4619]: chan_sip.c:4273 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
> Saved useragent “SIP.js/0.7.7” for peer 996003
[2017-05-31 20:43:01] ERROR[4619]: chan_sip.c:4273 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
[2017-05-31 20:43:05] NOTICE[2604]: chan_sip.c:29976 sip_poke_noanswer: Peer ‘996003’ is now UNREACHABLE! Last qualify: 0
[2017-05-31 20:43:15] ERROR[2604]: chan_sip.c:4273 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data

extension pjsip/6003 is configured with the account i tried to login
and the sip show peers:

996001 (Unspecified) D No No A 0 UNKNOWN
996003/ptb6kegr 192.168.1.100 D No No A 51014 UNREACHABLE


(Avayax) #9

Nobody seems to really know what this error is about.
There wasn’t much help on the Asterisk forum either.

I have seen this with misconfigured outbound firewall rules too.
I get it also when using Zulu soft phone on Asterisk 11.


(Avayax) #10

Is that your UCP WebRTC client and you are using Asterisk 11?

As I am getting the error for Zulu soft phone too, the problems might be related:


(Andrew Marba) #11

Its UCP WebRTC client. I get this error even when I am not logged in through UCP.


(Avayax) #12

Your WebRTC client probably caused the error, and it keeps displaying the message.
I have seen the same, but eventually the error message stopped.

Are you using asterisk 11?


(Andrew Marba) #13

Its Asterisk 13.14.0


(Steven Sedory) #14

So I’m on 13.14.0 as well. Getting similar logs.

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.


(Andrew Marba) #15

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.


Error[6641] chan_sip.c:4273 Serious Network Trouble; __sip_xmit returns error for pkt data
Chan_sip.c: Serious Network Trouble
(Steven Sedory) #16

Update: see what I just posted here Incomming Calls Going Nowhere


(Ricardas Jonikas) #17

I am Also getting the Error, when i log in to UCP.

Only when i have Web RTC enabled. It creates extensions. Something like bellow.
99200/b0e71a8h 192.168.101.109 D No No A 2382 UNREACHABLE

Once i disabled Web RTC for the users or OR Unnistall/Disable module errors are gone.


#18

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.


(Lorne Gaetz) closed #19

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