Dave Miller
2007-Apr-26 08:46 UTC
[asterisk-users] MeetMe + IAX2 + Asterisk 1.2.18 = calls dropped
We upgraded our asterisk server to 1.2.18 last night to pick up the security update. Since then, any calls coming in on IAX2 links get dropped if they try to enter a MeetMe conference room. The log shows this: Apr 26 08:33:16 NOTICE[27362]: chan_iax2.c:3167 iax2_read: I should never be called! Hanging up. I've temporarily worked around it by switching our inbound provider to use SIP instead of IAX, but that's not an ideal solution. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/
Tony Mountifield
2007-Apr-26 09:26 UTC
[asterisk-users] Re: MeetMe + IAX2 + Asterisk 1.2.18 = calls dropped
In article <4630C95D.4020502@mozilla.com>, Dave Miller <justdave@mozilla.com> wrote:> We upgraded our asterisk server to 1.2.18 last night to pick up the > security update. Since then, any calls coming in on IAX2 links get > dropped if they try to enter a MeetMe conference room. > > The log shows this: > > Apr 26 08:33:16 NOTICE[27362]: chan_iax2.c:3167 iax2_read: I should > never be called! Hanging up. > > I've temporarily worked around it by switching our inbound provider to > use SIP instead of IAX, but that's not an ideal solution.What was the last version that successfully worked for you? Cheers Tony -- Tony Mountifield Work: tony@softins.co.uk - http://www.softins.co.uk Play: tony@mountifield.org - http://tony.mountifield.org
Dave Miller
2007-Apr-26 09:39 UTC
[asterisk-users] MeetMe + IAX2 + Asterisk 1.2.18 = calls dropped
Dave Miller wrote on 4/26/07 11:46 AM:> We upgraded our asterisk server to 1.2.18 last night to pick up the > security update. Since then, any calls coming in on IAX2 links get > dropped if they try to enter a MeetMe conference room. > > The log shows this: > > Apr 26 08:33:16 NOTICE[27362]: chan_iax2.c:3167 iax2_read: I should > never be called! Hanging up. > > I've temporarily worked around it by switching our inbound provider to > use SIP instead of IAX, but that's not an ideal solution.Quick turnaround on the bug tracker, bug is resolved fixed already :) http://bugs.digium.com/view.php?id=9600 guess that'll be fixed in the next release. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/