Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring Multilink Point-to-Point Protocol between Juniper Networks SSG 520 Security Gateway and M7i Router to Support an Avaya H.323 Trunk Issue 1.0 Abstract These Application Notes describe the steps for configuring a Multilink Point-to-Point Protocol (MLPPP) link between a Juniper Networks SSG520 Security Gateway and a M7i router. This MLPPP link supports an Avaya H.323 trunk used to interconnect two Avaya Communication Manager systems. 1 of 23

2 1. Introduction These Application Notes describe a solution for configuring a Multilink Point-to-Point Protocol (MLPPP) link between a Juniper Networks SSG 520 Security Gateway and a M7i router. This MLPPP link supports an Avaya H.323 trunk used to interconnect two Avaya Communication Manager systems Overview The sample configuration consists of a Headquarters site and a Branch site connected together via a MLPPP link. The Headquarters site consists of an Avaya S8300 Server running Avaya Communication Manager hosted within an Avaya G700 Media Gateway and a Juniper Networks M7i router. The Branch site consists of an Avaya S8300 Server running Avaya Communication Manager hosted within an Avaya G250 Media Gateway and a Juniper Networks SSG 520 Security Gateway. All Avaya IP Telephones located at the Headquarters site are assigned to network region 1 while all Avaya IP Telephones located at the Branch site are assigned to network region 2. In order to provide the best audio experience and minimize bandwidth useage, all intra-region calls are configured to use the G.711 codec and all inter-region calls (calls between Headquarters and Branch) are configured to use the G.729A codec. Quality of Service is achieved through both inter-region call limiting in Avaya Communication Manager and traffic shaping on the M7i router and the SSG 520. The MLPPP link in the sample configuration used in these Application Notes is configured to allocate a maximum of 400kbps bandwidth for Voice over IP (VoIP) traffic. This 400kbps is defined in Avaya Communication Manager as the total bandwidth available for inter-region call. Any call requiring additional bandwidth beyond 400kbps will be denied. Since VoIP traffic must share the available bandwidth of the MLPPP link with other non-voip traffic, traffic shaping is deployed in both the M7i router and SSG 520 to ensure VoIP traffic is given the proper priority and bandwidth allocation. 2 of 23

3 2. Configuration Figure 1 illustrates the configuration used in these Application Notes. The Headquarter utilizes a M7i router for WAN connectivity while the Branch site utilizes a SSG 520. All Avaya IP Telephones are registered locally to their respective Avaya Communication Manager. All IP addresses are statically administered. Figure 1: Sample Network Configuration 3 of 23

4 3. Equipment and Software Validated The following equipment and software/firmware were used for the sample configuration: EQUIPMENT SOFTWARE Avaya S8300 Server with G700 Media Gateway Avaya Communication Manager (R014x ) Avaya S8300 Server with G250 Media Gateway Avaya Communication Manager (R014x ) Avaya 4610SW IP Telephone R2.8 Avaya 4625SW IP Telephone R2.8 Juniper Networks SSG 520 Security Gateway ScreenOS 6.0.0r2.0 Juniper Networks M7i router with AS-PIC JUNOS 8.4R Configure the Juniper Networks M7i router This section describes the configuration for Juniper Networks M7i router located at Headquarters as shown in Figure 1. The Command Line Interface (CLI) is used to configure the router. 1. Log in to the router using the appropriate credentials. Enter the configuration mode by typing configure at the command prompt. The M7i router will display the # prompt to indicate that it is in the configuration mode. 2. Configure the two serial t1-0/0/0 and t1-0/0/1 interfaces and the logical lsq-1/2/0 interface. The lsq-1/2/0 logical interface will make use of both of the physical t1 interfaces. Note that clocking is set to internal. This is done because the M7i and the SSG 520 are connected back-to-back. In most installation, clocking should be set to external. set interfaces fe-1/3/0 unit 0 family inet address /24 set interfaces t1-0/0/0 clocking internal set interfaces t1-0/0/0 encapsulation ppp set interfaces t1-0/0/0 t1-options timeslots 1-24 set interfaces t1-0/0/0 unit 0 family mlppp bundle lsq-1/2/0.0 set interfaces t1-0/0/1 clocking internal set interfaces t1-0/0/1 encapsulation ppp set interfaces t1-0/0/1 t1-options timeslots 1-24 set interfaces t1-0/0/1 unit 0 family mlppp bundle lsq-1/2/0.0 set interfaces t1-0/0/3 clocking internal set interfaces t1-0/0/3 encapsulation ppp set interfaces t1-0/0/3 t1-options timeslots 1-24 set interfaces t1-0/0/3 unit 0 family inet address /30 set interfaces lsq-1/2/0 per-unit-scheduler set interfaces lsq-1/2/0 unit 0 encapsulation multilink-ppp set interfaces lsq-1/2/0 unit 0 point-to-point ## The command in bolded text below is necessary for configuring MLPPP between ## ## a M7i router (with an AS-PIC) and SSG 520 ## set interfaces lsq-1/2/0 unit 0 disable-mlppp-inner-ppp-pfc set interfaces lsq-1/2/0 unit 0 family inet address /30 4 of 23

