Manuel d'utilisation / d'entretien du produit NN43001-121 du fabricant Nortel Networks
Aller à la page of 304
Nor tel Communication Ser v er 1000 Nor tel Con v erged Office Fundamentals — Microsoft Office Comm unications Ser v er 2007 NN43001-121 ..
Document status: Standard Document version: 01.03 Document date: 30 April 2008 Copyright © 2005–2008, Nor tel Networks All Rights Reser v ed. LEGAL NO TICE While the information in this document is belie ved to be accurate and reliable , except as otherwise expressly ag reed to in wr iting.
3 Contents New in this release 9 Office Communications Server 2007 features 9 Other changes 9 Revision History 10 How to get help 11 Getting help from the Nor tel web site 11 Getting help over the te.
4 Contents Load Balancer planning 43 Load Balancer requirements 44 Redundancy with Load Balancers 45 Nor tel Application Switch 46 Capacity planning 46 OC 2007 client requirements 47 Load Balancer cap.
Contents 5 Installation 101 OCS 2007 installation preparation and deployment 103 CS 1000 and Signaling Ser ver installation 105 OCS 2007 component installation 105 OCS Proxy server installation 107 Lo.
6 Contents CS 1000 configuration 173 Signaling Server configuration 177 SIP CTI Ser vices configuration settings 181 SIP CTI CLID configuration parameters 185 Configuring the SIP URI Map 189 Configuring CDR 190 Dialing E.
Contents 7 MCM logs 228 Activating MCM logging 229 OCS logs 231 Case checklists 234 Appendix A Call Flow and protocol details 237 Contents 237 Overview 237 Message sequence 238 Call flow 239 T elepho.
8 Contents Procedure Configuring a Mediation Ser ver 133 Procedure Enabling replication to the Global Catalog 146 Procedure Configuring the SIP T runk Domain name 164 Procedure Enabling Remote Call .
9 Ne w in this release Office Communications Server 2007 features Signaling traffic between Communication Ser v er 1000 and Office Communications Ser ver 2007 is suppor ted by Multimedia Conv ergence Manager (MCM) 3.0 . Media traffic is supported through the Mediation Ser ver .
10 New in this release — SIP UPD A TE method is not suppor ted by Mediation Ser ver . This method enables SIP Gate wa ys and Endpoints to update the call inf or mation dur ing a call.
11 Ho w to g et help This chapter explains how to get help for Nor tel products and ser vices. Getting help from the Nor tel web site The best wa y to get technical suppor t for Nor tel products is from the Nor tel T echnical Suppor t web site: w ww .
12 How to get help Getting help through a Nortel distributor or reseller If you purchased a service contract f or your Nor tel product from a distr ibutor or author ized reseller , contact the technical suppor t staff for that distributor or reseller .
13 Intr oduction This document describes the elements and processes necessar y to integrate Nor tel Communication Ser ver 1000 (CS 1000) with the Office Communications Ser ver 2007 (OCS 2007) in the Nor tel Conv erged Office. Prerequisites • Ensure CS 1000 Release 5.
14 Introduction Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.
15 Con ver g ed Office component o ver vie w This chapter provides a brief technical descr iption of all the components associated with Nor tel Conv erged Office.
16 Conv erged Office component ov erview The Nor tel Conv erged Office feature combines the business-g rade telephony of the CS 1000 with the OCS 2007 Enter prise V oice solution to offer a pow erful conv erged office solution set that improves work er productivity .
Enterpr ise V oice 17 • originate and receive Public Switched T elephone Network (PSTN) calls from the Office Communicator (OC) 2007 soft client when awa y from the office. • take adv antage of existing b usiness telephony f eatures on the CS 1000.
18 Conv erged Office component ov erview • the Mediation Ser ver perf or ms all necessar y media transcoding and routes the call to the IP-PSTN gate wa y .
Media Gatew ays 19 • Address Book Ser vice—normalizes enter pr ise user phone numbers to E.164 f or mat to provision user Contacts in Office Communicator .
20 Conv erged Office component ov erview Media gatew ays translate the f ollowing protocols between the circuit-s witched PSTN network and the packet-s witched Enter prise V oice infrastructure: • .
Mediation Server 21 • connects clients outside the network to inter nal Interactive Connectivity Establishment (ICE) components, to enab le media tra versal of NA T and firew alls • acts as an in.
22 Conv erged Office component ov erview Remote Call Control with SIP CTI (TR/87) The CS 1000 and OCS 2007 integ ration f eature allows clients of the two systems (Microsoft OCS 2007 and Nor tel CS 1000) to communicate with each other . Y ou can associate an OC Client, which connects to the OCS, with a CS 1000 line.
T elephony Gate way and Services 23 Figure 5 Remote Call Control The full set of b usiness-grade telephony f eatures av ailable with CS 1000 telephones is integrated with the OC 2007 client and can also be operated from a CS 1000 IP Phone, e ven when the client is unavailab le.
24 Conv erged Office component ov erview With this solution, y ou can configure P ersonal Call Assistant (PCA) on the CS 1000 f or each user with this functionality .
P ersonal Call Assistant 25 Figure 6 Dual forking e xample P ersonal Call Assistant Many of the f eatures provided by CS 1000 to traditional telephones are e xtended to Office Communicator clients configured with the P ersonal Call Assistant (PCA).
26 Conv erged Office component ov erview Gatew ay and Services to alwa ys tandem through the user’s active Call Ser ver . Note that with Geographic Redundancy f eatures, a user’s active Call Ser ver ma y change dur ing f ailure scenar ios.
OCS 2007 snap-in 27 specifically in Computer mode. F eatures such as Call Forw ard No Ans wer , Unified Messaging, Call Detail Recording, and Attendant Recall are maintained within the CS 1000 system for calls presented to the OC 2007. T elephony Gate wa y and Ser vices can access all of the telephony network resources using the OC 2007 client.
28 Conv erged Office component ov erview ser vers , and users. The Status pane also features a ne w Database tab , which can be used to quer y a pool’s back-end databases.
SIP CTI (TR/87) Protocol 29 SIP CTI (TR/87) Protocol The SIP CTI (TR/87) FE application introduced with this package is not limited to Microsoft applications. Through suppor t of the ECMA TR/87 standard, Nor tel par tners can use this interf ace to dev elop SIP CTI capabilities f or use with any specification-compliant application.
30 Conv erged Office component ov erview Figure 8 SIP diagram Figure 9 "IP diagram" (page 31) depicts the IP protocol inf or mation. Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.
Hardware Load Balancer 31 Figure 9 IP diagram A TTENTION Customers must not use their Office Communicator client to call Emergency numbers (for e xample, 911). T o ensure that emergency ser vice organizations can accurately trace the source of the call, alwa ys use a desktop phone to place an emergency call.
32 Conv erged Office component ov erview Hardware Load Balancers deliver load distribution to av oid a single point of failure . Other benefits include increased perf or mance and added redundancy . The CS 1000 uses Load Balancers for the signaling path of V oIP calls and Remote Call Control.
Documentation References 33 Ta b l e 1 Nortel technical documentation Technical document Content Primary audience Converged Office User Guide — Microsoft Office Communications Server 2007 (NN43001-123) Contains information about using the OC client.
34 Conv erged Office component ov erview Technical document Content Primary audience Transmission Parameters (NN43001-282) Contains information about configuring the loss plan and DTI Data Bock.
35 Planning and engineering This chapter contains information about topics you must consider bef ore you implement Con verged Office. Planning and engineering navigation • "Introduction" .
36 Planning and engineering Nor tel recommends that you implement the T elephony Gate wa y and Ser vices component to provide basic connectivity (which you can more readily debug), f ollowed b y the Remote Call Control (RCC) for more comple x f eature operation.
Network configuration 37 Note: The descriptions and gr aphical representations of the three network types are f or illustration only , and are not actual configurations .
38 Planning and engineering Figure 10 Small network configuration Medium network A medium network can include the follo wing components: • one or multiple CS 1000 systems with Media Gate wa y and S.
Network configuration 39 Figure 11 Medium network configuration Large network A large network can include the follo wing components: • multiple CS 1000 systems with Media Gatew ay and Signaling Se.
40 Planning and engineering The redundant, pr imar y , and alter nate NRS can be either the VxWorks NRS or the Linux-based NRS (SPS/SRS). For the OCS 2007 Enter prise Edition ser ver , a SQL back end database ser v er is a requirement.
Network configuration 41 Figure 13 "Multiple customer network" (page 41) provides an e xample of a multiple customer network. The figure shows two customers: Customer 1 (Ottaw a) and Customer 2 (Belleville), each with their own set of associated phones and Signalling Ser vers.
42 Planning and engineering The Signaling Ser ver , OCS Pro xy ser v er (which runs MCM), OCS 2007 F ront End ser ver , and Active Director y are separate. The number of Signalling Ser ver(s), OCS 2007 Pro xies, and OCS 2007 F ront End ser v ers required f or each customer are the same as if each customer were par t of a single system.
Load Balancer planning 43 Mediation ser vers suppor ts only TCP . Howe ver , it can interact with TLS gatew ay through SPS . SPS can act as a redirect ser ver f or SIP messages so the link between CS 1000 and the SPS can be TLS. Load Balancer planning This section provide inf or mation on the Load Balancer requirements.
44 Planning and engineering Ta b l e 3 Load balancer minimum configuration Service Protocol Port (range) Description TLS pool TCP 5061 The client listens over the same connection that is open to the server. By default, the server listens on port 5061 (TCP).
Load Balancer planning 45 • Every Office Communications Ser ver must ha ve e xactly one network adapter . Multihoming an Office Communications Ser v er is not suppor ted. If a 10/100 network adapter does not meet the required bandwidth constraints, a gigabit network adapter must be used.
46 Planning and engineering address is used b y clients as a single point of connection to the pool. This address is listed in DNS and has an FQDN. Inter nal OCS clients require the DNS ser ver to estab lish a connection with the Enter pr ise Edition P ool.
Capacity planning 47 Capacity planning navigation • "OC 2007 client requirements" (page 47) • "Load Balancer capacity requirements" (page 47) • "SIP CTI (TR/87) ser vice.
48 Planning and engineering T o illustrate this, consider the follo wing high-lev el e xample: Client A sends a TR/87 SIP INVITE to Node 1 to monitor DN 1000. The TR/87 association is estab lished. Client B then sends a TR/87 SIP INVITE to Node 1 (the same node) to monitor DN 1000.
Capacity planning 49 Figure 16 SIP CTI (TR/87) example Mediation ser ver requirements The CS 1000 can process up to 13 000 simultaneous calls. Therefore , you ma y require sev eral Mediation ser v ers for one CS 1000.
50 Planning and engineering F or example , MCM works as a software load balancer in addition to a router . MCM uses a round-robin algorithm f or load balancing. When the current Mediation Ser ver does not ans wer , MCM jumps to the next Mediation Ser ver .
General requirements 51 The number of users the OCS Proxy ser ver with MCM can handle depends on the usage and the number of calls per hour per user . For e xample, assuming 5 cph/user f or V oIP calls would give 3000 users (15 000 cph/5 cph/user = 3000 users).
52 Planning and engineering • "OC client authentication" (page 59) • "A uthor ization of TR/87 (Remote Call Control) Ser vice Requests" (page 59) • "Signaling and Media .
General requirements 53 Hard ware Requirements Use the f ollowing table to deter mine hardware requirements f or the OCS 2007 Standard and Enter pr ise Edition ser v er . Ta b l e 6 Office Communications Server 2007 Standard and Enterprise Edition hardware requirements Hardware Requirements CPU Dual processor, dual core 2.
54 Planning and engineering Ta b l e 9 Back end database f or a small to medium Enterprise pool CPU Dual processor, dual-core 2.6 GHz + Disk Drive 1 (2 × 18 GB) for OS and Page File Drive 2 (36 GB, 1.
General requirements 55 Communications Ser ver that runs Microsoft Vir tual Ser ver 2005. F or additional inf or mation about Vir tual Ser ver 2005, see the Vir tual Ser v er Web site at www .microsoft.com/windowsserversystem/vir tualser ver/def ault.
56 Planning and engineering Ta b l e 1 2 Inputs Input Description TN_MO_Users Total number of Office Communicator users that use the SIP Access Ports for voice services. PCA_MO_Users Number of Office Communicator users that use Personal Call Assistant (PCA).
General requirements 57 Traffic (CCS) Traffic (Erlang) Number of ports 70 1.94 7 75 2.08 7 80 2.22 7 85 2.36 7 90 2.5 8 95 2.64 8 100 2.78 8 125 3.47 9 150 4.17 10 175 4.86 12 200 5.56 13 225 6.25 14 250 6.94 15 275 7.64 16 300 8.33 17 325 9.03 18 350 9.
58 Planning and engineering Traffic (CCS) Traffic (Erlang) Number of ports 2000 55.56 74 2500 69.44 90 3000 83.33 106 3500 97.22 121 4000 111.11 137 4500 125 152 5000 138.89 168 6000 166.67 198 7000 194.44 228 8000 222.22 258 9000 250 288 10 000 277.78 318 20 000 555.
General requirements 59 The por t range can be controlled (restricted) to a smaller range using the group policy settings as described on the Microsoft W eb site: suppor t.microsoft. com/def ault.aspx?scid=KB;EN-US;903056 P or t ranges must not overlap .
60 Planning and engineering Figure 17 Signaling security • Secure Management Zone (SMZ) provides management access to local and remote devices ov er a secure connection. SMZ documents the LAN and W AN configurations required f or secure management.
General requirements 61 Figure 18 Signaling security with TLS Dial Plan considerations Nor tel Conv erged Office is comprised of the follo wing two components: • SIP CTI Ser vices provides CS 1000 native TR/87 suppor t to enable the Remote Call Control functionality av ailable with Office Communicator .
62 Planning and engineering • CS 1000 Call Ser ver configuration relating to the SIP Gatewa y • OCS Location Profile, P olicy , Phone Usage, and Route configuration.
General requirements 63 Figure 19 Signaling and media paths Number formats supported by Office Communicator Dialstrings and E.164 International number f or mat are the two types of numbers used by Office Communicator . Both number formats apply to computer and phone calls with Office Communicator .
64 Planning and engineering All E.164 numbers presented to the CS 1000, computer , or phone are e xpected in the f ollowing format: +<countr y code><national number> F or example , in Nor .
General requirements 65 A nor malization r ule can be used to str ip the digit in brac kets to conf or m to the e xpected f or mat f or E.164 numbers when using the Conv erged Office f eature: +31123456789 F or more inf or mation about Nor malization rules, see "Creating Nor malization rules" (page 193) .
66 Planning and engineering If calls that enter the Call Ser ver are inter national and outside of the countr y of the caller , the translator must contain entr ies that recognize the international numbers and route the call to the appropr iate route list.
T elephony Gate wa y and Ser vices planning 67 System, platform, or application Supported M1/CS 1000 Systems CS 1000M SG (CP PIV) Yes CS 1000M MG (CP3/4) Yes CS 1000M MG (CP PIV) Yes CS 1000E Yes MG 1.
68 Planning and engineering Figure 22 SIP routing Calls made to a CS 1000 that is different from the twinned telephone base uses two SIP trunks: one incoming and one outgoing. Additional SIP tr unks are needed, if users commonly call between CS 1000 systems.
T elephony Gate wa y and Ser vices planning 69 Figure 23 Computer call LG-Nortel IP Phone 8540 OCS desk phone An Enter pr ise V oice only client (no PBX integ ration enabled) that is configured f or an OC 2007 client or 8540 OCS desk phone, will be ab le to make PSTN calls using the CS 1000 as the gatewa y .
70 Planning and engineering Office Communicator-initiated Call T ransfer in Computer and PBX Integration Enabled If the Office Communicator transf ers a call, the SIP stack of the CS 1000 m ust handle the request to transf er the call.
T elephony Gate wa y and Ser vices planning 71 V oIP calls can only be placed to other Office Communicator users (computer to computer calls). Outgoing V oIP calls to telephone numbers for Microsoft Office Communicator Mobile are not suppor ted.
72 Planning and engineering Video Call T ransfer Office Communicator calls made in Computer mode that hav e established video can transf er to another Office Communicator user in Computer mode—although the new call is audio only . The transf erred Office Communicator user experiences the call becoming audio only .
Remote Call Control with SIP CTI 73 ipDialog Ethernet Phone Office Communicator clients can work with the ipDialog Ethernet Phone only if it is tandemed through a CS 1000. Country or region tone configuration Countr y or region tone configuration is not suppor ted by Office Communications Ser ver or Office Communicator .
74 Planning and engineering Figure 24 Simple network dia gram The TR/87 FE is the application that resides on the CS 1000 Signaling Ser ver to suppor t the telephony control requests and responses received from the Office Communicator 2007 client within an Office Communications Ser ver 2007 deplo yment.
Remote Call Control with SIP CTI 75 Systems, platforms, and applications Interoperable Supported CS 1000M SG (CP-PII and -PIV) Y Y CS 1000M SG (CP PIV) Y Y CS 1000M MG (CP-PII and -PIV) Y Y CS 1000E S.
76 Planning and engineering Systems, platforms, and applications Interoperable Supported WLAN Handset 2212 Y Y IP Phone 1110 Y Y IP Phone 2007 Y Y IP Phone 1120E Y Y IP Phone 1140E Y Y IP Phone 1150E .
Remote Call Control with SIP CTI 77 Systems, platforms, and applications Interoperable Supported Symposium Agent Y N Symposium Agent Greeting Y N Symposium Express Call Center (SECC) Y N Symposium Cal.
78 Planning and engineering Systems, platforms, and applications Interoperable Supported AT&T SIP trunk Y N Broadsoft Y N ACME SBC Y N 3100 Mobile Communication Gateway Y N Redundancy Remote Call .
Remote Call Control with SIP CTI 79 • After an ev ent occurs that causes the IP Phones to register to a ser ver other than the F ront End ser ver (and then to return to the F ront End ser ver), the Office Communicator 2007 client does not automatically f ollow the IP Phone registr ation.
80 Planning and engineering The Microsoft Office Communicator client has no automated mechanism to register to the branch. Users must wait f or the existing dialog to time out (30 minutes) or man ually log out and log on again after the IP phones change to local mode.
Remote Call Control with SIP CTI 81 Feature Operation Description • Conference Call - cannot be performed through Office Communicator . • Call Hold - can be performed through Office Communicator. • Call Transfer - Analog telephones do not support the Conference and Transfer key features.
82 Planning and engineering Feature Operation Description Office Communications Server and MCS coexistence ATTENTION All Converged Office users must have their extension configured as CLS CDMR. A user cannot have both Office Communications Server and MCS enabled for their extension (all TN’s that have a particular number and extension).
LCS 2005 and OCS 2007 coexistence 83 suppor ted configuration because of incompatible underlying libraries. The same CS 1000 can be connected to two or more different communication ser vers (LCS 2005 or OCS 2007). The follo wing must be considered f or coe xistence of LCS 2005 and OCS 2007: • The CS 1000 m ust be upgraded to Release 5.
84 Planning and engineering MCM 2.0 to MCM 3.0 There is no direct upgrade path from MCM 1.0 or 2.0 to MCM 3.0 . MCM 3.0 must be installed on the OCS Pro xy ser ver .
Migration planning from LCS 2005 to OCS 2007 85 Prerequisites Upgrading to Office Communications Ser ver 2007 assumes the follo wing: • An understanding of the basic migration process. Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.
86 Planning and engineering • An understanding of the coexistence interactions. F or more information, see "LCS 2005 and OCS 2007 coe xistence" (page 82) . • An understanding of CS 1000, Signaling Ser ver , and networks. • An understanding of the user migration process.
Migration planning from LCS 2005 to OCS 2007 87 Phase Description User experience 2. Deploy OCS 2007 and begin moving users to the new server or pool. Deploy a new Office Communications Server 2007 Enterprise pool or Standard Edition server. If required, deploy an Archiving and CDR Server.
88 Planning and engineering Phase Description User experience 8. Continue migrating users. Migrate remaining users. Enable users for enhanced presence. Roll out the OC 2007 client and the Live Meeting 2007 client to the users. • OC 2007 users can use the full functionality of OC 2007 when communicating with other OC 2007 users.
Migration planning from LCS 2005 to OCS 2007 89 Migrating users fr om LCS to OCS Step Action 1 Upgrade y our per imeter network by deplo ying an Access Edge Ser ver that communicates with Live Communications Server 2005 Director .
90 Planning and engineering 7 Configure PCA routing for ne w OC client users on the CS 1000. After configuration of PCA routing, users will be allowed to use T elephony Gate way and Services (V oIP) and RCC functionality . A Ser ver URI field should be changed for migr ated users to enable SIP CTI functionality .
Unified Messaging 91 Ta b l e 2 0 CallPilot configurations OC User (VoIP) with RCC and CS 1000 Phone OC User (VoIP) with no RCC and CS 1000 Phone OC User (VoIP) with no RCC and no CS 1000 Phone LG-N.
92 Planning and engineering A TTENTION For Con verged Office users not using a Nor tel telephone For Conv erged Office users who use v oice communications through the OC client or from an LG-Nor tel.
Unified Messaging 93 Logon from OC Logon and password direct direct direct N/A MWI on OC Yes Yes Yes Yes Yes Outlook New msg in inbox New msg in inbox New msg in inbox New msg in inbox New msg in inb.
94 Planning and engineering Ta b l e 2 2 Unified Messaging 2007 integrated Option 2 OC User (VoIP) with RCC and CS 1000 Phone OC User (VoIP) with no RCC and CS 1000 Phone OC User (VoIP) with no RCC a.
Unified Messaging 95 A TTENTION For Con verged Office users not using a Nor tel telephone For Con verged Office users who use voice communications through the OC client, an 8540 telephone, or both .
96 Planning and engineering VM access from OC Dial SA DN Dial SA DN Dial SA DN Dial SA DN N/A Login from OC p/w only p/w only p/w only p/w only N/A MWI on OC Yes Yes Yes Yes Yes Outlook New msg in inb.
Unified Messaging 97 A TTENTION For Con verged Office users not using a Nor tel telephone For Con verged Office users who use voice communications through the OC client, an 8540 telephone, or both .
98 Planning and engineering Figure 25 Signaling integrated Signaling with non-integrated V oice Mail In a non-integrated configuration, the Office Communicator (OC) client does not hav e the capability of selecting a V oice Mail option, the signaling between Exchange and the OC client is not defined.
Unified Messaging 99 Figure 26 Signaling non-integrated Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.0 30 Apr il 2008 Copyright © 2005–2008, Nor tel Networks .
100 Planning and engineering Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.0 30 Apr il 2008 Copyright © 2005–2008, Nor tel Networks .
101 Installation This chapter contains the procedures necessar y to install CS 1000 components and Office Communications Ser ver (OCS) 2007 on a CS 1000 system. The first step is to install the necessar y CS 1000 components (if you do not already hav e a working CS 1000 system in place), and then install the Microsoft ser ver components.
102 Installation Installation navigation Figure 27 Installation and configuration flow • "CS 1000 and Signaling Ser ver installation" (page 105) • "OCS 2007 component installation.
OCS 2007 installation preparation and deployment 103 OCS 2007 installation preparation and deployment The follo wing figure Figure 28 "OCS 2007 installation preparation and deplo yment flow char t" (page 104) depicts the high-le vel topics required to deplo y OCS 2007.
104 Installation Figure 28 OCS 2007 installation preparation and deployment flow chart Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.0 30 Apr il 2008 Copyright © 2005–2008, Nor tel Networks .
OCS 2007 component installation 105 CS 1000 and Signaling Ser ver installation The first step in the installation and configuration process is to install the CS 1000 and Signaling Ser v er .
106 Installation A TTENTION The following is a list of the required patches for the Microsoft OCS 2007 installation: • OCS 2007 – Standard Edition RTM KB 942872 V ersion 6362.0 plus hotfix • Description of the Office Comm unicator 2007 hotfix pac kage: December 17, 2007 KB 943083 V ersion 2.
OCS Proxy server installation 107 Office Communications Server (OCS ) 2007 Enterprise P ool OCS 2007 Enter prise Edition is designed for large-scale deployment where multiple Office Communications Ser v er Enter prise Edition ser vers are deplo yed as a pool, typically behind a load balancer .
108 Installation Installing the OCS Pro xy server Step Action 1 On the Windows Star t menu, choose Run . 2 Navigate to the C:Office Communications Ser ver_Ev alse_ev alsetupi386 f older . 3 F or OCS Standard Edition: ser ver .msi SER VER=PRO XY SKU=SE OR F or OCS Enter prise Edition: ser ver .
MCM installation 109 3 Select TCP/IP properties and add DNS ser ver IP . F or e xample, 47.11.108.50. 4 Go to My Computer , r ight-click and select System Pr oper ties . 5 Enter the Computer Name of each FE ser v er . F or e xample, ocs-fe-1. 6 Click domain.
110 Installation 2 Select Use an existing account and enter your user ID and pass word OR select Create a new account . 3 Open the MCM Console window and select the Actions menu. 4 On the Actions menu, choose Start to star t the MCM ser vice. —End— MCM must be installed on the OCS Proxy Server .
111 Configuration The follo wing flow char t depicts the configuration order of the components. Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.
112 Configuration Figure 29 Configuration flow chart Active Directory configuration Active Directory configuration takes place in the Active Director y Users and the Computers (ADUC) windo w . Selecting the Users f older re veals the list of users as depicted in Figure 30 "Active Director y (Microsoft LD AP ser v er)" (page 113) .
Active Directory configuration 113 By default MCM uses GC LD AP ser ver which contains par tial inf ormation about all objects in the Active Director y domain forest.
114 Configuration Defining users Step Action 1 Select a user from the list in the Users f older . 2 Right-click the user , and select Properties . 3 The Proper ties window opens as depicted in Figure 31 "User proper ties" (page 114) .
Active Directory configuration 115 6 Click the chec k box ne xt to Enable user f or Office Communications Server . 7 In the fields pro vided, define the user Sign-in name and the Server or pool ). Office Communicator 2007 uses these addresses to place calls.
116 Configuration 9 F or enabling Remote Call Control only , select Enable Remote Call Control and configure the Ser ver URI and Line URI. See Figure 33 "Enable Remote call control" (page 117) .
Active Directory configuration 117 Figure 33 Enable Remote call contr ol Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.0 30 Apr il 2008 Copyright © 2005–2008, Nor tel Networks .
118 Configuration Figure 34 Enable Enterprise V oice and PBX integration Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.0 30 Apr il 2008 Copyright © 2005–2008, Nor tel Networks .
Office Communications Server configuration 119 Figure 35 Enable both RCC and Enterprise V oice Office Communications Server configuration The star ting point for T elephony Gate wa y and Ser vices configuration is the Office Communications Ser ver 2007 component.
120 Configuration Load Balancer configuration The pool of F ront End ser vers is organiz ed to process inbound and outbound traffic. The role of the Load Balancer in this architecture is to route incoming SIP-messages to the less busy ser ver on the base of configured algorithm.
Office Communications Server configuration 121 V oice mail must alwa ys be configured on the CS 1000 and not Office Communicator . Configuring communication to the CS 1000 gate wa y is perf or med at the Mediation Ser ver .
122 Configuration —End— Applying policy Step Action 1 In the User Options window , click Enable Enterprise V oice . 2 Select Another P olicy . The policy can be assigned simultaneously to se veral users using the Configure Users wizard.
Office Communications Server configuration 123 1000. In this situation, the IP address of the CS 1000 m ust be added to the Authorized Host list. Configuring the Host Authorization and Routing for .
124 Configuration Figure 37 Office Communications Server Front Ends 3 Click on the Host A uthorization tab and select the Edit b utton. 4 In the Ser v er section, click on the IP Address b utton and enter the IP address of the OCS Pro xy ser v er . F or details, see Ta b l e 2 5 "Routing rules" (page 130) .
Office Communications Server configuration 125 Figure 38 Routing tab 8 In the Add Static Route window , For Domain: enter the domain defined in the Ser ver URI.
126 Configuration Configuring host authorization for the OCS Pro xy Step Action 1 Open the OCS Proxy ser ver , click the Windows Start button, point to Administrative T ools , and then click Computer Management .
Office Communications Server configuration 127 Figure 40 Office Communications Server Management Console 3 F or the OCS Proxy , no static route is required. MCM routes inbound calls to the proper Mediation Ser ver based on the Routing T able settings on the MCM.
128 Configuration Figure 41 Routing tab 5 Click the Host A uthorization tab . 6 Click Edit to open the Edit Authorized Host window . 7 In the Edit A uthor ized Host window , enter the IP address , select both the Throttle As Server and T reat As A uthenticated chec k bo xes , and then click OK .
Office Communications Server configuration 129 Figure 42 Edit Authorized Host —End— The f ollowing tab le shows a number of possible configur ations of OCS 2007 and the required entries f or each. The transpor t to CS 1000 is TCP f or all configuration types.
130 Configuration OCS Front End Servers Pool OCS Mediation Server OCS Application Server Port: 5060 Phone URI: No Replace host in request URI: No Host Authorization • IP Address of the OCS Applicat.
Office Communications Server configuration 131 Configuration Type Comp- onent Host Authorization Dest- ination User / Domain Phone URI Trans- port Port 3.
132 Configuration Configuration Type Comp- onent Host Authorization Dest- ination User / Domain Phone URI Trans- port Port Mediation Servers IP 6. Single Front End server and Pool of OCS Proxies, SIP.
Office Communications Server configuration 133 Configuration Type Comp- onent Host Authorization Dest- ination User / Domain Phone URI Trans- port Port 8.
134 Configuration 5 In the FQDN bo x, make sure the FQDN listed matches that of the Mediation Ser ver you ha ve selected. 6 Open a command prompt, change to the root director y , and type nslookup and (FQDN of the ser ver) using the FQDN displa yed on the Mediation Ser ver General tab , and then press Enter .
MCM 3.0 configuration 135 • Management Console The MCM Call Processing Ser vice handles the Session Initiation Protocol (SIP) telephony traffic betw een the CS 1000 and the Office Communications Ser ver .
136 Configuration Figure 43 MCM arc hitecture The f ollowing examples illustrate how MCM handles call inf or mation. Understanding the role of MCM in the T elephony Gatew a y and Ser vices component helps you to determine the configuration.
MCM 3.0 configuration 137 The call is routed to the NRS . The invite is sent to the NRS, which retur ns a 302, and the CS 1000 sends an invite to the MCM Pro xy . At this stage, the invite includes a special header called x-nt-ocn that contains the actual number called.
138 Configuration — Not responding - Pr imar y SRS/SPS is not responding. For normal processing, the Secondar y SRS/SPS m ust be s witched to an Active state.
MCM 3.0 configuration 139 Figure 44 MCM MCM menu options The f ollowing lit describes the function of each MCM menu command: • Actions — Star t - star t MCM ser vice — Stop - stop MCM ser vice .
140 Configuration — Active Directory Quer y — Backup — Restore — Set Log Le vel • Help — Get help and general inf or mation about MCM MCM Configuration T o access the MCM Configuration window , go to the MCM console window , select the T ools menu and then select Configuration .
MCM 3.0 configuration 141 Network T opology section The f ollowing is a description of some of the configuration fields in the Network T opology section of the MCM configuration window .
142 Configuration an INVITE request providing information about which dedicated Mediation Ser ver or Mediation Ser ver pool to process this message. The parameter value f or SIP Gatewa y Endpoint Name is configured in Element Manager under System, IP Network, Nodes: Servers, Media Car ds, Signaling Server Properties .
MCM 3.0 configuration 143 Ta b l e 2 7 Incoming Call Processing parameters Configuration field Description Called Phone Context Phone Context of calls to be processed by MCM. This entry depends on the dial-plan (CDP or UDP) and should be the same as Private/CDP domain name entries in the Signaling Server Element Manager.
144 Configuration Figure 47 Element Manager SIP URI MAP Active Directory configuration section There are two modes f or Active Director y (AD) Configuration: Realtime or Local Cache. Realtime mode is used for end-user ID mapping, which requires a Lightweight Director y Access Protocol (LD AP) quer y .
MCM 3.0 configuration 145 Active Directory quer y The Active Director y Quer y tool is used to check Active Directory mapping configuration. It searches for a user-id (SIP URI) by a giv en telephone number , and vice v ersa. This tool is only used f or maintenance, and emulates the same algorithm that is used by the MCM ser vice in r un-time.
146 Configuration Figure 49 Get phone Field propa gations to the Global Catalog MCM uses the Active Director y Global Catalog to search for necessar y user inf or mation. How e ver , by default, this Global Catalog contains f ew Activ e Director y fields that can be used f or MCM (for e xample, otherT elephone).
MCM 3.0 configuration 147 Step Action 1 Open the Active Director y Schema snap-in as depicted in the e xample Figure 50 "Replicating attr ibutes to the Global Catalog" (page 147) . 2 Select Attributes on the left pane. 3 In the Name pane, select the required field.
148 Configuration Network dial plan section The follo wing table describes the fields for Dial plan and Access code. Ta b l e 2 9 Network dial plan Configuration field Description Dial plan Use the dial plan to make calls between the CS 1000 and OCS (CDP or UDP).
MCM 3.0 configuration 149 Configuring MCM for Remote Call Control F or Remote Call Control, the Nor tel MCM application that resides within the Office Communications Ser ver domain provides suppor t for authorizing TR/87 ser vice requests and redundancy .
150 Configuration Figure 51 Enable phone integration on the client Redundancy Redundancy of the TR/87 interf ace is not provided nativ ely with Office Communications Ser ver 2007. Office Communicator does not suppor t multiple Remote Call Control SIP URIs or SIP 300/302 redirection messages.
T elephony Gate wa y and Ser vices configuration 151 Call Server configuration CS 1000 configuration in volv es two separate functions: Signaling Ser ver configuration and Call Ser ver Configuration. All of the Signaling Ser v er configuration is perf or med in Element Manager .
152 Configuration Figure 52 Codec configuration Loss Plan configuration In order for DTMF digits to be transmitted at the correct volume, especially f or Office Communicator 2007 to PSTN communications, the Loss Plan f or the CS 1000 must be correctly configured.
T elephony Gate wa y and Ser vices configuration 153 A TTENTION When any kind of in-band signaling is to be used as payload audio pack ets (for example , DTMF tones) in the egress direction (IP to TDM), the Signal Limiter functionality must be disabled.
154 Configuration In this figure, the CS 1000 has a HLOC of 354 and an LOC dialing plan entr y of 344. The LOC dialing plan 344 is not dialab le, how ev er , calls to the DN: 6712 e xtend the call to the number 6-344-5000. By PCA e xtending the call to 6-344-5000, a SIP Invite is sent to the OCS Proxy ser ver .
T elephony Gate wa y and Ser vices configuration 155 When you use a PCA, the MARP must be on the DN k ey of the phone itself , not the PCA. If the MARP is on the PCA, CTI clients (such as Office Communicator) do not receive Remote Call Control call pop-ups f or incoming calls (in addition to other problems).
156 Configuration DES PCA TN 096 0 08 15 VIRTUALTYPE PCA CDEN 8D CTYP XDLC CUST 0 NUID NHTN CFG_ZONE 000 CUR_ZONE 000 ERL 0 ECL 0 FDN TGAR 1 LDN NO NCOS 0 SGRP 0 RNPG 0 SCI 0 SSU XLST SFLT NO CAC_CIS.
T elephony Gate wa y and Ser vices configuration 157 ANIE 0 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 TRN 18 AO6 19 CFW 16 20 RGA 21 PRK 22 RNP 23 24 PRS 25 CHG 26 CPN 27 28 29 30 31 DATE 30 AUG 2007 F or more information about PCA, see Features and Services (NN43001-106).
158 Configuration F or PCA twinning to work correctly in a UDP environment, the full Original Called Number (OCN) must be sent b y the CS 1000 to the Office Communications Ser ver . T o hav e the full OCN sent, the CLID tab le must be configured with the Home Location (HLOC) of the CS 1000.
T elephony Gate wa y and Ser vices configuration 159 Ta b l e 3 5 LD 15 Prompt Response Description REQ chg TYPE net TYPE NET_DATA CUST 0 OPT AC2 FNP CLID yes SIZE 5 INTL 1 ENTRY 0 HNTN HLCL 967 HLOC 354 ... The response to SIZE m ust be a number g reater than 0.
160 Configuration all OCS and Enter prise Edition P ools. Also , the FQDN must resolv e to the IP address of the OCS for all types of DNS quer ies (not just f or the SIP ser vice type). DNS ser ver must respond with the correct IP f or a gener ic DNS quer y .
T elephony Gate wa y and Ser vices configuration 161 A CS 1000 with e xisting SIP tr unks requires a configuration change to be compatible with Office Comm unications Ser ver .
162 Configuration A TTENTION The Route Data Bloc k (RDB) must not ha ve a value configured f or the prompt INST . Otherwise, incoming calls from Office Communicator to the CS 1000 do not work.
T elephony Gate wa y and Ser vices configuration 163 The Route Data Block is ESN5 if the output from Element Manager , or a terminal window , is: TYPE RDB CUST 00 DMOD ROUT 10 DES IPROUTE TKTP TIE VTRK YES ZONE 100 PCID SIP .
164 Configuration Figure 56 SIP T runk Domain name Configuring the SIP T r unk Domain name describes how to configure the SIP T runk domain name to match the Office Communications Ser ver domain name. Configuring the SIP T runk Domain name Step Action 1 Log into the Element Manager page f or the Signaling Ser ver .
T elephony Gate wa y and Ser vices configuration 165 Figure 57 Element Manager Signaling Ser ver Properties 7 In most cases, the v alue f or the field SIP Domain Name must match the domain of the Office Communications Ser ver . In Figure 57 "Element Manager Signaling Ser v er Proper ties" (page 165) , the SIP Domain name is ocs2007a.
166 Configuration Figure 58 SIP URI Map The SIP URI Map must match the NRS ser ver configuration in the follo wing manner : • The Private/UDP domain name maps to the L0 Domain on the NRS • The Private/CDP domain name maps to the L1 Domain on the NRS MCM must be configured to match one of the domain names .
T elephony Gate wa y and Ser vices configuration 167 SIP Gateway CLID P arameters configuration The SIP Gatewa y CLID parameters are used to adjust the format of telephone n umbers for incoming call appearances.
168 Configuration +<countr ycode><area code><subscr iber number>. The parameters Subscriber/Number of digits to strip and prefix to inser t are used to modify the f or mat of subscr iber numbers presented from the PSTN due to region specific requirements.
T elephony Gate wa y and Ser vices configuration 169 • Three different modes : Pro xy All, Redirect, and Proxy SIP Gate wa y Calls • T ranspor t : TLS (5061) and TCP (5060) F or inf or mation on configur ing the SPS, see NRS configuration.
170 Configuration The NRS must ha ve the same UDP or CDP dialing plan prefix to route calls to the MCM endpoint. This UDP or CDP dialing plan prefix is the same one configured f or the PCA calls.
Remote Call Control configuration 171 In order to suppor t these calls, placed through the SIP Gate wa y , you must configure the parameters CNTC, NA TC, and INTC in LD 15.
172 Configuration 4 Choose Enable Remote call contr ol to enable clients control of the PBX phone or Enable Enterprise V oice and click the Enable PBX integration bo x to enab le both Remote Call Control and Enter prise V oice.
Remote Call Control configuration 173 Figure 61 Enable integration with your phone system CS 1000 configuration Application Module Link (AML) is the main interface used to suppor t call control requests from SIP CTI clients between the SS TR/87 FE application and the CS 1000.
174 Configuration LD 17: Configure AML Link Prompt Response Description REQ CHG Change existing data. TYPE ADAN ADAN <new ELAN #> A new AML link; the link is an ELAN type. The link number can be from 32 to 47 on a small system and from 32 and 127 on a large system.
Remote Call Control configuration 175 Configuring the SIP CTI TR/87 ISM limit Incremental Software Management (ISM) (SIP CTI TR/87) is used to define the number of TNs that can be configured with the T87A class of ser vice.
176 Configuration A new CLS (T87A) is introduced to allow a TN to suppor t the SIP CTI application. The AST prompt is used to configure which DN ke y on the TN is controlled or monitored by the SIP CTI application. A maximum of two k eys per TN can be configured as AST ke ys.
Remote Call Control configuration 177 • Any Remote Call Control ser vice request sent by Office Communicator , such as Make Call or Ans wer Call, alwa ys apply to the device defined as the MARP TN.
178 Configuration Node parameter configuration The node IP is the IP address of the TR/87 FE: • Y ou can configure multiple nodes to suppor t TR/87 applications f or additional capacity . The Remote Call Control SIP URI of users determines which node the y use.
Remote Call Control configuration 179 SIP Gatewa y parameter configuration The SIP Gate wa y application must be enab led. T o enable the SIP Gate wa y , TR/87 FE uses the follo wing SIP Gatewa y co.
180 Configuration Also , the FQDN must resolve to the IP address of the OCS ser v er f or all types of DNS queries (not just f or the SIP ser vice type). (see Figure 65 "DNS configuration" (page 180) ) DNS ser ver must respond with the correct IP f or a gener ic DNS quer y .
Remote Call Control configuration 181 SIP CTI Ser vices configuration settings In Element Manager , under SIP CTI ser vices, the Calling De vice URI F or mat must be configured as phone-context=<SIP URI Map Entries> to suppor t OCS 2007 RCC. Ensure the Dial Plan prefix section values under SIP CTI Ser vices are configured.
182 Configuration Figure 66 SIP CTI Services settings P arameter: Service Enabled The def ault state of the SIP CTI ser vice is disab led. T o enforce the change of state f or this parameter , you m ust reboot. The SIP CTI ser vice consumes appro ximately 140 MB of RAM on the Signaling Ser v er when enabled.
Remote Call Control configuration 183 P arameter: Maximum Associations P er DN This parameter defines the maximum number of simultaneous TR/87 SIP dialogs that can be active f or a single DN. Multiple instances of Office Communicator (f or e xample, home, office, laptop) are active and each of them can hav e its own activ e TR/87 session.
184 Configuration SIP CTI Dial Plan prefixes The SIP CTI dial plan prefix es configuration settings are used to prefix phone numbers sent to the Call Ser v er as a result of SIP CTI call attempts. P arameter: National Prefix When calls are made to E.
Remote Call Control configuration 185 SIP CTI CLID configuration parameters The SIP CTI CLID parameters are used to adjust the f or mat of phone numbers f or incoming call appearances. F or Office Communicator these settings impact the format of numbers that appear on the incoming call pop-up f or Remote Call Control.
186 Configuration can be entered using the home location code to ensure a consistent unique f or mat throughout the enter pr ise. T wo scenarios are provided using the f ollowing e xample parameters:.
Remote Call Control configuration 187 Scenario 2, Dial Plan = CDP , Calling Device URI Format = phone-context= SIP GW URI map entries: The TEL URI generated f or the caller is: "tel:3000;phone-conte xt=cdp.
188 Configuration • An RCC call from Office Communicator to the E.164 number +16135006000 produces a call from the controlled DN to 616135006000. An RCC call from Office Communicator to the E.164 number +33123456789 produces a call from the controlled DN to 601133123456789.
Remote Call Control configuration 189 • An RCC call from Office Communicator to the E.164 number +31123456789 produces a call from the controlled DN to 00123456789. • An RCC call from Office Communicator to the E.164 number +33123456789 produces a call from the controlled DN to 00033123456789.
190 Configuration Figure 69 SIP URI Map Configuring CDR Call Detail Recording (CDR) records are produced for calls controlled using the Remote Call Control f eature. The f or mat of these CDR records is the same as those of calls dialed directly from a telephone’s k eypad.
Remote Call Control configuration 191 Figure 70 SIP INFO message The TR/87 FE that resides on the Signaling Ser ver contains a f eature to inser t the appropriate dial plan prefix, either national or international, depending on the location of the Call Ser ver and destination of the call.
192 Configuration Normalizing phone numbers Office Communicator 2007 requires that all phone numbers be in standard TEL URI f or mat as defined in RFC 3966 f or dialing and f or rev erse number lookup .
Normalizing phone numbers 193 tel:+14255551212;e xt=5551212;ad-rdn=telephoneNumber ;displa y- Name=(425)555-1212 The ad-rdn = telephoneNumber is a proprietar y parameter describes the type of the phon.
194 Configuration MCM provides authorization of Remote Call Control ser vice requests based on the configuration defined in Active Directory for each Office Communications Ser ver user .
Normalizing phone numbers 195 Figure 71 Normalization rule example for UDP dial plan Result • The nor malized v ersion (tel:+16139675000;ext=$1$2) of the business number in Activ e Director y entries is stored in the Global Address List (GAL) and downloaded at login by the Office Communicator 2007 client from the Address Book Ser vice.
196 Configuration Figure 72 Company phone n umber normalization rules for CDP 2 Refresh the Address Book on the ser ver b y issuing the follo wing command on the ser ver running ABSer vice as shown i.
Normalizing phone numbers 197 Figure 73 Refresh Address Book on the server 3 Exit from Office Communicator 2007. 4 Refresh Address Book on the client as shown in Figure 74 "Refresh Address Book on the client" (page 197) .
198 Configuration SIP Routing and Redundancy configuration Office Communicator is a soft phone application as well as a SIP User Agent (U A). Office Communications Ser ver F ront End ser v er (Standard Edition Ser ver or Enter pr ise Edition Ser v er) hosts Office Communicator .
OCS 2007 users using UM 2007 in integrated mode 199 Configuring a basic mailbox f or the UM user Step Action 1 Configure the OCS user mailbox in Exchange UM. 2 Configure SIP URI. F or e xample, ocs2007a.cor p .nor tel.com 3 Add the Exchange UM Address (Extension) f or ev er y Exchange UM user .
200 Configuration Figure 75 User Properties window for Exchange UM 4 Click on the E-mail Ad dresses tab . 5 Click on the Add men u and select EUM Address . 6 In the UM Address (Extension) window , enter the useralias@domain of the user in the Address/Extension field .
OCS 2007 users using UM 2007 in integrated mode 201 Figure 76 UM Address 7 Click on the Br owse button to find the associated Dial plan f or the user .
202 Configuration Figure 77 Dial plan window 8 The ne w EUM address is added. T o find the ne w UM Extension, click on the Mailbo x Features tab , r ight-click on Unified Messa ging , and select Unified Messaging Properties . In the UM Addresses (Extensions) field, there are three addresses.
OCS 2007 users using UM 2007 in integrated mode 203 Figure 78 Unified Messaging Properties window —End— Option 2 adding CS 1000 DN as Exchange UM These procedures assume the installation procedures for Exchange UM hav e already been completed. Download Microsoft documentation from the Download Center at w ww .
204 Configuration 4 —End— Adding Exchange UM Step Action 1 F rom the Exchange Management Console windo w , clic k on Recipient Configuration , and select Mailbo x . 2 Select a user . For e xample, Brendan McCar th y 3 Right-click on the user and select Properties .
OCS 2007 users using UM 2007 in integrated mode 205 Figure 80 UM Address 7 Click on the Br owse button to find the associated Dial plan f or the user .
206 Configuration Figure 81 Dial Plan window 8 The ne w EUM address is added. T o find the ne w UM Extension, click on the Mailbo x Features tab , r ight-click on Unified Messa ging , and select Unified Messaging Properties . In the UM Addresses (Extensions) field, there are three addresses.
OCS 2007 users using UM 2007 in integrated mode 207 Figure 82 Unified Messaging Properties window —End— Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.
208 Configuration Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.
209 Maintenance Introduction The following are maintenance tips f or MCM 3.0 . F or more inf or mation on troubleshooting tips , see "T roub leshooting" (page 215) section. Communication Server 1000 No new SIP tracing capabilities are av ailable on the Communication Server 1000.
210 Maintenance SIP tracing can be filtered by DN number . MCM SIP tracing is implemented as par t of the application logging functionality . Special commands are not required.
Remote Call Control 211 Prompt Response Description > SIPCTITraceLevel <level> Configure the TR87 SIP message Trace Level. The level can be one of the following: 0 –TR87 SIP message body (E.
212 Maintenance Prompt Response Description > SIPCTIStop all De-acquire all AST DNs and terminate all the TR87 SIP sessions. > SIPCTIStop <dn> De-acquire one specific AST DN and terminate all the TR87 SIP sessions associated with this AST DN.
Remote Call Control 213 • SIPCTIT otalMonitorStopSuccesses • SIPCTIT otalConf erenceCallRequests • SIPCTIT otalConf erenceCallSuccesses • SIPCTIT otalSetF orwardingRequests • SIPCTIT otalSet.
214 Maintenance Prompt Response Description 4—Print all input and output AML data buffer except POLLING message with IE type and data decoding. ATTENTION This trace prints out AML messages to and from CS at the transport layer.
215 T r oubleshooting Use the follo wing procedures to assist in troubleshooting general Con verged Office problems . Checking T elephon y Gatewa y (SIP Gatewa y) configuration Checking T elephony G.
216 T roub leshooting Checking Remote Call Control (SIP CTI) configuration Checking Remote Call Contr ol configuration Step Action 1 Check all required Communication Server 1000 resources (packages , license, and Communication Ser v er 1000 patches).
SIP CTI ser vices does not come up 217 Symptom: After SIP CTI ser vices are activated, you are unab le to log on to the Signaling Ser ver through Element Manager . When rebooting, some HTTP tasks are not up. P ossible cause: Insufficient memor y . Solution: Check the memor y and upgrade the memor y to 1 gigabyte (GB), if required.
218 T roub leshooting Figure 83 nslookup tool Solution 1: Check configuration parameters in AD Check the configuration parameters in Active Director y for this user .
SIP CTI ser vices does not come up 219 P ossible cause: VSID or ELAN ID is lower than 32. Solution: F ollow the procedure "Reconfigure SIP CTI ser vice" (page 219) to solve this issue. Reconfigure SIP CTI ser vice Step Action 1 Reconfigure the VSID and ELAN IDs so both are greater than 32.
220 T roub leshooting 3 In LD 48, chec k the ELAN status on the Call Ser ver Ta b l e 4 0 LD 48 Prompt Response Description .stat elan Check the ELAN status on the Call Server Screen output: SER VER T ASK: ENABLED ELAN #: 032 DES: CDLCS APPL_IP_ID: 47.
MCM not synchronizing new users in AD Cache mode 221 Checking the Global Catalog content manually Step Action 1 Install the Operating System Suppor t T ools on the ser ver (usually the T ools setup is on the MS Windows 2003 Ser ver setup disk). 2 Run the LDP tool (%ProgramFiles%Suppor t T oolsldap .
222 T roub leshooting Accessing permissions for the AD object pr operties Step Action 1 Install the Operating System Suppor t T ools on the ser ver (usually the T ools setup is on the MS Windows 2003 Ser ver setup disk). 2 Run the ADSIEdit tool (%Prog ramFiles%Suppor t T oolsad- siedit.
P op-up not display ed 223 Enabling pr opagation of the Active Directory field to the Global Catalog Step Action 1 Open the Active Director y Schema snap-in. 2 Select the Attributes f older on the left pane . 3 Find and the right-click the necessar y field ( otherT elephone ).
224 T roub leshooting P ossible causes: The Phone Conte xt ma y be not correct. Address Book Ser vice ma y not be properly setup . Phone integration is not activ ated. Solutions: • Ensure that the user’s name is in Activ e Director y , the MCM, and the Signaling Ser ver (L1 parameter) hav e the correct Phone Context.
Capturing traces and logs 225 Symptom: The telephone is on Call F orward to another number . When the Office Communicator user who is associated to this telephone logs in (this telephone is controlled b y the Office Communicator user through SIP CTI), the Office Communicator cancels the Call F orward.
226 T roub leshooting AML traces on the Call Ser ver (SIP CTI only) In LD 48, activate AML traces on the Call Ser ver (SIP CTI only): Ta b l e 4 1 LD 48 Prompt Response Description EDD000 enl msgi 32 .
Capturing traces and logs 227 Figure 85 Example of screen output f or SIP CTI T races on the Signaling Server SIP Gatewa y traces on the Signaling Server In PDT , activate Gatewa y traces on the Signaling Ser ver .
228 T roub leshooting Figure 86 Example of screen output for SIP Gatewa y trace MCM logs MCM 3.0 generates a daily log file with no maximum siz e restr ictions and no cleanup procedures are implemented. The contents of the e xisting log file remain in all cases.
Capturing traces and logs 229 • SIP : SIP messages (filtered by distinct DN) are logged fur ther to alar ms. Only one DN can be specified at the same time in MCM. • Debug : Deb ug information is logged to the MCM log file. • SIP and Debug T o clear a log, clic k on the Clear Log b utton.
230 T roub leshooting T o tur n off MCM logging, see "Resetting MCM debug trace" (page 231) . MCM log file output The f ollowing shows a snippet from the log output file: 12/14/2007 11:11:37 AM: 3.0.1.76: Debug: OnCustomCom- mand: got command: update config data 12/14/2007 11:11:38 AM: 3.
Capturing traces and logs 231 Figure 88 Event Viewer window Resetting MCM debug trace Use the following procedures to reset the MCM deb ug trace . Resetting MCM debug trace Step Action 1 On the MCM interface , select T ools and then choose Logs from the menu.
232 T roub leshooting Activating OCS logs Step Action 1 Right-click on the OCS pool and select Logging T ool and then choose New Deb ug Session . 2 In the OCS 2007 Logging T ool window , specify the Components to trace, Se verity le vel, and other log file options.
Capturing traces and logs 233 2 Choose the General tab . 3 Select the T urn on logging in Communicator and the T urn on Windows Event Logging for Comm unicator checkbo xes . See Figure 90 "T ur n on Logging and Windows Ev ent Logging" (page 233) .
234 T roub leshooting Figure 91 No PBX connection for OC c lient Case chec klists Use the follo wing chec klists prior to opening a case to ensure that all rele vant inf or mation is collected: Ta b l.
Case checklists 235 Check In LD 48, perform the command stat elan Provide the print out for the SIP Route and all related RLI/DMI Ta b l e 4 6 NRS configuration information Check NRS configuration Pr.
236 T roub leshooting Check Print Capture of the OCS user for the Office Communications Server Print Capture of the OCS user for the Office Communication, Advanced Settings Ta b l e 5 0 T racing infor.
237 Appendix A Call Flo w and pr otocol details Contents This section contains information about the f ollowing topics: "Overview" (page 237) "Message sequence" (page 238) "Call flow" (page 239) Overview The Con verged Office feature provides interw orking between Nor tel and Microsoft products.
238 Appendix A Call Flow and protocol details Message sequence TR/87(4) is an ECMA T echnical Repor t that describes the use of SIP as a transpor t of ser vice requests and e vents defined b y the ECMA-269(5) specification as XML bodies within SIP messages.
Call flow 239 Figure 93 SIP INFO message with ECMA-323 content Call flow This section illustrates the call flow sequence f or the T elephony Gate wa y and Ser vices and Remote Call Control with Mediation Ser v er present.
240 Appendix A Call Flow and protocol details Figure 94 Inbound call to OC client with SPS, OC c lient answers Incoming calls to OC 2007 can or iginate directly from a phone behind the Communication Ser ver 1000 where the request URI represents the destination.
Call flow 241 A TTENTION This scenario would also apply if the inbound call originated from the PSTN. Figure 95 Inbound call to OC client with SRS, phone answers The ne xt scenar io as illustrated in.
242 Appendix A Call Flow and protocol details Figure 96 Direct inbound call to OC client, OC client answers This scenario as illustrated in Figure 97 "Outbound call from OC client to another clie.
Call flow 243 Figure 97 Outbound call from OC c lient to another client, phone answer s This scenario as illustrated in Figure 98 "Outbound call from OC client to another OC client, OC client ans wers" (page 244) depicts a configuration with a CDP dialing plan and the presence of the SRS component on the network.
244 Appendix A Call Flow and protocol details Figure 98 Outbound call from OC c lient to another OC client, OC c lient answer s Call Forward b y OC c lient This scenar io depicts a situation where the Communication Ser v er 1000 phone dials the phone number of an OC client Bob and is forw arded to another client Joe.
Call flow 245 Figure 99 Call Forward call flow b y OC client Remote Call Control Call Flo w Figure 100 "Remote Call Control Session Estab lishment through SRS" (page 246) illustrates the Remote Call Control Session Establishment through SRS.
246 Appendix A Call Flow and protocol details Figure 100 Remote Call Control Session Establishment through SRS Supported features Ta b l e 5 1 SIP CTI supported features Feature Supported by CS 1000 TR/87 FE Supported by Office Communicator 2007 Call Control Events 17.
Suppor ted features 247 Feature Supported by CS 1000 TR/87 FE Supported by Office Communicator 2007 Call Associated Events 18.2.5 - Service Completion Failure XX Logical Device Features 22.1.9 - Get Do Not Disturb X (Release 5.0) 22.1.10 - Get Forwarding XX 22.
248 Appendix A Call Flow and protocol details Feature Supported by CS 1000 TR/87 FE Supported by Office Communicator 2007 17.1.15 - Hold Call XX 17.1.18 - Make Call XX 17.1.21 - Reconnect Call X 17.1.22 - Retrieve Call XX 17.1.25 - Single Step Transfer Call XX 17.
249 Appendix B Configuration Examples Contents "Introduction" (page 249) "Standard Edition" (page 249) "Enter prise Edition" (page 275) "Host A uthor ization" .
250 Appendix B Configuration Examples Setting up the lab F ollow these steps to ensure the lab is set up correctly: Setting up the lab Step Action 1 Confirm that the CS 1000 ser ver is version 5.0 with the Product Enhancement P ackage or a later version.
Standard Edition 251 Collecting required data Collect the required data listed in the f ollowing three tables bef ore you begin to configure the Conv erged Office solution. The inf or mation entered here can be used to verify configuration settings later on.
252 Appendix B Configuration Examples SIP URI map, Private/CDP domain name cdp.udp SIP CTI Service, Service enabled Yes SIP CTI Service, Customer Number 0 SIP CTI Service, International Calls As Nati.
Standard Edition 253 Ta b l e 5 6 LD 22––chec k for licenses Prompt Response Description REQ prt TYPE slt Screen output: ANALOGUE TELEPHONES 32767 LEFT 32767 USED 0 CLASS TELEPHONES 32767 LEFT 327.
254 Appendix B Configuration Examples Ta b l e 5 7 LD 22–MS_CONV packa g e Prompt Response Description REQ prt TYPE pkg 408 Screen output: MS_CONV 408 5 Ensure that the VSID and the ELAN ID are greater than or equal to 32 and that the SECU parameter is configured to YES f or ELAN and f or V AS configuration.
Standard Edition 255 Prompt Response Description DATE <enter> PAGE <enter> DES <enter> Screen output: DES SIP TN 156 0 00 00 VIRTUAL TYPE IPTI CDEN 8D CUST 0 XTRK VTRK ZONE 000 TRK A.
256 Appendix B Configuration Examples ESN NO RPA NO CNVT NO SAT NO RCLS EXT VTRK YES ZONE 000 PCID SIP CRID YES NODE 81 DTRK NO ISDN YES MODE ISLD DCH 63 IFC SL1 PNI 00001 NCNA YES NCRD YES TRO YES F.
Standard Edition 257 Prompt Response Description PAGE <enter> DES <enter> Screen output: DN 2070 CPND CPND_LANG ROMAN XPLN 16 DISPLAY_FMT FIRST,LAST TYPE SL1 TN 100 0 03 04 V KEY 00 MARP D.
258 Appendix B Configuration Examples XLST 0 SCPW 2070 SFLT NO CAC_MFC 0 CLS CTD FBD WTA LPR MTD FND HTD TDD HFD CRPD MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1 POD DSX VMD CMSD SLKD CCSA-CS.
Standard Edition 259 Prompt Response Description DATE <enter> PAGE <enter> DES <enter> The screen output shown here ma y diff er depending on the setup used.
260 Appendix B Configuration Examples IAPG 0 AACS NO AACS NO ITNA NO DGRP MLWU_LANG 0 MLNG ENG DNDR 0 KEY 00 SCR 2070 0 CPND ANIE 0 01 HOT P 3 888 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 TRN .
Standard Edition 261 … . TYPE UEXT CDEN 8D CTYP XDLC CUST 0 UXTY TLSV … . KEY 00 SCR 2070 0 01 HOT P 3 888 10 Confirm that AST is not configured. 11 Configure TR87D and CDMR Class Of Ser vice. 12 Confirm that this PCA is not configured as MARP .
262 Appendix B Configuration Examples 16 Check LD 21 to confir m that PCA is activated. If not, configure LD 15 to PCA to ON to allow the incoming call to twin the PCA and make the SIP Gate wa y call work. —End— Signaling Server checklist Use the f ollowing procedure to confir m the correct configuration of the Signaling Ser ver .
Standard Edition 263 Figure 102 FQDN of the OCS 2007 Front End server 4 Define the IP address of the ser ver acting as DNS. For e xample, in Figure 103 "DNS configuration on the Signaling Ser ver" (page 263) , the IP address is 47.11.56.114 .
264 Appendix B Configuration Examples Figure 104 SIP GW Settings 6 Confirm that the SIP URI Map settings match the settings as shown in Figure 105 "SIP URI Map" (page 265) . Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.
Standard Edition 265 Figure 105 SIP URI Map 7 Confirm that the SIP CTI Ser vices settings match the settings as shown in Figure 106 "SIP CTI Ser vices" (page 266) . Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.
266 Appendix B Configuration Examples Figure 106 SIP CTI Services —End— Configuring Network Routing Service (NRS) Use the f ollowing procedure to check the configuration of NRS.
Standard Edition 267 Figure 107 Signaling Server and MCM Endpoints status on NRS Ensure that all the endpoints are registered (the endpoints must be listed as "Dynamic Sip" under the Suppor .
268 Appendix B Configuration Examples Figure 108 Routing Entry 3 Check the OCS 2007 Standard Edition configuration. In Host A uthorization for an OCS 2007 Standard Edition, configure the IP Address of the OCS Pro xy ser v er . (see Figure 109 "Host A uthor ization" (page 269) .
Standard Edition 269 Figure 109 Host Authorization 4 Check the OCS Pro xy ser ver configuration. See Ta b l e 5 3 "Network Routing Ser vice (NRS)" (page 251) , the OCS Pro xy IP is 47.
270 Appendix B Configuration Examples a. Compare and match your user proper ties settings with those in Figure 110 "General user proper ties" (page 270) . The telephone number in the T elephone Number field must be the same as the inf or mation recorded in T able 52 "Microsoft Active Director y" (page 251) .
Standard Edition 271 Figure 111 Communications pr oper ties c. Click the Comm unications tab and click the Configure button. Compare and match your settings with those in Figure 112 "User Options" (page 272) .
272 Appendix B Configuration Examples Figure 112 User Options —End— Checking the MCM installation and configuration Check that the MCM is properly installed and configured. Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.
Standard Edition 273 Checking the MCM installation and configuration Step Action 1 On the MCM, check that the user is a member of the RTC Ser ver Applications and R TC Ser ver Local Group .
274 Appendix B Configuration Examples Figure 114 MCM Gatewa y Endpoint configuration Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.0 30 Apr il 2008 Copyright © 2005–2008, Nor tel Networks .
Enterpr ise Edition 275 Figure 115 MCM Configuration screen Enterprise Edition This section describes the configuration of the OCS Enter prise Edition. Overview of general lab set-up Figure 116 "OCS Enter prise Edition General Over view" (page 276) , illustrates the lab set-up , which includes: • Call Ser ver v ersion 5.
276 Appendix B Configuration Examples • OCS FE Ser ver with a P ool and a Microsoft Software Load Balancer • 1 OCS Pro xy ser v er Figure 116 OCS Enterprise Edition General Over view Collecting D.
Enterpr ise Edition 277 Server URI sip:2070;phone-context=cdp.udp@te st.com Line URI tel:+16139675000;ext=2070 Telephone number 2070 Ta b l e 6 7 OCS Required information Record your information For example OCS 2007 Proxy server ocs2007a-proxy.ocs2007a.
278 Appendix B Configuration Examples LAN configuration, IP Address (OCS Proxy and OCS Pool) 47.11.56.54 Communication Server 1000 SIP gateway endpoint name ocs2007_node_A SIP Domain name ocs2007a.corp.nortel.com SIP Gateway Endpoint name ocs2007_node_A SIP URI map, Private/UDP domain name udp SIP URI map, Private/CDP domain name cdp.
Enterpr ise Edition 279 A TTENTION The OCS GUI is alwa ys display ed in lower case . T o determine the correct FQDN, right-click on pool, and the correct FQDN displays under Displa y Name as depicted in Figure 118 "Deter mining the exact FQDN of the pool" (page 280) .
280 Appendix B Configuration Examples Figure 118 Determining the exact FQDN of the pool OCS Default Applications Running Use the f ollowing procedure to deter mine which default applications are running.
Enterpr ise Edition 281 Figure 119 Default applications —End— General tab settings Use the f ollowing procedure to confirm the correct settings in the General tab . Step Action 1 Right-click on OCS 2007 F ront End ser v er and select Properties .
282 Appendix B Configuration Examples Figure 120 General settings Security/Certificates Prior to the setup of Conv erged Office, configure cer tificates. A TTENTION Cer tificate configuration is not covered in this section. Use the follo wing procedure to check your configuration settings of Cer tificates.
Enterpr ise Edition 283 3 Click the Select Certificate button to confir m the settings of the F ront End ser ver Cer tificate. Figure 121 Front End server Cer tificate —End— Host A uthorization Use the following procedure to check y our configuration settings of Host A uthor ization.
284 Appendix B Configuration Examples 3 Click the Edit b utton to confir m the settings of the Host A uthorization f or the F ront End ser ver (see Figure 122 "Host Authorization for F ront End ser v er" (page 284) ).
Enterpr ise Edition 285 Figure 123 Routing for Enterprise P ool 2 Choose the Routing tab . 3 Click the Edit b utton to confirm the Matching URI and Next hop settings. (see Figure 124 "Edit Static Route " (page 286) ). F orward all requests with the specified Domain.
286 Appendix B Configuration Examples Figure 124 Edit Static Route —End— Configuring DNS Use the follo wing procedure to check the settings for DNS Configuration. Checking these settings assumes that the DNS service is enabled on the Windows 2003 server .
Enterpr ise Edition 287 Figure 125 sipinternaltls SR V records 6 On the DNS ser ver , r ight-click on ocs2007apool and select Properties . 7 Select the Host (A) tab and check the Host A record for the P ool (see Figure 126 "Host (A) record f or the P ool" (page 288) ).
288 Appendix B Configuration Examples Figure 126 Host (A) record f or the Pool F or more information on these configurations , see the Microsoft Office Communications Ser ver 2007 Enter prise Edition Deployment Guide . Download Microsoft documentation from the Download Center at w ww .
Enterpr ise Edition 289 4 Click the Configure b utton. —End— See Figure 127 "User Advanced Settings" (page 289) to check the settings f or Ser ver URI and Line URI.
290 Appendix B Configuration Examples Checking that MCM is correctly installed and configured. Step Action 1 Assign the required Local group to the MCM user . Prior to installation of MCM, an MCM user inside the Activ e Director y is created and the RTC Ser ver Local Group and RTC Server Application local group is assigned to this user .
Enterpr ise Edition 291 Figure 129 RTC Server Application gr oup A TTENTION • MCM ma y not r un if the MCM user is not configured to belong to the required groups. • MCM ma y not r un if an incorrect passw ord is entered dur ing the MCM installation.
292 Appendix B Configuration Examples Figure 130 MCM configuration 7 Ensure that the correct Called Phone Context is entered. The Called Phone Context must correspond to what is configured for the user inside Active Directory and the SIP URI map (Private/CDP or UDP domain name) configured in Element Manager .
Enterpr ise Edition 293 Checking that the Signaling Server is correctly configured Step Action 1 Check the settings of SIP URI (see Figure 131 "SIP URI" (page 293) ). Figure 131 SIP URI —End— Configuring NRS Use the f ollowing procedure to chec k that the NRS is correctly configured.
294 Appendix B Configuration Examples Figure 132 MCM endpoints 2 F rom the Routing Entries tab , confir m that the settings are correct (see Figure 133 "Routing Entr ies for Endpoints" (page 295) ).
Enterpr ise Edition 295 Figure 133 Routing Entries for Endpoints —End— Normalizing Phone Numbers When nor malizing phone numbers, the T elephone Number field can be diff erent from what is configured in the OCS user configuration f or the Line URI field.
296 Appendix B Configuration Examples If the T elephone Number is normalized to the Line URI f or mat, you can use the "Click to Call" feature to show the caller’s user name when the Address Book Ser vice is av ailable.
297 Appendix C Abbre viations AC D Automatic Call Distribution AD Active Directory AML Application Module Link AT S Activity T rac king System AU X A uxiliar y B2BU A Back 2 Bac k User Agent BCC Basic.
298 Appendix C Abbreviations CDP Coordinated Dialing Plan CDR Call Detail Recording CS Communication Server CST A Computer Suppor ted T elecommunications Applications DC Domain Controllers DRAM Dynami.
Appendix C Abbre viations 299 IP Internet Protocol IPSec Secure Internet Protocol IVR Interactiv e V oice Response LD AP Lightweight Director y Access Protocol MISP Multipur pose ISDN Signaling Proces.
300 Appendix C Abbreviations PSTN Public Switched T elephone Network PRD Product Requirements Document RCC Remote Call Control Provides full Microsoft Office integration of telephony to control busin.
Appendix C Abbre viations 301 TN T er minal Number URI Unif or m Resource Identifier VIP Vir tual Inter net Protocol V oIP V oice over Internet Protocol VTRK Vir tual T runk XPEC Expanded P er iphera.
302 Appendix C Abbreviations Nor tel Communication Ser ver 1000 Nor tel Conv erged Office Fundamentals — Microsoft Office Communications Ser ver 2007 NN43001-121 01.03 Standard Release 5.0 30 Apr il 2008 Copyright © 2005–2008, Nor tel Networks .
.
Nor tel Communication Ser ver 1000 Nor tel Con verged Office Fundamentals — Microsoft Office Communications Ser v er 2007 Copyright © 2005–2008 , Nor tel Networks All Rights Reser ved. Publication: NN43001-121 Document status: Standard Document version: 01.
Un point important après l'achat de l'appareil (ou même avant l'achat) est de lire le manuel d'utilisation. Nous devons le faire pour quelques raisons simples:
Si vous n'avez pas encore acheté Nortel Networks NN43001-121 c'est un bon moment pour vous familiariser avec les données de base sur le produit. Consulter d'abord les pages initiales du manuel d'utilisation, que vous trouverez ci-dessus. Vous devriez y trouver les données techniques les plus importants du Nortel Networks NN43001-121 - de cette manière, vous pouvez vérifier si l'équipement répond à vos besoins. Explorant les pages suivantes du manuel d'utilisation Nortel Networks NN43001-121, vous apprendrez toutes les caractéristiques du produit et des informations sur son fonctionnement. Les informations sur le Nortel Networks NN43001-121 va certainement vous aider à prendre une décision concernant l'achat.
Dans une situation où vous avez déjà le Nortel Networks NN43001-121, mais vous avez pas encore lu le manuel d'utilisation, vous devez le faire pour les raisons décrites ci-dessus,. Vous saurez alors si vous avez correctement utilisé les fonctions disponibles, et si vous avez commis des erreurs qui peuvent réduire la durée de vie du Nortel Networks NN43001-121.
Cependant, l'un des rôles les plus importants pour l'utilisateur joués par les manuels d'utilisateur est d'aider à résoudre les problèmes concernant le Nortel Networks NN43001-121. Presque toujours, vous y trouverez Troubleshooting, soit les pannes et les défaillances les plus fréquentes de l'apparei Nortel Networks NN43001-121 ainsi que les instructions sur la façon de les résoudre. Même si vous ne parvenez pas à résoudre le problème, le manuel d‘utilisation va vous montrer le chemin d'une nouvelle procédure – le contact avec le centre de service à la clientèle ou le service le plus proche.
