VSP broken?

[ptruman]

Hi

I use voip.co.uk for my VSP.
Today, it wasn't showing registered. So I reregistered it.

voip.co.uk now show a "userAgent" of Voxalot having registered, however they show the registering ID as :

sip:XXXXXX9479@85.17.19.194:5061

Where did this 9479 come from?! The IP is correct, but the 9479 after my 6 digit Voxalot IP? I can't call out currently - which is a right pain as all my voice calls go via voip.co.uk!

Can we have some logging on voxalot.com to show what numbers we've dialled? At least I can see if Voxalot had received my dialstring and sent it to voip.co.uk ok....

Inbound calls to my voip.co.uk DID are working at least (bizarre, given the 9479 suffix?) but outbound calls are not. And I would have thought if Voxalot is sending acct auth details with the outgoing request, it should work regardless of registration...

[martin]

sip:XXXXXX9479@85.17.19.194:5061

This looks correct. The combined number (XXXXXX9479) is an internal representation that the Voxalot system uses.

This is not what's causing your call out problem. Are other providers within Voxalot working ok for you?

[ptruman]

I only have one VSP.

Having some call records would be good - along with possibly being able to see the SIP logs so we can see if the VSP provides an error or not...

Meanwhile, check out VoIP.co.uk :: Platform Status - they claim their upgrade now requires all SIP agents to use SRV - if they don't, they get unregistered. Does Voxalot support SRV?

[ptruman]

Bump

(FYI Voxalots page is now not showing me registered with voip.co.uk, and voip.co.uk don't show any connected/registered devices either...)

Voxalots VSP page now shows "Auth Sent" on the registration status page - nothing else...