Benutzeranleitung / Produktwartung NN43001-321 des Produzenten Nortel Networks
Zur Seite of 110
Nor tel Communication Ser v er 1000 Comm unication Ser v er 1000 to MCS 5100 Con v erged Desktop T ype 2 Configur ation Guide NN43001-321 ..
Document status: Standard Document version: 01.05 Document date: 15 February 2008 Copyright © 2005-2008, Nor tel Netw orks All Rights Reser v ed. Sourced in Canada LEGAL NO TICE While the information.
3 Re vision histor y February 2008 Standard 01.05. This document is up-issued to update the instructions f or Configuring Meet Me A udio Conf erencing in the NRS f or CDS. January 2008 Standard 01.04. This document is up-issued to add instructions f or Configuring Meet Me A udio Conf erencing in the NRS f or CDS.
4 Revision history CR Q01478214, two options are added to "Configur ing MCS 5100 in the NRS f or CDS" (page 90) . MCS 5100 is configured as a Gatew ay Endpoint in the first option and as a Collaborativ e Ser ver in the second. October 2006 Standard 3.
5 Contents How to get help 7 Finding the latest updates on the Nor tel Web site 7 Getting help from the Nor tel Web site 7 Getting help over the telephone from a Nor tel Solutions Center 7 Getting hel.
6 Contents Configuring CS 1000 49 Contents 49 Before y ou begin 49 CS 1000 SIP configuration and UDP location dialing 49 Configuring the Conv erged Desktop User 66 Configuring MCS 5100 67 Contents.
7 Ho w to g et help This chapter explains how to get help for Nor tel products and services. Finding the latest updates on the Nor tel W eb site The content of this documentation is current at the time the product is released. T o check f or updates to the latest documentation f or Communication Ser ver (CS) 1000, go to w ww .
8 How to get help Getting help from a specialist by using an Express Routing Code T o access some Nor tel T echnical Solutions Centers, y ou can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nor tel product or ser vice.
9 Intr oduction This document is a global document. Contact y our system supplier or your Nor tel representative to v er ify that the hardware and software described are suppor ted in your area.
10 Introduction • Meridian 1 PBX 11C Cabinet • Meridian 1 PBX 61C CP PII, CP PIV • Meridian 1 PBX 81C CP PII, CP PIV Note: When upgrading softw are, memor y upgrades ma y be required on the Signaling Ser ver , the Call Ser ver , or both.
Related information 11 • F eature Descr iption Guide (NN42020-125) • Interworking Fundamentals (NN42020-127) Online T o access Nor tel documentation online, click the T echnical Documentation link under Suppor t & T raining on the Nor tel home page: w ww .
12 Introduction Nor tel Communication Ser v er 1000 Communication Server 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide NN43001-321 01.
13 Con ver ged Desktop Services Contents This section contains information about the f ollowing topics: "Introduction" (page 13) "Scope of this document" (page 14) "How Conver.
14 Conv erged Desktop Ser vices Scope of this document This document is intended to assist technical administrators in designing and configuring a Conv erged Desktop environment betw een CS 1000 and MCS 5100 systems. The e xamples provided in this document represent only one example of design and configuration.
How Con verged Desktop Ser vices works 15 In Conv erged Mode, both the CS 1000 telephone and the MCS 5100 PC Client are integrated to provide both f eature sets.
16 Conv erged Desktop Ser vices When a call terminates to the CS 1000 telephone, the CDMV or CDMO Class of Ser vice redirects the call to the CSDN defined on the telephone, bef ore r inging the CS 1000 telephone.
How Con verged Desktop Ser vices works 17 In Conv erged Mode, incoming and outgoing calls to and from a con verged telephone notify the MCS 5100. Upon notification, the MCS 5100 then provides diff erent SIP ser vices and f eatures to the user .
18 Conv erged Desktop Ser vices • W eb co-browsing — Allo ws users to share a web browser . If both users hav e the web co-browsing f eature, then one user can automatically control (or drive) the other user’s web browser . All of these f eatures are achiev ed by sending or iginating and ter minating call notifications to the MCS 5100.
How Con verged Desktop Ser vices works 19 Note: When a Con verged Desktop user is not in a con verged state, the user eff ectively becomes an MCS 5100 user and the CS 1000 device becomes a stand-alone voice de vice.
20 Conv erged Desktop Ser vices — Select from a F r iends list or Director y book. In both instances the f ollowing functionality is automatically provided: • The Call Log is updated after the call. • A pop-up window is generated if another CD user or SIP user was called.
How Con verged Desktop Ser vices works 21 9 Converged user A releases. 10 Call disconnected; Disconnect message sent. 11 Release message sent. 12 Call timer stopped, Call Log updated. Figure 3 "Call flow: Clic k-to-Call" (page 21) shows the call flow and messaging that occurs dur ing a Click-to-Call session.
22 Conv erged Desktop Ser vices 9 Call between PCA and converged user A disconnected; call made from converged user A to user B. 10 Call placed to user B. Receiving a call Depending on the Class of Ser vice (CDMV or CDMO) of the conv erged user , the call flow will diff er slightly .
How Con verged Desktop Ser vices works 23 Legend: 1 User A dials user B; call is forwarded to CDN. 2 Incoming call to CDMV user sent to CDS. 3 PCA selected; call made to Service DN to select a Virtual Trunk. 4 Virtual Trunk reserved. 5 INVITE message sent to CDS URL.
24 Conv erged Desktop Ser vices Figure 5 Call flow: call terminating to a user with a CDMO Class of Service Legend: 1 User A dials user B; call is forwarded to CDN. 2 Incoming call to CDMO user sent to CDS. 3 PCA selected; call made to Service DN to select a Virtual Trunk.
How Con verged Desktop Ser vices works 25 When receiving a call, the functionality of the PC Client is diff erent from that when making a call. With CDMO , a call to a conv erged telephone alwa ys rings the converged telephone . It does not invok e P A routing.
26 Conv erged Desktop Ser vices The f ollowing steps must be perf or med when using Clic k-to-Call: • The caller makes a call from the PC Client software and the caller’s telephone rings.
Call walk-throughs 27 • In the Conv erged Desktop En vironment, voice mail is suppor ted only on the CS 1000 telephone, not the MCS 5100 Client. Call walk-throughs The figures in this section show messages exchanged between a CS 1000 system and an MCS 5100 system with different configurations .
28 Conv erged Desktop Ser vices Figure 7 Incoming call to CDMV user with forking Figure 8 Incoming call to CDMV user with NO forking Figure 9 Incoming call to CDMO user Nor tel Communication Ser v er 1000 Communication Server 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide NN43001-321 01.
Feature requirements 29 Figure 10 Combined incoming and outgoing Con verged Desktop call Feature requirements CS 1000 systems CS 1000 systems require: • CS 1000 Release 4.
30 Conv erged Desktop Ser vices Feature implementation F or CDS to operate, you m ust hav e the f ollowing conditions in place: • MCS 5100 clients must assume the location identifier (LOC) of a CS 1000 system.
Dialing and numbering plan issues f or the mixed network 31 A TTENTION Rule 1: All users in a mixed CS 1000/MCS 5100 network must be accessible by all systems through a digit-based address. On the MCS 5100 system, each username must ha ve an alias that is all digits , or each user name must be all digits.
32 Conv erged Desktop Ser vices Rule 2 is impor tant f or a CD user . Although a CD user can enter a destination number on the Multimedia PC Client, the call itself is originated under CS 1000 control.
Dialing and numbering plan issues f or the mixed network 33 — Local numbers — National numbers — International numbers — Special numbers • Private address space — which is subdivided into .
34 Conv erged Desktop Ser vices Non-telephony-based SIP URIs In accordance with the preceding Rule 4, non-telephony-based, or regular , SIP URIs must not be passed between systems in a mixed CS 1000/MCS 5100 network. There is one e xception to this r ule — regular SIP URIs can be passed between systems in the Ref er-to header .
Dialing and numbering plan issues f or the mixed network 35 The conv erged Multimedia PC Client provides se veral wa ys for a user to initiate Click-to-Call, including: • using the Director y window.
36 Conv erged Desktop Ser vices Nor tel Communication Ser v er 1000 Communication Server 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nor tel Networks .
37 Examples of dialing and numbering plan configuration f or mixed netw orks Contents This section contains information about the f ollowing topics: "Introduction" (page 37) "Mixed net.
38 Examples of dialing and numbering plan configuration for mixed netw or ks Sample network The sample network has the f ollowing characteristics: • The network includes sev eral sites. • Each site has a mixture of CS 1000 users , MCS 5100 users, and Conv erged Desktop users.
Mixed netw or k example: UDP 39 CS 1000 setup The CS 1000 setup includes both a user setup and translation setup . User setup The CS 1000 user setup inv olves both the general user setup and the Conv erged Desktop user setup. General user setup The general user setup applies to both stand-alone and Conv erged Desktop users.
40 Examples of dialing and numbering plan configuration for mixed netw or ks — UDP phone-conte xt F or example: phone-conte xt="udp" — CDP phone-conte xt F or example: phone-conte xt="cdp.
Mixed netw or k example: UDP 41 number . F or example: P AD = 63345573 The number 6 is the access code configured for UDP calls as configured on CS 1000.
42 Examples of dialing and numbering plan configuration for mixed netw or ks Mixed netw ork example: CDP The f ollowing is an e xample of a dialing plan setup for a mix ed CS 1000/MCS 5100 network.
Mixed netw or k example: CDP 43 Figure 12 Network dia gram: mixed CDP CS 1000 setup The CS 1000 setup includes both a user setup and translation setup . User setup The CS 1000 user setup inv olves both the general user setup and the Conv erged Desktop user setup.
44 Examples of dialing and numbering plan configuration for mixed netw or ks Note: Although the network is CDP-only , some UDP configuration is necessar y to suppor t MCS 5100 pr ivate charge ID , which is alwa ys presented as a UDP number . • Configure the Private Network Identifier (PNI) for user groups (that is, customers).
Mixed netw or k example: CDP 45 User setup The MCS 5100 user setup inv olves both the general user setup , stand-alone user setup, and the Conv erged Desktop user setup . General user setup The general user setup applies to both stand-alone and Conv erged Desktop users.
46 Examples of dialing and numbering plan configuration for mixed netw or ks • If the Public/International number is received, inser t 9011. F or e xample, DN star ts with a plus sign (+), inser t 9011.
47 CDS configuration: o verview Contents This section contains information about the f ollowing topics: "Introduction" (page 47) "Configuration notes" (page 47) "Description.
48 CDS configuration: ov er view Description of the network configured in this document The user will encounter one of many CDS configuration situations. This section describes the basic characteristics of the network to which the configuration described in the rest of this document applies.
49 Configuring CS 1000 Contents This section contains information about the f ollowing topics: "Before you begin" (page 49) "CS 1000 SIP configuration and UDP location dialing" (p.
50 Configuring CS 1000 2. "LD 17 Configure the Application Module Link (AML)." (page 51) . 3. "LD 17 Configure V alue Added Ser ver (V AS)." (page 51) . 4. "LD 23 Configure Automatic Call Distrib ution (ACD) Directory Number (DN).
CS 1000 SIP configuration and UDP location dialing 51 Prompt Response Description -PFX1 613 Prefix 1 -PFX2 962 Prefix 2 DITI Yes DID to TIE connections allowed. To connect external DID and internal network TIE trunks for the customer (which allows an external trunk to be transferred across an internal network TIE trunk), set DITI=YES.
52 Configuring CS 1000 LD 23 Configure Automatic Call Distribution (A CD) Director y Number (DN). Prompt Response Description REQ NEW Add new data. TYPE ACD Automatic Call Distribution data block CUST xx Customer number as defined in LD 15. (Customer number associated with this data block.
CS 1000 SIP configuration and UDP location dialing 53 Configuring HLOC is necessar y to proper ly handle a UDP number sent by the MCS 5100 based on the Private Charge ID of the MCS 5100 user profile. The MCS 5100 alwa ys qualifies this number as a UDP number .
54 Configuring CS 1000 Prompt Response Description ... AC1 or AC2 xxxx 1-4 digit Flexible Numbering Plan Access Code 1. The access code cannot conflict with the numbering plan. Remov al of the HLOC digits is necessary so that local termination is possible .
CS 1000 SIP configuration and UDP location dialing 55 Prompt Response Description AC1 = NARS/BARS AC2 = NARS TYPE: SPN Special Number translation (Special code translation block) Configure the CDS Service DN as an SPN, and point it to the SIP trunk.
56 Configuring CS 1000 Prompt Response Description Flexible length is the exact number of digits the system expects to receive before accessing a trunk and outpulsing those digits. -DSP aaa Display, where aaa = LSC, LOC, DN. -RRPA (NO) YES Remote Radio Paging Access -RLI xxx Route List to be accessed for Distant Steering Code.
CS 1000 SIP configuration and UDP location dialing 57 Prompt Response Description zzzz = agent’s position ID (zzzz can be up to 4 digits; up to 7 digits with Directory Number Expansion [DNXP] package 150).
58 Configuring CS 1000 3 Click Edit ne xt to the node f or which SIP CDS is to be configured. The Edit web page opens, as sho wn in Figure 14 "Edit web page" (page 58) . Figure 14 Edit web page 4 Select SIP CD Services to e xpand the section, as shown in Figure 15 "SIP CD Ser vices" (page 59) .
CS 1000 SIP configuration and UDP location dialing 59 Figure 15 SIP CD Services 5 Enter the necessar y inf or mation in the follo wing fields: a. Service Enabled: Select whether the Conv erged Desktop Ser vice application is enab led or disabled f or this node.
60 Configuring CS 1000 Vir tual T runk route based on translations. The CDS answers and reser ves the Vir tual T runk in case it is needed to ter minate the incoming call.
CS 1000 SIP configuration and UDP location dialing 61 sip:conv ergeddesktop@ SIPdomainname ;nor telcon verged= conditionalf or k Ensure that the SIPdomainname is par t of the string. The SIP Domain name should hav e been configured dur ing the SIP T runk Gatew ay configur ation.
62 Configuring CS 1000 user can be directed to RAN. The RAN typically will sa y , f or e xample, "Y our call is proceeding, please wait..." h. W ait time before a caller is sent to RAN Queue: Enter the time (in seconds) that the caller waits bef ore the called is directed to the RAN queue.
CS 1000 SIP configuration and UDP location dialing 63 Note: The fields require a character string that is less than 128 characters in length. The valid char acters include: alphanumeric (a-z, 0-9), per iod (.), dash (-), underscore (_), and plus sign (+).
64 Configuring CS 1000 8 Click Sa ve and T ransfer . —End— V erifying configuration After configuring the Vir tual IP D-channel, SIP Route, Con verged Desktop AML, and the other elements, log in to the Leader Signaling Ser ver of the node.
CS 1000 SIP configuration and UDP location dialing 65 Figure 17 V erifying configuration: cdsShow Figure 18 V erifying configuration: cdsAg entShow Nor tel Communication Ser v er 1000 Communication Server 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide NN43001-321 01.
66 Configuring CS 1000 Note: If your Agents do not show Up, you ma y not have Nor tel Symposium Call Center (NGCC) package 311 equipped. Y ou need CS 1000 PEP MPLR19786 if the package is not equipped and you are using CS 1000 Release 4.0 softw are. This PEP is not required on CS 1000 Release 4.
67 Configuring MCS 5100 Contents This section contains information about the f ollowing topics: "Before you begin" (page 67) "Implementation summary" (page 68) "Implementatio.
68 Configuring MCS 5100 Implementation summary The f ollowing is a summar y of the tasks in this section: • "Add IP address of IP T elephony node as an Authenticated Server" (page 68) . • "Configure the SIP Gate wa y , trunk, and tr unk group" (page 69) .
Implementation details 69 7 V erify the address appears in the list under the A uthentication tab , as shown in Figure 19 "IP address of IP T elephony node added as an A uthenticated Ser ver" (page 69) : a. Right-click on the application ser ver .
70 Configuring MCS 5100 Figure 20 Pro visioning Client Login 2 Enter your Username and P a s s wo rd . The Pro visioning Client web page opens, as shown in Figure 21 "Provisioning Client" (page 70) . The Provisioning Client navigator is in the section on the left of the web page.
Implementation details 71 Figure 22 Pro visioning Client: Add a new gatewa y b . Enter m ydomain.com:maddr=12.123.1.123 in the Gatewa y host te xt box. c. Select CS 1000 in the Gatewa y type drop-down list. d. Select Other from the Location drop-down list.
72 Configuring MCS 5100 c. Select m ydomain.com in the Domain drop-down list. d. Click Sa ve . 5 Add a trunk group directed to the gatew a y and route just created, as f ollows: a. Select Pro visioning > Gateways > Add T runkGroup in the Provisioning Client na vigator .
Implementation details 73 • CS 1000 NRS SIP URI phone-context in the Endpoint Routes (see Figure 26 "CS 1000 NRS Endpoint Routing Entries" (page 73) ). • MCS 5100 T elephony Routes Number Qualifiers (see Figure 27 "MCS 5100 Number Qualifiers" (page 74) ).
74 Configuring MCS 5100 Figure 27 MCS 5100 Number Qualifiers Procedure 4 Configuring number qualifiers Step Action 1 Enter the IP address of the MCS Provisioning Client in a w eb browser . The Pro visioning Client Login web page opens, as shown in Figure 20 "Provisioning Client Login" (page 70) .
Implementation details 75 4 Add a number qualifier f or each entry in the SIP URI map (shown in Figure 25 "CS 1000 SIP URI Map" (page 73) ) as f ollows: a. Enter the name in the Name text bo x, f or example cdp.udp . b . Enter a description in the Description text bo x, f or example My CDP phone context .
76 Configuring MCS 5100 The Pro visioning Client Login web page opens, as shown in Figure 20 "Provisioning Client Login" (page 70) . 2 Enter your Username and P a s s wo rd . The Pro visioning Client web page opens, as shown in Figure 21 "Provisioning Client" (page 70) .
Implementation details 77 a. Select Pro visioning > Domains > m ydomain.com > T elephony Routes > Add RouteList in the Provisioning Client navigator . The Create a New Route List web page opens, as shown in Figure 30 "Provisioning Client: Create a New Route List" (page 77) .
78 Configuring MCS 5100 • Gatew ay UDP route • private PSTN route • route f or local Dial-9 National (NP A) dialing using the Gate way CS 1000 PSTN • route f or national Dial-9 National (NP A.
Implementation details 79 Figure 31 Pro visioning Client: Create New T elephony Route b . Configure each ne w route, as follo ws: 1. Enter the values f or the appropriate fields, as listed in Ta b l e 2 "V alues f or configuring Routes" (page 79) .
80 Configuring MCS 5100 Route Type Entry Field Private CDP Private UDP Private PSTN Gateway CDP Gateway UDP Public Local Public National From Digits 7100 6334 9 7100 6334 9 9961 To Digits 7199 6334 9.
Configuring a Con verged Desktop user 81 Figure 32 Pro visioning Client: Pre translations b . Configure pretranslations f or each of the number qualifiers in the Add New Pretranslations section, as f ollows: 1. Select the appropr iate number qualifier from the Number Qualifier drop-down list.
82 Configuring MCS 5100 Procedure 7 Configuring a Ser vice Pac kage Step Action 1 Select Pro visioning > Domains > m ydomain.com > Service P ackage > Create Pac kage in the Provisioning Client navigator . The Create new pac kage web page opens, as shown in Figure 33 "Provisioning Client: Create new pac kage" (page 82) .
Configuring a Con verged Desktop user 83 —End— Configuring the Con verged User on the MCS 5100 Use Procedure 8 "Configur ing a Conv erged Desktop User in MCS 5100" (page 83) to configure each Conv erged Desktop user in MCS 5100.
84 Configuring MCS 5100 This is the HLOC + DN of the con verged telephone. This number is used f or Click-to-Call in Con verged Mode, and must be a UDP number . b . Enter 6139625573 in the Public Charge ID text bo x. This is the NP A + NXX + DN of the conv erged telephone.
Configuring a Con verged Desktop user 85 • If you are configuring CDP , enter the CDP number . d. Select Enterprise Con verged User from the Con verged Desktop User T ype drop-down list. —End— Nor tel Communication Ser v er 1000 Communication Server 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide NN43001-321 01.
86 Configuring MCS 5100 Nor tel Communication Ser v er 1000 Communication Server 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide NN43001-321 01.
87 CS 1000 NRS operation Contents This section contains information about the f ollowing topics: "Introduction" (page 87) "Operation" (page 88) "Domains" (page 88) ".
88 CS 1000 NRS operation This network configuration requires the CS 1000 SIP Redirect Ser v er and MCS 5100 to interw or k seamlessly . Theref ore, this section describes the basics of the redirect ser ver logic.
Operation 89 Figure 38 Level0 Domain Gatewa y Endpoints The Gatew ay endpoint is configured with the f ollowing proper ties: • ID — Node134Loc334 This matches the SIP Endpoint name configured in CS 1000. • Call Signaling IP address — 12.123.
90 CS 1000 NRS operation Routing entries The routing entr ies configured in CS 1000 NRS f or Gatew ay Endpoint Node134Loc334 are shown in Figure 40 "Routing Entries" (page 90) . Note: SIP URI phone-conte xts are configured in CS 1000 NRS as par t of the Le vel1 Domain (udp).
Operation 91 Configure at least two routing entr ies against this Gatewa y Endpoint, so the Gatew ay Endpoint can be added to the lookup tab le. • Configure the MCS 5100 as a Collaborativ e Ser v er . See Figure 41 "MCS 5100 configured as a Collaborativ e Ser v er" (page 92) .
92 CS 1000 NRS operation Figure 41 MCS 5100 configured as a Collaborative Server T o route calls from MCS 5100 to CS 1000 when MCS is configured as a Collaborativ e Ser v er , choose one of two configuration options: 1. Configure MCS 5100 as a Gatew ay Endpoint f or the NRS without routing entries for calls from CS 1000 to MCS 5100.
Operation 93 Figure 42 MCS 5100 configured as a Gate way Endpoint without routing entries 2. Configure telephony routes on MCS 5100 to contact the CS 1000 SIP Gatew ay directly (not through NRS). See Figure 43 "Configure telephony routes on MCS 5100" (page 94) .
94 CS 1000 NRS operation Figure 43 Configure telephony r outes on MCS 5100 Configuring Meet Me Audio Conferencing in the NRS for CDS T o configure Meet Me Audio Conf erencing for CDS , you must point the meetme DID to the conv ergeddesktop gatew ay end point as a CDP entr y .
Operation 95 7 Click Ad d . 8 Enter the DN T ype , DN Prefix , and Route Cost . 9 Click Sa ve . 10 Navigate to T ools > Database Actions . 11 Under Select database action , choose Cut over & Commit . Nor tel Communication Ser v er 1000 Communication Server 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide NN43001-321 01.
96 CS 1000 NRS operation 12 Click Submit . —End— Operational logic The f ollowing items describe the operational logic of the CS 1000 SIP Redirect Ser ver: • When an INVITE is received, the Public Address is e xtracted from the request URI. F or example: INVITE <sip:dn;phone-conte xt=pc@domain;user=phone> SIP/2.
Operational logic 97 Ta b l e 3 Searc h results of location database If... Then... The resolution fails (that is, no endpoints are found), the SIP Redirect Server redirects to a collaborating server. Note: For the purpose of this discussion, the collaborating server can be an MCS 5100 Session Manager.
98 CS 1000 NRS operation Nor tel Communication Ser v er 1000 Communication Server 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide NN43001-321 01.
99 Maintenance Contents This section contains information about the f ollowing topics: "Introduction" (page 99) "CS 1000 CLI commands" (page 99) "MCS 5100 tools" (page 10.
100 Maintenance Y ou must log in to the Signaling Ser ver to use the CLI commands. Ref er to Signaling Ser ver Installation and Commissioning (NN43001-312) fo r this procedure. T able 4 "CDS O AM commands" (page 100) shows the Conv erged Desktop CLI commands av ailable on the Signaling Ser ver from the O AM shell.
MCS 5100 tools 101 Command Description cdsCallTraceSetAll Enables CDS call trace for all calls. All messages to or from the Call Server and to or from the Signaling Server that relate to a Converged Desktop call are traced. cdsCallTraceOff Turns off CDS call trace for all calls.
102 Maintenance Figure 44 Pro visioning Client: T ranslation Verification T ool 4 Enter the SIP URI to be traced in the Request URI te xt box. 5 Enter the destination DN in the To text bo x. 6 Enter the originating DN in the From text bo x. 7 Click Ex ecute .
103 Appendix A P arameter configuration f or a SIP URI Contents This section contains information about the f ollowing topics: "Introduction" (page 103) "Example" (page 103) ".
104 Appendix A P arameter configuration f or a SIP URI Global uniqueness of phone-context strings is a prerequisite for being able to ser ve a domain (for example , CDP-domain or an area code) by se veral systems (such as CS 1000 and MCS 5100).
Phone-context strings 105 NPI/TON Scope Hierarchical domain-based schema Global prefixed-base d schema CS 1000 SIP Redirect Server implementation NPI=Public, TON=Special Area within nation For example, myarea, mynation myarea.
106 Appendix A P arameter configuration f or a SIP URI Ta b l e 8 Phone-context strings for priv ate number s (example) NPI/TON Scope Hierarchical domain-based schema Global prefixed-base d schema CS 1000 SIP Redirect Server implementation NPI=Private, TON=Level 1 Regional (UDP) Enterprise For example, myenterprise level1.
107 Appendix B PC Client windows T able 9 "PC Client: user expectations" (page 107) describes pop-up and other windows that ma y open and close on the PC Client when two users make a call on an Enter pr ise switch.
108 Appendix B PC Client windows Network Call Log Popup Window Video PCC Call Log/ Auto Presence Terminating PCC’s call window closes when originating PCC closes call window Originating PCC’s call.
.
Nor tel Communication Ser ver 1000 Communication Ser v er 1000 to MCS 5100 Conv erged Desktop T ype 2 Configuration Guide Copyright © 2005-2008, Nor tel Networks All Rights Reser ved. Publication: NN43001-321 Document status: Standard Document version: 01.
Ein wichtiger Punkt beim Kauf des Geräts Nortel Networks NN43001-321 (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie Nortel Networks NN43001-321 noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für Nortel Networks NN43001-321 - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von Nortel Networks NN43001-321 reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über Nortel Networks NN43001-321 erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon Nortel Networks NN43001-321 besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von Nortel Networks NN43001-321 verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit Nortel Networks NN43001-321. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei Nortel Networks NN43001-321 gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.
