12-15-2006, 09:43 PM | #1 |
Join Date: Feb 2006
Posts: 447
Thanks: 4 Thanked 8 Times in 8 Posts |
ENUM Failure
Martin,
Are ENUM lookups failing in general or just on toll-free (US 8XX) numbers? I've had to disable ENUM lookups in my Dial Plans in order to be able to call toll-free numbers. Otherwise I get a busy signal. Ron |
12-16-2006, 12:50 AM | #2 |
Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts |
Hi Ron,
Yes I noticed yesterday some U.S. 1800 numbers are blocking inbounds. This could be what you are seeing.
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
12-16-2006, 02:11 AM | #3 |
Join Date: Feb 2006
Posts: 447
Thanks: 4 Thanked 8 Times in 8 Posts |
|
12-16-2006, 04:07 AM | #4 |
Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts |
Are you able to check where they are currently resolving to?
http://www.sipbroker.com/sipbroker/action/enumLookup
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
12-16-2006, 04:27 AM | #5 | |
Join Date: Feb 2006
Posts: 447
Thanks: 4 Thanked 8 Times in 8 Posts |
Quote:
Every 18??xxxxxxx (where ?? is 00/88/77/66) that I plug in resolves to sip:18??xxxxxxx@tf.voipmich.com on both SIP Broker and VoXaLot, but I get an immediate fast busy when I try to actually call it. If I disable ENUM lookups in my Dial Plan, the call goes through via my provider just fine. It looks like the SIP handoff to the ENUM result is failing 100% of the time. Ron |
|
12-16-2006, 06:04 AM | #6 | |
Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts |
Quote:
1-516-687-5089 and it works OK. It is just the tf.voipmich.com URIs that are currently a problem.
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
|
12-16-2006, 09:34 PM | #7 |
Senior Member
Join Date: Feb 2006
Posts: 176
Thanks: 0 Thanked 14 Times in 10 Posts |
I reported it to the provider but I haven't had a reply to date and I'm going to remove them from the zone after I post this.
Second thoughts, I just tested voip.trxtel.com and it's working again, it stopped working at one stage and the provider never replied to me so I removed them from the zone as well ages ago. PS can any problems with data in e164.org please be reported to support@ so we know there is a problem and can deal with it sooner then later |
12-16-2006, 09:37 PM | #8 |
Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts |
18005551212 is working now. I just tried it.
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
12-16-2006, 10:57 PM | #9 | |
Join Date: Mar 2006
Posts: 188
Thanks: 4 Thanked 64 Times in 41 Posts |
Quote:
http://www.dslreports.com/forum/remark,17463500 |
|
12-17-2006, 11:19 AM | #10 |
Senior Member
Join Date: Feb 2006
Posts: 176
Thanks: 0 Thanked 14 Times in 10 Posts |
I tested trx yesterday or whenever and it was working, and silly me didn't test it this morning but voipmich kicked back in again...
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
e164.apra vs e164.org Same Lookup method? | MarkLL | e164.org Support | 6 | 12-25-2007 08:25 AM |
ENUM routing not working | jonfry | Voxalot Support | 1 | 07-25-2006 03:09 AM |
ENUM Records Using DYNDNS.ORG | Ron | e164.org Support | 10 | 06-10-2006 01:05 AM |
Possible ENUM Lookup Problem | melbournelees | Voxalot Support | 7 | 04-11-2006 08:21 AM |
ENUM + Dial Plans | Ron | Voxalot Support | 10 | 03-25-2006 05:46 AM |