5 3. A static route is defined to direct network traffic to IP network /24. set routing-options static route /24 next-hop Link Fragmentation and Interleave (LFI) is used to minimize latency. Below are the commands used in the sample network. set class-of-service fragmentation-maps crtplfi forwarding-class best-effort fragment-threshold 128 set class-of-service fragmentation-maps crtplfi forwarding-class expeditedforwarding no-fragmentation set class-of-service fragmentation-maps crtplfi forwarding-class assuredforwarding no-fragmentation set class-of-service fragmentation-maps crtplfi forwarding-class network-control fragment-threshold Prioritize the VoIP signaling and media traffic. The DiffServ/TOS PARAMETER defined in the ip-network-region form in Section 6, Step 4 is used to create a classifier to identify the signaling and media traffic. The sample configuration prioritizes signaling traffic (binary value of or decimal value of 34) as assured forwarding and media traffic (binary value of or decimal value of 46) as expedited forwarding. set class-of-service classifiers dscp sample-app forwarding-class expeditedforwarding loss-priority low code-points avaya-voip set class-of-service classifiers dscp sample-app forwarding-class assuredforwarding loss-priority low code-points avaya-sig set class-of-service code-point-aliases dscp avaya-voip set class-of-service code-point-aliases dscp avaya-sig set class-of-service forwarding-classes queue 1 expedited-forwarding set class-of-service forwarding-classes queue 2 assured-forwarding set class-of-service forwarding-classes queue 0 best-effort set class-of-service forwarding-classes queue 3 network-control 6. Each of the four forwarding classes (e.g. best-effort, expedited-forwarding, assured-forwarding, and network-control) are configured with scheduler-maps for a specific bandwidth allocation to ensure that the quality of service is maintained. Since Avaya Communication Manager in Section 6, Step 4 is configured to allow 400kbps for VoIP traffic; the expedited forwarding in the M7i router must be configured for at least 400kbps of bandwidth. The sample network uses a value of 30%, which is approximately equal to 460kbps for a each T1 circuit for a combine bandwidth of 920kbps. Any non-voip taffic will still be able to make use of bandwidth this allocated bandwidth in the absence of voice traffic. 5 of 23

6 set class-of-service scheduler-maps voip forwarding-class best-effort scheduler be-sched set class-of-service scheduler-maps voip forwarding-class expedited-forwarding scheduler ef-sched set class-of-service scheduler-maps voip forwarding-class assured-forwarding scheduler af-sched set class-of-service scheduler-maps voip forwarding-class network-control scheduler nc-sched set class-of-service schedulers nc-sched transmit-rate percent 5 set class-of-service schedulers nc-sched shaping-rate percent 5 set class-of-service schedulers nc-sched buffer-size percent 5 set class-of-service schedulers nc-sched priority high set class-of-service schedulers af-sched transmit-rate percent 5 set class-of-service schedulers af-sched buffer-size percent 5 set class-of-service schedulers af-sched priority high set class-of-service schedulers ef-sched transmit-rate percent 30 set class-of-service schedulers ef-sched shaping-rate percent 30 set class-of-service schedulers ef-sched buffer-size percent 30 set class-of-service schedulers ef-sched priority high set class-of-service schedulers be-sched transmit-rate percent 60 set class-of-service schedulers be-sched shaping-rate percent 60 set class-of-service schedulers be-sched buffer-size percent 60 set class-of-service schedulers be-sched priority low 7. Assign the scheduler-map, LFI, and classifier defined in Steps 4-6 to the individual interfaces. set class-of-service interfaces fe-1/3/0 scheduler-map voip set class-of-service interfaces fe-1/3/0 unit 0 classifiers dscp sample-app set class-of-service interfaces lsq-1/2/0 unit 0 scheduler-map voip set class-of-service interfaces lsq-1/2/0 unit 0 fragmentation-map crtplfi set class-of-service interfaces lsq-1/2/0 unit 0 classifiers dscp sample-app set class-of-service interfaces t1-0/0/0 scheduler-map voip set class-of-service interfaces t1-0/0/0 unit 0 classifiers dscp sample-app set class-of-service interfaces t1-0/0/1 scheduler-map voip set class-of-service interfaces t1-0/0/1 unit 0 classifiers dscp sample-app 6 of 23

