| |
| News & Reviews |
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.
Voxilla VoIP Forum |
Non-Standard SIP PortThis forum is for issues that do not relate to either a specific provider or a specific vendors hardware. General issues that affect the advancement of VoIP as a whole. |
| | LinkBack | Thread Tools | Rate Thread | Display Modes |
| |||
| Does anyone know of any VoIP provider that uses a SIP port other than 5060? The reason I want to use port other than 5060 is that in my country, port 5060 is blocked by the telco. I had been using FWD because one of it's SIP proxy server operates on port 5082. This port works for me but FWD proxy is very unreliable. It goes down for days at a time. Therefore I want to use another VoIP company. It would be great if someone could tell me if there is a VoIP provider that uses a SIP port like 5082 or anything other than 5060. Thanks a lot. |
| |||
| VBuzzer uses port 80. I also believe VoiceStick has an option to use port 80, however you may need to talk to their customer service about it to get the details. If your isp truly blocks port 5060 then don't forget to change the port that your ATA or softphone is using from 5060 to something else. That's the port number address that your VoIP provider uses to send sip signalling packets addressed to you. The non-standard people like Skype and Yahoo Voice don't use port 5060. |
| |||
| Thanks a lot for the tip. Vbuzzer seems like what I was looking for. But I am having difficulty getting registered using SPA3102 ATA. I have followed instructions on their web site but my ATA keeps failing the registration. Have you configured any ATA or SIP phone with vbuzzer? Specifically do you know how I should enable STUN settings? Thanks a lot. |
| |||
| Quote:
UserID: Your_VBuzzer_ID Password: Your_VBuzzer_Password For a STUN server I would set the following: On Line 1 tab: NAT Mapping Enable: YES NAT Keep Alive Enable: YES On Sip tab: Substitute VIA Addr:YES Send Resp To Src Port:YES STUN Enable:YES STUN Server:stun.softjoys.com (or any other stun server that is close to you and can respond quickly) A STUN server is a standardized function so you can use any STUN server. I would select one that can respond very quickly so that you get the response before the adapter sends the Register request or the Sip Invite. Edit: If you get no response at all to your register requests perhaps your isp isn't just blocking ports but blocking all sip packets. Last edited by hwittenb : April 30th, 2008 at 05:47 AM. |
| |||
| I initially thought that my ISP was blocking all SIP packets because when I used X-Lite softphone, I got error 408 registration failed. But this theory failed to hold weight because both X-Lite and SPA3102 work with FWD on port 5082. Furthermore vbuzzer windows client application works fine. Any other ideas why SPA3102 is failing the registration. I have tried STUN options, proxy, without proxy, etc. but to no avail. Will it help if I use SIP TLS? Is it compatible with vbuzzer? Last edited by abbaspaliwala : April 30th, 2008 at 01:49 PM. Reason: forgot one question |
| | |
![]() |
| |||
| To narrow down the problem, I would try to figure out if you are just not receiving a response from VBuzzer or if they are sending you some error message. You can do this with a sip debug trace. Search this forum for how to do a trace if you are unsure of how to do it. Traces are sometimes difficult to read but you should be see able to responses coming back from VBuzzer to your Register requests. A DNS error would cause the problem but that would also cause FWD to fail no matter what port you were using. No, I don't believe so. Last edited by hwittenb : April 30th, 2008 at 08:07 PM. |
| Thread Tools | |
| Display Modes | Rate This Thread |
| |
| | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Asterisk ignores non standard port in REGISTER directive | Amatory | Asterisk Support Forum | 1 | August 19th, 2007 11:18 PM |
| SPA3000 - Specifying Mapped SIP port | dimagiba | Linksys (Sipura) VoIP Support Forum | 1 | March 4th, 2007 08:00 PM |
| changing sip port(s) to 80 | rybshik | Asterisk Support Forum | 8 | February 26th, 2007 04:43 AM |
| Tribox@Home on non-standard port (SIP/RTP) | abcd_indya | Asterisk Support Forum | 1 | August 1st, 2006 10:13 PM |
| Changing Sip Port | arsh | Asterisk Support Forum | 4 | February 12th, 2006 03:04 PM |