From: Bert Kellerman (bkellerman@xxxxxxxxxxx)
Date: Thu Aug 03 2000 - 09:25:22 GMT-3
Scott,
Thanks for catching my error, I blatantly pasted it from this link without
checking. This appears to be an error on cisco's part as
I have other references that confirm your correction. Anyways, we should all
know transmit goes to receive. :)
http://www.cisco.com/univercd/cc/td/doc/product/ipvc/ipvc20/priguide/appd.htm#8
9543
Thanks,
Bert
Scott Morris wrote:
> Except for the fact that you have a transmit going to a transmit and a
> receive going to a receive, it's a good start. As pairs, 1-2 and 4-5 need
> to cross. Which usually means 1 goes to 4 (4 goes to 1) and 2 goes to 5 (5
> goes to 2). In your drawing below, the + and - are incorrect also. Just a
> note....
>
> Now, bear in mind, what you are doing at this point is creating a T-1
> crossover, which is what a PRI will use for it's base transport. You'll be
> able to bring the T-1 loop up, and play around with it. I'm not sure to
> what extent you'll be able to bring the D-channels up though. *shrug*
>
> Scott
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Bert Kellerman
> Sent: Thursday, August 03, 2000 1:59 AM
> To: Brian Edwards
> Cc: 'Kenneth Sacca'; Mark Lewis; ccielab@groupstudy.com
> Subject: Re: back-to-back BRI
>
> Sounds like a great feature, can't wait to set it up in the lab!
>
> >From a search, The answer to the next question(How do I make a crossover
> PRI
> cable?) is:
>
> Pin 1---Receive (+) Ring 2--------Pin 4---Transmit (-) Tip1
> Pin 2---Receive (+) Tip2---------Pin 1---Receive (+) Ring 2
> Pin 4---Transmit (-) Tip1--------Pin 5---Transmit (-) Ring1
> Pin 5---Transmit (-) Ring1-------Pin 2---Receive (+) Tip2
>
> Bert
>
> Brian Edwards wrote:
>
> > Ken,
> > Thanks for the link. Here is some text out of it...
> >
> > ===============
> > Before you begin to configure this feature, ensure that the selected
> access
> > server is in the following condition:
> > - The T1 or E1 controllers are operational and configured for ISDN PRI.
> > - The D-channel interfaces are operational and configured for ISDN PRI.
> > - Each D-channel interface is configured with the isdn incoming-voice
> modem
> > command.
> >
> > For example, the selected PRI interfaces might have a configuration
> similar
> > to the following:
> >
> > interface Serial1/0/0:23
> > no ip address
> > no ip directed-broadcast
> > isdn switch-type primary-ni
> > isdn protocol-emulate network
> > isdn incoming-voice modem
> > no cdp enable
> > ===============
> >
> > I think this is assuming you want to use this feature to connect to a PBX
> > (real world). When using this for back-to-back DDR practice for the CCIE
> lab
> > "isdn incoming-voice modem" isn't needed, correct?
> >
> > Thanks,
> > Brian
> >
> > P.S. Does anyone have two 2600's with PRI interfaces to try this out on?
> >
> > P.P.S Ken, would it be possible for Cisco implement this feature on a 2500
> > BRI interface in a future IOS release? Don't worry about conflict of
> > interest; Juniper is not planning on implementing ISDN any time soon.
> >
> > -----Original Message-----
> > From: Kenneth Sacca [mailto:ksacca@cisco.com]
> > Sent: Wednesday, August 02, 2000 2:36 PM
> > To: Brian Edwards
> > Cc: Mark Lewis; ccielab@groupstudy.com
> > Subject: Re: back-to-back BRI
> >
> > Ok. Try this link. It spells out exactly how to do this. Brian's link
> > is only for marketing. This link is how to configure this.
> >
> >
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121
> > t/121t3/dtpri_ni.htm
> >
> > Good luck.
> >
> > Ken
> >
> > Brian Edwards wrote:
> > >
> > > Here is what I've found. PRI only, IOS 12.1(3)T
> > >
> >
> http://www.cisco.com/warp/public/cc/pd/iosw/iore/iomjre121/prodlit/1065_pp.h
> > > tm#23001
> > > Network Side PRI Signaling, Trunking, and Switching
> > >
> > > Description
> > >
> > > The Network side PRI Signaling, Trunking, and Switching feature enables
> > > Cisco IOS Software to replicate the public switched network interface to
> a
> > > PBX. Network
> > > Side PRI enables the NAS to provide a standard ISDN PRI network-side
> > > interface to the PBXs and mimic the behavior of legacy phone switches.
> To
> > a
> > > PBX, the NAS
> > > functions as a National ISDN PRI switch type or an ETSI PRI Net5 switch.
> > No
> > > change in PBX capability or behavior is required.
> > >
> > > Call switching using dial peers enables Cisco (voice-over-IP) VoIP
> > gateways
> > > to switch voice and data calls between different interfaces based on the
> > > dial peer matching.
> > > An incoming call is matched against configured dial peers, and based on
> > the
> > > configured called number, the outgoing interface is selected. Any call
> > that
> > > arrives from an
> > > ISDN PRI network side on a supported platform is either terminated on
> the
> > > NAS, switched to an IP network, or switched to the PSTN, depending on
> the
> > > configuration. A dial peer is an addressable call endpoint identified,
> for
> > > example, by a phone number or a port number. In VoIP, there are two
> kinds
> > of
> > > dial peers: POTS
> > > and VoIP. The Cisco AS5800 access server switches both voice and data
> > calls.
> > > The Cisco AS5300 access server switches only voice calls.
> > >
> > > The Trunk Group Resource Manager (TGRM) supports the logical grouping,
> > > configuration, and joint management of one or more PRI interfaces. The
> > TGRM
> > > is used to
> > > store configuration information and to accept or select an interface
> from
> > a
> > > trunk group when requested. A trunk group is provisioned as the target
> of
> > a
> > > dial peer, and the
> > > TGRM transparently selects the specific PRI interface and channels to
> use
> > > for incoming or outgoing calls. A trunk group can include any number of
> > PRI
> > > interfaces, but all
> > > the interfaces in a trunk group must use the same type of signaling.
> > >
> > > The Class of Restrictions (COR) functionality provides the ability to
> deny
> > > certain call attempts based on the incoming and outgoing class of
> > > restrictions provisioned on
> > > the dial peers. This functionality provides flexibility in network
> design,
> > > allows users to block calls (for example, to 900 numbers), and applies
> > > different restrictions to call
> > > attempts from different originators. COR is used to specify which
> incoming
> > > dial peer can use which outgoing dial peer to make a call.
> > >
> > > In Cisco IOS Software Release 12.1(2)XH, the trunking and COR parts of
> > this
> > > feature are available only on the Cisco AS5800. The remainder of the
> > feature
> > > is
> > > platform independent.
> > >
> > > Benefits
> > >
> > > The Network Side PRI Signaling, Switching, and Trunking feature
> > allows
> > > you to bypass PSTN tariffed services such as trunking and
> administration,
> > > extending the
> > > cost savings of VoIP.
> > >
> > > It allows your PBXs to be connected directly to a Cisco NAS, so PBX
> > > station calls can be routed automatically to the IP network without the
> > need
> > > for special IP
> > > telephones.
> > >
> > > It provides flexibility in network design.
> > >
> > > It also enables you to block calls selectively based on the called
> > > number or the calling number.
> > >
> > > Platforms/Considerations
> > >
> > > Routers
> > > C2600, C36xx, C4x00, C7x00,
> > > Access Servers (AS)
> > > 5300, 5800
> > >
> > > First appearance in a Cisco IOS Software Release: 12.1(3)T.
> > >
> > > Marketing Contact
> > >
> > > Anita Freeman
> > >
> > > anfreema@cisco.com
> > > ---------------------------------------
> > > Brian Edwards
> > > Juniper Networks, Inc.
> > > JTAC / Technical Support Engineer
> > > Ph: 408-745-2152
> > > ---------------------------------------
> > >
> > > -----Original Message-----
> > > From: Kenneth Sacca [mailto:ksacca@cisco.com]
> > > Sent: Wednesday, August 02, 2000 12:25 PM
> > > To: Mark Lewis
> > > Cc: ccielab@groupstudy.com
> > > Subject: Re: back-to-back BRI
> > >
> > > A colleague provided me these instructions. I haven't tried
> > > it yet. I think you need at least a 12.0 IOS version but I
> > > don't know which IOS you will need.
> > >
> > > HTH Ken
> > >
> > > Are you trying to set up a back-to-back connection using ISDN ? If
> > > that's the case, on the peer serial0:23 interace, you need to issue the
> > > command ISDN network. This simulates the network (switch) side of the
> > > ISDN connection.
> > >
> > > You can verify that by doing 'show isdn status' and it should say
> > > '**network side configuration'. Be careful with clock sources tho.
> > > Generally I make the side which is acting as the network use the
> > > internal clock. This can be done by doing 'clock source internal' on the
> > > t1 controller.
> > >
> > > Mark Lewis wrote:
> > > >
> > > > Sorry, not possible! I wish it was!
> > > >
> > > > >From: "Ola Aiyegbusi" <ola@compath.com>
> > > > >Reply-To: "Ola Aiyegbusi" <ola@compath.com>
> > > > >To: <ccielab@groupstudy.com>, <cisco-cert@cciecert.com>
> > > > >Subject: back-to-back BRI
> > > > >Date: Wed, 2 Aug 2000 12:43:06 -0400
> > > > >
> > > > >Can you connect two BRI or PRI interfaces back to back to simulate
> ISDN
> > > or
> > > > >connect BRI to PRI directly? I don't have an ISDN simulator but have
> > BRI
> > > > >and PRI interfaces on my routers
> > > > >
> > > > >Ola Aiyegbusi
> > > > >Network Engineer CCDP, CCNP (Voice Access Specialization)
> > > > >ComPath Inc.
> > > > >10201 Lee Hwy Suite 140 Fairfax VA 22030
> > > > >Phone: 703-383-9550 Ext. 122
> > > > >Pager: 1-888-857-5620
> > > > >Cell: 703-395-8808
> > > > >Fax: 703-383-1369
> > > > >Email: ola@compath.com
> > > > >Web: http://www.compath.com
> > > >
> > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:20 GMT-3