Linksys WAG310G Connection Issues

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Linksys WAG310G Connection Issues

k14

631 posts

Ultimate Geek
+1 received by user: 94

#94941 22-Dec-2011 15:50

Well, this is starting to become just a little frustrating. I got transferred over from World Exchange to Slingshot yesterday. I went to change my username/password to the new ones and it wasn't working at first so on the advice of tech support I did a factory reset of the router. I think that is possibly what is causing all the issues.

Does anyone have experience setting up a WAG310G from scratch? I have been on the phone to tech support for the best part of 2 hours today trying to get the modem to connect. At the moment I have gone back to my old trusty Alcatel Speedtouch Pro and it is working nicely (however no VOIP or wireless). It has the most basic gui ever so all I need to do is type in username/password and it was away laughing. The Linksys has so many options and I have to change quite a few of the default settings but to no avail. I have followed the guides on the Linksys support website and tried their tech support but after they said I had to pay $47.99 to get help I told them to get stuffed (maybe in slightly different words...).

Standard process for me to setup a new connection is with the following changes to the default profile:
- Encapsulation - PPPoA (RFC2364)
- Multiplexing - VCMUX
- VPI - 0
- VCI - 100
- Modulation - Multimode
All other settings standard (and of course enter my slingshot username/password which is currently working on my old modem).

I have tried moving the modem physically to another phone port but didn't make a difference. The DSL light is always solid and connected, the Internet light is just flashing. It seems that the modem just isn't getting through to the exchange/slingshots servers ever since the factory reset. In the back of my mind I have an inkling that when I setup the modem in the first place that Worldexchange talked me through the setup (this is over 2 years ago now) and there was some trick that you had to do to reboot it at some stage or something like that. Can't remember it was so long ago.

So has anyone experienced the same thing?

1 | 2 | 3 | 4 | 5 | 6

1004 posts

Uber Geek
+1 received by user: 59

Trusted

Slingshot

#560791 22-Dec-2011 19:17

Hi k14,

Looking at the settings you have posted here I can confirm they are all correct, there are a couple of optional ones we can also try changing, although I am unsure if they will actually make a difference (but hey, its worth a try!)

First of all, try doing another factory reset so we can start with a clean slate.

Heres a quick printscreen I've made as a guide.

Red indicates a required value. Without these the connection will not work.
Green is an optional value - but generally only helps in low speed issues.
Pink is another thing we can try as a last resort - changing this to G.DMT will force the modem into ADSL1 mode, which is sometimes useful for troubleshooting purposes.

Another thing worth checking, for the username field are you trying "username" or "username@slingshot.co.nz"?

-Shaun

www.slingshot.co.nz

www.twitter.com/SlingshotNZ

https://www.facebook.com/SlingshotNZ

k14

631 posts

Ultimate Geek
+1 received by user: 94

#560794 22-Dec-2011 19:33

Hi Shaun, thanks for the reply.

Man what a debarcle. I finally figured it out, the router was programmed by a muppet. I had everything set exactly as shown above, the trick is that you have to first just enter the PVC settings (no username or password) and then click the save box near the top. This sets up the PVC so that you can then enter your password and username using the basic view (the above screenshot is of the advanced view), then you click "Add Connection" and the username etc is stored correctly. So badly programmed and not logical at all. I'd be surprised if I am the first person to have this problem.

So now I just have to get VOIP going. I have a dial tone but can't call out. Will probably have a closer look tomorrow. When I call a number I just get a high pitched tone that sort of sounds like an engaged sound. I set the proxy to dud.italk.co.nz and my username/password to what the tech on the phone told me. It says that the line is registered on the network but not sure what else I need to change.

Slingshot

1004 posts

Uber Geek
+1 received by user: 59

Trusted

Slingshot

#560799 22-Dec-2011 20:00

Good to hear that's sorted :)

The high pitched sound you have described sounds like it could possibly be a codec issue.

Try having a look in the Voice tab on the configuration page. On the far right hand side of the window you should see an option for Admin View, click that, then it should give you a new tab for "Line 1".

Under "Line 1", close to the bottom of this page, there should be an option for "Preferred Codec". Try changing that to "G729a", and let me know if that helps :)

-Shaun

www.slingshot.co.nz

www.twitter.com/SlingshotNZ

https://www.facebook.com/SlingshotNZ

k14

631 posts

Ultimate Geek
+1 received by user: 94

#560808 22-Dec-2011 20:34

I tried changing the codec, still same thing. I originally had the codec as G711U, which is what the guy at your helpdesk told me to do.

Do I have the proxy and username etc set up correctly?

Edit: Realised I didn't put right screenshot in. Try this one.

gkjones

24 posts

Geek

#563269 31-Dec-2011 15:30

Did you get this working in the end? I have a few settings that are different than yours. notably no AUTHO required.

k14

