Avaya Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 User manual

Brand: Avaya

Model: Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000

Category: Rack accessories

Type: User manual

Nortel Mobile Communication 3100

Mobile Communication 3100

and Communication Server 1000

Solution Integration Guide

Release: 3.0

Document Revision: 01.04

www.nortel.com

NN49000-315

Nortel Mobile Communication 3100

Release: 3.0

Publication: NN49000-315

Document release date: 19 June 2009

While the information in this document is believed to be accurate and reliable, except as otherwise expressly

agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF

ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are

subject to change without notice.

Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

Contents

New in this release 5

Features 5

Other changes 5

Introduction 7

MC 3100 and CS 1000 deployment overview 9

CS 1000 engineering for MC 3100 9

CS 1000 Source Based Routing 13

SIP Gateway CLID Parameters configuration 14

Mobility Home Location Code 15

Data Access Planning 16

ECM overview 16

CS 1000 data access considerations 17

Licensing requirements 17

Dialing plans and telephone numbers 18

Service DN 20

Universal Extensions 20

Caller ID table 21

Device Handoff key configuration in PBX telephones 21

CallPilot MWI Configuration 25

MC 3100 and CS 1000 integration 27

Prerequisites 29

Establishing the system baseline 29

Checking the CS 1000 release from Element Manager 31

Checking the CS 1000 release from the command line 31

Integration worksheet 32

MCG 3100 configuration 39

CS 1000 configuration 41

CS 1000 licensing 43

Verifying package requirements 43

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

Verifying PCA requirements 44

Configuring ISM requirements 45

Printing system license limits 45

NRS configuration 47

Configuring gateway endpoints on the NRS 48

Adding an NRS Routing rule 49

Adding a User Endpoint 51

CS 1000 configuration for client support 55

Configuring features and keys 56

Configuring the Device Handoff key 57

Configuring the TSC steering codes 58

Configuring dial plan parameters 58

Configuring the Digit Manipulation Index 60

Configuring a Route List Index 60

Configuring Call Forward No Answer 61

MCC 3100 configuration 63

Autoconfiguration settings 64

Validate deployment 65

Validating MCG 3100 registration 65

Validating MCC 3100 for BlackBerry communication 66

Validating MC 3100 and CS 1000 deployment 66

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

New in this release

The following sections detail what’s new in Nortel Mobile Communication

3100 and Communication Server 1000 Solution Integration Guide

(NN49000-315) for Mobile Communication 3100 (MC 3100) Release 3.0.

•

"Features" (page 5)

•

"Other changes" (page 5)

Features

For information on the features, see Nortel Mobile Communication 3100

Fundamentals (NN42030-109).

Other changes

This document is new for MC 3100 Release 3.0.

MC 3100 Release 3.0 supports Nortel Communication Server 1000

Release 5.5.

Revision history

June 2009 Standard 01.04. This document is up-issued to add technical information in

Table 3.

April 2009 Standard 01.03. This document is up-issued to add a new section called

"CallPilot MWI Configuration" and to delete the following sections:

• Installing the ECM MCG 3100 software

• Adding the MCG 3100 as an element from the primary ECM

• Upgrading to a different network framework

• Accessing the MC 3100 Web Console from the ECM

January 2009 Standard 01.02. This document is up-issued to add a new section called "SIP

Gateway CLID Parameters configuration".

December

2008

Standard 01.01. This document is issued to support Nortel Mobile

Communication 3100 Release 3.0 and Nortel Communication Server 1000

Release 5.5.

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

6 New in this release

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

Introduction

This document describes the interworking of the Mobile Communication

3100 (MC 3100) and Communication Server 1000 (CS 1000). The

MC 3100 consists of the Mobile Communication Gateway 3100

(MCG 3100) and three clients: Nortel Mobile Communication Client 3100

(MCC 3100) for BlackBerry, MCC 3100 for Nokia, and MCC 3100 for

Windows Mobile.

For information on the MC 3100 solution, see Nortel Mobile

Communication 3100 Fundamentals (NN42040-109), Nortel Mobile

Communication 3100 Planning and Engineering (NN42030-200), and the

Nortel Mobile Communication 3100 Technology Transfer (located in the

MC 3100 product area of w

ww.nortel.com).

In this document, the term Enterprise Communication Server (ECS) refers

to the Nortel Communication Server 1000.

Attention: This document assumes a detailed knowledge of

Communication Server 1000 configuration.

Navigation

•

"MC 3100 and CS 1000 deployment overview" (page 9)

