Nortel NN49000-315 Quick setup guide

Nortel Mobile Communication 3100
Mobile Communication 3100
and Communication Server 1000
Solution Integration Guide
Release: 3.1
Document Revision: 02.01
www.nortel.com
NN49000-315
.

Nortel Mobile Communication 3100
Release: 3.1
Publication: NN49000-315
Document release date: 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
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.
.

3
.
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 13
Mobile prefix 15
Data Access Planning 15
CS 1000 data access considerations 16
Licensing requirements 16
Dialing plans and telephone numbers 17
Service DN 18
Universal Extensions 19
Caller ID table 19
Device Handoff key configuration in PBX telephones 20
CallPilot MWI Configuration 23
MC 3100 and CS 1000 integration 25
Prerequisites 27
Establishing the system baseline 27
Checking the CS 1000 release from Element Manager 29
Checking the CS 1000 release from the command line 29
Integration worksheet 30
MCG 3100 configuration 37
CS 1000 configuration 39
CS 1000 licensing 41
Verifying package requirements 41
Verifying PCA requirements 42
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

4
Configuring ISM requirements 43
Printing system license limits 43
NRS configuration 45
Configuring gateway endpoints on the NRS 46
Adding an NRS Routing rule 47
Adding a User Endpoint 49
CS 1000 configuration for client support 53
Configuring features and keys 54
Configuring the Device Handoff key 55
Configuring the TSC steering codes 56
Configuring dial plan parameters 56
Configuring the Digit Manipulation Index 58
Configuring a Route List Index 59
Configuring Call Forward No Answer 59
MCC 3100 configuration 61
Autoconfiguration settings 62
Validate deployment 63
Validating MCG 3100 registration 63
Validating MCC 3100 for BlackBerry communication 64
Validating MC 3100 and CS 1000 deployment 64
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

5
.
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.1.
•"Features" (page 5)
•"Other changes" (page 5)
Features For information on the features, see Nortel Mobile Communication 3100
Fundamentals (NN42030-109).
Other changes
The following changes were made for MC 3100 Release 3.1:
•updated document to reference the MC 3100 Web User Interface
•ECM is no longer used for MC 3100 administration, so this information
was removed. ECM information related to the CS 1000 is contained in
the CS 1000 documentation suite.
•Renamed the MC 3100 Web Console to Web Administration Console.
MC 3100 Release 3.1 supports Nortel Communication Server 1000
Release 5.5 and Release 6.0.
Revision history
October 2009 Standard 02.01. This document is issued to support Nortel Mobile
Communication 3100 Release 3.1.
June 2009 Standard 01.04. This document is up-issued to add technical information in
Table 3.
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

6New in this release
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 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

7
.
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), the MC 3100 Web User Interface (MC 3100 Web UI), and
the 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 www.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 25)
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

8Introduction
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

9
.
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 15)
•"Licensing requirements" (page 16)
•" Dialing plans and telephone numbers" (page 17)
•"Service DN" (page 18)
•"CallPilot MWI Configuration" (page 23)
•"Universal Extensions" (page 19)
•"Device Handoff key configuration in PBX telephones" (page 20)
CS 1000 engineering for MC 3100
The MC 3100 Web User Interface, 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 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

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 prefix to support the client. The
UEXT target DN uses the mobility prefix as a prefix to identify mobile
users. The mobility prefix 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) is a DN that appears
on multiple terminal numbers (TN). The Multiple Appearance Directory
Number Redirection Prime (MARP) is a designation that is put on one
of the TNs to identify that specific features apply to the DN that is on
multiple TNs should be configured for the group on the TN that is the
MARP. For more information, see Features and Services Fundamentals
(NN43001-106).
The CS 1000 NRS-SPS supports the Source Based Routing (SBR)
feature. SBR ensures that, for all users of an MCG 3100, the CLID NCOS
and dial plan they see on their mobile phone is consistent with their desk
phone. The SPS routes all MC 3100 call attempts to the user’s home call
server so that those features configured on the home call server can be
applied to the MC 3100 call. 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 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

CS 1000 engineering for MC 3100 11
Figure 1
Client with CS 1000 and UDP
Figure 2 "Client with CS 1000 and CDP" (page 11) shows an example of
clients using a CS 1000 CDP.
Figure 2
Client with CS 1000 and CDP
The UEXT configuration requirements are shown in the following table.
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

