Issues with incoming calls via SPA2102 and using 2talk

Forums › VoIP › Issues with incoming calls via SPA2102 and using 2talk

DragonSlayre

24 posts

Geek

#42814 11-Oct-2009 21:39

I've recently installed a SPA2102 at home for VoIP using 2talk.

I'm on telstra cable, so have quite a fast connection, and a static IP. I've got my normal phone connected to SPA2102, connected to my Linksys router via ethernet.

I set it all up with the instructions at http://blog.2talk.co.nz/spa2102.html - I managed to follow the instructions, apart from updating the firmware (I downloaded the firmware installer, but it wouldn't upload to the device!).

I've got no probs calling out, but I have had a few issues with people trying to call in and getting no tone whatsoever. I also just had a call from overseas, and the phone didn't ring, I just got a voicemail. Generally, calling my home phone from my cellphone works fine, but I know that people have tried calling from their home phone and gotten no tone. I've then tried calling from my cellphone, and also had no dial tone. When I then call my voicemail from home phone and hang up, I call my home from my cell and the phone rings.

The SPA2102 uses dhcp, and as such I haven't set up port forwarding. Is this something I should be doing?If so, what ports should I be forwarding?

Any ideas on what would make my phone more reliable would be really handy :)

hads

392 posts

Ultimate Geek

Trusted

#263408 12-Oct-2009 09:19

It does sound like a possible NAT issue. If you can try a different router that would confirm it.

nicegear.co.nz - VoIP, DVB and other Linux compatible hardware

dynamiccomputers

37 posts

Geek

#263495 12-Oct-2009 14:26

definitely try setting up port 5060/udp (SIP) inbound into the ATA. It sounds like your router may not be passing established connections through so you may need to open up the port.

DragonSlayre

24 posts

Geek

#263498 12-Oct-2009 14:37

Ok, I'll give that a go and let you know how it turns out. I gave my home phone a test today -ringing from a landline, I got an extremely short ringing tone, and then no tone. Will try the port forwarding.

DragonSlayre

24 posts

Geek

#263790 13-Oct-2009 23:07

I've setup my Linksys router to forward port 5060 to 192.168.1.11

I'm trying to figure out how I setup the spa2102 so that it doesn't use DHCP for getting assigned its IP address (which I want to be 192.168.1.11). The SPA2102 has WAN and LAN setup tabs, so I've tried to change the WAN settings, so that it has a static IP rather than using DHCP.

I've set the static IP to 192.168.1.11
The netmask to 255.255.255.0
The Gateway (my router address) which is 192.168.1.1

When I switch from DHCP to Static, I can no longer get a line out - so obviously it's not working.

Can anyone give me some tips on how to get the port forwarding working?

DragonSlayre

24 posts

Geek

#263956 14-Oct-2009 21:21

Ok , so I've noticed that When I assign the static IP (192.168.1.11) on the SPA2102 and enable the web server on it, then I can connect to the web interface via the network rather than connecting directly with it.

The problem is that calls in and out no longer work!

My setup currently looks like this:

Internet
---->Linksys router (local IP: 192.168.1.1) port fwd 5060 to 192.168.1.11
-----------> Linksys SPA2102 (192.168.1.11)
-------------------> Normal phone

I'm not sure why the phone calls aren't working..... I'm sure there's heaps of people here that are more clued up than what I am - any ideas?

DragonSlayre

24 posts

Geek

#263963 14-Oct-2009 22:01

Ok, i fixed the issue - I entered in the dns settings from my router into the SPA2102 settings, and calls are now working with a local static IP and port forwarding. Will just have to do some testing now to see if it's made a difference to the reliability of it all :)

mikerussellnz

283 posts

Ultimate Geek

#263964 14-Oct-2009 22:02

I had a similar issue with my Linksys PAP2T, it thought it was registered but sometimes wouldn't recieve calls, rebooting it fixed it although it would reoccur again. It seems the router was closing the incoming port that it was using to recieve incoming notifications.

I had to change the UDP timeout on my router from the default 120 seconds to 240 seconds. Also ensure sure you have NAT keepalive enabled on the voip adapter. My register expires on the adapter is set to 600 seconds.

I think NAT keepalive was what fixed it for me.