VoIP Mailing List Archives

[roel at 1afa.com]

Hi list!

I have a problem where SIP packets sent by Asterisk do not hit the wire, and
I don't know what could cause this.

I'm running Asterisk 1.8.28_cert5 with full SIP debug. At the same time, I'm
doing a tcpdump of the traffic on the network interface. I can see in the SIP
debug log that asterisk is sending packets. Most of the time, I can see
those packets in the tcpdump, as you would expect.
However, sometimes Asterisk sends a packet that *does not show up* in the
tcpdump. Asterisk then does several retransmits (that also don't show up).
The next packet that is not a retransmit does show up again.

This causes Asterisk to log the peer it was sending packets to temporarily
as Lagged or unreachable.

There is no outgoing firewall on this box.

Could anyone give me some pointers where to look?

If Asterisk logs "VERBOSE[13019] chan_sip.c: Reliably Transmitting (NAT) to
x.x.x.x:" you would expect to see that packet in a tcpdump trace, right?
What could cause this not to be so? Are there network statistics I could
look at? Is there a counter in /proc or /sys for problems with sending
packets? Anything?

If more information is necessary please do let me know.

Thanks a lot in advance,

Roel

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

[dovid at telecurve.com]

The tcpdump that you are running is on the Asterisk box or via port mirroring?

Regards,

Dovid

-----Original Message-----
From: Roel van Meer <roel@1afa.com>
Sender: asterisk-users-bounces@lists.digium.comDate: Thu, 31 Mar 2016 13:34:51
To: <asterisk-users@lists.digium.com>
Reply-To: Asterisk Users Mailing List - Non-Commercial Discussion
<asterisk-users@lists.digium.com>
Subject: [asterisk-users] Lost outgoing SIP packets

Hi list!

I have a problem where SIP packets sent by Asterisk do not hit the wire, and
I don't know what could cause this.

I'm running Asterisk 1.8.28_cert5 with full SIP debug. At the same time, I'm
doing a tcpdump of the traffic on the network interface. I can see in the SIP
debug log that asterisk is sending packets. Most of the time, I can see
those packets in the tcpdump, as you would expect.
However, sometimes Asterisk sends a packet that *does not show up* in the
tcpdump. Asterisk then does several retransmits (that also don't show up).
The next packet that is not a retransmit does show up again.

This causes Asterisk to log the peer it was sending packets to temporarily
as Lagged or unreachable.

There is no outgoing firewall on this box.

Could anyone give me some pointers where to look?

If Asterisk logs "VERBOSE[13019] chan_sip.c: Reliably Transmitting (NAT) to
x.x.x.x:" you would expect to see that packet in a tcpdump trace, right?
What could cause this not to be so? Are there network statistics I could
look at? Is there a counter in /proc or /sys for problems with sending
packets? Anything?

If more information is necessary please do let me know.

Thanks a lot in advance,

Roel

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

[roel at 1afa.com]

Dovid Bender writes:

[dovid at telecurve.com]

Just guessing I would verify that the out of : iptables -L -nv
Shows no dropped packets, try disabling selinux as well as look at the limits of the asterisk pid (cat /proc/<Asterisk PID>/limits). I know the defualt for rhel is 1024 which was never enough for us.


Regards,

Dovid

-----Original Message-----
From: Roel van Meer <roel@1afa.com>
Date: Thu, 31 Mar 2016 14:10:48
To: <dovid@telecurve.com>; Asterisk Users Mailing List - Non-Commercial Discussion<asterisk-users@lists.digium.com>
Subject: Re: [asterisk-users] Lost outgoing SIP packets

Dovid Bender writes:

[roel at 1afa.com]

Dovid Bender writes:

[ethy.brito at inexo.co...]

Hi Roel

Just guessing: do you have conntrack enabled?
If not, "modprobe nf_conntrack_netlink" (you can remove it and its dependencies
later)

What are the outputs of
sysctl net.netfilter.nf_conntrack_count
and
sysctl net.netfilter.nf_conntrack_max

when the problem shows up?

cheers

Ethy

On Thu, 31 Mar 2016 12:17:12 +0000
"Dovid Bender" <dovid@telecurve.com> wrote:

[roel at 1afa.com]

Ethy H. Brito writes:

[asterisk at voipbusine...]

Hello;
I ran into a similar problem not long ago. Always try the easiest (and
cheapest) solutions first. My solution was to replace the Ethernet cable and
then to change the network switch port. Did the trick. Switches with errors
tend to be due to faulty switch ports.
Regards;
John V.

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Roel van Meer
Sent: Thursday, March 31, 2016 7:35 AM
To: asterisk-users@lists.digium.com
Subject: [asterisk-users] Lost outgoing SIP packets

Hi list!

I have a problem where SIP packets sent by Asterisk do not hit the wire, and
I don't know what could cause this.

I'm running Asterisk 1.8.28_cert5 with full SIP debug. At the same time, I'm
doing a tcpdump of the traffic on the network interface. I can see in the
SIP debug log that asterisk is sending packets. Most of the time, I can see
those packets in the tcpdump, as you would expect.
However, sometimes Asterisk sends a packet that *does not show up* in the
tcpdump. Asterisk then does several retransmits (that also don't show up).
The next packet that is not a retransmit does show up again.

This causes Asterisk to log the peer it was sending packets to temporarily
as Lagged or unreachable.

There is no outgoing firewall on this box.

Could anyone give me some pointers where to look?

If Asterisk logs "VERBOSE[13019] chan_sip.c: Reliably Transmitting (NAT) to
x.x.x.x:" you would expect to see that packet in a tcpdump trace, right?
What could cause this not to be so? Are there network statistics I could
look at? Is there a counter in /proc or /sys for problems with sending
packets? Anything?

If more information is necessary please do let me know.

Thanks a lot in advance,

Roel

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to
Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users


--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

[ethy.brito at inexo.co...]

On Thu, 31 Mar 2016 15:29:07 +0200
Roel van Meer <roel@1afa.com> wrote:

[ethy.brito at inexo.co...]

On Thu, 31 Mar 2016 14:41:14 +0200
Roel van Meer <roel@1afa.com> wrote:

[roel at 1afa.com]

Ethy H. Brito writes:

[asterisk.org at sedwar...]

On Thu, 31 Mar 2016, Dovid Bender wrote:

[andres at telesip.net]

On 3/31/16 7:34 AM, Roel van Meer wrote:

[pete at fiberphone.co.nz]

Roel,

Just another thought bouncing around... Your ifconfig output was specific to eth1. Is there an eth0 too? Is there a chance packets are heading to that other interface when they shouldn't be? Running a second tcpdump on eth0 at the same time should at least disprove the theory quickly.

Pete

[duncan at e-simple.co.nz]

One issue that can catch you is a packet MTU limit in your path to your SIP box lower than your standard MTU. You can check that with ping -s 1500 <host> option

Cheers Duncan

On 01/04/16 17:12, Pete Mundy wrote: