Voxalot / SIP Broker Support Forums

Voxalot / SIP Broker Support Forums (https://forum.sipbroker.com/index.php)
-   Voxalot Support (https://forum.sipbroker.com/forumdisplay.php?f=4)
-   -   ENUM Failure (https://forum.sipbroker.com/showthread.php?t=817)

Ron 12-15-2006 09:43 PM

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

martin 12-16-2006 12:50 AM

Hi Ron,

Yes I noticed yesterday some U.S. 1800 numbers are blocking inbounds. This could be what you are seeing.

Ron 12-16-2006 02:11 AM

Quote:

Originally Posted by martin (Post 4345)
Hi Ron,

Yes I noticed yesterday some U.S. 1800 numbers are blocking inbounds. This could be what you are seeing.

Martin,

I can't seem to find a single one that goes through. They all get a fast busy. Are you sure this is an isolated case?

Ron

martin 12-16-2006 04:07 AM

Are you able to check where they are currently resolving to?

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

Ron 12-16-2006 04:27 AM

Quote:

Originally Posted by martin (Post 4347)
Are you able to check where they are currently resolving to?

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

Martin,

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

martin 12-16-2006 06:04 AM

Quote:

Originally Posted by Ron (Post 4348)
Martin,

Every 18??xxxxxxx (where ?? is 00/88/77/66) that I plug in resolves to sip:18??xxxxxxx@tf.voipmich.com
Ron

Yes it appears tf.voipmich.com are not servicing the inbound. I just tried another ENUM number:

1-516-687-5089

and it works OK. It is just the tf.voipmich.com URIs that are currently a problem.

evilbunny 12-16-2006 09:34 PM

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 :)

martin 12-16-2006 09:37 PM

18005551212 is working now. I just tried it.

DracoFelis 12-16-2006 10:57 PM

Quote:

Originally Posted by evilbunny (Post 4359)
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.

A possibly relevant thread (on a different forum) about what is happening with trxtel:

http://www.dslreports.com/forum/remark,17463500

evilbunny 12-17-2006 11:19 AM

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...


All times are GMT. The time now is 07:59 PM.

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.