|
05-30-2007, 02:56 PM | #1 |
Junior Member
Join Date: May 2007
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
5060 blocked issue
First of all, I would like to thank you all for the
amazing wealth of information that is contained in all these forums. Here is my issue: Port 5060 (both incoming and outgoing) is blocked by my ISP. I currently use us.voxalot.com:4060 as my SIP server on my ATA. My ATA listens on 5061 to bypass the incoming port block. ATA registers fine. However, I cannot make any outgoing or incoming calls with this setup. When I make an outgoing call, it rings the destination phone. Calls do not get completed. The same happens for incoming calls as well. I hear the rings but the calls do not get completed when the phone goes off hook. I have traced the root of the problem as follows: While the adapter sends the REGISTER messages to the correct unblocked 4060 port, it responds to INVITE messages to the default 5060 port. This is probably because the INVITE messages from the Voxalot server contain the IP address only and not the port # specification. The adapter attaches the default port # which is 5060 and sends the ACK messages to a blocked port. The adapter referred here is a Grandstream HT486. This is the reason I find calls do not get completed. Is there any way to work around this issue? Can something be done on the server side to correct this issue? Any help with this issue is very much appreciated. Thanks in advance. |
06-01-2007, 02:19 PM | #2 |
Junior Member
Join Date: May 2007
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
I wanted to include the following transcript for
clarity: INVITE sip:nnnnnn@xx.xx.xx.225:5061;user=phone SIP/2.0 Record-Route: <sip:64.34.173.199;lr=on;ftag=as50965e53> Record-Route: <sip:64.34.163.35;lr=on;ftag=as50965e53> Record-Route: <sip:64.34.162.221;lr=on;ftag=as50965e53> Via: SIP/2.0/UDP 64.34.173.199;branch=z9hG4bKe781.6fde1fe6.0 Via: SIP/2.0/UDP 64.34.163.35;branch=z9hG4bKe781.30329f5.0 Via: SIP/2.0/UDP 64.34.162.221;branch=z9hG4bKe781.07a4ffb.0 Via: SIP/2.0/UDP 204.11.194.10:5070;branch=z9hG4bK2bfde41f;rport=50 70 Please note the Via: field only contains an IP address 64.34.173.199 and not 64.34.173.199:4060. It is SIP convention to use 5060 as a default port if no port number is specified. As a result, the replies(ACK) go to 64.34.173.199:5060 which is blocked by the ISP. Is it possible to do someting about this? Please let me know. Thanks. |
06-01-2007, 07:26 PM | #3 |
Junior Member
Join Date: May 2007
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
Here is the response from Grandstream support on this:
"Unfortunately, we can not help you in case port are blocked by ISP. According to SIP standard message should be send according to port arrived in Via or Route header, and if these ports do not arrive, the message will be sent to default 5060" Is there anything Voxalot can do about this to help several of us that are behind ISPs that block 5060? Thank you. |
06-01-2007, 11:06 PM | #4 | |
Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts |
Quote:
4060 3060 2060 In your ATA try registering us.voxalot.com, eu.voxalot.com or au.voxalot.com using any of the above ports.
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
|
06-02-2007, 02:38 PM | #5 |
Junior Member
Join Date: May 2007
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
Martin,
Thanks for your reply. A simple redirection of ports 2060, 3060 and 4060 doesn't seem to be working. The issue is with the Via header in the INVITE messages. Currently it is: Via: SIP/2.0/UDP 64.34.173.199 It should read: Via: SIP/2.0/UDP 64.34.173.199:4060 (or 2060/3060) In the absence of a port number in the Via header, a SIP compliant device automatically uses 5060 as the default port. Since this is blocked by the ISP, ACK messages (that are necessary for call completion) do not reach the server. In addition to the redirection of ports 2060/3060/4060 to 5060, something that can be done to correct this issue is to run the server as below: $ ./ser -f x.cfg -l 192.168.X.X -p 5060 -l 192.168.X.X -p 4060 I sincerely request Voxalot to consider this request as it will help so many of us that may be behind ISPs that block 5060. Thank you very much. |
06-23-2007, 02:56 PM | #6 |
Junior Member
Join Date: Jun 2007
Posts: 2
Thanks: 0 Thanked 0 Times in 0 Posts |
if you could run the service on port 80 or 443 I'm with you!!
You would be the first SIP provider that have done it in the world. I've spent last 3 days looking for one and couldn't find. Is is possible? Will it be in future? My problem is my ISP... blocks almost everything. Moreover, I think that a lot of people got the same problem (corp firewalls, isp firewalls etc). Thanks Last edited by gregd72002; 06-23-2007 at 03:02 PM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
us.voxalot.com blocked by Sipgate too? | Hellmaker | Voxalot Support | 2 | 06-07-2007 01:37 PM |
TRX Telecom IP blocked | wmp | Voxalot Support | 3 | 11-04-2006 02:57 AM |
Port 5060 ? | shezad | Voxalot Support | 0 | 10-29-2006 01:13 PM |
weired issue - help??? | jmstosch | Voxalot Support | 1 | 09-22-2006 11:31 PM |
provider ports 5060 | muzzza | Voxalot Support | 2 | 09-06-2006 03:03 AM |