Geographic lookup problem
 

I know there were some issues with this recently that evilbunny & Martin fixed but something is still not working?

I have called a few 13 numbers (132058 & 132265) yesterday & today, they are in the e164 system, & when I try the test dial plan option in Voxalot with my dial plan it correctly finds the alternative (local) number to call.
I go into my MyNetFone call records & the call registers to the 13 number & a .25c fee?

ozimarco could not see an issue with my dial plan, any ideas from anyone else?

Yes, something weird is going on here.

I've tested on my system and can confirm that, although 132058 translates correctly into the 02 number in the test box and Voxalot shows me via which VSP it will send the call, when the number is actually dialled, it is sent as a 13 number via the provider assigned to handle 13 number calls.

Sorry for the delay guys. Seems the TEL: records (e164 Geo records) in the DNS no longer have a leading + which is why these calls were failing.

We have since patched the telephony engine and calls should now be working.

Please confirm if this is the case.

Thanks

Yup, it's working for me. :)

Thanks, Martin.

Yep working now for myself as well, thank-you:)

This same issue seems to be happening for me at the moment.
The TEL: records seem to contain the leading + again.

I am also having similar symptoms with UK NG numbers. Test works OK but the dial plan rule ignores the NG lookup and tries to dial using the provider on the dial plan entry.

I am having the same problem here. I have just set up the ngn lookup and can not get it to work. The Test Call shows the correct local number being returned and routed to the correct VSP. However when I check my call records it shows that the 6113xx number was used.

ping Martin / Evilbunny
 

Any news on this, as it does still appear to be a problem...

I announced that we (e164.org) were intending to make changes to Martin a while back, but he never returned any of my calls or messages. However the + is no doubt messing VoXaLoT up as they probably weren't expecting it, but it should have always been there to be compliant with RFCs.

We have spent a bit of time of late trying to fix up our systems to make sure we comply 100% with RFCs in doing so we are making sure we didn't lack anything in records or overlook them in the past.

I'm sorry if this has cause inconvenience for anyone, but we're trying to do our part to follow relevant standards as close to 100% as we possibly can.

For future reference, if there is a better contact for this kind of thing at VoXaLoT than Martin please let us (support at e164) know so we can address all future correspondences to them instead.

Did not realise until this morning that this problem had surfaced again. A check of MNF call records reveals 13 #'s being charged .25c in lieu of a local call rate. The same as before in that the test dial routes the call to alternate # correctly??

Whatever Martin did before fixed it, but broke again....

Nothing on the Voxalot side has changed since the original fix.

I will do another check when I get home from work 2morrow but I have not altered any of my dial plans either. The test dial plan works but it is not working in reality..
This is the same thing that happened last time, & after your fix the 13 # calls routed correctly with the appropriate call charge refelected on my MNF records.

Using the test dial plan feature just now:

"132265 will get forwarded to 0386419083 via MyNetFone"

Logged into my MNF call records & sure enough the call went to 132265 & hence a .25c call charge.

Something is not right?

The only thing I can think of is that the e164.org records in the DNS may have changed. Maybe evilbunny can help shed some light on this?

Please see this post:

http://forum.voxalot.com/voxalot-sup...html#post16998

Correct me if I'm wrong but I think that:

• Initially e164.org was returning records with leading +
• During their initial reworking, the leading + was dropped for some reason, and this was then patched in Voxalot
• The leading + is back, but the patch in Voxalot was not removed

--> conclusion Voxalot patch needs to be reversed

Perhaps I am misunderstanding something here but this is certainly what I read into the various messages.

Martin any comment on this?

Can anyone confirm if this has been fixed?

Edit: I just checked and although it says that it'll call the local number it still dials the 13/1300 number.

Martin, Can you please look at evilbunny's post, http://forum.voxalot.com/voxalot-sup...html#post16998, and make any necessary fixes.

Thank you.

The + (plus) is fine we have always supported it. The reason it is no longer working is because the URI scheme stored on e164.org changed from TEL: (uppercase) to tel: (lowercase)

The lower case URI scheme appears to be the right one to use, however before we make the change we would like to know from e164.org that we will only be expected to support the lower case version.

Evilbunny, please advise?

Edit: We made the change to support tel: (lowercase), please advise if this has resolved your issues?

Thanks

Will check when I get home and update.

Edit:
I totally forgot to check this. Seems to be working fine now. Thanks!

It works again for me! Fantastic!

Thanks for the fix.

A thanks from me also, it is working again!!!

Works in UK too!

Many thanks!

As per my last message, the changes are so that we are RFC compliant. If anyone knows of anything we're doing that isn't RFC compliant please let me know so we can look at rectifying it.