If this remote site is in the same LATA, have BS run phone service over a
PRI from the switch that serves the remote area to your main location.
This is we did and it saved us the cost of rent, although we're not in BS
territory. Ameritech here.
Mike
-----Original Message-----
From: Scott Rothgaber <scott@easley.net>
To: Portmaster List <portmaster-users@livingston.com>
Date: Wednesday, May 20, 1998 12:46 PM
Subject: (PM) Remote POP
>I'm currently investigating a remote POP. My current setup is a single PM3
>fed by PRI, using FR for bandwidth (separate CSU and router, not the PM3).
>Based on what I've been told, the best way to do this is to get a PM3
>somewhere in the new city with a local PRI, then backhaul the bandwidth
>here via FR.
>
>Here's where I'm temporarily confused. The way it was explained to me by
>BS, the bandwidth from the remote PM3 would go out its pipe, come across
>the cloud (PVC) to this POP, down my pipe then right back out to the
>cloud. Seems like that would choke the pipe here unnecessarily.
>
>My question is this: Can the bandwidth from the remote PM3 just go out to
>the cloud, period? Is there any reason that the data must come here first?
>The only thing that comes to mind is RADIUS authentication. The remote
>unit will use the RADIUS servers here. Are passwords and the shared
>secret sent in the clear?
>
>Thanks,
>Scott
>
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>* *
>* Easley Internet Solutions AIM: ExCavSGT *
>* Easley, SC USA ICQ: 10722606 *
>* http://www.easley.net 864.859.2400 *
>* *
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
>
>
>-
>To unsubscribe, email 'majordomo@livingston.com' with
>'unsubscribe portmaster-users' in the body of the message.
>Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>