SPA2102 basic connection

Forums › VoIP › SPA2102 basic connection

helicrew

77 posts

Master Geek

#90583 24-Sep-2011 16:55

Hi all,

Excuse the newb questions. I'm just setting out in VOIP - it's a steep learning curve. I have purchased an SPA2101 and set up a 2Talk account to 'play' with.

I want to connect the SPA2102 into my existing wireless router. Can I just confirm that;

I need to plug the Internet port of the SPA2102 into my wireless router using a cross-over cable?
I should set the Internet IP address to my home IP range i.e 192.168.1.x then set up port forwarding from the WRT54 router/firewall for VOIP ports to that IP.
I need to plug the Ethernet port of the SPA2102 also into my router to access the admin pages??? I've set the local IP address via the web page to my home IP range - still working on getting that connection working.

Many thanks
Colin

vinnieg

2260 posts

Uber Geek

Trusted

#525371 24-Sep-2011 17:02

Hi:

I need to plug the Internet port of the SPA2102 into my wireless router using a cross-over cable?

- No, just a standard patch cable will work, to configure it first you can plug it in via patch cable to your PC or your router and it should show up

I should set the Internet IP address to my home IP range i.e 192.168.1.x then set up port forwarding from the WRT54 router/firewall for VOIP ports to that IP.

That's right, set up the Internet side to 192.168.1.2 and put that in your DMZ of your router, turn off any SIP on the WRT54 too as it'll interfere. Try and set your router to keep the MAC address of your Voip at 192.168.1.2 so no other devices try to steal the port

I need to plug the Ethernet port of the SPA2102 also into my router to access the admin pages??? I've set the local IP address via the web page to my home IP range - still working on getting that connection working.

That is correct, easiest way is to first plug it into your laptop/PC, using a patch cable on the ethernet side, then change the LAN settings to Bridge. Also make sure on the WAN side Enable Web Server is set to YES. Then remove it from your PC and put it back on the router through the internet port. You can now access it from any other device connected to the network.

I've got a SPA2102 here, but my router has SIP enabled by default(TPLink), which unfortunatley I have to disable each time I restart my router. It only takes a few seconds through telnet, but it's still a pain. the WRT54 should have a setting in the browser luckily.

I think TPLink are working on getting a SIP setting in there browser soon, but not soon enough for me. I've just ordered a SRP527W to replace both the TPLink and SPA2102

I have moved across the ditch. Now residing in Melbourne as a VOIP/Video Technical Trainer/Engineer.

Mighty Ape

Shop Mighty Ape for electronics, games, computers books and more (affiliate link).

helicrew

77 posts

Master Geek

#525379 24-Sep-2011 17:37

Thanks for that. I've at least got it connected to the home network and I can see the admin web pages.

For whatever reason it does need the crossover cable when connected to WRT54G router/firewall before I can get to it.

I've just set up the provisioning to grab the "sbiddle" config files. next I'll figure out where to put the 2talk settings.

Progress is being made, thanks again.

helicrew

77 posts

Master Geek

#525507 25-Sep-2011 09:41

Not having a lot of "luck" here. This SPA2102 is one of the most difficult beasts I have ever dealt with

(don't ask how many times I've had to reset the darned thing via the phone!)

I set up the provisioning page as per the sbiddle instructions (the screen looks identical) but overnight it's done nothing at all that I can tell.
I've just had a look at the WAN setup page and realised that there were no dns servers set, I think I stupidly assumed that it would get picked up from the gateway setting.

So now with dns servers in there I'm hoping it will all come right. Is there anything else that I may not have thought of that's a trap for young players??

Cheers all

Colin.

vinnieg

2260 posts

Uber Geek

Trusted

#525530 25-Sep-2011 12:30

helicrew: Not having a lot of "luck" here. This SPA2102 is one of the most difficult beasts I have ever dealt with (don't ask how many times I've had to reset the darned thing via the phone!)

I set up the provisioning page as per the sbiddle instructions (the screen looks identical) but overnight it's done nothing at all that I can tell.
I've just had a look at the WAN setup page and realised that there were no dns servers set, I think I stupidly assumed that it would get picked up from the gateway setting. So now with dns servers in there I'm hoping it will all come right. Is there anything else that I may not have thought of that's a trap for young players??

Cheers all

Colin.

Totally agree there, I had a lot of issues with mine too

Yeah for teh WAN setup, put in 192.168.1.2
DNS use your ISP DNS and Gateway set to 192.168.1.1

Turn of QoS on your router, and for ports I use(all only on 192.168.1.2)
5060-5080 UDP
10000-11000 UDP
16384-32767 UDP

Do you get a dialtone or signal at all?