7 5. Configure the Juniper Networks SSG 520 Security Gateway This section describes the configuration for Juniper Networks SSG 520 Security Gateway located at the Branch site as shown in Figure Connect to the SSG 520 by entering the IP address into a Web Brower URL in the form of IP address>. Log in using the appropriate credentials. 2. The screen capture below shows the network interfaces used in the sample configuration. ethernet0/0 is used strictly for the management of the SSG50. ethernet0/1 connects directly to the default gateway for the local Branch network. Both serial1/0 and serial1/1 interfaces are part of the logical ml1 (MLPPP) interface. Both ethernet0/0 and ethernet1/1 are configured for the Trust zone and the serial1/0, serial1/1, and ml1 interfaces are configured for the Untrust zone. 7 of 23

8 3. The abbreviated screen capture below shows the configuration for the ml1 MLPPP interface. 4. The screen capture below shows the configuration of the serial1/0 interface. Although not shown, the serial1/1 interface has the same configuration. 8 of 23

9 5. One static default route is configured to route all unknown destination traffic to the M7i router. 9 of 23

10 6. The screen capture below shows the hosts and IP networks defined in the SSG 520 for both Trust and Untrust zone. These hosts and IP networks are used in defining traffic Policy in Step Two custom Avaya VoIP services are defined in the SSG 520. The Avaya-Signaling service is defined to allow for H.323 Trunk signaling traffic between the Headquarters and Branch, and the Avaya-RTP service is defined for media traffic between the Headquarters and Branch network. 10 of 23

11 8. A total of four Policies are configured to manage Avaya VoIP traffic, two from Untrust to Trust, and two from Trust to Untrust. An additional policy (ID s 8 and 9 shown below) is used strictly to allow for the Management PC s traffic. These policies utilize the hosts and IP networks defined in Step 6 as well as the Services defined in Step 7. Below is a brief description for each of the policies. Policy ID Description 4, & 5 This policy is defined to allow for H.323 signaling as well as keep alive (ICMP) traffic to communicate between the Avaya Communication Managers at the Headquarters and the Branch. Each of these policies has both the Avaya-Signaling (defined in Step 7) as well as ICMP-ANY (default system Service) services associated with it. 6, & 9 This policy is defined to allow for media traffic (defined in Step 7) to traverse between the Headquarters and Branch networks. 11 of 23

12 The screen capture below shows the detailed entry for policy ID 4. Since multiple Service is used within this policy the word (Multiple) is displayed. The screen capture above shows the individual services included in this policy. 9. In addition to managing traffic traversing between the Trust and Untrust zones, the policies defined above are used for traffic shaping. In order to provide QoS for VoIP traffic, each policy is configured with a specific bandwidth allocation. The Traffic Shaping portion of the configuration is accessed by clicking on the Advanced button under each individual policy edit screen. The abbreviated screen capture below shows the Traffic Shaping setting for policy ID s 4 and 5, which are defined for H.323 Trunk and keep alive traffic. 12 of 23

13 The table below lists the Traffic Shaping setting for the different policies. The selection of these bandwidth allocations is for illustration purpose only. Actual allocation should be based on the total number of simultaneous calls that needs to be supported by the system as well as codec used. Since the sample network is design to allocate 400kbps for VoIP traffic, Guaranteed Bandwidth for traffic shaping for policy ID 6 and 9 is set to 400kbps. Policy ID Guaranteed Bandwidth (kbps) Maximum Bandwidth (kbps) Traffic Priority 4, & , & of 23

