Manuals / Nortel Networks / Computer Equipment / Server

Nortel Networks NN43001-121 manual Ofﬁce Communications Server conﬁguration

Models: NN43001-121

1 304

Download 304 pages 15.62 Kb

Page 119

Ofﬁce Communications Server conﬁguration 119

Figure 35

Enable both RCC and Enterprise Voice

Ofﬁce Communications Server conﬁguration

The starting point for Telephony Gateway and Services conﬁguration is the Ofﬁce Communications Server 2007 component.

Nortel Communication Server 1000

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Copyright © 2005–2008, Nortel Networks

Image 119

Nortel Networks NN43001-121 manual Ofﬁce Communications Server conﬁguration, Enable both RCC and Enterprise Voice

Contents

NN43001-121 Legal Notice Contents NN43001-121 01.03 Standard Release April Installation 101 Maintenance 209 Appendix a Call Flow and protocol details 237 Copyright 2005-2008, Nortel Networks Other changes Ofﬁce Communications Server 2007 featuresDecember Revision HistoryJanuary Getting help from the Nortel web site How to get helpGetting help through a Nortel distributor or reseller Introduction navigation PrerequisitesIntroduction Converged Ofﬁce Component overview navigationConverged Ofﬁce component overview Enterprise Voice components OCS Enterprise VoiceOCS 2007 Voice components Core routing server components Media GatewaysCS 1000 and OCS 2007 logical network elements Mediation ServerSignaling and Media path between the OC client and CS Example of RCC with SIP CTI TR/87 Remote Call Control with SIP CTI TR/87Remote Call Control Telephony Gateway and ServicesConverged Ofﬁce component overview Dual forking example Personal Call AssistantPersonal Call Assistant PCA service OCS 2007 snap-in Access Edge ServerCDR data collection Multimedia Convergence ManagerCall Appearance pop-up window SIP CTI TR/87 ProtocolSIP diagram IP diagram page 31 depicts the IP protocol informationHardware Load Balancer IP diagramDocumentation References Ofﬁce CommunicatorDocumentation References Technical document Content Primary audience Planning process Planning and engineering navigationNetwork conﬁguration Small network Small network conﬁguration Medium networkMedium network conﬁguration Large networkLarge network conﬁguration Multiple customer networkMultiple customer network Multiple location network Multiple location networkLoad Balancer prerequisites Load Balancer planningLoad balancer navigation TCP Load Balancer requirementsHigh-scale and high availability conﬁguration Redundancy with Load BalancersIncoming Load Balancer Nortel Application SwitchCapacity planning Load Balancer capacity requirements SIP CTI TR/87 services requirementsCapacity planning navigation OC 2007 client requirementsPlanning and engineering SIP CTI TR/87 example Signaling Server requirementsMediation server requirements Maximum call rate Usage Call Server requirementsOCS Proxy and MCM capacity requirements General requirements navigation General requirementsOperating System Requirements Server topologyOCS Proxy server hardware requirements Hardware RequirementsMediation Server hardware requirements Hardware Ofﬁce Communicator client requirements Virtual ServerBack end database for a small to medium Enterprise pool Back end database for a large Enterprise poolTrunks SIP access portStorage Trafﬁc ﬁgures Traffic CCS Traffic Erlang Number of ports Inputs DescriptionTraffic CCS Traffic Erlang Number of ports Port use Basic Client ConﬁgurationSecurity Signaling and media encryptionSignaling security Computer SIP Calls Signaling security with TLSDial Plan considerations Phone RCC or TR/87 Calls International Format Numbers Signaling and media pathsNumber formats supported by Ofﬁce Communicator DialstringsOutside North America format North American formatOutside North America Within North AmericaSystems, platforms, and applications Telephony Gateway and Services planningTelephony Gateway and Services navigation International format numbers for SIP Gateway and SIP CTISIP routing CapacityRedundancy SIP routing Feature InteractionsComputer call Planning and engineering Telephony Gateway and Services planning Planning and engineering Remote Call Control with SIP CTI Supported systems, platforms, and applications Simple network diagramNortel applications Other systems, call servers GatewaysCDR Competitors Third party applicationsGeographic redundancy Single node RedundancyCampus redundancy Branch Ofﬁce redundancy MG 1000B/SRG SIPCTIStop all command Command DescriptionCall Forward state changes Feature Interactions of RCC Feature Operation DescriptionFeature Operation Description Converged Ofﬁce functionality LCS 2005 and OCS 2007 coexistenceClient considerations LCS 2005 and OCS 2007 coexistence Load balancer considerations Default conﬁguration parameters Parameter Default valueMigration planning from LCS 2005 to OCS MCM 2.0 to MCMPrerequisites Migration process User experience Phase DescriptionDetermine your deployment options Phase Description User experience Functionality Description of Migration PhasesStep Action Migrating users from LCS to OCSEnd OCS 2007 users using CallPilotUniﬁed Messaging Uniﬁed Messaging navigationCallPilot conﬁgurations For Converged Ofﬁce users using a Nortel telephoneUniﬁed Messaging 2007 integrated Option OCS 2007 users using UM 2007-integratedFor Converged Ofﬁce users not using a Nortel telephone SA DN For Converged Ofﬁce users using a Nortel telephone Uniﬁed Messaging 2007 non-integrated OCS 2007 users using UM 2007-non-integratedSA DN PCA Cfna Signaling with integrated Voice Mail Signaling integrated Signaling with non-integrated Voice MailSignaling non-integrated Planning and engineering Installation Installation and conﬁguration ﬂow Installation navigationOCS 2007 installation preparation and deployment OCS 2007 installation preparation and deployment ﬂow chart Installing the Signaling Server CS 1000 and Signaling Server installationOCS 2007 component installation Installing the CS 1000 systemActive Directory Prerequisite OCS 2007 informationOfﬁce Communications Server OCS 2007 Enterprise Pool OCS Proxy server installationSelect Network Connections Load Balancer installationInstalling the OCS Proxy server Installing the Load BalancerPrerequisite MCM information MCM installationInstalling MCM Select Create a new account Conﬁguration Active Directory conﬁguration Conﬁguration ﬂow chartActive Directory Microsoft Ldap server User properties Deﬁning usersClick the Conﬁgure button 116 Conﬁguration Enable Remote call control Enable Enterprise Voice and PBX integration Ofﬁce Communications Server conﬁguration Enable both RCC and Enterprise VoiceVoice Properties conﬁguration Load Balancer conﬁgurationStep Action Click Forest and then Properties Enabling dual forking-globallyEnabling dual forking-by user Applying policy OCS conﬁguration procedures Conﬁguration of Static RoutesHost Authorization and Routing conﬁguration Opening Ofﬁce Communications Server Ofﬁce Communications Server Front Ends For an example, see Routing tabRouting tab Opening the Computer Management console Conﬁguring host authorization for the OCS ProxyOfﬁce Communications Server Management Console Click the Host Authorization tab Edit Authorized Host OCS Front End OCS Mediation OCS Application Servers Pool Host AuthorizationCTI TLS SIP CTI TLS OCS Conﬁguring a Mediation Server Mediation Server conﬁgurationClick the Next Hop Connections tab MCM 3.0 conﬁgurationMCM architecture MCM architecture Example 1 Outgoing calls from Ofﬁce CommunicatorExample 2 Incoming calls to Ofﬁce Communicator MCM management console MCM Direct conﬁguration138 Conﬁguration MCM menu options MCM conﬁguration window SPS Network topology ﬁelds Configuration field DescriptionMediation routing table Following Element Manager SIP URI MAP Element Manager SIP URI MAP Get SIP URI Get phone Enabling replication to the Global CatalogReplicating attributes to the Global Catalog Network dial plan Configuration field Description MCM 3.0 conﬁguration Enable phone integration on the client Telephony Gateway and Services conﬁgurationConﬁguring the Codec Call Server conﬁgurationCodec conﬁguration Loss Plan conﬁgurationDialing plan to route to MCM Dialing Plan conﬁguration to route to MCMMarp Conﬁguring the Personal Call AssistantPrompt Response Description Screen output156 Conﬁguration Caller ID table conﬁguration Following is a portion of the screen output DNS Server conﬁguration Home LOC and Home NPA conﬁgurationDNS conﬁguration SIP Trunk conﬁgurationSIP Gateway conﬁguration window STRI/STRO WNK WNK Sigo ESN5 Domain namingSIP Trunk Domain name Conﬁguring the SIP Trunk Domain nameURI Mapping Element Manager Signaling Server PropertiesSIP URI Map SIP GW Clid Parameters SIP Gateway Clid Parameters conﬁgurationParameter Subscriber / Preﬁx to insert Parameter Country CodeParameter Area Code Parameter Subscriber / Number of Digits to stripNRS conﬁguration Ofﬁce Communications Server Service DomainCDR conﬁguration Remote Call Control conﬁguration Step Action Go to the Ofﬁce Communicator menu RCC and PBX integration on OC clientConﬁguring the AML Enable integration with your phone systemCS 1000 conﬁguration Type Adan LD 17 Conﬁgure AML Link Prompt Response DescriptionLD 22 ISM Limit printout Conﬁguring the SIP CTI TR/87 ISM limitConﬁguring a station LD 11-Twinning a station Prompt Response Description Considering Madn Multiple Appearance DNSignaling Server conﬁguration TR/87 Node conﬁguration Node parameter conﬁgurationSIP Gateway conﬁguration SIP Gateway parameter conﬁguration180 Conﬁguration SIP CTI Services conﬁguration settings Parameter Customer Number Parameter Service EnabledSIP CTI Services settings Parameter International Calls As National Parameter Maximum Associations Per DNSIP CTI Dial Plan preﬁxes Parameter Dialing Plan SIP CTI Clid conﬁguration parametersParameter Calling Device URI Format Scenario 1 SIP STI Dial Plan = CDPScenario 2 SIP CTI Dial Plan = UDP Parameter National/Number of Digits to strip Parameter Home Location CodeParameter Subscriber/Number of Digits to strip Parameter Subscriber/Preﬁx to insertNorth American Clid manipulation Non-North American SIP CTI conﬁguration exampleNon-North American Clid Manipulation Conﬁguring the SIP URI MapConﬁguring CDR SIP Info message Normalizing Ofﬂine Recommended Normalizing phone numbersCreating Normalization rules Normalizing using the Address Book ServiceExample Normalization rule example for UDP dial plan Adding a new Normalization ruleResult Adding a new normalization rule Step ActionCompany phone number normalization rules for CDP Refresh Address Book on the client Refresh Address Book on the serverOption 1 adding user Alias as Exchange UM OCS 2007 users using UM 2007 in integrated modeSIP Routing and Redundancy conﬁguration Redundancy conﬁgurationAdding user Alias as Exchange UM Conﬁguring a basic mailbox for the UM userUser Properties window for Exchange UM UM Address Dial plan window Uniﬁed Messaging Properties window Adding Exchange UM UM Address 206 Conﬁguration End 208 Conﬁguration Tools IntroductionCommunication Server MCMRemote Call Control Patches and upgradesSignaling Server OAM Level CLI Commands TTY SIP CTI Operational Measurements for SIP CTISignaling Server Expert Level CLI Commands Polling message with IE type Checking Telephony Gateway conﬁguration Checking Telephony Gateway SIP Gateway conﬁgurationChecking Remote Call Control conﬁguration Lack of memory on Signaling ServerProblem Checking Remote Call Control SIP CTI conﬁgurationSIP Dialog not established SIP CTI services does not come upSymptom SolutionSIP CTI service is down Solution 1 Check conﬁguration parameters in ADSolution 2 Conﬁrm Fqdn and the IP address are correct Screen output example for SIP CTI status Reconﬁgure SIP CTI serviceLD 48, check the Elan status on the Call Server MCM not synchronizing new users in AD Cache modeSolution 1 Check the Global Catalog content manually Solution 2 Access permissions for the AD object properties Checking the Global Catalog content manuallySelect User objects in the ﬁeld Apply onto Accessing permissions for the AD object propertiesPop-up not displayed Enable Replicate this attribute to the Global CatalogOC client not registered Two pop-ups are displayed Delay for a SIP Gateway callCall Forward is cancelled by Ofﬁce Communicator SolutionsCommunication Server 1000 traces Ofﬁce Communicator disconnecting from the networkCapturing traces and logs SIP CTI trace in PDT Prompt Response Description SIP CTI traces on the Signaling ServerAML traces on the Call Server SIP CTI only SIP Gateway trace in PDT Prompt Response Description SIP Gateway traces on the Signaling ServerExample of screen output for SIP Gateway trace MCM logsMCM logs Activating MCM loggingSIP and Debug MCM Event log MCM log ﬁle outputEvent Viewer window Resetting MCM debug traceResetting MCM debug trace Step Action OCS logsOCS debugging tool Activating OCS logsOC logs Enabling OC logs Step ActionTurn on Logging and Windows Event Logging OC client start-up debuggingCall Server information Check Case checklistsSignaling Server information Check No PBX connection for OC clientActive Directory conﬁguration information Check NRS conﬁguration information CheckMCM conﬁguration information Check OCS conﬁguration informationTracing information Check Overview ContentsMessage sequence Call ﬂow Telephony Gateway and Services call ﬂowSIP Info message with ECMA-323 content Inbound call to OC client with SPS, OC client answers Inbound call to OC client with SRS, phone answers Direct inbound call to OC client, OC client answers Call ﬂow Call Forward by OC client Call Forward call ﬂow by OC client Remote Call Control Call FlowRemote Call Control Session Establishment through SRS Supported featuresSupported features Supported by Standard Edition Appendix B Conﬁguration ExamplesOverview of lab setup Setting up the labCollecting required data Required Information Record your information For example Conﬁguring the Call ServerChecking the Call Server conﬁguration Slt LD 22--check for licenses Prompt Response DescriptionPrt LD 20-SIP Trunk conﬁguration Prompt Response Description LD 22-MSCONV package Prompt Response DescriptionType RDB Cust Rout DES SIP Tktp TIE Npidtblnum LD 21-SIP Route conﬁguration Prompt Response DescriptionLD 11-TN conﬁguration Prompt Response Description Tnb 152 0 0 LD 21-Conﬁrm PCA for SIP Gateway Prompt Response Description LD 21-Conﬁrm PCA is activated Prompt Response DescriptionScreen output shown here may differ depending on the setup Iapg Aacs no Itna no Dgrp Mlwulang 0 Mlng ENG Dndr Flen DSP LSC Rrpa no RLI Ccba no NPA NXX LD 87-Conﬁgure DSC for PCA Prompt Response DescriptionChecking the conﬁguration of the Signaling Server Signaling Server checklistFqdn of the OCS 2007 Front End server DNS conﬁguration on the Signaling ServerSIP GW Settings SIP URI Map Checking NRS conﬁguration Step Action Conﬁguring Network Routing Service NRSSIP CTI Services Signaling Server and MCM Endpoints status on NRS Routing Entry Active Directory user conﬁguration Checking the settings of Active Directory user conﬁgurationGeneral user properties Communications properties User Options Checking the MCM installation and conﬁgurationMCM Application MCM Gateway Endpoint conﬁguration MCM Conﬁguration screen Enterprise EditionOverview of general lab set-up Microsoft Active Directory Collecting Data for Enterprise EditionOCS Enterprise Edition General Overview Required information Record your For example Information OCSOCS Management Console OCS Management Console Determining the exact Fqdn of the pool OCS Default Applications RunningIdentifying the active default applications Step Action Default applications General tab settingsChecking the conﬁguration of Certiﬁcates General settingsSecurity/Certiﬁcates Front End server Certiﬁcate Host AuthorizationChecking the conﬁguration of Host Authorization Choose the Host Authorization tabChecking that Routing is correctly conﬁgured Host Authorization for Front End serverRouting Routing for Enterprise Pool Select sipinternaltls Click on the Service Location SRV tabConﬁguring DNS Checking that DNS is correctly conﬁguredSipinternaltls SRV records Host a record for the Pool Active Directory conﬁgurationUser Advanced Settings Installing and conﬁguring MCMRTC Server Local Group Checking that MCM is correctly installed and conﬁguredRTC Server Application group MCM conﬁguration Checking that NRS is correctly conﬁgured Checking that the Signaling Server is correctly conﬁguredConﬁguring NRS MCM endpoints Routing Entries for Endpoints Normalizing Phone NumbersAppendix B Conﬁguration Examples Appendix C Abbreviations CDP OCS IPSecPstn Xpec VoIPAppendix C Abbreviations Page Nortel Communication Server