12 MC 3100 and CS 1000 deployment overview
Table 1
UEXT configuration parameters
Parame
ter Description UDP example CDP example
Subtype UEXT subtype; must be
FMCL FMCL FMCL
primary
DN 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
[phone]
5335
contributes to a DN of
3435335 and a DID of
[phone]
target
DN 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 12).
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 mobile prefix 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).
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

CS 1000 engineering for MC 3100 13
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).
SIP Gateway CLID Parameters configuration
The SIP Gateway CLID parameters are used to adjust the format
of telephone numbers for incoming call appearances. For Mobile
Communication 3100 (MC 3100) these settings impact the format of
numbers that appear on the incoming call popup on the MCC 3100 client.
Figure 3
SIP GW CLID Parameters
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

14 MC 3100 and CS 1000 deployment overview
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.
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.
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

Data Access Planning 15
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.
Mobile prefixBefore configuring and deploying the MCC 3100 solution, the administrator
determines the Mobile prefix for the MCG 3100. The mobile prefix 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 mobile prefix 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.
mobile prefixes have the following requirements:
•One mobile prefix 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 mobile prefix. 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 mobile prefix 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 mobile prefix is configured on the MCG 3100 in the User Prefix
for Call Termination field.
Data Access Planning
This section describes things to consider when planning data access.
•"CS 1000 data access considerations" (page 16)
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

16 MC 3100 and CS 1000 deployment overview
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
•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.
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

Dialing plans and telephone numbers 17
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 [phone] and
[phone].
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.
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 [phone].
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
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

18 MC 3100 and CS 1000 deployment overview
produce 00123456789
Call to a number outside Switzerland
A user initiates a call to a contact with the phone number [phone].
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 [phone].
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 [phone].
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
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:
<mobile prefix><service DN>
In the following example, 88888 is the mobile prefix and 2200 is the
service Directory Number (DN).
Example: sip:[email protected]
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

Universal Extensions 19
Configure the mobile prefix 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 [phone]).
The mobile prefix is a prefix to all mobile user identities on the UEXT
target DN. The mobile prefix 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 + (mobile prefix) + 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
or /HTTPS). It can take a few seconds for the data transmission to reach
the client depending on the current state of the mobile phone. If the FNA
timeout is too short users do not have reasonable time to (potentially log
on) and answer the call before the call server invokes FNA and sends the
call to the FNA destination.
Caller ID table
All CS 1000 telephones use the Caller ID table. The Caller ID table is
required for the MCC 3100 to correctly build the Caller ID (CLID) for both
Private network and Public network calls from a number or extension.
Outgoing SIP calls from the MCG 3100 on behalf of the mobile client
use the CLID table configured against the Multiple Appearance Directory
Number Redirection Prime (MARP) TN in the Multiple Access Directory
Number (MADN) group of the MCC 3100 user.
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.

20 MC 3100 and CS 1000 deployment overview
Device Handoff key configuration in PBX telephones
To allow an MCC 3100 user to perform Device Handoff between the
MCC 3100 and PBX telephone, a Handoff key must be configured on
the desktop telephone. The MCC 3100 uses the same configuration and
same user interface for device handoff as the Mobile Extension feature
introduced in CS 1000 Release 5.5.
Only one handoff key can be configured for a desktop telephone. Once
configured, the key label on the telephone shows “Handoff” as the text
display for the device handoff key.
Attention: Nortel M3902 telephones do not display the key label for
Handoff key. This label needs to be configured manually on the telephone.
Sample configuration from LD 11:
REQ: PRT
TYPE: 3904
TN4073
DATE
PAGE
DES DESK
TN 004 0 07 03 VIRTUAL
TYPE 3904
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
FDN
TGAR 0
LDN NO
NCOS 7
SGRP 0
RNPG 0
SCI 0
SSU
XLST
SCPW
SFLT NO
CAC_CIS 3
CAC_MFC 0
CLS UNR FBD WTA LPR MTD FND HTD TDD HFA GRLD CRPD STSD
MWD LMPN RMMD SMWD AAA IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LND CNDA
Nortel Mobile Communication 3100
Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide
NN49000-315 02.01 2 October 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.