Actually, most of the newer CSU/DSUs and AT&T Paradyne boxes have slightly
better built-in logic then years ago..
Switching voicelines to dial out only, dial in only or both is dependent
on the type of voice gear one has and nothing to do with the splitting off
of voice and data lines.. Pairing out lines for specific uses will
provide an organization a somewhat low level protection from those would
be wardial kiddies out there..
The real trick is do configure your phone switch to log everything
Stating that mixing data and voice with your carrier is not a good idea,
then why is DSL so popular..??:)
/sincerely,
an old phone switch hack.. :)
On Wed, 5 Jul 2000 [EMAIL PROTECTED] wrote:
> Just out of curiosity have you ever tried to change carriers with this
> arrangement? Upgrade your voice lines to DID or two-way DID? Add data to
> an advanced T1? Are you using T1s with B8ZS encoding or PRIs? All of
> these scenerios require VERY different arrangements on the carrier side.
> Sharing data and voice on point-to-point circuits between company sites is
> pretty staight forward but I will stand by my orginal statement:
>
> It has been my experience that mixing data and voice to your carrier is
> not a good idea and tends to limit what you can do with the circuit.
>
> Bill Stackpole, CISSP
>
>
>
>
>
> <[EMAIL PROTECTED]>
> 07/05/00 09:09 AM
>
>
> To: [EMAIL PROTECTED]
> cc: "Malt, Rob" <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
> [EMAIL PROTECTED]
> Subject: Re: T1 Help - Slightly Off Topic
>
> That is actually not true, if one uses an AT&T Paradyne CSU/DSU, one can
> very easily configure voice and data. A normal CSU/DSU may not fit the
> bill in this case, since in many organizations one tends to have more
> voice lines than data lines. If in the case of an organization taking
> existing channels from the voice line and moving it towards data. Usually
> this is not an overly difficult task.. The difficult part is getting
> everything to sync once the channels have been allocated.
>
> A Netopia box is capable of doing ISDN, Data, etc, and has some features
> that a Cisco 766 or Cisco 1000 does not yet have..
> In the cases of remote offices or SOHO (as some marketing weenies have
> deemed them). A netopia with 64 or 128K will sustain a remote office of
> 20 or so people barring their usage is strictly business and is not used
> to download dirty pictures, MPEGS, or MP3s..
>
> A Cisco 1600 is a little overkill for a SOHO office, but that is besides
> the point. Most SOHO's do not have a Cisco expert on hand so
> troubleshooting may be an issue when there is a problem.
>
> /cheers
>
> /mht
>
>
>
> On Wed, 5 Jul 2000 [EMAIL PROTECTED] wrote:
>
> > Malt,
> >
> > It has been my experience that mixing data and voice to your carrier is
> > not a good idea and tends to limit what you can do with the circuit. You
>
> > probably don't need a full blown channel bank, a drop and insert CSU/DSU
>
> > should work fine. The data will come off the CSU via a V.35 and connect
>
> > to any standard high speed serial port. It's hard to go wrong with a
> > Cisco router. They are everywhere, consequently they are easy to get
> > configured and serviced. It doesn't take much effort to keep up with a
> > 128K data stream so any of their remote office models will work fine. We
>
> > used 1600 series boxes at the last place I worked.
> >
> > -- Bill Stackpole, CISSP
> >
> >
> >
> >
> >
> > "Malt, Rob" <[EMAIL PROTECTED]>
> > Sent by: [EMAIL PROTECTED]
> > 06/29/00 02:20 PM
> >
> >
> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> > cc:
> > Subject: T1 Help - Slightly Off Topic
> >
> > Currently I have a LAN with around 20 users connected to the 'net via a
> > dual-homed Windows NT server running MS Proxy 2. The external NIC is
> > connected to an ISDN router. That router is using NAT and has basic
> > packet
> > filtering. We are looking at getting a T1 and using two channels (128k)
>
> > for
> > data and the rest for voice. I've been told by the MCI guys that we
> will
> > need a channel bank, and whatever router we get will be connected to
> that.
> > Question one: What type of WAN interface card will the router need to
> > talk
> > to the channel bank? Just a 'T1' card? Also, can someone recommend a
> > good
> > router/firewall? I'd like to spend less than $2000 on the router. So
> far
> > I've been looking at Cisco and Nortel Networks' products, but I know
> there
> > are other nice products out there.
> >
> > Thanks,
> >
> > -Rob
> >
> > -
> > [To unsubscribe, send mail to [EMAIL PROTECTED] with
> > "unsubscribe firewalls" in the body of the message.]
> >
> >
> >
>
>
>
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