14 6. Configure Avaya Communication Manager This section highlights the important areas in configuring an H.323 trunk in Avaya Communication Manager at the Headquarters site. A similar configuration must also be administered in Avaya Communication Manager at the Branch site. For detailed information on the installation, maintenance, and configuration of Avaya Communication Manager, consult references [1], [2], [3] and [4] in Section 9. All steps in this section are administered via the System Access Terminal (SAT) of Avaya Communication Manager. 1. Use the change node-names ip form to add a Name and IP address of the Branch Avaya Communication Manager into the system. change node-names ip Page 1 of 2 IP NODE NAMES Name IP Address Branch default msgserver procr Use the add signaling-group form to create a new signaling group. The screen capture below shows the parameters used in the signaling group. Note that the Far-end Network Region is set to 2. The different Network Region assignment allows for the use of different codec to be used for encoding. In the sample network, all Intra-Region call uses the G.711 codec while Inter- Region call uses the G.729 codec in order to provide a better efficient use of bandwidth. add signaling-group 5 Page 1 of 5 SIGNALING GROUP Group Number: 5 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 SBS? n Max number of CA TSC: 0 IP Video? n Trunk Group for NCA TSC: Trunk Group for Channel Selection: 5 TSC Supplementary Service Protocol: a T303 Timer(sec): 10 Near-end Node Name: procr Far-end Node Name: Branch Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Media Encryption? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n Enable Layer 3 Test? n Interworking Message: PROGress DCP/Analog Bearer Capability: 3.1kHz 14 of 23

15 3. Use the add trunk-group form to create a new trunk group. add trunk-group 5 Page 1 of 21 TRUNK GROUP Group Number: 5 Group Type: isdn CDR Reports: y Group Name: OUTSIDE CALL COR: 1 TN: 1 TAC: 105 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? n Queue Length: 0 Service Type: tie Busy Threshold: 255 Night Service: Auth Code? n Member Assignment Method: auto Signaling Group: 5 Number of Members: 6 add trunk-group 5 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: public UUI IE Treatment: service-provider Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n Hold/Unhold Notifications? n Modify Tandem Calling Number? n 15 of 23

16 4. Use the change ip-network-region form to specify the bandwidth allocation for inter-region calling. The sample network is configure to allocate 400kbps for VoIP call. change ip-network-region 2 Page 1 of 19 IP NETWORK REGION Region: 2 Location: Authoritative Domain: Name: MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 2 Inter-region IP-IP Direct Audio: yes UDP Port Min: 2048 IP Audio Hairpinning? n UDP Port Max: 3329 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 34 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5 change ip-network-region 2 Page 3 of 19 Inter Network Region Connection Management src dst codec direct WAN-BW-limits Video Dyn rgn rgn set WAN Units Total Norm Prio Shr Intervening-regions CAC IGAR y Kbits y n Use the change ip-codec-set form to specify the codec set used. G.729A codec is specified for ip-codec-set 2 to minimize bandwidth requirement for inter-region call. change ip-codec-set 1 Page 1 of 2 Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n : G.729A n : 16 of 23

17 change ip-codec-set 2 Page 1 of 2 Codec Set: 2 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.729A n : 6. The dialplan analysis screen displayed below shows that calls to Branch extensions 4xxxx are of call type AAR. display dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Percent Full: 3 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 1 3 dac 33 5 ext 4 5 aar 7. The aar analysis screen displayed below shows calls to extension 4xxxx should use Route Pattern 5. display aar analysis 4 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 3 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n aar n 8. The route-pattern screen displayed below shows that the calls will be routed using trunk group of 23

18 display route-pattern 5 Page 1 of 3 Pattern Number: 5 Pattern Name: To_Branch-4 SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 5 0 n user 2: n user 3: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR M 4 W Request Dgts Format Subaddress 1: y y y y y n n rest none 2: y y y y y n n rest none 3: y y y y y n n rest none 7. Verification Steps The following steps may be used to verify the configuration: 1. Use the status ip-network-region form in SAT to verify the bandwidth allocation has been set correctly in Avaya Communication Manager. status ip-network-region 2 Inter Network Region Bandwidth Status Number of # Times Src Dst Conn Conn BW-limit BW-Used(Kbits) Connections BW-Limit IGAR Rgn Rgn Type Stat Tx Rx Tx Rx Hit Today Now/Today 2 1 direct pass 400 Kbits / 0 Video: 0 Kbits Priority: 0 Kbits Use the list trace station form to verify call progress. The screen capture below shows no bandwidth being available when additional bandwidth required for the new call exceeds what is available as configured in Section 6, Step 4. list trace station Page 1 LIST TRACE time data 13:55:32 active station cid 0x296 13:55:32 G711MU ss:off ps:20 rn:1/ : : :55:32 xoip: fax:relay modem:off tty:us :2054 uid:0x1 13:55:34 dial route:aar 13:55:34 denial event 1012: Destination Unavailable D1=0x1 D2=0x296 13:55:34 dial route:aar 13:55:34 reorder trunk-group 5 cid 0x296 13:55:34 denial event 2329: No BW, prowler <--> IP ep D1=0x2 D2=0x1 18 of 23

