You are here: Home > Participate > Join a Discussion > Mailman Archives
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

AW: Yet Another SIP Community:

  • To: "Otmar Lendl" < >
    < >
    < >
  • From: "Stastny Richard" < >
  • Date: Thu, 7 Aug 2003 21:49:39 +0200

This Lindows guy just lauched another FWD and is in addition
selling pairs of Grandstreams. You get a "FWD" number, the gag
is only that he used an suspended NANP area code in front and
a also the NA dialing plan. For the cross connections to
FWD and is is not using the wacko ** or 1010 like EdGuy,
he is using other UNUSED NANP area codes: 
I absolutely do not like this approach, because this is confusing the
issue even more. We should get ENUM on track for linking these 
ITADs asap.
BTW, anybody can sign up for a number, get a PW  and use it with 
any other SIPphone:
SIP Server: ( 
STUN Server: ( 
NTP Server: 
TFTP Server: ( 


	-----Ursprüngliche Nachricht----- 
	Von: Otmar Lendl [
] Gesendet: Do 07.08.2003 18:57 An: enum-trials@localhost Cc: Betreff: Yet Another SIP Community: Michael Robertson, the guy behind Lindows just launched a SIP community and sells preconfigured SIP phones (Grandstreams) two for $ 130. See, or the slashdot discussion at They seem to use a numbering schema similar to the North American Dialing plan, where they are in 1-747 xxx yyyy, a crosslink to FWD uses 1-393 <fwd-nr> and for iptel the prefix is 1-477. I have no idea about the allocation status of the area codes 747, 393 and 477. All these "if you want to call from system X to system Y use prefix Z" lists remind me of the email routing guides I needed back in the days of Bitnet, Fido, Maus, Internet, X.400, Compuserve, GENIE & co. I wonder when they'll discover that ENUM might do the same magic for them that RFC822 + DNS + MX records did for email? /ol -- < Otmar Lendl (lendl@localhost) | Systems Engineer >

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