Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am encountering a strange problem on my VOIP setup. Basically, I have a asterisk appliance IP04. I have setup all the extensions and everything. I use a Linksys PAP2T as an ATA remotely. Now, my problem is the ATA sometimes is okay can call SIP and PSTN but sometimes I just can't hear anything. I thought it was my ISP blocking the VOIP packets but I have tried both the SIP softphone and IAX2 softphone on my PC. For IAX2, it works perfectly however in the SIP, I can hear the other end but they cannot hear me.
These are the ports I have opened on my router
1.) UDP 5060 - SIP Port
2.) UDP 10000 - 20000 - RTP Port
3.) UDP 4569 - IAX2
Do I need to open both TCP/UDP for these ports or UDP should be enough?
These are the test cases:
1.) Using my Wifi Connection and a analog phone connected to ATA --> Sometimes working sometimes not and sometimes you can call SIP but the other end cannot hear you
2.) Using IAX2 in wifi connection --> This one works perfectly
3.) Using a mobile phone connected to Wifi Network --> The same...but you can call and go out on PSTN but the other end cannot hear you
4.) Using a mobile phone connected via 3G --> Works perfectly but as expected it is quite slow and voice quality is awful
Can you suggest what is wrong? I am really lost here. I want to use SIP rather than IAX2 because it is widely used and since my ATA doesn't support IAX2.
Are there other ports I need to open or configure?
I have had similar problems in the past, with great audio one day and nothing the next, and the best I can figure is that the service provider was doing something bizarre with those ports. For me, the solution has been to change the ports SIP and RTP are using away from the defaults of UDP/5060 and UDP/10-20k. SIP, RTP, and RTCP all operate over UDP exclusively.
Failing that, taking packet captures at each hop in the network would help narrow where things are breaking down.
Edit: This is also the poster child problem for firewall or NAT issues. On both ends, your firewalls are set to accept both incoming and outgoing traffic on those ports?
Last edited by gratuitous_arp; 11-17-2009 at 11:11 AM.
I have only firewall opened on my base station where my asterisk is located. I did not open anything on client side. Though, I have tried to put it on DMZ but still no luck.
By the way, what ports have you tried that worked?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.