Avaya 16-601423 User Manual

Avaya Video Telephony Solution Release 4.0 Networking Guide

16-601423

Issue 3

January 2008

Notice

While reasonable efforts were made to ensure that the infor mation in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases.

For full legal page information, please see the complete document, A vaya Legal Page for Software Documentation, Document number 03-600758.

To locate this document on the website, simply go to

http://www.avaya.com/support

search box. Documentation disclaimer

Avaya Inc. is not responsible for any modifications, addition s, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User.

Link disclaimer

Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or informa tion described or o ff ered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warran ty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site:

http://www.avaya.com/support

Except where expressly stated otherwise, the Product is protected by copyrigh t and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense un der the applicable law.

Avaya support

Avaya provides a telephone number for you to use to report pro blems or t o ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site:

http://www.avaya.com/support

and search for the document number in the

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Overview of Avaya Video Telephony Solution. . . . . . . . . . . . . . . . . . . . 7

What’s New in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Managing Video on Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Classifying Video Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Set Up Your Bandwidth Pools . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Sample Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2: Design and Deployment Checklist. . . . . . . . . . . . . . . 17

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Network and PBX-Network Requirements . . . . . . . . . . . . . . . . . . . . . . 18

Feature Interactions and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . 20

Avaya Communication Manager Global Administration . . . . . . . . . . . . . . 21

Avaya Communication Manager Administration for

Ad-hoc Video Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Avaya Communication Manager Administration for Polycom

Multipoint Stations (VSX and HDX) . . . . . . . . . . . . . . . . . . . . . . . . . 28

Avaya Communication Manager Administration for Polycom MGC Systems. . . 29 Avaya Communication Manager Administration for Polycom RMX Systems . . . 32

Polycom MGC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Polycom RMX Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Polycom VSX System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 37

