Nortel-networks NN43001-121 Manual de usuario Pagina 1

Nortel Communication Server 1000Nortel Converged OfficeFundamentals — MicrosoftOffice Communications Server2007NN43001-121.

10 New in this release— SIP UPDATE method is not supported by Mediation Server. Thismethod enables SIP Gateways and Endpoints to update the callinform

100 Planning and engineeringNortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007NN43001-12

101InstallationThis chapter contains the procedures necessary to install CS 1000components and Office Communications Server (OCS) 2007 on a CS 1000syst

102 InstallationInstallation navigationFigure 27Installation and configuration flow•"CS 1000 and Signaling Server installation" (page 105)•&qu

OCS 2007 installation preparation and deployment 103OCS 2007 installation preparation and deploymentThe following figure Figure 28 "OCS 2007 insta

104 InstallationFigure 28OCS 2007 installation preparation and deployment flow chartNortel Communication Server 1000Nortel Converged Office Fundamentals

OCS 2007 component installation 105CS 1000 and Signaling Server installationThe first step in the installation and configuration process is to install t

106 InstallationATTENTIONThe following is a list of the required patches for the Microsoft OCS 2007installation:•OCS 2007 – Standard Edition RTMKB 942

OCS Proxy server installation 107Office Communications Server (OCS ) 2007 Enterprise PoolOCS 2007 Enterprise Edition is designed for large-scale deploy

108 InstallationInstalling the OCS Proxy serverStep Action1On the Windows Star t menu, choose Run.2Navigate to the C:\Office CommunicationsServer_Eval\

MCM installation 1093Select TCP/IP properties and add DNS server IP. For example,47.11.108.50.4Go to My Computer, right-click and select System Proper

11How to get helpThis chapter explains how to get help for Nortel products and services.Getting help from the Nortel web siteThe best way to get techn

110 Installation2Select Use an existing account and enter your user ID andpasswordORselect Create a new account.3Open the MCM Console window and selec

111ConfigurationThe following flow chart depicts the configuration order of the components.Nortel Communication Server 1000Nortel Converged Office Fundame

112 ConfigurationFigure 29Configuration flow chartActive Directory configurationActive Directory configuration takes place in the Active Directory Users an

Active Directory configuration 113By default MCM uses GC LDAP server which contains partial informationabout all objects in the Active Directory domain

114 ConfigurationDefining usersStep Action1Select a user from the list in the Users folder.2Right-click the user, and select Properties.3The Properties

Active Directory configuration 1156Click the check box next to Enable user for Office CommunicationsServer.7In the fields provided, define the user Sign-i

116 Configuration9For enabling Remote Call Control only, select Enable Remote CallControl and configure the Server URI and Line URI. See Figure 33"

Active Directory configuration 117Figure 33Enable Remote call controlNortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft Of

118 ConfigurationFigure 34Enable Enterprise Voice and PBX integrationNortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft Of

Office Communications Server configuration 119Figure 35Enable both RCC and Enterprise VoiceOffice Communications Ser ver configurationThe starting point f

12 How to get helpGetting help through a Nortel distributor or resellerIf you purchased a service contract for your Nortel product from a distributoro

120 ConfigurationLoad Balancer configurationThe pool of Front End servers is organized to process inbound andoutbound traffic. The role of the Load Balan

Office Communications Server configuration 121Voice mail must always be configured on the CS 1000 and not OfficeCommunicator. Configuring communication to

122 Configuration—End—Applying policyStep Action1In the User Options window, click Enable Enterprise Voice.2Select Another Policy. The policy can be as

Office Communications Server configuration 1231000. In this situation, the IP address of the CS 1000 must be addedto the Authorized Host list.Configuring

124 ConfigurationFigure 37Office Communications Server Front Ends3Click on the Host Authorization tab and select the Edit button.4 In the Server section

Office Communications Server configuration 125Figure 38Routing tab8 In the Add Static Route window, For Domain: enter the domaindefined in the Server URI

126 ConfigurationConfiguring host authorization for the OCS ProxyStep Action1Open the OCS Proxy server, click the Windows Start button, point toAdminist

Office Communications Server configuration 127Figure 40Office Communications Server Management Console3For the OCS Proxy, no static route is required. MC

128 ConfigurationFigure 41Routing tab5 Click the Host Authorization tab.6Click Edit to open the Edit Authorized Host window.7In the Edit Authorized Hos

Office Communications Server configuration 129Figure 42Edit Authorized Host—End—The following table shows a number of possible configurations of OCS 2007

13IntroductionThis document describes the elements and processes necessary tointegrate Nortel Communication Server 1000 (CS 1000) with the OfficeCommun

130 ConfigurationOCS Front EndServers PoolOCS MediationServerOCS ApplicationServerPort: 5060Phone URI: NoReplace host in requestURI: NoHost Authorizati

Office Communications Server configuration 131ConfigurationTypeComp-onentHostAuthorizationDest-inationUser /DomainPhoneURITrans-portPort3. Pool ofFront

132 ConfigurationConfigurationTypeComp-onentHostAuthorizationDest-inationUser /DomainPhoneURITrans-portPortMediationServers IP6. Single FrontEnd server

Office Communications Server configuration 133ConfigurationTypeComp-onentHostAuthorizationDest-inationUser /DomainPhoneURITrans-portPort8. Pool ofFront

134 Configuration5In the FQDN box, make sure the FQDN listed matches that of theMediation Server you have selected.6Open a command prompt, change to th

MCM 3.0 configuration 135•Management ConsoleThe MCM Call Processing Service handles the Session Initiation Protocol(SIP) telephony traffic between the C

