Hello.
I'm having a strange problem with the IAX2 channel and
IAXmodem and I was hoping to get some light from someone in these lists.
On my logs and on the console I'm getting a bunch of lines with:
[Oct 23 14:26:18] NOTICE[4417] chan_iax2.c: Peer 'XXX' is now
UNREACHABLE! Time: 3
[Oct 23 14:26:28] NOTICE[4413] chan_iax2.c: Peer 'XXX' is now REACHABLE!
Time: 3
The strangeness comes when I debug the iax2 channel (iax2 set
debug): the events(missed PONG I guess) that lead to the UNREACHABLE state
don't appear on the console and on the log I get only 10% of the total state
change messages I was getting first. Disabling the debug, the lines reappear as
before.
The state is changed from UNREACHABLE to REACHABLE after 10
seconds(given by qualifyfreqnotok), as documented above.
Here is what I'm using to do my tests:
Debian 5.0.2 Kernel 2.6.26
Asterisk 1.4.21 (tried 1.6 but the problem it's still there)
Iaxmodem-1.1.1
DAHDI 2.2.0
Sangoma A104 CARD and to be safe I loaded the dahdi_dummy too
*CLI> dahdi show status
Description Alarms IRQ bpviol CRC4
wanpipe1 card 0 OK 0 0 0
wanpipe2 card 1 RED 0 0 0
wanpipe3 card 2 RED 0 0 0
wanpipe4 card 3 RED 0 0 0
DAHDI_DUMMY/1 (source: HRtimer) 1 UNCONFIGUR 0 0 0
The unreachable part is rather odd given that the two apps are
on the same host.
Reading some articles on the subject I found that this behavior
can become a problem if the call arrives when the iaxmodem peer is in the
unreachable state.
Is there anyone that has an idea on what might be causing this?
Sorry for the English and thanks in advance for any help you can provide,
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20091023/22d723c0/attachment.htm