Subject: RE: VOIP question ??

From: "David R. Oran" <[email-masked]>
Date: Mon, 8 Feb 1999 13:24:25 -0500

> -----Original Message-----
> From: [email-masked]
> [mailto:[email-masked]]On Behalf Of Ami Amir
> Sent: Thursday, January 28, 1999 5:42 AM
> To: [email-masked]; [email-masked]
> Cc: Sebastien Ducarne; IP Telephony
> Subject: RE: VOIP question ??
>
>
> Hi All
>
> Once you walk through and analyze the situation, you will
> find out that a
> Gatekeeper is really needed.
>
Not really. A GK is just a RAS engine and RAS is just a packaging of
functionality that could just as easily be provided by judicious use of
existing protocols like DNS, LDAP, RADIUS, etc.

> An example of one issue -dialing schemes: If you are willing
> to support
> multiple stage dialing or assign a rigid dialing scheme (e.g.
> prefix 6 for
> PBX A, prefix 7 for PBX B etc) then you can make do w/o
> gatekeepers - and
> sacrifice functionality, mobility and flexibility.
>
Hmm, let's see. Most of this I could get via an LDAP query. The rest I
need a real routing protocol for anyway, and gatekeepers don't run
routing protocols
(yet).

> Another issue is economical: If you have more than 3 PBX's -
> you have two
> options; either create a mesh, and let each PBX support as
> many trunks as
> there are PBX's (= lots of hardware) - or support a flexible
> scheme, where a
> single PBX to GW trunk can support connections to multiple
> GWs. This, less
> expensive, functionality requires a GK.
>
Huh? This is IP. The IP network provides the full mesh.

---------
This message came from the IETF IPTEL Working Group Mailing List.