gkjones: yea its the iphone..why didn;t you say..hahahaha...i bloody wish. Na i got 3 of those and they are simple to set up. The ipad on Viber was a tad more challenging but they are a piece of piss c/w voip. I duno man..were all trying our best at brain storming this. The pc is the brain and in many cases the router goes to it for configuring. If the brain says " na i don't know that then the router just wont do it. " Plenty of times i have seen router settings enabled but then find out either an extrenal device does not support that setting or worse the device controlling it has disabled a setting. Think Auto dhcp and how easy it is to totally mess with a system by turning this off in services in windows. Now i anin got an xbox but apparently they use Pnp so suposidly its just plug it in and away it goes. yea right....anyway theses way more cleverer Voip people on the forum than me like maverick who are way more able to help with devices i have not got. Sorry to put you crook earlier.

Anything connected to the router has no bearing on this problem, the VOIP side of things is just part of the WAG310G so the issue resides solely with the router alone. As I said before, I have compared settings between a fully working WRP400 and the WAG310G and they are, as much as possible, exactly the same. The only differences are the omission of some settings in the WAG310G.

Looking closely at the debug syslog it looks like each time the router registers it fails first time but then repeats the registration immediately and the second attempt works. Quite why this happens seems strange but it repeats every time and I don't understand why it should fail on one attempt and then pass immediately afterwards. Can you get a syslog debug trace of what is happening with your router to compare?

gkjones: Best ask maverick. i have not got a wag310g. I have cpa2102 and pap2t both linkysys and a tp wr1043nd router and a netgear router.

OK, but the WAG310G should do the job of all of them so you should only need the one router to provide ADSL2+ and VOIP (which is the issue we are talking about. Agreed, if I turn off the VOIP on my WAG310G and connect a VOIP configured WRP400 to it I get voice working fine.

Yes you would think so. There was quite a wealth of information on lynksys wag310G FAQ thats worth trolling through but in saying that maverick seemed to know what the issue was ...Sip and router config. Its nothing really basic like one of the devices not having the latest firmware or something really madengly stupid like that.

The reason it will fail first time is that the invite will not contain the auth details, so when you send the invite without it the SIP server will respond with an unauthorized you should then send the invite with the authid and password, ask said this is slingshots issue and should be helping you, my quess will be that you do not have authid set , try that and set it to use authid.

Actually should really move this to slingshot page as they now seem all of a sudden to be a bit active here, but again not really sure of their level of expertise around SIP and what they can see but from what I saw from the debugs this is pretty simple and basic stuff which they should capable of sorting,

And this whole thread shows the benefits of providers like WxC who offer full auto provisioning of devices - the end user needs to know nothing and gets all the benefits of a full PLV solution that just works.

maverick: The reason it will fail first time is that the invite will not contain the auth details, so when you send the invite without it the SIP server will respond with an unauthorized you should then send the invite with the authid and password, ask said this is slingshots issue and should be helping you, my quess will be that you do not have authid set , try that and set it to use authid.

Actually should really move this to slingshot page as they now seem all of a sudden to be a bit active here, but again not really sure of their level of expertise around SIP and what they can see but from what I saw from the debugs this is pretty simple and basic stuff which they should capable of sorting,

Looking at the help section on Slingshot's X-Lite iTalk setup page it looks like the Auth ID should be set to the same as the User ID. I tried that, checked the Info page to make sure it showed Registered, but it still fails in exactly the same way. I still think this is a firmware issue as I don't have to set Auth ID to make my WRP400 work.

From what I can gather this router was never available retail only through X-Net and has specific firmware. Many thanks for your help with this maverick and I appreciate that it's a Slingshot problem. Think I'll give up and go back to my Cisco 877W + WRP400, this is as much fun as kicking a dead whale up a beach.

maverick: The reason it will fail first time is that the invite will not contain the auth details, so when you send the invite without it the SIP server will respond with an unauthorized you should then send the invite with the authid and password, ask said this is slingshots issue and should be helping you, my quess will be that you do not have authid set , try that and set it to use authid.

Actually should really move this to slingshot page as they now seem all of a sudden to be a bit active here, but again not really sure of their level of expertise around SIP and what they can see but from what I saw from the debugs this is pretty simple and basic stuff which they should capable of sorting,

Looking at the help section on Slingshot's X-Lite iTalk setup page it looks like the Auth ID should be set to the same as the User ID. I tried that, checked the Info page to make sure it showed Registered, but it still fails in exactly the same way. I still think this is a firmware issue as I don't have to set Auth ID to make my WRP400 work.

From what I can gather this router was never available retail only through X-Net and has specific firmware. Many thanks for your help with this maverick and I appreciate that it's a Slingshot problem. Think I'll give up and go back to my Cisco 877W + WRP400, this is as much fun as kicking a dead whale up a beach.

AuthID is only needed if the SIP proxy requires it. The vast majority of VoIP providers don't use AuthID, they just use the SIP username and password. As an added layer of security many providers now use AuthID as well, which to actually be secure shouldn't actually be the same as the SIP UserID.

sbiddle: And this whole thread shows the benefits of providers like WxC who offer full auto provisioning of devices - the end user needs to know nothing and gets all the benefits of a full PLV solution that just works.

Yeah that is a fair call but it isn't worth the extra $30-40 a month. For $400 a year I am happy to be without a landline for a while until I sort this out. But I guess it depends on the person. I use the landline about once a week so it is no inconvenience for me.

sar10538: From what I can gather this router was never available retail only through X-Net and has specific firmware. Many thanks for your help with this maverick and I appreciate that it's a Slingshot problem. Think I'll give up and go back to my Cisco 877W + WRP400, this is as much fun as kicking a dead whale up a beach.

I bought mine from Ascent and I am sure there are other people using it with VOIP providers other than WxC. I might try the suggesting from GKJones of setting up a free 2talk account, letting the auto provision go through and then change the username/proxy etc.

sbiddle: And this whole thread shows the benefits of providers like WxC who offer full auto provisioning of devices - the end user needs to know nothing and gets all the benefits of a full PLV solution that just works.

Yeah that is a fair call but it isn't worth the extra $30-40 a month. For $400 a year I am happy to be without a landline for a while until I sort this out. But I guess it depends on the person. I use the landline about once a week so it is no inconvenience for me.

My comment was nothing to do with landlines - it was the fact if you go with a provider that offers a fully autumated and managed provisoning system then issues such as this thread wouldn't exist.

If people are using VoIP as a PLV solution it shouldn't be something that works most of the time, it should be a robust solution that works all the time, and works properly. End users also shouldn't have to need to understand details of how SIP works just to get a dialtone.

hey we may be dealing with this after the horse has bolted but Xnet (world exchange ) offers a totally locked down solution provided by them and unless you are able to totally reset that router/ata whatever h/w then thats why its never going to go. Can we assume you have reset this devise and d/l the latest firmware?

gkjones: hey we may be dealing with this after the horse has bolted but Xnet (world exchange ) offers a totally locked down solution provided by them and unless you are able to totally reset that router/ata whatever h/w then thats why its never going to go. Can we assume you have reset this devise and d/l the latest firmware?

I looked on the Linksys website a few weeks ago and it seems as though there is only 1 version of firmware ever released for this router.