136 ConfigurationFigure 43MCM architectureThe following examples illustrate how MCM handles call information.Understanding the role of MCM in the Telep

MCM 3.0 configuration 137The call is routed to the NRS. The invite is sent to the NRS, which returnsa 302, and the CS 1000 sends an invite to the MCM P

138 Configuration— Not responding - Primary SRS/SPS is not responding. For normalprocessing, the Secondary SRS/SPS must be switched to an Activestate.—

MCM 3.0 configuration 139Figure 44MCMMCM menu optionsThe following lit describes the function of each MCM menu command:• Actions— Start - start MCM ser

14 IntroductionNortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007NN43001-121 01.03 Stand

140 Configuration— Active Directory Query— Backup— Restore— Set Log Level•Help— Get help and general information about MCMMCM Configuration To access th

MCM 3.0 configuration 141Network Topology section The following is a description of some ofthe configuration fields in the Network Topology section of th

142 Configurationan INVITE request providing information about which dedicated MediationServer or Mediation Server pool to process this message. The pa

MCM 3.0 configuration 143Table 27Incoming Call Processing parametersConfiguration fieldDescriptionCalled Phone Context Phone Context of calls to be pro

144 ConfigurationFigure 47Element Manager SIP URI MAPActive Directory configuration section There are two modes for ActiveDirectory (AD) Configuration: R

MCM 3.0 configuration 145Active Directory query The Active Directory Query tool is used to checkActive Directory mapping configuration. It searches for

146 ConfigurationFigure 49Get phoneField propagations to the Global Catalog MCM uses the ActiveDirectory Global Catalog to search for necessary user in

MCM 3.0 configuration 147Step Action1Open the Active Directory Schema snap-in as depicted in theexample Figure 50 "Replicating attributes to the G

148 ConfigurationNetwork dial plan section The following table describes the fields forDial plan and Access code.Table 29Network dial planConfiguration

MCM 3.0 configuration 149Configuring MCM for Remote Call Control For Remote Call Control,the Nortel MCM application that resides within the Office Commun

15Converged Office component overviewThis chapter provides a brief technical description of all the componentsassociated with Nortel Converged Office.Co

150 ConfigurationFigure 51Enable phone integration on the clientRedundancy Redundancy of the TR/87 interface is not provided nativelywith Office Communi

Telephony Gateway and Services configuration 151Call Server configurationCS 1000 configuration involves two separate functions: Signaling Serverconfigurat

152 ConfigurationFigure 52Codec configurationLoss Plan configurationIn order for DTMF digits to be transmitted at the correct volume, especiallyfor Office