631 posts

Ultimate Geek
+1 received by user: 94

#563286 31-Dec-2011 16:45

gkjones: Did you get this working in the end? I have a few settings that are different than yours. notably no AUTHO required.

Yeah I managed to get internet to work finally, after many hours of trying. Although I am still unable to get VOIP working. You don't happen to use iTalk with slingshot do you?

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

gkjones

24 posts

Geek

#563324 31-Dec-2011 18:20

yes i do and i think it will be a pretty simple operation to get it to go.
1) have you in your router s/w set up 2 ports to trigger ( port triggering )

gkjones

24 posts

Geek

#563326 31-Dec-2011 18:26

Do this for me please. goto speedtest.net and run a test to a US site. Anything on the west coast is fine. Tell me what the latency figure says please. THis is real important for voip rather than the actual speed of your connection. If you have a good latemcy < 150 m/s then you can just use my setting swith your ISP details for login and p/w etc.

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#563388 1-Jan-2012 02:01

gkjones: Do this for me please. goto speedtest.net and run a test to a US site. Anything on the west coast is fine. Tell me what the latency figure says please. THis is real important for voip rather than the actual speed of your connection. If you have a good latemcy < 150 m/s then you can just use my setting swith your ISP details for login and p/w etc.

Latency to the USA has absolutely nothing at all to do with iTalk not working on this device - regardless if it was 10ms or 10000ms. The iTalk servers are in Auckland, not the US.

gkjones

24 posts

Geek

#563407 1-Jan-2012 09:05

You haven't answered the question of port triggering. The latency question has nothing to do with getting VoIP working it's to do with getting the call quality once you have outbound connection. Work with me please and you will soon have a good VoIP.

k14

631 posts

Ultimate Geek
+1 received by user: 94

#563413 1-Jan-2012 09:48

gkjones: yes i do and i think it will be a pretty simple operation to get it to go.
1) have you in your router s/w set up 2 ports to trigger ( port triggering )

No I don't have any ports forwarded. Which ports do I need to open? I just assumed that since the router and ata are all in one there would be an embedded port for the voip to use.

I did the speedtest and my ping to a server in San Francisco is 222ms and one in LA was 214ms. Pretty crap but I am unsure how this effects local calling??

Lego

Shop now for Lego sets and other gifts (affiliate link).

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#563421 1-Jan-2012 10:13

k14:
gkjones: yes i do and i think it will be a pretty simple operation to get it to go.
1) have you in your router s/w set up 2 ports to trigger ( port triggering )

No I don't have any ports forwarded. Which ports do I need to open? I just assumed that since the router and ata are all in one there would be an embedded port for the voip to use.

I did the speedtest and my ping to a server in San Francisco is 222ms and one in LA was 214ms. Pretty crap but I am unsure how this effects local calling??

You may need some port forwarding for iTalk to work, since in effect the ATA is behind the firewall.

You really need to ask Slingshot/iTalk for help, but I know they provide very little, if any, support for iTalk and offer no auto provisioning of devices for the correct settings. In effect you're getting the service you pay for..

k14

631 posts

Ultimate Geek
+1 received by user: 94

#563425 1-Jan-2012 10:32

sbiddle:
k14:
gkjones: yes i do and i think it will be a pretty simple operation to get it to go.
1) have you in your router s/w set up 2 ports to trigger ( port triggering )

No I don't have any ports forwarded. Which ports do I need to open? I just assumed that since the router and ata are all in one there would be an embedded port for the voip to use.

I did the speedtest and my ping to a server in San Francisco is 222ms and one in LA was 214ms. Pretty crap but I am unsure how this effects local calling??

You may need some port forwarding for iTalk to work, since in effect the ATA is behind the firewall.

You really need to ask Slingshot/iTalk for help, but I know they provide very little, if any, support for iTalk and offer no auto provisioning of devices for the correct settings. In effect you're getting the service you pay for..

Ok. It seems that port 5060 is the standard VOIP port? But what IP do I use? I can't see any specific IP address for the phone that is connected to the router? Do I just use the IP of the router 192.168.1.1

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#563427 1-Jan-2012 10:34

Ahh forget that last post, with the Cisco/Linksys all in one units there is no need for port forwarding.

gkjones

24 posts

Geek

#563627 1-Jan-2012 23:41

Ypu need to give yourself a smack in the head. Read the post. Triggering triggering triggering. Nothing about forwarding. And that latency is crap so yes we will have to use different settings but that's down the track. The sip port 5060 is in the Ata and is correct but it's the actual port that the router must open when it receives a sinal from the Ata we need to set up. In the router configuration 192.168.1.1 if factory unchanged go to the advanced section on forwarding and triggering. You want to set up 2090 in both options. This is not in the Ata section it's the router. Now you might have a dial tone.

1 | 2 | 3 | 4 | 5 | 6