19 3. On the SSG 520, click on the icon under the View Detail column for a policy to view whether traffic is utilizing a specific policy and how much bandwidth is being consumed. The screen display below shows the details for policy ID 6 when one phone call was place through the network. 19 of 23

20 4. Use the show interface queue command on the M7i router to verify whether VoIP traffic is being assigned to the appropriate forwarding class. The abbreviated screen capture below shows 50pps is being assigned to the expedited-forwarding class when a active call is in progress for interface t1-0/0/1. interop@m7i> show interfaces queue t1-0/0/1 Physical interface: t1-0/0/1, Enabled, Physical link is Up Interface index: 129, SNMP ifindex: 25 Forwarding classes: 4 supported, 4 in use Egress queues: 4 supported, 4 in use Queue: 0, Forwarding classes: best-effort Queued: Packets : pps Bytes : bps Queue: 1, Forwarding classes: expedited-forwarding Queued: Packets : pps Bytes : bps 5. Use the show class-of-service forwarding-table command on the M7i router to verify the bandwidth allocation is correct. The abbreviated screen capture below shows the bandwidth allocation as configured in Section 4, Step 6. interop@m7i> show class-of-service forwarding-table Interface: t1-0/0/0, (Index: 128, Map index: 45418, Map type: FINAL, Num of queues: 4): Index: 0 Entry 0 (Scheduler index: 13005, Forwarding class #: 0, Queue #: 0): Tx rate: 0 Kb (60%), Buffer size: 60 percent Priority low PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 1 (Scheduler index: 62197, Forwarding class #: 1, Queue #: 1): Tx rate: 0 Kb (30%), Buffer size: 30 percent Priority high PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 2 (Scheduler index: 62165, Forwarding class #: 2, Queue #: 2): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority high PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 3 (Scheduler index: 45740, Forwarding class #: 3, Queue #: 3): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority high PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Interface: t1-0/0/1, (Index: 129, Map index: 45418, Map type: FINAL, Num of queues: 4): Index: 0 Entry 0 (Scheduler index: 13005, Forwarding class #: 0, Queue #: 0): Tx rate: 0 Kb (60%), Buffer size: 60 percent Priority low PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 1 (Scheduler index: 62197, Forwarding class #: 1, Queue #: 1): Tx rate: 0 Kb (30%), Buffer size: 30 percent Priority high 20 of 23

21 PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 2 (Scheduler index: 62165, Forwarding class #: 2, Queue #: 2): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority high PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 3 (Scheduler index: 45740, Forwarding class #: 3, Queue #: 3): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority high PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Interface: lsq-1/2/0.0, (Index: 70, Map index: 45418, Map type: FINAL, Num of queues: 4): Index: 0 Entry 0 (Scheduler index: 13005, Forwarding class #: 0, Queue #: 0): Tx rate: 0 Kb (60%), Buffer size: 60 percent Priority low PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 1 (Scheduler index: 62197, Forwarding class #: 1, Queue #: 1): Tx rate: 0 Kb (30%), Buffer size: 30 percent Priority high PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 2 (Scheduler index: 62165, Forwarding class #: 2, Queue #: 2): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority high PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 Entry 3 (Scheduler index: 45740, Forwarding class #: 3, Queue #: 3): Tx rate: 0 Kb (5%), Buffer size: 5 percent Priority high PLP high: 1, PLP low: 1, TCP PLP high: 1, TCP PLP low: 1 21 of 23

22 8. Conclusion These Application Notes have described the administration steps required to configure the MLPPP link between Juniper Networks M7i router and SSG 520 Security Gateway to support an H.323 trunk between two Avaya Communication Manager systems as depicted in Figure References Product documentation for Avaya products may be found at [1] Administrator Guide for Avaya Communication Manager, Doc # , February 2007 [2] Avaya Communication Manager Advanced Administration Quick Reference, Doc # , February [3] Administration for Network Connectivity for Avaya Communication Manager, Doc # , February 2007 [4] Avaya IP Telephony Implementation Guide, May 1, 2006 Product documentation for Juniper Networks products may be found at [5] JUNOS TM Internet Software Service Interfaces Configuration Guide Release 8.4, Part number Rev. 1 [6] JUNOS TM Internet Software Class of Service Configuration Guide Release 8.4, Part number Rev. 2 [7] JUNOS TM Internet Software Network Interfaces Configuration Guide Release 8.4, Part number Rev of 23

23 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. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 23 of 23