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
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

AW: [enum-wg] Kapsch CarrierCom first company to be reached with ENUM (questionable)

  • To: "Carsten Schiefner" < >
  • From: Christoph Künkel < >
  • Date: Fri, 8 Oct 2004 10:34:24 +0200

Hi Carsten,

kind of "Freud'sche Fehlleistung", isnt it ;-)  [ does someone volunteer to translate that therm to english? ]

Yes, I am using a h323: URI.  We do that for more than 6 months now and some of our customers too, using comercially available equipment.  My point is that ENUM and SIP are only loosely related.  And VoIP is not SIP, as well as H323 is not VoIP.  

ENUM is neither about H323 nor SIP nor PSTN.  It is about associating e164 numbers to various kinds of services (internet related or not, doesnt matter).

:-) Christoph


-----Ursprüngliche Nachricht-----
Von: Carsten Schiefner [
] > no mention of ENUM. ENUM is 3761 - so just one digit mixed up; and they even look almost the same. :-) Happens to me all the time, too... > also, I work in a company that has ENUM enabled. You can call me (+49 > 7031 73009) via ENUM from the internet and I certainly have no SIP URI. So what kind of URI you are using then - "h323:"? Or "tel:", so that it is about Internet->PSTN termination? > Same goes true for a number of our customers I know of, which are using > ENUM in their telephony production environment. > > Do I miss something or is this thread falsely mixing up only loosely > coupled issues? What _exactly!_ is only loosely coupled here from you PoV? Best, Carsten

  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community