About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

Re: [enum-wg] Austria starts with the ENUM-based number range

  • To:
  • From: Alexander Mayrhofer <
    >
  • Date: Wed, 20 Apr 2005 09:21:35 +0200
  • Cc:
    ,
    ,

chenhui@localhost wrote:
Hi all,

I have several questions...
1) Which switching machine takes in charge of "triggering an ENUM query"? Is it
the local-part machine?
It will usually consist of several components: A SS7 "speaking" component, a ISDN to SIP/H.323 (talking about voice) Gateway, probably an external box doing the ENUM lookup and controlling the gateway, plus a session border controller / firewall ...


2) Is it that ENUM registry in Austria stores all the ENUM NAPTR records of all
users? And telco service providers agree to cooperate with ENUM registry?
Neither. But:

It's the user's choice to opt in for ENUM (although the Telco is allowed to opt-in for the user as well). The NAPTRs are the user's choice, too. Validation can take place without an cooperating telco as well (eg. via providing paperwork, invoices, directory entries etc.)

However, with regards to the number range +43 780, a user is required to have the corresponding ENUM-Domain, because it's a prerequisite to number allocation.

3) What is the charge module of ENUM application now? Is it based on number of
services, just ENUM number, or some other things?
If you're talking about the registry costs: it's a "per-delegation" based model - the registrar is esentially charged "<fee> x <number of domains>" with the fee slightly decreasing as the number of domains increases.

cheers

axelm




 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community