VSP Registration
 

Hi Martin
I'm having a problem with one of my vsp registrations.
I have a number of services listed, of which four have Registration enabled.
Two of these services are from MNF and these register OK and call handling is correct.

I also have a third MNF account which is giving problems.
If I try to register it, the status goes to Pending, then Auth Sent, then Fail.
If I then disable the Register setting, the status remains as Fail.
This is the state it is in now.

I have talked to MNF who say everything seems to be OK at their end.

Is it possible for you to have a look at it from your end to see what the status is from your perspective please?

My Voxalot ID is 596620

Thanks in advance for any help on this.

Auth Sent -> Fail is an authentication issue. You need to double check the provider credentials.

Set the SIP Register back to "Yes" and Save. It should go into "Pending" status and after 10 mins or so the status should change.
.

Martin
Thanks for the reply.
There are two separate issues at play here.
The first is that the status shows as Fail, even though there is no setting in place to try to Register the service. It should simply show a '-' character, but it shows 'Fail'.

The second issue is that when I try to register, it fails. (I have double checked the credentials and I can successfully register with them from an ATA) However I don't want to pursue this issue until I can understand why the first issue exists.

There seems to be something 'sticky' in the Voxalot side of things that makes it think there is a fail condition even though there is no request for registration.

I have deleted and re-created the entry in an attempt to clear the problem, but to no effect.

Is there any way you can look at what is happening from your end that makes the status show as Fail please?

Is it possible that there is another Voxalot account trying to register the service for example?

Thanks again for your help.

Just checked all the servers and you can rest assured that there are no registrations within the telephony system. It looks like the web portal has a zombie status (sometimes caused during server synchronisation). These zombie statuses get cleaned up by a house keeping job that runs every 24 hours. The AU server job is scheduled to run at approx 4:30am AEST. You can force it yourself by doing a quick "SIP Register"="No" -> Save -> "SIP Register"="Yes" -> Save and wait for 10 mins or so.

Don't know what else to tell you here as this is what an Auth Sent error indicates. Is it possible the credentials were entered incorrectly?

OK Thanks.
I'll let the overnight process run and see what it looks like in the morning.

Hi Martin
The Failed status still remains after the overnight process.
Any thoughts?

Hi Martin

11:50 am
OK I see the Failed status has now cleared (sometime between 7am and now)
I'll try registering the service again.

12:50
So I've now successfully got the service to register.

Next problem: call forwarding

I have three MNF accounts being registered from Voxalot, and three ATAs (all the same - Billion 7402VGP) registered to Voxalot, and I want to forward the calls appropriately to each ATA.
So I have set up three call forwarding rules - each looks for incoming calls on the respective MNF account, and forwards to the appropriate SIP URI of each ATA. I have used the URI corresponding to the Voxalot registration on each ATA.

The problem is only one of the three will successfully forward the calls. The other two go straight to MNF Voicemail.
I have checked that the MNF accounts are set up identically with regard to voicemail.
I have tried calling from MNF and non-MNF accounts with same outcome.

Any thoughts or suggestions please?

Martin
Can you see any difference at your end between the way the three MNF accounts are registering with MNF please?

I just looked at the call records and see calls being forwarded to the respective SIP URI's for 2 out of the 3.

Are you sure the SIP URI's can receive an inbound on the dyndns targets you have defined as this might explain why MNF voicemail is kicking in.

I don't see any records for calls routing to r*****n.dyndns.org if that helps.
.

I just made a test call to each of the three.

The first was to t....t@dyndns and it rang OK
The second was to ro...n@dyndns and it went to voicemail
The third was to rb...g@dyndns and it rang and was answered (somewhat to my surprise) however the audio quality was pretty ordinary.

Do you see calls these OK at your end?

So it seems that the dyndns addresses are being resolved OK.

It also appears that the third one (rb...g@dyndns) is now ringing OK where it went to voicemail earlier.

Interestingly, the problem child is the same account that was having registration problems earlier ( the one forwarding to ro...n@dyndns).

Thanks again for your time on this. Sorry to be a nuisance.