Tasks 5.1 – PRI Inbound and Outbound Configuration
The following tasks are required for this lab:
1. Configure the Adtran Atlas 550 for the appropriate dial plan to support the additional PRI circuit, as depicted in Lab 1.
2. Configure the VWIC2-MFT1-T1/E1 card on each router to support ESF framing, B8ZS line code, and an appropriately length cable.
3. Create outbound dial peers so that internal users can call external PSTN numbers. Internal users must dial “9” to place and outside call.
4. On the Baltimore router, the destination pattern should be configured as simply as possible, but users should not have to unnecessarily long to have their outbound calls placed.
5. On the New York router, the destination pattern should be configured in such a way to allow outbound calls to be placed as quickly as possible, but without modifying any of the default characteristics of the PRI’s voice-port.
6. Create appropriate inbound dialing for support the future DID range depicted in the diagram in Lab 1.
5. Verify the ability to call outbound to and inbound from the PSTN.
Tasks 5.2 –PRI Inbound and Outbound Verification
1. The configuration process for the PRI ports on the Adtran Atlas 550 is very similar to the process described in Lab 1 for adding the FXS port dial plan. From the main menu, scroll down to Dial Plan; from the User Term screen arrow over to the left hand menu and press the “I” key to insert a dial plan component. Select the appropriate T1/PRI card and ports. Once the port has been added, use the arrow keys to select the Incoming Number Accept List. For first PRI port, I’ve added 410-555-10XX as the Accept Number. No other modifications are required on the PRI port.
2. Configuring a VWIC2-1MFT-T1/E1 can be a bit tricky the first time. If the VWIC has not been previously configured, you need to enable the T1 controller using the card type t1 global command. The second task is to configure the VWIC to receive clocking from the network, using the network-clock-participate wic command. The next step is to configure the isdn switch type. Finally, under the controller, one needs to configure the line code, framing, clocking source, the proper cable length, and finally the pri-group for the timeslots. Below are the outputs described about from the Baltimore router. Once the controller is up, a corresponding Serial interface is created by the router, along with a voice-port. A show isdn status will verify proper Layer 1 and Layer 2 connectivity.
Real World Note: If you are using a dual-port PRI module, be aware of timing issues, especially if one port is connecting to service provider "A" and the second to service provider "B". This can result in clocking slips on the router. A detailed explanation is available here.
Baltimore#sh run
!
!output omitted
!
card type t1 0 0
!
!output omitted
!
network-clock-participate wic
!
!output omitted
!
isdn switch-type primary-ni
!
!output omitted
!
!
controller T1 0/0/0
framing esf
linecode b8zs
cablelength short 133
pri-group timeslots 1-24
!
!
interface Serial0/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
no cdp enable
!
!
voice-port 0/0/0:23
!
!
Baltimore#sh isdn status
Global ISDN Switchtype = primary-ni
ISDN Serial0/0/0:23 interface
dsl 0, interface ISDN Switchtype = primary-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x807FFFFF
Number of L2 Discards = 0, L2 Session ID = 0
Total Allocated ISDN CCBs = 0
Baltimore#
3. On the Baltimore router, I’ve modified the voice-port 0/0/0:23 so that its interdigit timeout has been reduced to 3 seconds. Secondly, an inbound dial-peer as been configured to the DIDs. Finally, an outbound dial-peer has been added to take advantage to the added PRI circuit, using the 9T pattern.
Baltimore#sh run
!
!output omitted
!
voice-port 0/0/0:23
timeouts interdigit 3
description PRI ciruit to PSTN
!
!output omitted
!
dial-peer voice 3 pots
description inbound PRI dial-peer
incoming called-number 41055510..
direct-inward-dial
port 0/0/0:23
!
dial-peer voice 4 pots
description outbound PRI dial-peer
destination-pattern 9T
port 0/0/0:23
!
4. A slightly different configuration as made on the NY router. Recall the task stated to use dial-pattern that allowed for quick calls outbound without modify the interdigit timeout. Below is the configuration used on the NY router. Notice the difference between dial-peers 3 and 4 on router NewYork as compared to router Baltimore.
NewYork#sh run begin voice-port
voice-port 0/0/0:23
description PRI to PSTN
!
!output omitted
!
!
dial-peer voice 3 pots
description Inbound Dial-Peer via PRI
incoming called-number 21255520..
direct-inward-dial
port 0/0/0:23
!
dial-peer voice 4 pots
description Outbound Dial-Peer via PRI
destination-pattern 9[2-9].........
port 0/0/0:23
!
5. Finally, we can easily verify outbound calling by shutting down the two FXO ports on Baltimore and dialing out to the PSTN. Below is a sample debug as the dial-peers are match outbound. Finally, notice that the call was sent out via channel 23 on the PRI circuit.
.Sep 29 2008 00:20:35.412 EDT: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=, Called Number=94105559995, Peer Info Type=DIALPEER_INFO_SPEECH
.Sep 29 2008 00:20:35.412 EDT: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=94105559995
.Sep 29 2008 00:20:35.412 EDT: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
.Sep 29 2008 00:20:35.412 EDT: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=4
2: Dial-peer Tag=1
3: Dial-peer Tag=2
Baltimore#
Baltimore#u all
All possible debugging has been turned off
Baltimore#sh voice port sum
IN OUT
PORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC
============== == ============ ===== ==== ======== ======== ==
0/0/0:23 01 isdn-voice up dorm none none y
0/0/0:23 02 isdn-voice up dorm none none y
0/0/0:23 03 isdn-voice up dorm none none y
0/0/0:23 04 isdn-voice up dorm none none y
0/0/0:23 05 isdn-voice up dorm none none y
0/0/0:23 06 isdn-voice up dorm none none y
0/0/0:23 07 isdn-voice up dorm none none y
0/0/0:23 08 isdn-voice up dorm none none y
0/0/0:23 09 isdn-voice up dorm none none y
0/0/0:23 10 isdn-voice up dorm none none y
0/0/0:23 11 isdn-voice up dorm none none y
0/0/0:23 12 isdn-voice up dorm none none y
0/0/0:23 13 isdn-voice up dorm none none y
0/0/0:23 14 isdn-voice up dorm none none y
0/0/0:23 15 isdn-voice up dorm none none y
0/0/0:23 16 isdn-voice up dorm none none y
0/0/0:23 17 isdn-voice up dorm none none y
0/0/0:23 18 isdn-voice up dorm none none y
0/0/0:23 19 isdn-voice up dorm none none y
0/0/0:23 20 isdn-voice up dorm none none y
0/0/0:23 21 isdn-voice up dorm none none y
0/0/0:23 22 isdn-voice up dorm none none y
0/0/0:23 23 isdn-voice up up none none y
0/1/0 -- fxo-ls down down idle on-hook y
0/1/1 -- fxo-ls down down idle on-hook y
0/3/0 -- fxs-ls up up off-hook idle y
0/3/1 -- fxs-ls up dorm on-hook idle y
PWR FAILOVER PORT PSTN FAILOVER PORT
================= ==================
Lab references:
Schmidt, Cheryl A. and Friend, Ernie (2007). IP Telephony Using CallManager Express Lab Portfolio. Indianapolis: Cisco Press.
Wallace, Kevin (2007). Cisco Voice over IP (CVoice), Authorized Self-Study Guide, 2nd Edition (Chapters 3 & 4). Indianapolis: Cisco Press.
No comments:
Post a Comment