• "MC 3100 and CS 1000 integration" (page 27)

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

8 Introduction

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

MC 3100 and CS 1000 deployment

overview

This section describes the deployment of the Mobile Communication 3100

(MC 3100) with the Communication Server 1000 (CS 1000).

For information on the planning aspects related to the MC 3100

and CS 1000, see Nortel Mobile Communication 3100 Planning and

Engineering (NN42030-200), which covers the following topics:

• Mobile Communication Client 3100 (MCC 3100) deployment

considerations

• Dialing plans and telephone numbers

•

MC 3100 high availability support

•

MC 3100 port tables

• CS 1000 deployment considerations

Navigation

•

"CS 1000 engineering for MC 3100" (page 9)

•

"Data Access Planning" (page 16)

•

"Licensing requirements" (page 17)

•

"Dialing plans and telephone numbers" (page 18)

•

"Service DN" (page 20)

• "CallPilot MWI Configuration" (page 25)

• "Universal Extensions" (page 20)

• "Device Handoff key configuration in PBX telephones" (page 21)

CS 1000 engineering for MC 3100

The MCC 3100 for BlackBerry, MCC 3100 for Nokia, MCC 3100 for

Windows Mobile, and MCG 3100 depend on the following CS 1000

components:

• Call server

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

10 MC 3100 and CS 1000 deployment overview

— Each user requires one Universal Extension (UEXT). Each UEXT

supports the SIP interface on the client. Configure the UEXT with

the Fixed Mobile Convergence Line (FMCL) subtype.The FMCL

subtype requires an Incremental Software Management (ISM)

independent of the Mobile Extension (MOBX) subtype.

— SIP Access Port license

•

SIP Gateway, operating on the VxWorks Signaling Server platform

•

SPS, using the NRS-SPS on the Linux-based NRS.

— Configure each MCG 3100 as a Dynamic Gateway Endpoint with

an endpoint name. Configure the Dynamic Gateway Endpoint with

authentication turned off.

— Each client requires the configuration of an NRS-SPS User

Endpoint (UE). Clients use the UE for user name and password

information, not for SIP routing. Therefore, the NRS-SPS must

never match a destination number against the client UEs (including

the corresponding UEXT Target DN).

The Direct Inward Dial (DID) number for the Dial in Service DN terminates

on the MCG 3100.

Configure the CS 1000 with a Mobility Home Location Code (HLOC) to

support the client. The UEXT target DN uses the HLOC as a prefix to

identify mobile users. The HLOC is a unique digit sequence that does

not conflict with the CS 1000 Universal Dialing Plan (UDP), Coordinated

Dialing Plan (CDP), and routing configuration.

The Multiple Access Directory Number (MADN) contains the UEXT and

the Multiple Appearance Directory Number Redirection Prime (MARP)

Terminal Number. The MARP contains the CLID and NCOS definitions.

For more information, see Features and Services Fundamentals

(NN43001-106).

The CS 1000 NRS-SPS supports the Source Based Routing (SBR)

feature. The SBR feature allows the CLID, NCOS, and dial plan for

the MCG 3100 to align with the CS 1000 as the home call server. For

information about Source Based Routing (SBR), see "CS 1000 Source

Based Routing" (page 13).

Figure 1 "Client with CS 1000 and UDP" (page 11) shows an example of

clients using a CS 1000 UDP.

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

CS 1000 engineering for MC 3100 11

Figure 1

Client with CS 1000 and UDP

Figure 2 "Client with CS 1000 and CDP" (page 12) shows an example of

clients using a CS 1000 CDP.

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

12 MC 3100 and CS 1000 deployment overview

Figure 2

Client with CS 1000 and CDP

The UEXT configuration requirements are shown in the following table.

Table 1

UEXT configuration parameters

Parame

ter

Description UDP example

CDP example

Subtype UEXT subtype; must be

FMCL

FMCL FMCL

primary

On key 0; this determines

the user’s published

addresses for both private

electronic switched network

(ESN) and public direct

inward dial (DID).

5335

contributes to an ESN of

3435335 and a DID of

+16139615335

5335

contributes to an ESN of

3435335 and a DID of

+16139615335

target

Extends the user’s

incoming calls to mobile

clients that are accessible

trough the SIP domain

65553435335 888885335

On the NRS-SPS, configure the UE attributes as described in Table 2

"User Endpoint attributes" (page 13).

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

CS 1000 engineering for MC 3100 13

Table 2

User Endpoint attributes

Parameter Description Example

User name User’s Electronic Switched Network (ESN)

number

3435335