Telephony Gateway and Services configuration 153ATTENTIONWhen any kind of in-band signaling is to be used as payload audio packets (forexample, DTMF to

154 ConfigurationIn this figure, the CS 1000 has a HLOC of 354 and an LOC dialing planentry of 344. The LOC dialing plan 344 is not dialable, however, c

Telephony Gateway and Services configuration 155When you use a PCA, the MARP must be on the DN key of the phoneitself, not the PCA. If the MARP is on t

156 ConfigurationDES PCATN 096 0 08 15 VIRTUALTYPE PCACDEN 8DCTYP XDLCCUST 0NUIDNHTNCFG_ZONE 000CUR_ZONE 000ERL 0ECL 0FDNTGAR 1LDN NONCOS 0SGRP 0RNPG 0

Telephony Gateway and Services configuration 157ANIE 002030405060708091011121314151617 TRN18 AO619 CFW 1620 RGA21 PRK22 RNP2324 PRS25 CHG26 CPN27282930

158 ConfigurationFor PCA twinning to work correctly in a UDP environment, the fullOriginal Called Number (OCN) must be sent by the CS 1000 to the Office

Telephony Gateway and Services configuration 159Table 35LD 15Prompt Response DescriptionREQ chgTYPEnetTYPE NET_DATACUST0OPTAC2FNPCLIDyesSIZE5INTL1ENTRY

16 Converged Office component overviewThe Nortel Converged Office feature combines the business-gradetelephony of the CS 1000 with the OCS 2007 Enterpri

160 Configurationall OCS and Enterprise Edition Pools. Also, the FQDN must resolve tothe IP address of the OCS for all types of DNS queries (not just f

Telephony Gateway and Services configuration 161A CS 1000 with existing SIP trunks requires a configuration change tobe compatible with Office Communicat

162 ConfigurationATTENTIONThe Route Data Block (RDB) must not have a value configured for the promptINST. Otherwise, incoming calls from Office Communica

Telephony Gateway and Services configuration 163The Route Data Block is ESN5 if the output from Element Manager, or aterminal window, is:TYPE RDBCUST 0

164 ConfigurationFigure 56SIP Trunk Domain nameConfiguring the SIP Trunk Domain name describes how to configure the SIPTrunk domain name to match the Offi

Telephony Gateway and Services configuration 165Figure 57Element Manager Signaling Ser ver Properties7In most cases, the value for the field SIP Domain

166 ConfigurationFigure 58SIP URI MapThe SIP URI Map must match the NRS server configuration in the followingmanner:•The Private/UDP domain name maps to

Telephony Gateway and Services configuration 167SIP Gateway CLID Parameters configurationThe SIP Gateway CLID parameters are used to adjust the formatof

168 Configuration+<countrycode><area code><subscriber number>.The parameters Subscriber/Number of digits to strip and prefix to insert

Telephony Gateway and Services configuration 169•Three different modes: Proxy All, Redirect, and Proxy SIP GatewayCalls•Transport: TLS (5061) and TCP (

Enterprise Voice 17•originate and receive Public Switched Telephone Network (PSTN) callsfrom the Office Communicator (OC) 2007 soft client when away fr

170 ConfigurationThe NRS must have the same UDP or CDP dialing plan prefix to route callsto the MCM endpoint. This UDP or CDP dialing plan prefix is the

Remote Call Control configuration 171In order to support these calls, placed through the SIP Gateway, youmust configure the parameters CNTC, NATC, and I

172 Configuration4Choose Enable Remote call control to enable clients control of thePBX phone or Enable Enterprise Voice and click the Enable PBXintegr

Remote Call Control configuration 173Figure 61Enable integration with your phone systemCS 1000 configurationApplication Module Link (AML) is the main in

174 ConfigurationLD 17: Configure AML LinkPrompt Response DescriptionREQ CHG Change existing data.TYPE ADANADAN <new ELAN #> A new AML link; the l

Remote Call Control configuration 175Configuring the SIP CTI TR/87 ISM limitIncremental Software Management (ISM) (SIP CTI TR/87) is used to definethe nu

176 ConfigurationA new CLS (T87A) is introduced to allow a TN to support the SIP CTIapplication.The AST prompt is used to configure which DN key on the

Remote Call Control configuration 177•Any Remote Call Control service request sent by Office Communicator,such as Make Call or Answer Call, always apply

178 ConfigurationNode parameter configurationThe node IP is the IP address of the TR/87 FE:•You can configure multiple nodes to support TR/87 application

Remote Call Control configuration 179SIP Gateway parameter configurationThe SIP Gateway application must be enabled. To enable the SIP Gateway,TR/87 FE

18 Converged Office component overview•the Mediation Server performs all necessary media transcoding androutes the call to the IP-PSTN gateway.•the IP-

180 ConfigurationAlso, the FQDN must resolve to the IP address of the OCS server for alltypes of DNS queries (not just for the SIP service type). (see

Remote Call Control configuration 181SIP CTI Services configuration settingsIn Element Manager, under SIP CTI services, the Calling Device URIFormat mus

182 ConfigurationFigure 66SIP CTI Services settingsParameter: Service EnabledThe default state of the SIP CTI service is disabled. To enforce the chang

Remote Call Control configuration 183Parameter: Maximum Associations Per DNThis parameter defines the maximum number of simultaneous TR/87 SIPdialogs th

184 ConfigurationSIP CTI Dial Plan prefixesThe SIP CTI dial plan prefixes configuration settings are used to prefixphone numbers sent to the Call Server as

Remote Call Control configuration 185SIP CTI CLID configuration parametersThe SIP CTI CLID parameters are used to adjust the format of phonenumbers for

186 Configurationcan be entered using the home location code to ensure a consistent uniqueformat throughout the enterprise. Two scenarios are provided

Remote Call Control configuration 187Scenario 2, Dial Plan = CDP, Calling Device URI Format =phone-context= SIP GW URI map entries:The TEL URI generate

188 Configuration•An RCC call from Office Communicator to the E.164 number+16135006000 produces a call from the controlled DN to616135006000.An RCC call

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 001

Media Gateways 19•Address Book Service—normalizes enterprise user phone numbers toE.164 format to provision user Contacts in Office Communicator.The fo

190 ConfigurationFigure 69SIP URI MapConfiguring CDRCall Detail Recording (CDR) records are produced for calls controlled usingthe Remote Call Control f

Remote Call Control configuration 191Figure 70SIP INFO messageThe TR/87 FE that resides on the Signaling Server contains a featureto insert the appropr

192 ConfigurationNormalizing phone numbersOffice Communicator 2007 requires that all phone numbers be in standardTEL URI format as defined in RFC 3966 fo

Normalizing phone numbers 193tel:+14255551212;ext=5551212;ad-rdn=telephoneNumber;display-Name=(425)555-1212The ad-rdn = telephoneNumber is a proprieta

194 ConfigurationMCM provides authorization of Remote Call Control service requestsbased on the configuration defined in Active Directory for each OfficeC

Normalizing phone numbers 195Figure 71Normalization rule example for UDP dial planResult•The normalized version (tel:+16139675000;ext=$1$2) of the bus

196 ConfigurationFigure 72Company phone number normalization rules for CDP2Refresh the Address Book on the server by issuing the followingcommand on th

Normalizing phone numbers 197Figure 73Refresh Address Book on the server3Exit from Office Communicator 2007.4Refresh Address Book on the client as show

198 ConfigurationSIP Routing and Redundancy configurationOffice Communicator is a soft phone application as well as a SIP UserAgent (UA). Office Communica

OCS 2007 users using UM 2007 in integrated mode 199Configuring a basic mailbox for the UM userStep Action1Configure the OCS user mailbox in Exchange UM.

Document status: StandardDocument version: 01.03Document date: 30 April 2008Copyright © 2005–2008, Nortel NetworksAll Rights Reserved.LEGAL NOTICEWhil

20 Converged Office component overviewMedia gateways translate the following protocols between thecircuit-switched PSTN network and the packet-switched

200 ConfigurationFigure 75User Properties window for Exchange UM4Click on the E-mail Addresses tab.5Click on the Add menu and select EUM Address.6In th

OCS 2007 users using UM 2007 in integrated mode 201Figure 76UM Address7Click on the Browse button to find the associated Dial plan for theuser. Click O

202 ConfigurationFigure 77Dial plan window8The new EUM address is added. To find the new UM Extension,click on the Mailbox Features tab, right-click on

OCS 2007 users using UM 2007 in integrated mode 203Figure 78Unified Messaging Properties window—End—Option 2 adding CS 1000 DN as Exchange UMThese proc

204 Configuration4—End—Adding Exchange UMStep Action1From the Exchange Management Console window, click onRecipient Configuration, and select Mailbox.2S

OCS 2007 users using UM 2007 in integrated mode 205Figure 80UM Address7Click on the Browse button to find the associated Dial plan for theuser. Click O

206 ConfigurationFigure 81Dial Plan window8The new EUM address is added. To find the new UM Extension,click on the Mailbox Features tab, right-click on

OCS 2007 users using UM 2007 in integrated mode 207Figure 82Unified Messaging Properties window—End—Nortel Communication Server 1000Nortel Converged Of

208 ConfigurationNortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007NN43001-121 01.03 Stan

209MaintenanceIntroductionThe following are maintenance tips for MCM 3.0 . For more information ontroubleshooting tips, see "Troubleshooting"

Mediation Server 21•connects clients outside the network to internal Interactive ConnectivityEstablishment (ICE) components, to enable media traversal

210 MaintenanceSIP tracing can be filtered by DN number. MCM SIP tracing isimplemented as part of the application logging functionality. Specialcommand

Remote Call Control 211Prompt Response Description>SIPCTITraceLevel<level>Configure the TR87 SIP messageTrace Level. The level can beone of t

212 MaintenancePrompt Response Description>SIPCTIStop all De-acquire all AST DNs andterminate all the TR87 SIPsessions.>SIPCTIStop <dn> De

Remote Call Control 213•SIPCTITotalMonitorStopSuccesses•SIPCTITotalConferenceCallRequests•SIPCTITotalConferenceCallSuccesses•SIPCTITotalSetForwardingR

214 MaintenancePrompt Response Description4—Print all input and outputAML data buffer exceptPOLLING message with IE typeand data decoding.ATTENTIONThi

215TroubleshootingUse the following procedures to assist in troubleshooting general ConvergedOffice problems.Checking Telephony Gateway (SIP Gateway) c

216 TroubleshootingChecking Remote Call Control (SIP CTI) configurationChecking Remote Call Control configurationStep Action1 Check all required Communi

SIP CTI services does not come up 217Symptom:After SIP CTI services are activated, you are unable to log on to theSignaling Server through Element Man

218 TroubleshootingFigure 83nslookup toolSolution 1: Check configuration parameters in ADCheck the configuration parameters in Active Directory for this

SIP CTI services does not come up 219Possible cause:VSID or ELAN ID is lower than 32.Solution:Follow the procedure "Reconfigure SIP CTI service&qu

22 Converged Office component overviewRemote Call Control with SIP CTI (TR/87)The CS 1000 and OCS 2007 integration feature allows clients of the twosys

220 Troubleshooting3In LD 48, check the ELAN status on the Call ServerTable 40LD 48Prompt Response Description.statelan Check the ELAN status on theCa

MCM not synchronizing new users in AD Cache mode 221Checking the Global Catalog content manuallyStep Action1Install the Operating System Support Tools

222 TroubleshootingAccessing permissions for the AD object propertiesStep Action1Install the Operating System Support Tools on the server (usuallythe

Pop-up not displayed 223Enabling propagation of the Active Directory field to the GlobalCatalogStep Action1Open the Active Directory Schema snap-in.2Se

224 TroubleshootingPossible causes:The Phone Context may be not correct. Address Book Service may not beproperly setup. Phone integration is not activ

Capturing traces and logs 225Symptom:The telephone is on Call Forward to another number. When the OfficeCommunicator user who is associated to this tel

226 TroubleshootingAML traces on the Call Server (SIP CTI only)In LD 48, activate AML traces on the Call Server (SIP CTI only):Table 41LD 48Prompt Res

Capturing traces and logs 227Figure 85Example of screen output for SIP CTI Traces on the Signaling ServerSIP Gateway traces on the Signaling ServerIn

228 TroubleshootingFigure 86Example of screen output for SIP Gateway traceMCM logsMCM 3.0 generates a daily log file with no maximum size restrictions

Capturing traces and logs 229•SIP: SIP messages (filtered by distinct DN) are logged further to alarms.Only one DN can be specified at the same time in

Telephony Gateway and Services 23Figure 5Remote Call ControlThe full set of business-grade telephony features available with CS1000 telephones is inte

230 TroubleshootingTo turn off MCM logging, see "Resetting MCM debug trace" (page 231).MCM log file outputThe following shows a snippet from

Capturing traces and logs 231Figure 88Event Viewer windowResetting MCM debug traceUse the following procedures to reset the MCM debug trace.Resetting

232 TroubleshootingActivating OCS logsStep Action1Right-click on the OCS pool and select Logging Tool and thenchoose New Debug Session.2In the OCS 200

Capturing traces and logs 2332Choose the General tab.3Select the Turn on logging in Communicator and the Turn onWindows Event Logging for Communicator

234 TroubleshootingFigure 91No PBX connection for OC clientCase checklistsUse the following checklists prior to opening a case to ensure that allrelev

Case checklists 235CheckIn LD 48, perform the command stat elanProvide the print out for the SIP Route and all related RLI/DMITable 46NRS configuration

236 TroubleshootingCheckPrint Capture of the OCS user for the Office Communications ServerPrint Capture of the OCS user for the Office Communication,A

237Appendix ACall Flow and protocol detailsContentsThis section contains information about the following topics:"Overview" (page 237)"M

238 Appendix A Call Flow and protocol detailsMessage sequenceTR/87(4) is an ECMA Technical Report that describes the use of SIP asa transport of servi

Call flow 239Figure 93SIP INFO message with ECMA-323 contentCall flowThis section illustrates the call flow sequence for the Telephony Gatewayand Service

24 Converged Office component overviewWith this solution, you can configure Personal Call Assistant (PCA) on theCS 1000 for each user with this function

240 Appendix A Call Flow and protocol detailsFigure 94Inbound call to OC client with SPS, OC client answersIncoming calls to OC 2007 can originate dir

Call flow 241ATTENTIONThis scenario would also apply if the inbound call originated from the PSTN.Figure 95Inbound call to OC client with SRS, phone an

242 Appendix A Call Flow and protocol detailsFigure 96Direct inbound call to OC client, OC client answersThis scenario as illustrated in Figure 97 &qu

Call flow 243Figure 97Outbound call from OC client to another client, phone answersThis scenario as illustrated in Figure 98 "Outbound call from O

244 Appendix A Call Flow and protocol detailsFigure 98Outbound call from OC client to another OC client, OC client answersCall Forward by OC clientThi

Call flow 245Figure 99Call Forward call flow by OC clientRemote Call Control Call FlowFigure 100 "Remote Call Control Session Establishment through

246 Appendix A Call Flow and protocol detailsFigure 100Remote Call Control Session Establishment through SRSSupported featuresTable 51SIP CTI supporte

Supported features 247FeatureSupported by CS1000 TR/87 FESupported byOfficeCommunicator2007Call Associated Events18.2.5 - Service CompletionFailureXXL

248 Appendix A Call Flow and protocol detailsFeatureSupported by CS1000 TR/87 FESupported byOfficeCommunicator200717.1.15 - Hold CallXX17.1.18 - Make

249Appendix BConfiguration ExamplesContents"Introduction" (page 249)"Standard Edition" (page 249)"Enterprise Edition" (pa

Personal Call Assistant 25Figure 6Dual forking examplePersonal Call AssistantMany of the features provided by CS 1000 to traditional telephones areext

250 Appendix B Configuration ExamplesSetting up the labFollow these steps to ensure the lab is set up correctly:Setting up the labStep Action1Confirm th

Standard Edition 251Collecting required dataCollect the required data listed in the following three tables before you beginto configure the Converged O

252 Appendix B Configuration ExamplesSIP URI map, Private/CDPdomain namecdp.udpSIP CTI Service, ServiceenabledYesSIP CTI Service, CustomerNumber0SIP CT

Standard Edition 253Table 56LD 22––check for licensesPrompt Response DescriptionREQprtTYPE sltScreen output:ANALOGUE TELEPHONES 32767 LEFT 32767 USED

254 Appendix B Configuration ExamplesTable 57LD 22–MS_CONV packagePrompt Response DescriptionREQprtTYPE pkg 408Screen output:MS_CONV 4085Ensure that th

Standard Edition 255Prompt Response DescriptionDATE<enter>PAGE<enter>DES<enter>Screen output:DES SIPTN 156 0 00 00 VIRTUALTYPE IPTIC

256 Appendix B Configuration ExamplesESN NORPA NOCNVT NOSAT NORCLS EXTVTRK YESZONE 000PCID SIPCRID YESNODE 81DTRK NOISDN YESMODE ISLDDCH 63IFC SL1PNI 0

Standard Edition 257Prompt Response DescriptionPAGE<enter>DES<enter>Screen output:DN 2070CPNDCPND_LANG ROMANXPLN 16DISPLAY_FMT FIRST,LASTT

258 Appendix B Configuration ExamplesXLST 0SCPW 2070SFLT NOCAC_MFC 0CLS CTD FBD WTA LPR MTD FND HTD TDD HFD CRPDMWD LMPN RMMD SMWD AAD IMD XHD IRD NID

Standard Edition 259Prompt Response DescriptionDATE<enter>PAGE<enter>DES<enter>The screen output shown here may differ depending on

26 Converged Office component overviewGateway and Services to always tandem through the user’s active CallServer. Note that with Geographic Redundancy

260 Appendix B Configuration ExamplesIAPG 0AACS NOAACS NOITNA NODGRPMLWU_LANG 0MLNG ENGDNDR 0KEY 00 SCR 2070 0CPNDANIE 001 HOT P 3 88802030405060708091

Standard Edition 261….TYPE UEXTCDEN 8DCTYP XDLCCUST 0UXTY TLSV….KEY 00 SCR 2070 001 HOT P 3 88810Confirm that AST is not configured.11Configure TR87D and

262 Appendix B Configuration Examples16Check LD 21 to confirm that PCA is activated. If not, configure LD15 to PCA to ON to allow the incoming call to tw

Standard Edition 263Figure 102FQDN of the OCS 2007 Front End server4Define the IP address of the server acting as DNS. For example, inFigure 103 "

264 Appendix B Configuration ExamplesFigure 104SIP GW Settings6Confirm that the SIP URI Map settings match the settings as shownin Figure 105 "SIP

Standard Edition 265Figure 105SIP URI Map7Confirm that the SIP CTI Services settings match the settings asshown in Figure 106 "SIP CTI Services&qu

266 Appendix B Configuration ExamplesFigure 106SIP CTI Services—End—Configuring Network Routing Service (NRS)Use the following procedure to check the co

Standard Edition 267Figure 107Signaling Server and MCM Endpoints status on NRSEnsure that all the endpoints are registered (the endpoints must beliste

268 Appendix B Configuration ExamplesFigure 108Routing Entry3Check the OCS 2007 Standard Edition configuration.In Host Authorization for an OCS 2007 Sta

Standard Edition 269Figure 109Host Authorization4Check the OCS Proxy server configuration. See Table 53"Network Routing Service (NRS)" (page

OCS 2007 snap-in 27specifically in Computer mode. Features such as Call Forward NoAnswer, Unified Messaging, Call Detail Recording, and Attendant Recall

270 Appendix B Configuration Examplesa. Compare and match your user properties settings with those inFigure 110 "General user properties" (pa

Standard Edition 271Figure 111Communications propertiesc. Click the Communications tab and click the Configure button.Compare and match your settings w

272 Appendix B Configuration ExamplesFigure 112User Options—End—Checking the MCM installation and configurationCheck that the MCM is properly installed

Standard Edition 273Checking the MCM installation and configurationStep Action1On the MCM, check that the user is a member of the RTC ServerApplication

274 Appendix B Configuration ExamplesFigure 114MCM Gateway Endpoint configurationNortel Communication Server 1000Nortel Converged Office Fundamentals — M

Enterprise Edition 275Figure 115MCM Configuration screenEnterprise EditionThis section describes the configuration of the OCS Enterprise Edition.Overvie

276 Appendix B Configuration Examples•OCS FE Server with a Pool and a Microsoft Software Load Balancer•1 OCS Proxy serverFigure 116OCS Enterprise Editi

Enterprise Edition 277Server URI sip:2070;[email protected] URI tel:+16139675000;ext=2070Telephone number2070Table 67OCSRequired info

278 Appendix B Configuration ExamplesLAN configuration, IP Address(OCS Proxy and OCS Pool)47.11.56.54Communication Server 1000SIP gateway endpoint name

Enterprise Edition 279ATTENTIONThe OCS GUI is always displayed in lower case. To determine the correct FQDN,right-click on pool, and the correct FQDN

28 Converged Office component overviewservers, and users. The Status pane also features a new Database tab,which can be used to query a pool’s back-end

280 Appendix B Configuration ExamplesFigure 118Determining the exact FQDN of the poolOCS Default Applications RunningUse the following procedure to det

Enterprise Edition 281Figure 119Default applications—End—General tab settingsUse the following procedure to confirm the correct settings in the General

282 Appendix B Configuration ExamplesFigure 120General settingsSecurity/CertificatesPrior to the setup of Converged Office, configure certificates.ATTENTIO

Enterprise Edition 2833Click the Select Certificate button to confirm the settings of theFront End server Certificate.Figure 121Front End server Certifica

284 Appendix B Configuration Examples3Click the Edit button to confirm the settings of the Host Authorizationfor the Front End server (see Figure 122 &q

Enterprise Edition 285Figure 123Routing for Enterprise Pool2Choose the Routing tab.3Click the Edit button to confirm the Matching URI and Next hopsetti

286 Appendix B Configuration ExamplesFigure 124Edit Static Route—End—Configuring DNSUse the following procedure to check the settings for DNS Configurati

Enterprise Edition 287Figure 125sipinternaltls SRV records6On the DNS server, right-click on ocs2007apool and selectProperties.7Select the Host (A) ta

288 Appendix B Configuration ExamplesFigure 126Host (A) record for the PoolFor more information on these configurations, see the MicrosoftOffice Communic

Enterprise Edition 2894Click the Configure button.—End—See Figure 127 "User Advanced Settings" (page 289) to check the settingsfor Server URI

SIP CTI (TR/87) Protocol 29SIP CTI (TR/87) ProtocolThe SIP CTI (TR/87) FE application introduced with this package is notlimited to Microsoft applicat

290 Appendix B Configuration ExamplesChecking that MCM is correctly installed and configured.Step Action1Assign the required Local group to the MCM user

Enterprise Edition 291Figure 129RTC Server Application groupATTENTION•MCM may not run if the MCM user is not configured to belongto the required groups

292 Appendix B Configuration ExamplesFigure 130MCM configuration7Ensure that the correct Called Phone Context is entered. TheCalled Phone Context must c

Enterprise Edition 293Checking that the Signaling Server is correctly configuredStep Action1Check the settings of SIP URI (see Figure 131 "SIP URI

294 Appendix B Configuration ExamplesFigure 132MCM endpoints2From the Routing Entries tab, confirm that the settings are correct(see Figure 133 "Ro

Enterprise Edition 295Figure 133Routing Entries for Endpoints—End—Normalizing Phone NumbersWhen normalizing phone numbers, the Telephone Number field c

296 Appendix B Configuration ExamplesIf the Telephone Number is normalized to the Line URI format, you can usethe "Click to Call" feature to

297Appendix CAbbreviationsACDAutomatic Call DistributionADActive DirectoryAMLApplication Module LinkATSActivity Tracking SystemAUXAuxiliaryB2BUABack 2

298 Appendix C AbbreviationsCDPCoordinated Dialing PlanCDRCall Detail RecordingCSCommunication ServerCSTAComputer Supported Telecommunications Applica

Appendix C Abbreviations 299IPInternet ProtocolIPSecSecure Internet ProtocolIVRInteractive Voice ResponseLDAPLightweight Directory Access ProtocolMISP

3ContentsNew in this release 9Office Communications Server 2007 features 9Other changes 9Revision History 10How to get help 11Getting help from the Nor

30 Converged Office component overviewFigure 8SIP diagramFigure 9 "IP diagram" (page 31) depicts the IP protocol information.Nortel Communica

300 Appendix C AbbreviationsPSTNPublic Switched Telephone NetworkPRDProduct Requirements DocumentRCCRemote Call ControlProvides full Microsoft Office i

Appendix C Abbreviations 301TNTerminal NumberURIUniform Resource IdentifierVIPVirtual Internet ProtocolVoIPVoice over Internet ProtocolVTRKVirtual Trun

302 Appendix C AbbreviationsNortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007NN43001-12

Nortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft OfficeCommunications Server 2007Copyright © 2005–2008 , Nortel Networks

Hardware Load Balancer 31Figure 9IP diagramATTENTIONCustomers must not use their Office Communicator client to call Emergencynumbers (for example, 911)

32 Converged Office component overviewHardware Load Balancers deliver load distribution to avoid a single pointof failure. Other benefits include increa

Documentation References 33Table 1Nortel technical documentationTechnical documentContentPrimary audienceConverged Office UserGuide — Microsoft Office

34 Converged Office component overviewTechnical documentContentPrimary audienceTransmission Parameters(NN43001-282)Contains information aboutconfigurin

35Planning and engineeringThis chapter contains information about topics you must consider beforeyou implement Converged Office.Planning and engineerin

36 Planning and engineeringNortel recommends that you implement the Telephony Gateway andServices component to provide basic connectivity (which you c

Network configuration 37Note: The descriptions and graphical representations of the threenetwork types are for illustration only, and are not actual co

38 Planning and engineeringFigure 10Small network configurationMedium networkA medium network can include the following components:•one or multiple CS

Network configuration 39Figure 11Medium network configurationLarge networkA large network can include the following components:•multiple CS 1000 systems

4 ContentsLoad Balancer planning 43Load Balancer requirements 44Redundancy with Load Balancers 45Nortel Application Switch 46Capacity planning 46OC 20

40 Planning and engineeringThe redundant, primary, and alternate NRS can be either the VxWorks NRSor the Linux-based NRS (SPS/SRS). For the OCS 2007 E

Network configuration 41Figure 13 "Multiple customer network" (page 41) provides an example of amultiple customer network. The figure shows tw

42 Planning and engineeringThe Signaling Server, OCS Proxy server (which runs MCM), OCS 2007Front End server, and Active Directory are separate. The n

Load Balancer planning 43Mediation servers supports only TCP. However, it can interact with TLSgateway through SPS. SPS can act as a redirect server f

44 Planning and engineeringTable 3Load balancer minimum configurationServiceProtocol Port (range) DescriptionTLS pool TCP5061The client listens over th

Load Balancer planning 45•Every Office Communications Server must have exactly one networkadapter. Multihoming an Office Communications Server is notsup

46 Planning and engineeringaddress is used by clients as a single point of connection to the pool. Thisaddress is listed in DNS and has an FQDN. Inter

Capacity planning 47Capacity planning navigation•"OC 2007 client requirements" (page 47)•"Load Balancer capacity requirements" (pa

48 Planning and engineeringTo illustrate this, consider the following high-level example:Client A sends a TR/87 SIP INVITE to Node 1 to monitor DN 100

Capacity planning 49Figure 16SIP CTI (TR/87) exampleMediation server requirementsThe CS 1000 can process up to 13 000 simultaneous calls. Therefore, y

Contents 5Installation 101OCS 2007 installation preparation and deployment 103CS 1000 and Signaling Server installation 105OCS 2007 component installa

50 Planning and engineeringFor example, MCM works as a software load balancer in addition to a router.MCM uses a round-robin algorithm for load balanc

General requirements 51The number of users the OCS Proxy server with MCM can handle dependson the usage and the number of calls per hour per user. For

52 Planning and engineering•"OC client authentication" (page 59)•"Authorization of TR/87 (Remote Call Control) Service Requests" (

General requirements 53Hardware RequirementsUse the following table to deter mine hardware requirements for the OCS2007 Standard and Enterprise Editio

54 Planning and engineeringTable 9Back end database for a small to medium Enterprise poolCPU Dual processor, dual-core 2.6 GHz +Disk Drive 1 (2 × 18 G

General requirements 55Communications Server that runs Microsoft Virtual Server 2005. Foradditional information about Virtual Server 2005, see the Vir

56 Planning and engineeringTable 12InputsInput DescriptionTN_MO_Users Total number of Office Communicator users that use the SIP Access Portsfor voice

General requirements 57Traffic (CCS)Traffic (Erlang) Number of ports70 1.947752.08780 2.22785 2.36790 2.5 895 2.64 8100 2.78 8125 3.47 9150 4.17 10175

58 Planning and engineeringTraffic (CCS)Traffic (Erlang) Number of ports2000 55.56 742500 69.44 903000 83.33 1063500 97.22 1214000 111.11 1374500 125

General requirements 59The port range can be controlled (restricted) to a smaller range usingthe group policy settings as described on the Microsoft W

6 ContentsCS 1000 configuration 173Signaling Server configuration 177SIP CTI Services configuration settings 181SIP CTI CLID configuration parameters 185C

60 Planning and engineeringFigure 17Signaling security•Secure Management Zone (SMZ) provides management access to localand remote devices over a secur

General requirements 61Figure 18Signaling security with TLSDial Plan considerationsNortel Converged Office is comprised of the following two components

62 Planning and engineering•CS 1000 Call Server configuration relating to the SIP Gateway•OCS Location Profile, Policy, Phone Usage, and Route configurat

General requirements 63Figure 19Signaling and media pathsNumber formats supported by Office CommunicatorDialstrings and E.164 International number form

64 Planning and engineeringAll E.164 numbers presented to the CS 1000, computer, or phone areexpected in the following format:+<country code><

General requirements 65A nor malization rule can be used to strip the digit in brackets to conform tothe expected format for E.164 numbers when using

66 Planning and engineeringIf calls that enter the Call Server are international and outside of thecountry of the caller, the translator must contain

Telephony Gateway and Services planning 67System, platform, or application SupportedM1/CS 1000 SystemsCS 1000M SG (CP PIV) YesCS 1000M MG (CP3/4) YesC

68 Planning and engineeringFigure 22SIP routingCalls made to a CS 1000 that is different from the twinned telephone baseuses two SIP trunks: one incom

Telephony Gateway and Services planning 69Figure 23Computer callLG-Nortel IP Phone 8540 OCS desk phone An Enterprise Voice onlyclient (no PBX integrat

Contents 7MCM logs 228Activating MCM logging 229OCS logs 231Case checklists 234Appendix A Call Flow and protocol details 237Contents 237Overview 237Me

70 Planning and engineeringOffice Communicator-initiated Call Transfer in Computer and PBXIntegration Enabled If the Office Communicator transfers a cal

Telephony Gateway and Services planning 71VoIP calls can only be placed to other Office Communicator users (computerto computer calls). Outgoing VoIP c

72 Planning and engineeringVideo Call Transfer Office Communicator calls made in Computer modethat have established video can transfer to another Office

Remote Call Control with SIP CTI 73ipDialog Ethernet Phone Office Communicator clients can work with theipDialog Ethernet Phone only if it is tandemed

74 Planning and engineeringFigure 24Simple network diagramThe TR/87 FE is the application that resides on the CS 1000 SignalingServer to support the t

Remote Call Control with SIP CTI 75Systems, platforms, and applicationsInteroperableSupportedCS 1000M SG (CP-PII and -PIV) Y YCS 1000M SG (CP PIV) Y Y

76 Planning and engineeringSystems, platforms, and applicationsInteroperableSupportedWLAN Handset 2212 Y YIP Phone 1110 Y YIP Phone 2007 Y YIP Phone 1

Remote Call Control with SIP CTI 77Systems, platforms, and applicationsInteroperableSupportedSymposium Agent Y NSymposium Agent Greeting Y NSymposium

78 Planning and engineeringSystems, platforms, and applicationsInteroperableSupportedAT&T SIP trunk Y NBroadsoft Y NACME SBC Y N3100 Mobile Commun

Remote Call Control with SIP CTI 79•After an event occurs that causes the IP Phones to register to a serverother than the Front End server (and then t

8 ContentsProcedure Configuring a Mediation Server 133Procedure Enabling replication to the Global Catalog 146Procedure Configuring the SIP Trunk Domain

80 Planning and engineeringThe Microsoft Office Communicator client has no automated mechanismto register to the branch. Users must wait for the existi

Remote Call Control with SIP CTI 81Feature OperationDescription•Conference Call - cannot be performed through Office Communicator .•Call Hold - can be

82 Planning and engineeringFeature OperationDescriptionOffice CommunicationsServer and MCScoexistenceATTENTIONAll Converged Office users must have the

LCS 2005 and OCS 2007 coexistence 83supported configuration because of incompatible underlying libraries. Thesame CS 1000 can be connected to two or mo

84 Planning and engineeringMCM 2.0 to MCM 3.0There is no direct upgrade path from MCM 1.0 or 2.0 to MCM 3.0 . MCM3.0 must be installed on the OCS Prox

Migration planning from LCS 2005 to OCS 2007 85PrerequisitesUpgrading to Office Communications Server 2007 assumes the following:•An understanding of t

86 Planning and engineering•An understanding of the coexistence interactions. For more information,see "LCS 2005 and OCS 2007 coexistence" (

Migration planning from LCS 2005 to OCS 2007 87Phase Description User experience2. Deploy OCS 2007 and beginmoving users to the new serveror pool.Depl

88 Planning and engineeringPhase Description User experience8. Continue migrating users. Migrate remaining users.Enable users for enhancedpresence. Ro

Migration planning from LCS 2005 to OCS 2007 89Migrating users from LCS to OCSStep Action1Upgrade your perimeter network by deploying an Access EdgeSe

9New in this releaseOffice Communications Ser ver 2007 featuresSignaling traffic between Communication Server 1000 and OfficeCommunications Server 2007 i

90 Planning and engineering7Configure PCA routing for new OC client users on the CS 1000.After configuration of PCA routing, users will be allowed to us

Unified Messaging 91Table 20CallPilot configurationsOC User(VoIP) withRCC and CS1000 PhoneOC User(VoIP) with noRCC and CS1000 PhoneOC User(VoIP) withno

92 Planning and engineeringATTENTIONFor Converged Office users not using a Nortel telephoneFor Converged Office users who use voice communications throu

Unified Messaging 93Logon fromOCLogon andpassworddirect direct direct N/AMWI on OC Yes Yes Yes Yes YesOutlook New msg ininboxNew msg ininboxNew msg ini

94 Planning and engineeringTable 22Unified Messaging 2007 integrated Option 2OC User(VoIP) withRCC and CS1000 PhoneOC User(VoIP) with noRCC and CS1000

Unified Messaging 95ATTENTIONFor Converged Office users not using a Nortel telephoneFor Converged Office users who use voice communications through the O

96 Planning and engineeringVM accessfrom OCDial SA DN Dial SA DN Dial SA DN Dial SA DN N/ALogin from OC p/w only p/w only p/w only p/w only N/AMWI on

Unified Messaging 97ATTENTIONFor Converged Office users not using a Nortel telephoneFor Converged Office users who use voice communications through the O

98 Planning and engineeringFigure 25Signaling integratedSignaling with non-integrated Voice MailIn a non-integrated configuration, the Office Communicat

Unified Messaging 99Figure 26Signaling non-integratedNortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft Office Communicatio