Avaya IP Softphone (IPSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Avaya IP Softphone Performance Issues . . . . . . . . . . . . . . . . . . . . . . 41

Priority Bandwidth Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

SIP Administration (Global). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

SIP Trunk Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

SIP Station Administration (OPTIM) . . . . . . . . . . . . . . . . . . . . . . . . . 45

SIP Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Issue 3 January 2008 3

Contents

Chapter 3: Setting Up Video Endpoints . . . . . . . . . . . . . . . . . . 47

Required Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configure IP Codec Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configure IP Network Regions . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configure a Station Endpoint for Avaya IP Softphone Release 6.0

and Video Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configure Polycom VSX/HDX Series Video Conferencing Systems

and V500/V700 Video Calling Systems . . . . . . . . . . . . . . . . . . . . . . . 57

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configure a Polycom RMX Series Video Conferencing Bridge Platform . . . . . 65

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configure Ad-hoc Video Conferencing for a Polycom RMX Series

Video Conferencing Bridge Platform . . . . . . . . . . . . . . . . . . . . . . . . 71

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Display Capacity for Ad-hoc Video Conferencing. . . . . . . . . . . . . . . . 77

View Video Conferencing Bridges . . . . . . . . . . . . . . . . . . . . . . . . 77

Configure a Polycom MGC-25 Video Conferencing Bridge Platform

for an Avaya S8300 Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configure Polycom MGC Video Conferencing Bridge Platforms

with Avaya S8500 and S87xx Server . . . . . . . . . . . . . . . . . . . . . . . . 82

Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Signaling Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Group Member Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Outgoing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Configure Ad-hoc Video Conferencing for a Polycom MGC

Video Conferencing Bridge Platform . . . . . . . . . . . . . . . . . . . . . . . . 89

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Display Capacity for Ad-hoc Video Conferencing. . . . . . . . . . . . . . . . 95

View Video Conferencing Bridges . . . . . . . . . . . . . . . . . . . . . . . . 95

4 Avaya Video Telephony Solution Networking Guide

Configure an Avaya Meeting Exchange 5.0.1 S6800 Bridge . . . . . . . . . . . . 96

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Things to Keep in Mind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configure a Polycom MGC Video Conferencing Bridge Platform

as an H.320 Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Route Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

AAR Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

MGC Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Configure a Polycom PathNavigator/SE200 Gatekeeper . . . . . . . . . . . . . . 128

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Configure Video Trunks between Two Avaya Communication Manager Systems 131

Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Monitor the Status of Video Bandwidth Usage . . . . . . . . . . . . . . . . . . . 134

Contents

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Issue 3 January 2008 5

Contents

6 Avaya Video Telephony Solution Networking Guide

Chapter 1: Introduction

Overview of Avaya Video Telephony Solution

The Avaya Video Telephony Solution enables Avaya Communication Manager to me rge a set of enterprise features with Polycom’s videoconferencing adjuncts. It unifies voice over IP with video, web applications, Avaya’s video-enabled IP Softphone, third-party gatekeepers, and other H.323 endpoints. With the Avaya Video Telephony Solution, you can provide video for desktop and group communications.

The Avaya Video Telephony Solution supports video calls on the following products:

● Avaya IP Softphone Release 6.0 and Video Integrator

● Polycom HDX series video conferencing system

● Polycom VSX series video conferencing system

● Polycom V500/V700 video calling system

● Polycom RMX series video conferencing bridge platform

● Polycom MGC video conferencing bridge platform

● Avaya Meeting Exchange 5.0.1 S6800 bridge

● third-party gatekeepers, including Polycom PathNavigator/SE200 gatekeepers

● H.320 gateways

Note:

Note: You must perform a network readiness or network assessment to ensure your

network is capable of supporting the high bandwidth demands of video over IP. You should also consider implementing QoS across your network.

Issue 3 January 2008 7

Introduction

What’s New in this Release

Avaya Video Telephony Solutions Release 4.0 introduces the following new features and enhancements:

● Ability to support Ad-hoc video conferencing with Polycom MGC systems, Polycom RMX

systems, and Avaya Meeting Exchange 5.0.1 systems.

● Ability to support the Polycom RMX series video conferencing bridge platform.

● Ability to support the Polycom HDX series video conferencing system.

● Ability to support SIP video telephony with Avaya DevConnect-approved SIP video

endpoints and Avaya Meeting Exchange 5.0.1 bridges.

Requirements

Video Telephony Solution Release 4.0 requires:

● an S8xx server that is running Avaya Communication Manager software release 5.0.

● Avaya-enabled Polycom MGC Manager software installed and running.

● Avaya licensing keys (for RMX and HDX systems)

8 Avaya Video Telephony Solution Networking Guide

Managing Video on Your Network

Before configuring video endpoints, you should determine how you want to manage video on your network. To control how your bandwidth is used, you must:

1. Determine whether you want to provide some endpoints with video whenever possible.

2. Set up your bandwidth pools.

Classifying Video Users

You can identify two types of video stations: priority video stations and normal video stations. Priority stations have an increased likelihood of receiving bandwidth and may also be allocated a larger maximum bandwidth per call. By having a larger maximum bandwidth per call, priority video stations may receive better quality and more reliable video during calls. Priority video stations will have an increased likelihood of having video on outgoing calls they make. However, they might not receive video on incoming calls they receive from “non-priority” stations due to the following conditions:

Managing Video on Your Network

● No bandwidth is available.

● No “normal” bandwidth is available even though priority bandwidth is available. Since the

call is made by a normal (non-priority) video station, this station would not have access to the priority bandwidth.

These non-priority stations are referred to as “normal” stations. Normal video stations may or may not get video, depending on the available bandwidth.

Issue 3 January 2008 9

Introduction

Set Up Your Bandwidth Pools

Bandwidth pools enable you to control video usage for normal video users and priority video users. You can divide the bandwidth into three pools:

● Audio pool

The audio pool contains bandwidth for all audio calls, including the audio-component of multimedia calls.

● Normal video pool

The normal video pool contains bandwidth for the video portion of a call made by a normal (non-priority) video user. You can set this pool to be shared. When this pool is shared, audio-only calls are allowed to borrow bandwidth from this pool.

● Priority video pool

The priority video pool contains bandwidth that is dedicated to priority video users only. Audio calls and normal video users are not allowed to borrow bandwidth from this pool. However, if all of the priority video pool bandwidth is currently in use, priority video users can borrow bandwidth from the normal video pool, if available.

Sample Scenarios

This section provides some examples of how you could specify the bandwidth settings for your network.

Example 1

In this example, you do not want to allocate any bandwidth for video. You want to configure the network to use IP audio. Figure 1 example.

Table 1: Bandwidth Settings for Example 1

Total Bandwidth

3 Mb 3 Mb 0 Mb 0 Mb No

Audio Bandwidth Pool

shows how you would configure the bandwidth pools for this

Priority Video Bandwidth Pool

Normal Video Bandwidth Pool

Share Normal Video Bandwidth Pool

10 Avaya Video Telephony Solution Networking Guide

Example 2

In this example, your network has unlimited bandwidth. Since all of your users can get as much bandwidth as they need, there is no need to specify priority users. There is only one pool of bandwidth to be shared by audio and multimedia calls. Audio will come from the normal video pool. Figure 2

Table 2: Bandwidth Settings for Example 2

Managing Video on Your Network

shows how you would configure the bandwidth for this example.

Total Bandwidth

3 Mb 0 Mb 0 Mb 3 Mb Yes

Example 3

In this example, you have bandwidth for video only, and you want to reserve some bandwidth for the CEO. All voice calls will be routed another way. You want to reserve half of your bandwidth (1.5 Mb) for priority users. If priority users need more than 50% of the bandwidth, they will be able to use the available bandwidth from the normal video pool. Audio will come from the normal video pool. Figure 3 example.

Table 3: Bandwidth Settings for Example 3

Total Bandwidth

Audio Bandwidth Pool

Priority Bandwidth Pool

shows how you would configure the bandwidth for this

Priority Video Bandwidth Pool

Normal Video Bandwidth Pool

Share Normal Video Bandwidth Pool

3 Mb 0 Mb 1.5 Mb 1.5 Mb No

Issue 3 January 2008 11

Introduction

Example 4

In this example, you do not want to use too much bandwidth on audio. You want to reserve most of the bandwidth for video, but you want to allow a few audio calls to keep costs down. You have a small number priority users. Figure 4 example.

Table 4: Bandwidth Settings for Example 4

shows how you would configure the bandwidth for this

Total Bandwidth

3 Mb 0.9 Mb 0.6 Mb 1.5 Mb No

The settings in table will allow a few audio calls and one or two priority calls depending on the bit rate. After the audio pool runs out of bandwidth, the calls will be forced to take another route since the since the normal video bandwidth pool is not shared. If a priority call occurs when all of the priority video bandwidth is used, it will use any available bandwidth in the normal video bandwidth pool before using bandwidth from the audio bandwidth pool.

Example 5

In this example, you do not want to use any IP bandwidth for audio. You want to use IGAR for audio. All IP bandwidth will be used for video. Figure 5 bandwidth for this example.

Table 5: Bandwidth Settings for Example 5

Total Bandwidth

Audio Bandwidth Pool

Priority Video Bandwidth Pool

Normal Video Bandwidth Pool

shows how you would configure the

Normal Video Bandwidth Pool

Share Normal Video Bandwidth Pool

3 Mb 0 Mb 0 Mb 3 Mb No

Since you have allocated no audio bandwidth, audio calls will fall over to the public-switched telephone network. However, multimedia calls will take audio bandwidth and video bandwidth from the normal video bandwidth pool.

12 Avaya Video Telephony Solution Networking Guide

Example 6

In this example, you want video only for the Polycom VSX systems in the boardroom and in the CEO’s office. Also, this bandwidth must be available always. There are no normal video users. The extensions for the Polycom VSX systems are administered for priority video. Figure 6 shows how you would configure the bandwidth for this example.

Table 6: Bandwidth Settings for Example 6

Managing Video on Your Network

Total Bandwidth

3 Mb 2.1 Mb 0.9 Mb 0 Mb No

Example 7

In this example, the following conditions exist:

● You want to guarantee a certain audio bandwidth and video bandwidth.

● You do not want to share the normal video bandwidth pool because you have very strict

limitations on the bandwidth.

● You do not want to exceed any of the provisioned pools.

Figure 7

Table 7: Bandwidth Settings for Example 7

Total Bandwidth

Audio Bandwidth Pool

Priority Video Bandwidth Pool

Normal Video Bandwidth Pool

shows how you would configure the bandwidth for this example.

Audio Bandwidth Pool

Priority Video Bandwidth Pool

Normal Video Bandwidth Pool

Share Normal Video Bandwidth Pool

3 Mb 0.9 Mb 0 Mb 2.1 Mb No

Issue 3 January 2008 13

Introduction

Example 8

In this example, the following conditions exist:

● You want to guarantee a certain audio bandwidth and video bandwidth.

● You do not want to share the normal video bandwidth pool because you have very strict

● You do not want to exceed any of the provisioned pools.

● You want to specify a proportion of priority video users.

limitations on the bandwidth. By not sharing the normal video bandwidth pool, you guarantee:

- a minimum level of video bandwidth

- audio-only calls cannot impact the normal video bandwidth pool

Figure 8

shows how you would configure the bandwidth for this example.

Table 8: Bandwidth Settings for Example 8

Total Bandwidth

Audio Bandwidth Pool

Priority Video Bandwidth Pool

Normal Video Bandwidth Pool

Share Normal Video Bandwidth Pool

3 Mb 0.9 Mb 0.6 Mb 1.5 Mb No

In this example, 600 Kbit is reserved for priority video. A priority video user will be able to use the normal video pool if the priority pool is all used and bandwidth exists in the normal video pool.

14 Avaya Video Telephony Solution Networking Guide

Example 9

In this example, the following conditions exist:

● You want to share the normal video bandwidth pool.

● You have no priority video users.

Managing Video on Your Network

Figure 9

Table 9: Bandwidth Settings for Example 7

Total Bandwidth

3 Mb 0.9 Mb 0 Mb 2.1 Mb Yes

Since there are no priority video users, the normal video bandwidth pool is the entire video bandwidth pool. With no priority users and the bandwidth being shared, all of the bandwidth could be used as audio.

Example 10

In this example, the following conditions exist:

● You want to guarantee a certain audio bandwidth and video bandwidth.

● You want to share the normal video bandwidth pool.

● You have priority video users.

shows how you would configure the bandwidth for this example.

Audio Bandwidth Pool

Priority Video Bandwidth Pool

Normal Video Bandwidth Pool

Share Normal Video Bandwidth Pool

Figure 10

shows how you would configure the bandwidth for this example.

Table 10: Bandwidth Settings for Example 7

Total Bandwidth

Audio Bandwidth Pool

Priority Video Bandwidth Pool

Normal Video Bandwidth Pool

Share Normal Video Bandwidth Pool

3 Mb 0.9 Mb 0.6 Mb 1.5 Mb Yes

In this example, 600 Kbit of bandwidth is reserved for priority video users. Audio cannot use this bandwidth. The maximum available bandwidth for au dio is 2.4 Mb. (In this case, there wou ld be no normal video bandwidth available.) The maximum available bandwidth for priority video users is 2.1 Mb.

Issue 3 January 2008 15

Introduction

16 Avaya Video Telephony Solution Networking Guide

Chapter 2: Design and Deployment Checklist

Overview

The chapter provides a checklist that will help you design and deploy the Avaya Video Telephony Solution R4.0.

Note:

Note: For the latest firmware video compatibility matrix, go to

www.avava.com/support. and access Video Telephony Solution.

Issue 3 January 2008 17

Design and Deployment Checklist

Network and PBX-Network Requirements

Question 1: Has a multimedia QoS policy been designed and deployed?

 Yes.

No. Avoid best effort treatment of video. Avaya IP Softphone (IPSP), Polycom MGC,



Polycom RMX, and Polycom VSX all support QoS for video. See the checklist in section 11.0 of the white paper from Polycom Global Services titled “Supporting Real-time Traffic: Preparing Your IP Network for Video Conferencing.”

Question 2: Has a default enterprise Maximum Call Rate been selected?

Note:

Note: Use change ip-codec-set and enable “Allow Direct IP Multimedia” on page 2 of

the form. In Avaya Communication Manager Release 4.0, there are two options: Normal users and Priority users.



Yes.



No. Recommend initial deployment with Maximum Call Rate of 384 Kbps.

Note:

Note: Keep in mind the following:

- Allow for 20% for IP protocol overheads.

- High definition room systems support call rates of 4 Mbps.

Question 3: Is inter-PBX network connectivity less than 150 ms end-to-end one-way delay and less than 1% packet loss at all times?

 Yes.



No. Expect slower call establishment. Compared to audio-only calls, multimedia calls have

a greater number of round-trip signaling messages by a factor of 5.

18 Avaya Video Telephony Solution Networking Guide

Network and PBX-Network Requirements

Question 4: Does the VPN connection for Avaya IP Softphone have less than 150 ms one-way delay to Avaya Communication Manager, is packet loss less than 1%, and is jitter less than 20 ms?

 Yes.



No. Avaya IP Softphone does not support automatic bit rate downgrades on packet loss

feedback, nor does it perform ping tests for video assessment. The user must reduce call rate and reattempt the call to achieve the best video experience for the network conditions. In worst-case conditions, users may experience video disablement by Avaya Communication Manager for the call duration due to excessive video update requests.

Question 5: Are there video call scenarios that would cross more than three Avaya Communication Manager systems?

Note that a limitation of the solution is that shuffling to direct-ip is blocked for Avaya Communication Manager systems that are pushing tandem trunk-to-trunk multimedia calls. Hairpinning is allowed.



Yes. Administer additional trunks to minimize the use of tandem Avaya Communication

Manager systems, thereby reducing video-update latency. Avoid the use of slow CPU servers (for example, S8700) in tandem scenarios, since video signaling across many Avaya Communication Manager systems is exponentially more expensive than audio-only calls.

 No.

Issue 3 January 2008 19

Design and Deployment Checklist

Feature Interactions and Limitations

Question 1: Is Call Recording, Whisper Page, or Service Observing going to occur on video calls?

 Yes. Expect audio-only calls. It is working as designed. From Avaya Communication Manager Release 5.0, the ad-hoc video conferencing feature may resolve some of these limitations.

 No.

Question 2: Is “transfer to MGC/RMX” being used for ad-hoc conferencing?

 Yes. Avoid scenarios where a user attempts to transfer to a meeting room where tandem Avaya Communication Manager systems link the user to the Polycom MGC/RMX. Multiple Avaya Communication Manager shuffling (if allowed) may legitimately block the transfer. A reattempted transfer should succeed.

 No.

Question 3: Should a customer with a network of PBXs trunked together who will want to deploy ad-hoc video conferencing with Polycom RMXs in the future deploy those RMXs in a distributed manner?

 Yes. Ad-hoc conferencing will require at least one Polycom RMX per active Avaya Communication Manager system to support future ad-hoc video conferencing via the Conference button.

 No.

Question 4: Have additional media resources been allocated for Avaya Communication Manager systems that are used for tandem multimedia calls?

In a typical hub and spoke arrangement of Avaya Communication Manager systems, the core PABX that is doing the tandem calls between remote PABX systems should have additional media resources deployed as shuffling to direct-ip is blo cked for multimedia calls.

 Yes.



No. Expect higher utilization of media resources on tandem Avaya Communication

Manager systems.

20 Avaya Video Telephony Solution Networking Guide

Avaya Communication Manager Global Administration

Question 1: Are the video capacities on system-parameters customer-options, page 2 configured correctly?

Maximum Video Capable H.323 Stations should be 1 x the number of single point Polycom VSX systems.

Maximum Video Capable IP Softphones should be equal to the number of video softphones.

Maximum Administered Ad-hoc Video Conferencing Ports should be based on the number of RMX systems and the maximum port count capability for the RMX systems.

 Yes.



No.

Question 2: Are the fields on system-parameters customer-options, page 4 configured correctly?

“Enhanced Conferencing?” = y “IP Trunks?” = y “IP Stations?” = y “ISDN-BRI Trunks?” = y “ISDN-PRI?” = y “Multimedia Call Handling (Basic)?” = n “Multimedia Call Handling (Enhanced)?” = n

 Yes.



No.

Issue 3 January 2008 21

Design and Deployment Checklist

Question 3: Are the fields in ip-network-region, page 1 configured properly for all regions used by video endpoints?

“Intra-region IP-IP Direct Audio” = y “Inter-region IP-IP Direct Audio” = y

Note:

Note: For network regions containing third-party gatekeepers, these values must be set

to No for direct audio because shuffling may not be supported by all third-party endpoints.

 Yes.

No. Note the actual settings in this page and find out the customer’s reasons/requirements



for these options to be disabled. Video endpoints do not need to be shuffled to resume video. Third-party endpoints will support basic call setup only.

Question 4: Are the fields in ip-network-region, page 2 configured properly for all regions used by video endpoints?

H.323 SECURITY PROFILES must contain any-auth for Polycom VSXs to authenticate. challenge is used by Avaya IP Softphone. pin-eke is used by Polycom VSX. any-auth encompasses both challenge and pin-eke.

 Yes.



No. Expect registration failures.

Question 5: Is the ip-codec-set form configured properly?

Review all codec-sets used across the enterprise including the codec-sets used by media processors, trunks, and stations as well as inter-region codec sets. Has the enterprise selected a single version of G.711 across all Avaya Communication Manager systems globally?

 Yes.



No. Simplify the codec-set administration by selecting one variant of G.711 across the entire

network of Avaya Communication Manager systems. A single variant can be used globally. Otherwise expect codec mismatch errors and call drops between Avaya Communication Manager systems. Multimedia signaling uses H.245, which is more sensitive to codec administration than audio-only repeat-fast start signaling.

22 Avaya Video Telephony Solution Networking Guide

Avaya Communication Manager Global Administration

Question 6: Is the intra-region audio administration correct in the ip-codec-set form?

Review all IP codec-sets used across the enterprise including the IP codec-sets used by media processors, IP trunks, and IP stations.

Wide-band codecs (for example, SIREN series, G.722.1 series, and G.722-64k) should appear first and are supported for shuffled Polycom VSX calls only across a single Avaya Communication Manager system.

G.711 should appear next. Then follow with G.729/G.729A codec, etc.

 Yes.

No.



Question 7: Is the inter-region audio administration correct in the ip-codec-set form?

Review all codec-sets used across the enterprise including the codec-sets used by media processors, IP trunks, and IP stations.

Are there bandwidth issues? If no, then re-use the one codec set also in use for intra-region. If there are bandwidth issues, specify a low bandwidth codec first followed by one G.711

codec. If there are severe bandwidth issues, customers can choose to leave out G.711 and also ensure video is disabled.

 Yes.



No.

Question 8: Is the audio administration for Polycom VSXs correct in the ip-codec-set form?

Review all codec-sets used across the enterprise including the codec-sets used by media processors, trunks, and stations.

If codec-sets used for stations include G.729, then a new network-region and codec must be defined for use by Polycom VSXs. VSX stations do not support G.729 but do support G.729A.

Note that media encryption is not supported by VSX stations.

 Yes.



No. Expect call setup failure. This is a work around for a VSX signaling issue.

Issue 3 January 2008 23

Design and Deployment Checklist

Question 9: Is the video administration correct in the ip-codec-set form?

Review page 2 of all the codec-sets to be used by video stations and video trunks. Is “Allow Direct-IP Multimedia?” set to yes? Is “Maximum Call Rate for Direct-IP Multimedia” set appropriately considering whether the

codec-set is used for inter-region where there are bandwidth issues.?

 Yes.



No. Expect audio only calls.

Question 10: Is ip-network-region inter-region video bandwidth management used across WAN links?

Ensure appropriate video total bandwidth limits on ip-network-region page 3 are set correctly.

 Yes.



No. Expect low-quality video. Avaya recommends replacement of CAC via trunk-member

counting with cumulative bandwidth management. Note that unlike audio, Avaya Communication Manger’s bandwidth management feature does not take into account the variable video headers. Allow 20% overheads. Best practice recommends video applications should consume no more than 35% of the total WAN bandwidth.

Question 11: Is video station administration correct in the station form?

First refer to this guide or the quick setup guide. Ensure “IP Video?” is yes. Ensure “IP Video Softphone?” is yes. On page 2, ensure “Direct IP-IP Audio Connections?” is yes.

 Yes.



No. Expect audio only calls.

24 Avaya Video Telephony Solution Networking Guide

Avaya Communication Manager Global Administration

Question 12: Is signaling group administration appropriate for video support?

Review the signaling groups used between Avaya Communication Manager systems, to Polycom MGCs/RMXs, and to PathNavigators. Also refer to this guide or the quick setup guide.

Ensure “IP Video?” is yes. Ensure “Direct IP-IP Audio Connections?” is yes. Ensure “Calls Share IP Signaling Connection?” is No, though this setting may be Yes

between Avaya Communication Manager systems. Does the network-region value correspond to an ip-codec-set that supports video?

 Yes.



No. Expect audio only calls.

Question 13: Does the network-region value in the change signaling-group form correspond to an ip-codec-set that supports video?

 Yes.



No. Expect audio only calls.

Question 14: Is DSCP tagging provisioned correctly?

Ensure that DSCP parameters are provisioned for the network region to which endpoints are registered.

For Avaya Communication Manager Release 4.0: Polycom VSX 8.5.3 onwards and Polycom MGC 8.0.1 onwards will automatically obtain DSCP parameters as configured in the network region. All other endpoints should have DSCP parameters set manually to the same values to which Avaya Communication Manager is set.

 Yes.



No. This is not best practice.

Issue 3 January 2008 25

Design and Deployment Checklist

Question 15: For shared control of IP sets, is the network region of the Avaya IP Softphone the same as the IP set?

Use the change ip-network-map command to ensure that the Avaya IP Softphone is mapped to the same network region as the IP set.

Note:

Note: For shared control when using video, the only option supported is via the server .

Do not try using the via the phone (CTI) option.

 Yes.  No. Do not do this. This is not supported, so expect undefined results. When using shared

control with video, the network region used for Avaya IP Softphone must match the network region used by the IP set. For Avaya Communication Manager Release 5.0 and later, this will not be a limitation.

26 Avaya Video Telephony Solution Networking Guide

Avaya Communication Manager Administration for Ad-hoc Video Conferencing

Question 1: Are the Ad-hoc conferencing video capacities on system-parameters customer-options, page 2 configured correctly?

Ensure the “Maximum Administer Ad-hoc Video Conferencing Ports” is set to the number of ports available for Ad-hoc video conferencing.



Yes.

 No.

Question 2: Has a Class of Service (COS) been assigned with “Ad-hoc Conferencing” enabled?

 Yes.  No. Use the change COS command to enable Ad-hoc Video Conferencing.

Question 3: Has a video bridge been added using the add video-bridge command?

 Yes.

No. Use the add video-bridge command to add Polycom MGC or Polycom RMX details for



Ad-hoc video conferencing.

Issue 3 January 2008 27

Design and Deployment Checklist

Avaya Communication Manager Administration for Polycom Multipoint Stations (VSX and HDX)

Question 1: Does each extension for a given multipoint endpoint have the same password configured on the station form?

For a multipoint station, each extension must have the same password. However, this password does not need to match the password for other multipoint stations.



Yes.

 No. Use the change station command to set the “Security Code” entries to match. If these entries do not match, Avaya Communication Manager may reject registration by the station or confine it to one extension only.

Question 2: Has “Hunt-to Station” been configured to a circular hunt on the station form?

Configuring “Hunt-to Station” to a circular hunt enables Avaya Communication Manager to find the unused extension when dialing a multipoint station that is already in a call. This allows you to always call the main extension for the multipoint station.

Yes.



 No. Use the change station command to set “Hunt-to Station” so that each station hunts to

the next one, and the last station hunts to the first one.

Question 3: Has “Coverage” been configured on the station form?

The coverage feature has priority over the hunt-to feature and will interfere with it. The first call to the main Polycom VSX/HDX extension will succeed, but other calls will be busy (instead of hunting correctly). Setting "Station Hunt Before Coverage?" to "y" will also work but has system-wide consequences.

 Yes. U se the change station command and set “Coverage” to blank.



No.

28 Avaya Video Telephony Solution Networking Guide

Avaya Communication Manager Administration for Polycom MGC Systems

Question 1: Polycom MGCs with multiple IP boards in conjunction with S87xx servers with multiple CLAN boards in regions require administration planning. Has this guide or the quick setup guide been used and understood?

 Yes.  No. Complex signaling group and trunk group administration is required. Follow the rules in

this guide and the quick setup guide. This solution offers a number of high availability options. CLAN board failures and IP board failures can be survivable. Incorrect administration can cause intermittent service.

Question 2: In Avaya Communication Manager Release 4.0, do signaling groups to Polycom MGCs have “Layer 3 Tests?” set to No?

 Yes.  No. Expect signaling groups to go out of service (OOS).

Question 3: Is the outgoing trunk group to the Polycom MGC configured correctly in the change trunk-group form?

On Trunk group page 1, “Direction” must be outgoing. On Trunk group page 1, “Outgoing Display” may be y. This is helpful for diagnostics. On Trunk group page 2, “Disconnect Supervision – Out?” must be y to allow transfer to the

MGC. On Trunk group page 3, “Send Calling Number” must be set to allow the MGC to resolve

calling party against the participant list on MGC conferences when pre-administered with participants.

 Yes.



No. Expect trunk transfer failure. Expect wasted resources on the MGC.

Issue 3 January 2008 29

Design and Deployment Checklist

Question 4: Is the incoming trunk group for the Polycom MGC configured correctly in the change trunk-group form?

On Trunk group page 1, “Direction” must be incoming. On Trunk group page 2, “Disconnect Supervision – In?” must be y to allow transfer of

MGC-initiated calls to other trunks.

 Yes.



No. Expect trunk transfer failure.

Question 5: Is there only one incoming trunk group per Polycom MGC?

 Yes.



No. Read this guide or the quick setup guide.

Question 6: Does the Polycom MGC have additional IP boards?

 Yes. For board redundancy, administer a second outgoing trunk group for the second to “nth” IP boards.

No. Only one outgoing trunk group is required.



Question 7: Is the outgoing signaling group to the MGC configured correctly?

“LRQ Required?” must be y. “Near end Listen Port” must be 1719. “Far end Listen Port” must be 1719. “Trunk Group for Channel Selection” must be clear.

 Yes.



No. Expect call failures or intermittent call failures, or shuffling that shuts down video.

30 Avaya Video Telephony Solution Networking Guide

+ 106 hidden pages