asterisk users - Jun 2007 - Threading troubles 1.4.5 & IAX2-> SIP (FreeBSD specific??)

Hi there,

 I've asked this question to the BSD group too, but I'd like to know
whether anybody
else had similar experiences on Linux 2.6.20 etc.??

 FreeBSD 6.2
 Asterisk 1.4.5 (and 1.4.3 from ports)

Sip phone - PBX(*) -IAX2-VROUTER(*)- SIP-Voip provider
(SPA901 & SPA922 phones)

We've see a situation where the IAX2 appears to "loose"/drop the
voice
data to be sent to the
SIP side of things. This happens "semi" intermittently, but we can
reliably regenerate it
at >40 alaw calls (even on a dedicated 1G network) and also with G729
(but a tad more calls).
It appears to happen using both trunking and non-trunking modes.

 This happened with DONT_OPTIMIZE setting on or off, but with it ON it
doesn;t dump core.
At least when it was dumping core, it appeared to have been in the
pthread_cancel
calls.

We've recompiled the PBX asterisk with no threading, and the
milliwat/etc. tests to the vrouter
from the SIP phones ran clean (other than when we pushed the bandwidth
limits <grin>)

 This morning it was consistently the agent (on the SIP Phones) who
could hear the remote side complaining that the remote side can't hear
them anymore. After we've recompiled the VROUTER Asterisk with
non-threading, the calls stayed stable.

 What appears to happen is that somewhere in the threading the IAX
voice data is discarded or something on the way to the SIP side.

 Anybody else anything like this?
Any other work around for this issue/problem??

--
Hendrik Visage

On 6/25/07, Hendrik Visage <hvjunk at gmail.com>
wrote:
> We've see a situation where the IAX2 appears to "loose"/drop
the voice
> data to be sent to the
> SIP side of things. This happens "semi" intermittently, but we
can
> reliably regenerate it
> at >40 alaw calls (even on a dedicated 1G network) and also with G729
> (but a tad more calls).
> It appears to happen using both trunking and non-trunking modes.
I'm making a wild guess here, but I'd say that if you're using
trunking, then you're probably getting close to exceeding the MTU size
or possibly the MAX_TRUNKDATA size as defined in chan_iax2.c.  If it's
happening without IAX2 trunking turned on, then I have no idea what's
happening... you'd have to look at the IAX2 and SIP packets when the
problem is happening, and try to figure out what's causing the issue.

-Jared