voip.co.uk registration problems
 

voip.co.uk appear to have had a few problems with their servers this week. However a few people on the uk.telecom NG concurred with my experience (on one sip account) that re-booting my ATA does the job. This is certainly what they have advised.

With Voxalot of course "re-booting the ATA" is a bit harder, and despite cycling the sip registration status in the provider set-up, the accounts I use through Voxalot are stubbornly refusing to register.

Anybody have any other ideas? I know there was some unexpected outage of Voxalot sip servers but I am not aware this should still be an issue...

Any ideas anyone???

Your best bet for a full reset is to remove voip.co.uk completely, wait 1-2 hours, then re-add it.

That should be enough time to clear the registration on the VoXalot server.

Hopefully that'll do the trick....

Thanks for the tip. I began to realise yesterday that it is not picking up changes for about half an hour or so.

Anyway, I did try to wait for an extended period. I noticed that if you changed the SIP registration to No, it would go to "pending" in the registration status. I waited till this disappeared and set the SIP registration back to Yes. I am still not registered.

I guess I need to speak to voip.co.uk to get them to look at it from their end, as I don't believe cycling SIP registration is doing the trick. Any ideas though from anybody why it works OK on an ATA now but not Voxalot?

Response back from voip.co.uk:

It sounds like Voxalot don't check their DNS records very often.
You should connect only to proxy.voip.co.uk and not registrar.voip.co.uk or
proxy.sov.voip.co.uk.

p.s. (edit): proxy.sov.voip.co.uk was a server recommended in uk.telecom newsgroup which seemed to solve the issue with Voxalot, but is not their recommended solution as you can see.

Voxalot checks the DNS records as dictated by the expires time set by the domain owner. In other words, it stays in the DNS cache for as long as they tell us it should before being refreshed.

I'm having the same problem, works for a short while and then fails for some reason.

See my thread, "VSP problem", for this.

They have switched infrastructure over the weekend, and were (for some reason) mostly rejecting anything now not using DNS SRV, and referring anyone back to their ATA manufacturer for SRV support.

I CAN ring the 121 answerphone, but can't connect anything else. Voxalot does not show me registered.

VoIP.co.uk :: Platform Status shows an update on the possible problems, but it's bl**dy annoying as it's my only VSP which does all my PSTN routing (yes I can drop back to POTS but it's a PITA!)

I am now (this morning) showing "Online/SBC" with Proxy/SRV on the voip.co.uk status page - but my Voxalot page just shows "-" for the registration status.

I'm at work, so can't test the thing easily until later.

Ok DNS problem has gone but still having problems with registration. Although these problems appear to be the same with all their customers, they are saying that most of the time it is due to buggy clients not being able to handle SRV correctly.

Is there any chance someone from Voxalot could look at some of these registration issues. It doesn't help that a lot of the time, Voxalot does not believe the account has registered, whereas the voip.co.uk status page is saying it is...

All help greatfully appreciated.

BTW thanks for looking at the call forwarding via Beta max issue. It was trying to test this that made me realise the accounts were unregistered again!

Please see:

http://forum.voxalot.com/voxalot-sup...r-problem.html

I've been on vacation for a week, and it's still dead.
Have just tried to disable/enable the VSP acct to see what happens.

121 (their voicemail) DOES connect, but asks me for my mailbox number, (which implies no registration?) but outgoing calls fail - does Voxalot not pass creds along with each outgoing call? (which should work regardless of registration - which should only be needed for incoming calls?)

If the VSP challenges for credentials on an outbound call, then yes, they will be passed.

Voicemail has started asking for mailbox number (followed by #) since the upgrades. It is not linked to the other registration issues.

voip.co.uk via Voxalot is now working for me (although Voxalot does not show it being registered). You may need to set all voip.co.uk accounts not to register on Voxalot (SIP register = NO) and wait a couple of hours to set it back to ON. This is the only reliable way doing the equivalent of a reboot.

By the way, I think the reason accounts do not show as registered on Voxalot is probably something to do with the SIP expiry time of voip.co.uk (2 minutes) and the fact that Voxalot status is not real-time (generally 5-10 minutes out of sync).

The reason it does not show up as registered is because the provider changes the port from 5060 to some other value during registration.

So when our system tries to reconcile the status information it does not match.

We have an item in our problem tracking system to look at alternate ways to perform this reconciliation.

I'm afraid i can't wok out what your problem is from the brief description you gave ...

Our platform responds to REGISTERs exactly as defined in RFC 3261 - or at least should! If you have any problems then feel free to email me directly (theo@voip.co.uk) and we can work out any interop issues.

PS: a quick trace shows nothing wrong other than the fact your client is showing the same pathologically broken symptoms asterisk exhibits (see the notes about asterisk & SRV on products:asterisk [wiki.VoIP.co.uk]

REGISTER sip:proxy.voip.co.uk:6060 SIP/2.0
[snip]
Contact: <sip:XXXXXX@85.17.19.194:5061>

SIP/2.0 200 OK
[snip]
Contact: <sip:XXXXXX@85.17.19.194:5061>;expires=120
Content-Length: 0

Erm :

voip.co.uk say id you don't use SRV, it should be ok - what does Voxalot do?

"Yes this is the correct address. However if you use proxy.voip.co.uk
'without' SRVs it will fall back to standard DNS name resolution and
will not try and use the load balancing. This could resolve the
registration issues is the device(s) that are trying to connect (inc
voxalot) are having trouble maintaining registrations as there is only
one point to register to."

Also, please see VoIP.co.uk Customer Support Forum :: Service Support :: Never thought I would say this but

Given I now can't even reg to eu.voxalot.com I am not having much fun...