similar to: RE: [E164-discuss] RE: E164 updater Client

Long time coming, but we finally have a 3rd party interface on the website to add block of enum numbers in regex form... eg +4412345[678] which will match +44123456 +44123457 +44123458 also +4412345[16-18] which will match +441234516 +441234517 +441234518 or just short prefixes +4412345 so anything starting with +4412345 will match... Currently this is accessible via web interface

And the whole idea of using an enum service is to save those costs and also to encourage intelligent use, If I'm going to call Duane to ask him a question I'm going to call him on his mobile if he's not at home hang the expense but the point is that is wasted money that us intelligent people do not need to spend in the first place. Cheers, Dean -----Original Message----- From:

e164.org is a public name service which provides ENUM.164, a method devised by the IETF and ITU to allow an ordinary telephone to be connected to an Internet type network and provided dialling service from other, regular telephones. Unlike many other "free" voice over IP systems, e164.org allows users who have a regular telephone line, to also hook themselves up to the Internet

There is now a peering arrangement between e164.org and FreeWorldDialup which means any and all subscribers on FWD are now easily able to make enum calls by prefixing their call with **164, like wise it's almost as simple to make a call to FWD by hitting 8829990<fwd number> This means that for those of you wanting to send/receive calls to/from FWD subscribers you can now do so, easily

Dear Duane: Thanks for the steer (presently I route calls to 1800 via iaxtel, but I'll turn that off for that test) I came up with a thought for an interesting e164 service last night - distributed custom ringtones, and custom announcements on a callerid lookup via enum. You'd be able to embed a RINGTONE - an url pointing to either a ringtone definition or a wav file that contains

Firstly we've setup a SIP proxy that uses e164.org to do enum lookups, also rather then issuing people with yet more numbers they have to remember we've coded up a watered down version of e164.org for people that would just like to have a single SIP phone rather then run their own PABX. http://www.Like2Fone.Com for more details on that service. The plan is to get people hooked on VoIP

Hi Asterisk users/e164 developers, I have had an idea on how to improve the functionality of the E164 service. The idea is that when I'm no longer at my house I actually want to receive calls at another number So I have a small software client on my windows desktop and I tell it I'm no longer here I'm going to be on my mobile (similar to the no-ip.com dns updater I use) The client

Exactly but without the follow me charges. I think it sounds like a great idea to let people know where you can be contacted. Cheers, Dean -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Gary Sent: Friday, 30 April 2004 3:38 PM To: asterisk-users@lists.digium.com Subject: Re: [Asterisk-Users] RE: E164 updater

For a long time now we've allowed people to publish a wide variety of URI against their enum records such as SIP/IAX2/H323 for VoIP and other types for non-VoIP such as HTTP/MAILTO etc. For the most part these record types aren't listed or aren't utilised so I've done up a quick hack for firefox users as a proof of concept and I'm hoping others will take advantage of this and

So I just saw this VoIP-centric article at slashdot (http://slashdot.org/article.pl?sid=04/05/22/1840220) which mentions e164.org. It's a "non-profit public DNS root designed to map phone numbers to Internet protocols." Is anyone on this list actually using this? They have asterisk config instructions: http://www.e164.org/config.php I wonder if someone can help me understand

works, but there are some issues. I've had asterisk up and running on a suse 9.0 beta 7 x86_64 for about two weeks now. I used then-current cvs, and the compile went smoothly with only a dozen complaints about 64 bit casting of pointer types. The good news : Latency is effectively non-existent (especially when compared to the lame c3 itx box I normally use), and asterisk has not crashed

Since e164.org added DNC and ADDRESS records my enum configuration has failed. Using both the old EnumLookup app and the new ENUMLOOKUP function, the lookups have consistantly failed since e164.org added E2U+ADDRESS and E2U+DNC records. Mar 6 17:39:44 WARNING[14222]: enum.c:235 parse_naptr: NAPTR Regex match failed. Mar 6 17:39:44 WARNING[14222]: enum.c:354 enum_callback: Failed to parse naptr

ENUM lookups at e164.org return a IP route for ALL toll-free numbers. I was surprised to observe that ALL toll-free numbers get a hit at e164.org. It appears that ALL toll-free prefixes have been delegated, thereby publishing an IP route for YOUR TOLL-FREE NUMBERS, my toll-free numbers, and even toll-free numbers that have not been allocated. :-) See below Should I care? Even though this

Hello, we have set up e164.lu as a test zone, as the delegation for 2.5.3.e164.arpa hasn't been completed yet. For all those who want to call the numbers currently availble directly via SIP, please use the zone name in your enum.conf. If you decide to use the zone, please tell me at mstorck@luxadmin.org, so as soon as the 2.5.3.e164.arpa zone is ready, I will mail you, so you may disable

Does anyone know if the e164.org ENUM service is still active? If anyone who has anything to do with the e164.org ENUM site monitors this list could you check your signup page as the Captcha's (the test to see if you are human) fails for both the text and audio tests every time. I'd post a message on the e164.org forums but the signup page there has the test missing altogether. Greyman.

Hi. I'm using Asterisk & oh323. My gatekeeper needs h323 ID and e164 ID for registration. But I don't know how to send e164 ID. I configure register section in my oh323.conf file like below. [general] <<snip>> gatekeeper=xxx.xxx.xxx.xxx [register] alias=abc alias=777 <<snip>> And the gatekeeper doesn't need passward. It authenticates to use only both h323

Is there a proper and accepted way to go about setting an E164 compliant caller ID (ANI) ? Currently, we're using just the Set(CALLERID(num)=XX) where XX is some E164 compliant number like 3539146632431 or some such. Is there another way we should be doing that or is that proper? N.

hello all, i want to have ooh323 connection between asterisk and cisco. in my scenario, asterisk is gateway and cisco is gatekeeper. this is my ooh323.conf file: [general] port=1720 bindaddr=192.168.0.227 gateway=yes faststart=yes h245tunneling=yes h323id=gw10 at test.com settracelevel=10 gatekeeper=192.168.0.212 context=from-trunk disallow=all allow=ulaw allow=alaw allow=gsm dtmfmode=rfc2833

Recently, I've been having issues with the URIs returned from e.164.org and toll free calls. It seems that the URIs that are returned from ENUMQUERY and ENUMRESULT are no longer the proper numbering schemes that the poviders use. I've been using the following [enum] template in my outbound route for quite some time with great success until recently. [enum](!) exten =>

For those interested, I'm giving a talk about VoIP/enum.164/asterisk tonight in Sydney at the Sydney LUG meeting which is about 7pm in the UTS build #2, 4th floor, room 10. Sorry for the late notice, it didn't occur to me that there might be people on this list interested and able to attend etc... -- Best regards, Duane http://www.cacert.org - Free Security Certificates