Tandem gateway

endpoint name

Endpoint name.

Do not configure this parameter

L0 DN Based on the user’s directory number (DN).

Cannot match anything in the Coordinated

Dialing Plan or unqualified dialing plan. Can

be the last digit of the Mobility HLOC with the

User’s ESN DN.

53435335

L1 DN prefix not required

Authentication

enabled

Determines if Authentication is required. Authentication on

Authentication

password

The password for authentication

xxxxxxxx

For more information about UEXTs, see Features and Services

Fundamentals – Book 6 of 6 (NN43001-106-B6). For information about

SIP Gateway configuration, see IP Peer Networking Installation and

Commissioning (NN43001-313).

CS 1000 Source Based Routing

CS 1000 Source Based Routing (SBR) occurs when the request Uniform

Resource Indicator (URI) of the INVITE message sent from the Mobile

Communication Client 3100 (MCC 3100) or the MCG 3100 contains the

tag x-nt-net-feature=x-nt-home. For example, the following request URI

triggers SBR:

INVITE sip:[email protected];x-nt-sip-line-service;x-nt-net-featur

e=x-nt-home SIP/2.0

SBR causes the CS 1000 Network Routing Service-SIP Proxy Service

(NRS-SPS) to route the call attempt (INVITE) to the P-Asserted-Id in the

SIP INVITE instead of using the Request URI.

Using SBR means that all calls from a SIP user route to the home call

server for origination, allowing the call server to apply features such as

Calling Line ID (CLID) and Network Class of Service (NCOS) to SIP calls.

In the MCG 3100, use the User Prefix/Phone-context for Call origination

field to configure SBR. For information, see Nortel Mobile Communication

3100 Administration and Security (NN42030-600).

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

14 MC 3100 and CS 1000 deployment overview

SIP Gateway CLID Parameters conﬁguration

The SIP Gateway CLID parameters are used to adjust the format

of telephone numbers for incoming call appearances. For Mobile

Communication 3100 (MC3100) these settings impact the format of

numbers that appear on the incoming call popup on the MCC3100 client.

Figure 3

SIP GW CLID Parameters

For all public calls (subscriber (for example, NXX in North America),

national (for example, NPA in North America), or international) E.164 fully

qualified numbers are used to represent the caller. This is made possible

through the use of the following parameters:

• Country Code

• Area Code

• Subscriber/Number of Digits to strip

• Subscriber/Prefix to insert

• National/Number of Digits to strip

• National/Prefix to insert

The E.164 format of subscriber calls (for example, NXX in North America)

is:

+<countrycode><area code><subscriber number>.

The parameters Subscriber/Number of digits to strip and prefix to insert are

used to modify the format of subscriber numbers presented from the PSTN

due to region specific requirements.

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

Mobility Home Location Code 15

The E.164 format of national calls (for example, NPA in North America) is:

•

+<countrycode><national number>.

The parameters National/Number of digits to strip and prefix to insert are

used to modify the format of national numbers presented from the PSTN

due to region specific requirements.

Parameter: Country Code

This parameter defines the country code to be used in CLID generation.

Parameter: Area Code

This parameter defines the area code to be used in CLID generation.

Parameter: Subscriber/Number of Digits to strip

For incoming subscriber (NXX) calls this parameter defines the number of

digits to strip from the incoming phone number prior to conversion to E.164

format.

Parameter: Subscriber/Prefix to insert

For incoming subscriber (NXX) calls this parameter defines the prefix to

insert after stripping any digits necessary from the incoming phone number

prior to conversion to E.164 format.

Parameter: National/Number of Digits to strip

For incoming national (NPA) calls this parameter defines the number of

digits to strip from the incoming phone number prior to conversion to E.164

format.

Parameter: National / Prefix to insert

For incoming national (NPA) calls this parameter defines the prefix to

insert after stripping any digits necessary from the incoming phone number

prior to conversion to E.164 format.

Mobility Home Location Code

Before configuring and deploying the MCC 3100 solution, the administrator

determines the Mobility Home Location Code (HLOC) for the MCG 3100.

The Mobility HLOC is a digit prefix used to prefix to all calls that will be

sent to the MCG 3100. This includes the target DN number of all UEXTs

for MC 3100 users as well as the service DN calls from MCC 3100 clients.

The Mobility HLOC provides a unique digit sequence within the SIP

domain to route calls to a specific MCG 3100 that does not conflict with the

existing dial plan and routing configuration for CDP and UDP numbers. If

the UEXT target DN did not have this prefix to distinguish MCC 3100 calls,

