site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
490
Share Topic
Posting?
Post a:
Post a:
Links: ·Submit a new forum topic ·Forum FAQ ·Submit a FAQ ·Docs Guidelines and Advisories ·EOS/EOL thread
AuthorAll Replies

mbruno

join:2003-07-03
Fruitland, MD

[HELP] opening up a port on a router

Greeting all, I am trying to setup my linksys ATA adapter for VOIP and I am having some problems. I believe I opened up a port on my router but would like for someone to verify I did this right. I wrote the following line in my router config to let port 5060 through to the other side.

IP nat inside source static UDP 10.10.10.219 5060 74.63.41.218 5060

This should let my voip provider talk to my ATA adapter on port 5060 going to a static IP I have assign to my ATA. Would I be correct on this?

Thanks

HELLFIRE

join:2009-11-25
kudos:7

That only sets up a static NAT translation, it doesn't really "open up a port" per se.

Post up your config; but if this is not working, the first thing I'd check is whether you have any ACLs,
especially if you have anything applied to the ISP-facing interface.

Another option is use an online port scanner to check.

Regards


mbruno

join:2003-07-03
Fruitland, MD

I am currently at work but will post when I get home.



TomS_
Git-r-done
Premium,MVM
join:2002-07-19
London, UK
kudos:4

reply to mbruno
You shouldnt need to forward any ports for this to work.

If your VoIP provider is any good, then as soon as your ATA registers with them and your router has an established NAT session, their SBC should try to maintain that session by sending periodic "keepalives." By maintaining the session they are able to send calls to you.

By forwarding a port youre actually opening yourself up to attack. If the ATA has a flaw, someone could start routing calls through you.



battleop

join:2005-09-28
00000

reply to mbruno
You should not have to do any forwards to begin with.


mbruno

join:2003-07-03
Fruitland, MD

reply to TomS_
when I arrived home last night I removed my static routes I had put in and it worked. It appears that the webpage for the VOIP provider has two spots for a password. one for the main account and one for the SIP password. For some reason I had a password set in the SIP password field.

The weird thing is I never set a SIP password. When you setup an account, the main password becomes your SIP password if you didn't create custom SIP password. This would explain why I could not get connected.

It took me three hours to figure this out even with the help of support. I finally stumble upon this after looking at every setting. Other then using the wrong password I was not aware of, setting up an ATA was quite simple and straight forward. Now I need to work on the call plan settings and fix the delayed ring.


Monday, 20-May 13:36:27 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics