|
Title: IS is A BUGGGGGGGGGGGGGGGGG? Post by: MST on Tuesday 15 December 2009, 01:48:34 pm Gents from Ednian,
I have a pleasure testing 2.3 version. Rather is is a nightmare than pleasure. A Trixbox server and a of IP phones are plugged to EDNIAN, and every Endian restart something is not working corectly. Having RTP ports open all the time is so mess up on EDNIAN, I use wireshark and see clearly that Endian is blocking them even if they are open. OK I understand that I am human being and might do mistakes. I simply enabled 4569 for IAX2 and it works for some time, for another not !!!!!!!!! Again use wireshark and see clearly that EDnain is blocking that simple UDP port. How should I use this software if it is not capable to do simple stuff? Open VPN works ok, better than 2.2 vesrion. I don't but I think I have to switch again to 2.2 because at least it did not make any troubles to VOIP. Is there any solution to that problem? Is it only me experiencing such problems or someone else is using 2.3 for VOIP stuff? MST Title: Re: IS is A BUGGGGGGGGGGGGGGGGG? Post by: Saltee on Thursday 07 January 2010, 05:27:48 am Hi MST,
I'm using EFC 2.3 with AsteriskNOW and routing via IAX (well IAX2) with no issues. I migrated from a physical Trixbox CE machine to a virtual AsteriskNOW machine hosted in ESXi. Both run without issue. A of things spring to mind re' your post: - you mention that your endpoints can't get RTP out because EFW is blocking, but you suggest that you are routing (VOIP) via IAX. The RTP requests should be embedded within the IAX stream on UDP 4569, so there should be no actual RTP ports to open. - check that you have configured an outbound (and inbound) route for UDP 4569 (I'm guessing you already did this correctly). - check that you didn't use another protocol such as SIP inadvertently on some endpoints and that your EFW 2.2 was configured to allow the RTP through. I've been using EFC 2.3 for a month now without issue both with Trixbox and AsteriskNOW, although they're both really Asterisk. Before this I used IPCop. You might also want to turn on IAX2 debuging on tha Asterisk CLI (IAX2 set debug) to see whether IAX2 is getting around as far as Asterisk is concerned, although Wireshark will give you a more detailed picture - and you already have this :) . I'm very interested to read about your findings as I am using a very similar configuration, albeit probably scaled down! |