No subject

Fri Sep 2 03:59:05 CDT 2011

x100 (g729) read/write =3D 0x100 (g729)/0x100 (g729)"

- As Kevin says, the packet is arriving from somewhere.

- The error is coming from chan_sip.c, so we can assume that at least one l=
eg of the call is SIP.

- Has anyone that sees this error tried using Wireshark to capture and deco=
de the SIP conversation that causes the message to see whether it is a remo=
te endpoint sending a uLaw packet in the middle of the g729 stream when it =
should not?

Just a thought.

-- Bandwidth and Colocation Provided by --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:

More information about the asterisk-dev mailing list