the UEXT extended SIP calls would loop back to the UEXT.

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

16 MC 3100 and CS 1000 deployment overview

Mobility HLOCs have the following requirements:

•

One Mobility HLOC is required per gateway.

•

On the call server you must configure

— The dial plan to send all calls with this prefix to the NRS.

— All UEXT’s for MCC 3100 users must have a target DN with

the prefix of the MCG 3100 to which their MCC 3100 client is

registered.

— The incoming service DN call must have its digits manipulated so

that the PSTN number dialed for the service DN is mapped to a

number prefixed by the Mobility HLOC. This mapping will trigger the

NRS to send this call to the MCG 3100 and the MCG 3100 will strip

this prefix as with any other Mobility HLOC prefixed call to reveal

the service DN configured on the MCG 3100.

•

The NRS must have a routing rule to send all calls with this prefix to

the MCG 3100.

• The Mobility HLOC is configured on the MCG 3100 in the User Prefix

for Call Termination field.

Data Access Planning

•

"ECM overview" (page 16)

•

"CS 1000 data access considerations" (page 17)

ECM overview

The ECM provides a common management environment for Nortel

products. The ECM user interface communicates with the configured

products to manage and administer the product.

The ECM software is packaged with the Communication Server 1000

software. ECM supports access using hypertext transport protocol (HTTP)

and HTTP secure (HTTPS).

ECM requires the following ports to be open on the managed products:

• 80—for nonsecure (HTTP) access

•

443—for secure (HTTPS) access

When firewalls exist between the ECM and the managed products, the

following ports must be opened on the firewall:

• Transmission Control Protocol (TCP) port 5061 for SIP Transport Layer

Security (TLS) communication

• User Datagram Protocol (UDP) port 500 for Internet Protocol Secure

(IPSec) Internet Key Exchange (IKE)

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

Licensing requirements 17

• Protocol 50 for IPSec Encapsulated Payload Protocol (ESP)

•

Internet Control Message Protocol (ICMP) port for ping

•

TCP port 22 for Secure shell (SSH)

•

TCP port 80 for HTTP

• TCP port 443 for HTTPS

• TCP port 58080 for SAML

• TCP port 58081 for SAML secure mode

•

TCP port 389 for Lightweight Directory Access Protocol (LDAP)

• TCP port 646 or LDAP

•

TCP port 15080 for X Message (XMSG)

For more information on the ECM, see Enterprise Common Manager

Fundamentals (NN43001-116).

CS 1000 data access considerations

The MCG 3100 requires data access to the TLAN of the CS 1000. The

MCG 3100 uses the CS 1000 SPS as the SIP Signaling Proxy. The media

for all calls to and from MCC 3100 clients is anchored on the MCG 3100.

The MCG 3100 will accept or transmit RTP to any IP endpoint within the

enterprise (e.g. Media Cards, Other SIP clients, IP sets).

Example

If an UNISTIM set calls a user answering through the MCC 3100 on the

mobile phone the RTP for the active call will be between the MCG 3100

and IP set directly and then forwarded from the MCG 3100 to the CS 1000

media gateway (for the trunk call to the mobile phone)

Careful consideration is required based on the data network and security

requirements of the Enterprise to allow the public internet traffic to

reach the MCG 3100 from the clients while at the same time giving the

MCG 3100 access to the TLAN of the CS 1000 for SIP and RTP.

Licensing requirements

Communication Server licensing requirements

• Requires CS 1000 Release 5.5

• Uses SIP Access Port Licenses for CS 1000 SIP infrastructure support

• Requires 1 Universal Extension (UEXT) for each MCC 3100 user. The

UEXT is configured with the Fixed Mobile Convergence Line (FMCL)

subtype.

MCC 3100 licensing requirements

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

18 MC 3100 and CS 1000 deployment overview

• Each MCC 3100 client requires a license.

• Each license key can only be used once per user.

• The MCC 3100 licenses are installed on the MCG 3100.

The MCG 3100 allocates the license on a first come, first served basis as

the MCC 3100 registers with the MCG 3100.

• There is no requirement to distribute licenses to each end user.

• The MCG 3100 administrator can revoke licenses on a per user basis,

if necessary, to reclaim user licenses.

Dialing plans and telephone numbers

MC 3100 supports telephone numbers in the following formats

•

Dial strings, where the user enters all the digits to be dialed. Examples

of dial strings include 2356, 63432356, 93432356 and 3432356.

• E.164 Fully Qualified International Numbers, where telephone

