News & Reviews
More How-To's & Tips More News
More Reviews Device Configuration Tools
No account yet? Create one
Forgot your Username or Password?

Welcome to the Voxilla VoIP Forum.

Voxilla has been a trusted source for accurate, up-to-date information on the IP Communications industry since 2002. A dedicated staff of reporters and engineers produce feature articles and product reviews to keep industry watchers abreast of the people, companies, and trends driving a fast moving market.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact us.





Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old August 12th, 2007, 01:53 AM
Amatory Amatory is offline
Junior Member
 
Join Date: May 2006
Posts: 2
Amatory
Default Asterisk ignores non standard port in REGISTER directive

I am facing this error in both Trixbox 2.2 (Asterisk 1.2.18) and Trixbox 2.3.0 (Asterisk 1.4.6). I would appreciate any insight.
I have the following REGISTER string in sip.conf
register=usernameassword@192.168.14.250:6060/username
Asterisk should thus send the register request to: 192.168.14.250 at port 6060. However, it actually sends the request to the standard 5060 port. Here is the output from CLI
Retransmitting 0000005 (NAT) to 192.168.14.250:5060:
REGISTER sip:192.168.14.250:6060 SIP/2.0
Via: SIP/2.0/UDP 192.168.14.104:5070;branch=z9hG4bK3a63040b;rport
From: ;tag=as7857a350
To:
Call-ID: 7dba5db402361ef80ba686c94f60bc51@127.0.0.1
CSeq: 102 REGISTER
User-Agent: Asterisk PBX
Max-Forwards: 70
Expires: 120
Contact:
Event: registration
Content-Length: 0
Does anyone know how to send the register request to a non standard port (6060)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old August 19th, 2007, 11:18 PM
AbNormal AbNormal is offline
Member
 
Join Date: Sep 2004
Location: Canada
Posts: 37
AbNormal
Default Re: Asterisk ignores non standard port in REGISTER directive

First of all, who are you trying to register WITH? Do you have an account with a VoIP provider? The IP address you show in the register string is a private address. Is this your own? Normally you would put the provider's IP addess or domain name there.

Secondly, the register string needs a ':' between the username and password. Did you inadvertantly delete it when you edited it for 'us' or is that how it actually was setup?

Third, try adding 'port=6060' (without the quotes) in your context. The register string doesn't seem to like anything but the default 5060 port.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:



Similar Threads for: Asterisk ignores non standard port in REGISTER directive
Thread Thread Starter Forum Replies Last Post
Tribox@Home on non-standard port (SIP/RTP) abcd_indya Asterisk Support Forum 1 August 1st, 2006 10:13 PM
route standard calls out with voicepulse rlek VoicePulse Support Forum 2 March 12th, 2006 10:06 PM
Port 5060 blocked in China: how to register with Broadvoice? roblongo BroadVoice Support Forum 56 December 6th, 2005 11:04 AM
Sipura SPA3000 PSTN-TO-VOIP Gateway ignores DTMF after auth bodosom Linksys (Sipura) VoIP Support Forum 10 August 24th, 2005 07:13 PM
How to multiline access with Asterisk and standard phone MustardMan Asterisk Support Forum 6 June 16th, 2004 12:49 AM



All times are GMT. The time now is 10:07 AM.


vBulletin, Copyright ©2000 - 2009, Jelsoft Enterprises Ltd. SEO by vBSEO 3.0.0 ©2007, Crawlability, Inc. Logos and trademarks are the property of Voxilla or their respective owner. All other content © 2003-2007 by Voxilla, Inc.