Avaya Solution & Interoperability Test Lab Application Notes for Configuring compressed Real Time Protocol over Multi-Link Point-to-Point Protocol between Juniper Networks J4300 and M7i routers to Support an Avaya IP Telephony Infrastructure – Issue 1.
1. Introduction Real Time Protocol (RTP) packets generated by Voice over IP (VoIP) telephony are typically small in size ranging in tens of bytes per packet. IP (20 bytes) and UDP (8 bytes) headers are then added onto each packet before transmission. Because of the relative small packet size of RTP packet, the IP and UDP headers are all overhead.
2. Configuration Figure 1 illustrates the configuration used in these Application Notes. Telephones with range number 3xxxx are registered with the Avaya S8300 Media Server on the right side of the figure, and telephones with extension range 2xxxx are registered with the Avaya S8500 Media Server on the left side of the figure. An H.323 IP trunk was used to route calls between the two Avaya Media Servers. Note that extensions from both Avaya Communication Manager systems are located in each location.
3. Equipment and Software Validated The following equipment and software/firmware were used for the sample configuration: Equipment Avaya S8300 Media Server with G350 Media Gateway Avaya S8500 Media Server Avaya G650 Media Gateway TN2312BP IPSI TN799DP C-LAN TN2302AP IP MedPro Analog telephone Avaya 6408D digital Telephone Avaya 4602SW IP Telephone (H.323) Avaya 4610SW IP Telephone (H.323) Avaya 4620SW IP Telephone (H.
4. Avaya Communication Manager There is no unique configuration required in Avaya Communication Manager to support compressed RTP (cRTP) or any feature mentioned in this document. For detailed information on the Installation, Maintenance, and Configuration of Avaya Communication Manager, please consult reference [1], [2], and [3]. Step Description Below is the output from the display ip-network-region command showing the 1.
5. Configure the Juniper Networks Routers The following sections describe the steps for configuring the different Juniper Networks routers in the sample configuration. Unless otherwise specified, all router configurations are based on Juniper Networks recommendation. 5.1. Configure the Juniper Networks J4300 Router This section shows the necessary steps in configuring the Juniper J4300 router as shown in the sample network.
Step Description Configure the code-point-aliases and classifier for Avaya VoIP traffic. 3. • • • The alias helps identify the binary dscp setting. The sample network uses the name “avaya-rtp” to denote dscp binary bit 101110 for media traffic. This is equivalent to the decimal Audio PHB Value of 46 set in Avaya Communication Manager for RTP Media in Section 4, Step 1. The sample network uses the name “avaya-sig” to denote dscp binary bit 100010 for signaling traffic.
Step Description Configure the scheduler to specify how much bandwidth to allocate for each type of 4. traffic queue. • The sample configuration defines a scheduler-maps called “voip”, and assigns a name for each of the 4 queues types.
Step Description Assign the scheduler-map to each interface. 5. • Configure each interface with scheduler-map voip using the classifier defined above.
Step Description Configure the Ethernet and T1 interfaces. 6. • • Configure the Ethernet interface to use the scheduler. Assign an IP address to the interface. interop@J4300# interop@J4300# interop@J4300# interop@J4300# • • • • Configure the logical interface for the WAN connection to use the scheduler. Limit packet fragmentation of packet at 128 bytes. Assigned an IP address to the interface. Specify the RTP traffic to be compressed.
Step Description Configure the routing options for the J4300 router and forwarding table. The sample 8. configuration uses static routes. interop@J4300# interop@J4300# interop@J4300# interop@J4300# 9. edit routing-options static route 172.28.10.0/24 next-hop 192.168.1.2 set forwarding-table export pplb exit Save the changes. interop@J4300# commit 5.2. Configure the Juniper Networks M7i Router This section shows the necessary steps in configuring the Juniper M7i router as shown in the sample network.
Step Description Configure the code-point-aliases and classifier for Avaya VoIP traffic. 3. • • • The alias helps identify the binary dscp setting. The sample network uses the name “avaya-rtp” to denote dscp binary bit 101110 for media traffic. This is equivalent to the decimal Audio PHB Value of 46 set in Avaya Communication Manager for RTP Media in Section 4, Step 1. The sample network uses the name “avaya-sig” to denote dscp binary bit 100010 for signaling traffic.
Step Description interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# 5.
Step Description Assign the scheduler-map to each interface. 6. • Configure each interface with scheduler-map voip using classifier defined above. interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# 7.
Step Description interop@M7I# interop@M7I# interop@M7I# interop@M7I# interop@M7I# • • edit int lsq-1/2/0 set per-unit-scheduler set unit 0 compression rtp port min 2048 max 3029 set unit 0 family inet 192.168.1.2/30 exit Configure the T1 interface timing, encapsulation, and timeslots. Configure the T1 interface to use logical interface lsq-1/2/0.0 defined above. An IP address is not necessary because an IP address is already defined for the logical interface.
6. Verification Steps The following steps may be used to verify the configuration. Step Description Verify network connectivity. All network devices should be reachable. 1. 2. Use the show service crtp flows command on the Juniper router to verify traffic is being compressed. For an active phone call, there should be at least two flows displayed, one transmits and one received. interop@J4300> show services crtp Interface: Interface: ls-0/0/0.0 Flow Source Transmit 172.28.20.128:2300 Receive 172.28.10.
Step Description Queued: Packets Bytes 4. : : 9722 141217 0 pps 0 bps Use the show class-of-service forwarding-table command to verify the bandwidth allocation has been assigned to each interface. The following output has been abbreviated to only show the relevant interfaces. The allocation of bandwidth should match what is configured in Section 5.1 and 5.2, Step 4.
Step Description Interface: t1-2/0/0, (Index: 139,, Map index: 2,, Map type: FINAL,, Num of queue s: 2): Index: 0 Entry 0 (Scheduler index: 17, Queue #: 0): Tx rate: 0 Kb (95%), Buffer size: 95 percent Priority low PLP high: 1, PLP low: 1, PLP medium-high: 1, PLP medium-low: 1 Entry 1 (Scheduler index: 19, Queue #: 3): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority low PLP high: 1, PLP low: 1, PLP medium-high: 1, PLP medium-low: 1 Interface: ls-0/0/0.
Step Description Entry 1 (Scheduler index: 62197, Queue #: 1): Tx rate: 0 Kb (80%), Buffer size: 80 percent Priority high PLP high: 1, PLP low: 1, PLP medium-high: 1, PLP medium-low: 1 Entry 2 (Scheduler index: 62165, Queue #: 2): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority high PLP high: 1, PLP low: 1, PLP medium-high: 1, PLP medium-low: 1 Entry 3 (Scheduler index: 45740, Queue #: 3): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority high PLP high: 1, PLP low: 1, PLP medium-high: 1, PLP medium-l
8. Additional References Product documentation for Avaya products may be found at http://support.avaya.com [1] Administrator Guide for Avaya Communication Manager, Doc # 03-300509, Issue 2.
©2007 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice.
