I can not call 800XXX

zaq · 01-23-2007, 10:48 AM

I had no luck calling to Voxalot number 800XXX, a dial plan test reveals the following:

A call to:800XXX will get forwarded to sip:800XXX@public.sip.magrathea.net

Replace XXX with any numbers, all my dial plans are not active.

What did I do wrong?

Thanks

martin · 01-23-2007, 11:20 AM

An ENUM lookup is kicking in. There must be a number in one of the roots that matches this number.

Try searching:

http://www.sipbroker.com/sipbroker/action/enumLookup

zaq · 01-23-2007, 11:42 AM

Quote:

Originally Posted by martin

An ENUM lookup is kicking in. There must be a number in one of the roots that matches this number.

Try searching:

http://www.sipbroker.com/sipbroker/action/enumLookup

Yes there were!
Can we have ENUM lookup off by default ? To me this makes more sense.

Thanks

Ron · 01-23-2007, 11:51 AM

Martin,

I think zaq has found a real problem. Dialing any 6-digit number of 800xxx gets a fast busy instead of either ringing, going to voicemail or getting a "your call cannot be connected" response. A test on the Dial Plan page shows these numbers will be forwarded (A call to:800123 will get forwarded to sip:800123@public.sip.magrathea.net). It may be an ENUM issue, but I don't think VoXaLot should be doing ENUM lookups on 6-digit numbers that are being treated as internal VoXaLot extensions.

Ron

martin · 01-23-2007, 12:03 PM

This is one of the reasons why we ammended the internal dialling convention.

Unfortunately we have no control of number ranges added to ENUM roots.

Ron · 01-23-2007, 12:17 PM

Quote:

Originally Posted by martin

This is one of the reasons why we ammended the internal dialling convention.

Unfortunately we have no control of number ranges added to ENUM roots.

I guess I don't understand. Why is it desirable to do ENUM lookups on internal (6-digit) VoXaLot numbers?

In the current state, all VoXaLot numbers from 800000 - 800999 are inaccessible. If that's always been the case and you're willing to continue this restriction, then I guess there's not a problem (at the moment). If VoXaLot numbers in this range used to work and have been assigned, then it's an issue.

Ron

martin · 01-23-2007, 12:34 PM

These numbers are accessible via *010800000-*010800999 from VoXaLot. The only reason we still support xxxxxx dialling is because some devices dont send leading *'s

Our recommendation is people use *010 infront of VoXaLot extensions.

zaq · 01-23-2007, 12:23 PM

Uhm it is a hard one, what we are saying all VSPs will face difficulties once they start supporting ENUM! Or may be ENUM is not mature enough? Or the whole VOIP thingy is not mature!

01-23-2007, 10:48 AM	#1
zaq Junior Member Join Date: Nov 2006 Posts: 15 Thanks: 0 Thanked 0 Times in 0 Posts	I can not call 800XXX I had no luck calling to Voxalot number 800XXX, a dial plan test reveals the following: A call to:800XXX will get forwarded to sip:800XXX@public.sip.magrathea.net Replace XXX with any numbers, all my dial plans are not active. What did I do wrong? Thanks

01-23-2007, 11:20 AM	#2
martin Join Date: Feb 2006 Posts: 2,930 Thanks: 528 Thanked 646 Times in 340 Posts	An ENUM lookup is kicking in. There must be a number in one of the roots that matches this number. Try searching: http://www.sipbroker.com/sipbroker/action/enumLookup __________________ Martin Please post support questions on the forum. Do not send PMs unless requested.

01-23-2007, 12:03 PM	#5
martin Join Date: Feb 2006 Posts: 2,930 Thanks: 528 Thanked 646 Times in 340 Posts	This is one of the reasons why we ammended the internal dialling convention. Unfortunately we have no control of number ranges added to ENUM roots. __________________ Martin Please post support questions on the forum. Do not send PMs unless requested.

01-23-2007, 12:34 PM	#7
martin Join Date: Feb 2006 Posts: 2,930 Thanks: 528 Thanked 646 Times in 340 Posts	These numbers are accessible via 010800000-010800999 from VoXaLot. The only reason we still support xxxxxx dialling is because some devices dont send leading 's Our recommendation is people use 010 infront of VoXaLot extensions. __________________ Martin Please post support questions on the forum. Do not send PMs unless requested.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Call forwording?	majo	Voxalot Support	1	05-08-2007 09:47 PM
Call forwarding	shezad	Voxalot Support	9	01-09-2007 03:27 AM
Call Quality and Voxalot	shibukraj	Voxalot Support	1	12-01-2006 03:39 AM
What am I doing wrong here?	code-	Voxalot Support	16	10-20-2006 05:12 PM
Newbie - but please be nice	Mallycat	Voxalot Support	21	04-15-2006 07:50 AM

01-23-2007, 11:51 AM	#4
Ron Join Date: Feb 2006 Posts: 447 Thanks: 4 Thanked 8 Times in 8 Posts	Martin, I think zaq has found a real problem. Dialing any 6-digit number of 800xxx gets a fast busy instead of either ringing, going to voicemail or getting a "your call cannot be connected" response. A test on the Dial Plan page shows these numbers will be forwarded (A call to:800123 will get forwarded to sip:800123@public.sip.magrathea.net). It may be an ENUM issue, but I don't think VoXaLot should be doing ENUM lookups on 6-digit numbers that are being treated as internal VoXaLot extensions. Ron

01-23-2007, 12:23 PM	#8
zaq Junior Member Join Date: Nov 2006 Posts: 15 Thanks: 0 Thanked 0 Times in 0 Posts	Uhm it is a hard one, what we are saying all VSPs will face difficulties once they start supporting ENUM! Or may be ENUM is not mature enough? Or the whole VOIP thingy is not mature!