Nortel Networks NN43001-321 - page 61

CS 1000 SIP conﬁguration and UDP location dialing 61

sip:convergeddesktop@SIPdomainname;nortelconverged=

conditionalfork

Ensure that the SIPdomainname is part of the string. The SIP

Domain name should have been conﬁgured during the SIP Trunk

Gateway conﬁguration.

If the string is missing the SIP Domain name (that is, the string

is sip:convergeddesktop@;nortelconverged=conditionalfork),

then the SIP Domain name was not conﬁgured during the SIP

TrunkGateway conﬁguration. The SIP Domain name is found

under Signaling Server > Signaling Server xxx.xxx.xxx.xxx

Properties on the Edit web page (Figure 14 "Edit web page"

(page 58)).

This ﬁeld is used in the INVITE message for Converged Desktop

terminating call handling if the telephone is both a multimedia

and a voice telephone.

f. User Info. ﬁeld in the notify message for Converged

Desktop: Verifythe ﬁeld against the following string:

sip:convergeddesktop@SIPdomainname

Ensure that the SIPdomainname is part of the string. The SIP

Domain name should have been conﬁgured during the SIP Trunk

Gateway conﬁguration.

If the string is missing the SIP Domain name (that is, the string is

sip:convergeddesktop@), then the SIP Domain name was not

conﬁgured during the SIP Trunk Gatewayconﬁguration. The SIP

Domain name is found under Signaling Server > Signaling

Server xxx.xxx.xxx.xxx Properties on the Edit web page

(Figure 14 "Edit web page" (page 58)).

This ﬁeld is used in the NOTIFY message for Converged

Desktop.

g. RAN route for Announce: Enter the Recorded Announcement

(RAN) route number forcall announce. The route was conﬁgured

in LD 16. The range is 0 to 127 for Small Systems. The range

is 0 to 511 for Large Systems.

The RAN deﬁnition in this ﬁeld can be used in two distinctways:

•Call progress – A customer may wantto announce to a caller

that their call is proceeding and to please wait. RAN can be

used when delays may be longer than expected, as PCA

makes calls to other devices. If RAN is not used, callers will

hear only ringback tone.

•PCA busy – If PCA agents are busy processing a call and the

caller must wait for a PCA so CDS can process the call, the

Nortel Communication Server 1000

Communication Server 1000 to MCS 5100 ConvergedDesktop Type 2 Conﬁguration Guide

NN43001-321 01.05 Standard

Release 5.0 15February 2008

Copyright© 2005-2008, Nor tel Networks

.

Contents

Main Page Revision history February 2008 January 2008 December 2007 June 2007 October 2006 April 2006 September 2005 Contents How to get help 7 Introduction 9 Converged Desktop Services 13 Examples of dialing and numbering plan conguration for mixed networks 37 Conguring CS 1000 49 Conguring MCS 5100 67 CS 1000 NRS operation 87 Maintenance 99 Appendix A Parameter conguration for a SIP URI 103 How to get help Finding the latest updates on the Nortel Web site Getting help from the Nortel Web site Getting help over the telephone from a Nortel Solutions Center Getting help from a specialist by using an Express Routing Code Getting help through a Nortel distributor or reseller Introduction Subject Note on legacy products and releases Applicable systems Intended audience Conventions Related information Technical Documents Online CD-ROM Page Converged Desktop Services Introduction Scope of this document How Converged Desktop Services works Page Page Page Users in a mixed CS 1000/MCS 5100 network Converged Mode and Unconverged Mode CDS originating and terminating call handling Making a call Page Page Receiving a call Page Page AML ELAN numbers and VAS numbers Click-to-Call Operating parameters and feature interactions Call walk-throughs Page Feature requirements CS 1000 systems MCS 5100 systems Product Enhancement Packages and Patches Feature implementation Implementation summary Dialing and numbering plan issues for the mixed network Digit-based addresses and alphanumeric addresses Dialing plan issues DNs as MCS aliases versus DNs as MCS usernames Directory Number qualication Page Non-telephony-based SIP URIs Converged Desktop implications Problematic Click-to-Call scenarios Page Examples of dialing and numbering plan conguration for mixed networks Introduction Mixed network example: UDP Sample network CS 1000 setup MCS 5100 setup Page Mixed network example: CDP Sample network CS 1000 setup MCS 5100 setup Page Page CDS conguration: overview Introduction Conguration notes Description of the network congured in this document Conguring CS 1000 Before you begin CS 1000 SIP conguration and UDP location dialing Conguring the Call Server Page Page Page Page Page Page Page Congure the Signaling Server using CS 1000 Element Manager Page Page Page Page Page Page Verifying conguration Page Conguring the Converged Desktop User Conguring MCS 5100 Before you begin Implementation summary Implementation details Add IP address of IP Telephony node as an AuthenticatedSer ver Congure the SIP Gateway, trunk, and trunk group Page Page Congure number qualiers Page Page Congure a route list Page Congure routes for each dialing plan entry Page Page Page Conguring a Converged Desktop user Congure a Service Package Page Conguring the Converged User on the MCS 5100 Page Page Page CS 1000 NRS operation Introduction Operation Domains Gateway Endpoints Routing entries Conguring MCS 5100 in the NRS for CDS Page Page Page Conguring Meet Me Audio Conferencing in the NRS for CDS Page Operational logic Page Page Maintenance Introduction CS 1000 CLI commands Page MCS 5100 tools Translation Vericationtool Page Appendix A Parameter conguration for a SIP URI Introduction Example Phone-context strings Phone-context strings for public numbers Phone-context strings for unknown numbers Phone-context strings for private numbers Page Appendix B PC Client windows Page Page Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Conguration Guide