Also make sure you put upload speed at 1000-1200kbps, if it stays at 128 your internet will slow down. Even if it's plugged into the secondary router port and not your switch!

As above, I returned mine, mostly due to the annoying double NAT issue and slightly lower internet speeds. Oh and my SIP on SIP issue. Where every reboot my router turns SIP back on.

I have moved across the ditch. Now residing in Melbourne as a VOIP/Video Technical Trainer/Engineer.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#525541 25-Sep-2011 13:00

helicrew: Not having a lot of "luck" here. This SPA2102 is one of the most difficult beasts I have ever dealt with (don't ask how many times I've had to reset the darned thing via the phone!)

I set up the provisioning page as per the sbiddle instructions (the screen looks identical) but overnight it's done nothing at all that I can tell.
I've just had a look at the WAN setup page and realised that there were no dns servers set, I think I stupidly assumed that it would get picked up from the gateway setting. So now with dns servers in there I'm hoping it will all come right. Is there anything else that I may not have thought of that's a trap for young players??

Cheers all

Colin.

I'm not quite sure what steps you have taken but these devices are incredibly simply to configure.

If your SPA2102 is set up for DHCP it'll retrieve it's IP address and DNS settings from your router. If you have manually entered a static IP you'll also need to load in the DNS servers and gateway IP.

Also change the device to allow web access from the WAN port. You can now also safely change the networking mode to bridge rather than leaving it as NAT

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#525544 25-Sep-2011 13:05

vinnieg: Yeah for teh WAN setup, put in 192.168.1.2
DNS use your ISP DNS and Gateway set to 192.168.1.1

Turn of QoS on your router, and for ports I use(all only on 192.168.1.2)
5060-5080 UDP
10000-11000 UDP
16384-32767 UDP

Do you get a dialtone or signal at all?

Also make sure you put upload speed at 1000-1200kbps, if it stays at 128 your internet will slow down. Even if it's plugged into the secondary router port and not your switch!

As above, I returned mine, mostly due to the annoying double NAT issue and slightly lower internet speeds. Oh and my SIP on SIP issue. Where every reboot my router turns SIP back on.

These IP details will only be correct if the OP has a router that uses the 192.168.1.0/24 range and 192.168.1.1 as the router.

Double NAT is a totally avoidable situation, I can't comment on how you configured your network but it sounds like you created an overly complex setup for yourself if you're even playing with the QoS settings. You shouldn't ever use double NAT, and obviously reaslised the trouble it causes.

I've also never ever used port forwarding for an SPA, if configured correctly there is no need. Exposing port 5060 to the world also exposes you to security risks and issues with SIP attacks on your device, especially since you can't enable "restrict source IP" on 2talk. Bots out there port scanning the internet for insecure SIP proxies can result in your phone randomly ringing as inbound SIP URI traffic hits your device.

vinnieg

2260 posts

Uber Geek

Trusted

#525562 25-Sep-2011 15:26

sbiddle:

These IP details will only be correct if the OP has a router that uses the 192.168.1.0/24 range and 192.168.1.1 as the router.
That's true, which he mentions in the first post. Although I was automatically assuming since he used the 192.168.1.0/24 range, that he'd use .1 as his router, I could have been wrong
- "I should set the Internet IP address to my home IP range i.e 192.168.1.x then set up port forwarding from the WRT54 router/firewall for VOIP ports to that IP."

Double NAT is a totally avoidable situation, I can't comment on how you configured your network but it sounds like you created an overly complex setup for yourself if you're even playing with the QoS settings. You shouldn't ever use double NAT, and obviously reaslised the trouble it causes.

Yeah my bad, I think I did make it more complicated in my initial setup. Basically because TPLink automatically puts their SIP ALG on, without having anything in the web setup to turn it off, apart from temporarily turning it off through telnet. So that initially led me to believe that the ports were being blocked. Thanks for telling me that, I've now turned my port forwarding off and it still works :)
Just wish I didn't have to do the telnet commands every time the router is rebooted to be able to answer incoming calls :(

I have moved across the ditch. Now residing in Melbourne as a VOIP/Video Technical Trainer/Engineer.

helicrew

77 posts

Master Geek

#525571 25-Sep-2011 16:36

All up and running, thanks for the hints. I've left it inside the network (not out in the DMZ) and haven't had to open any firewall ports. The dns fixed the provisioning problem (doh!). I'll have a play with it for a while before attempting the dreaded number porting. I may move to VFX before I do that, but 2Talk will make a good place to learn a bit more about the whole voip thing.

AKT

333 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#526444 27-Sep-2011 20:20

IF you want an entirely painfree setup use VFX - plug in to the router and VFX set it up for you. Just one line to alter once. been running flawlessly for 10 months now.

A