numbers start with the plus (+) symbol. E.164 Fully Qualified

International Numbers are also known as "plus numbers". Examples

of Fully Qualified International Numbers include +16131234567 and

+31123456789.

The dial plan available from MC 3100 should be the same as the dial plan

for a desk telephone. That is, if the user has a desk telephone and an

MCC 3100 device, the dial plan should be the same.

MC 3100 users should use the E.164 Fully Qualified International Numbers

for all stored Public Switched Telephone Network (PSTN) numbers in

address books and mobile device applications. By using this format, the

numbers can be dialed from any region or country, within the wireless

network or from the communication server.

The E.164 Fully Qualified International Numbers ensure that users do not

need to be concerned about dial prefixes or long distance codes. The

network determines how to place the call, based on the user’s location and

network connection.

When the user dials an E.164 Fully Qualified International Number, the

communication server puts the number in the request Uniform Resource

Indicator (URI) of the SIP INVITE message in the following format

sip: +CCCXXXXXXXX@domain; user=phone.

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

Dialing plans and telephone numbers 19

When using the ECS, configure the CNTC, NATC, and INTC parameters

in LD 15 to support E.164 Fully Qualified International Numbers. These

parameters ensure that fully qualified numbers within the same country

are dialed as national numbers, and international numbers are prefixed

correctly.

Example 1 (Switzerland)

ECS is Nortel Communication Server 1000 (CS 1000)

AC1=0, CNTC=41, NATC=0, INTC=00

Call to a number within Switzerland

A user initiates a call to a contact with the phone number +41123456789.

The URI incoming for the SIP INVITE for the call is

sip:[email protected];user=phone

CS 1000 digit processing strips the CNTC and adds <AC1 + NATC> to

produce 00123456789

Call to a number outside Switzerland

A user initiates a call to a contact with the phone number +14161234567.

The URI incoming for the SIP INVITE for the call is

sip:[email protected];user=phone

CS 1000 digit processing adds <AC1 + INTC> to produce

00014161234567

Example 2 (North America)

ECS is CS 1000

AC1=6, CNTC=1, NATC=1, INTC=011

Call to a number within North America

A user initiates a call to a contact with the phone number +14161234567.

The URI incoming for the SIP INVITE for the call is

sip:[email protected];user=phone

CS 1000 digit processing strips the CNTC and adds <AC1 + NATC> to

produce 614161234567

Call to a number outside North America

A user initiates a call to a contact with the phone number +41123456789.

The URI incoming for the SIP INVITE for the call is

sip:[email protected];user=phone

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

20 MC 3100 and CS 1000 deployment overview

CS 1000 digit processing adds <AC1 + INTC> to produce

601141123456789.

Service DN

The mobile clients use a Service DN to originate calls in direct outbound

mode. The CS 1000 must route the calls to the SPS in the following

format:

In the following example, 88888 is the mobility Home Location (HLOC) and

2200 is the service Directory Number (DN).

Example: sip:[email protected]

Configure the mobility HLOC on the MCG 3100 gateway configuration tab

as the incoming prefix for call termination. Configure the Service DN field

on the MCG 3100 gateway configuration with the service DN.

Universal Extensions

A CS 1000 Universal Extension (UEXT) represents each mobile client

instance.

The Primary DN of the UEXT determines the user’s published addresses:

both private electronic serial number (ESN) and public direct inward dialing

DID (for example, Primary DN: 5335 contributes to the ESN address

3435335 and DID address +16139675335).

The mobility HLOC is a prefix to all mobile user identities on the UEXT

target DN. The Mobility HLOC provides a digit sequence that is unique

within the SIP domain to identify a mobile client that does not conflict with

the existing dial plan and routing configuration for their CDP and UDP

numbers.

The Target DN of the UEXT extends the user’s incoming calls to mobile

clients that are accessible through SIP domain. A typical setup would be

AC1 + Mobility Home Location (HLOC) + the user’s ESN number (for

example, Target DN: 65553435335).

Attention: It can be necessary to increase the Forward No Answer

(FNA) timeout for mobile client users. The UEXT extends all calls to the

MCG 3100. The MCG 3100 then presents the incoming call to the MCC

3100 clients over the cellular data channel of the MCC 3100 (using HTTP

Nortel Mobile Communication 3100

Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide

NN49000-315 01.04 19 June 2009

Page is loading ...

Avaya Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 User manual

Brand: Avaya

Model: Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000

Category: Rack accessories

Type: User manual

Download PDF

report

Avaya Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 User manual

Avaya Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 User manual

Related papers

Other documents