Nortel Networks NN43001-121 instruction

Nortel Communication Server 1000

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

NN43001-121

Image 1

Nortel Networks NN43001-121 manual

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 features January Revision HistoryDecember Getting help from the Nortel web site How to get help Getting help through a Nortel distributor or reseller Introduction navigation Prerequisites Introduction Converged Ofﬁce Component overview navigation Converged Ofﬁce component overview Enterprise Voice components OCS Enterprise Voice OCS 2007 Voice components Core routing server components Media Gateways CS 1000 and OCS 2007 logical network elements Mediation Server Signaling and Media path between the OC client and CS Example of RCC with SIP CTI TR/87 Remote Call Control with SIP CTI TR/87 Remote Call Control Telephony Gateway and Services Converged Ofﬁce component overview Dual forking example Personal Call Assistant Personal Call Assistant PCA service OCS 2007 snap-in Access Edge Server CDR data collection Multimedia Convergence Manager Call Appearance pop-up window SIP CTI TR/87 Protocol SIP diagram IP diagram page 31 depicts the IP protocol information Hardware Load Balancer IP diagram Documentation References Ofﬁce Communicator Documentation References Technical document Content Primary audience Planning process Planning and engineering navigation Network conﬁguration Small network Small network conﬁguration Medium network Medium network conﬁguration Large network Large network conﬁguration Multiple customer network Multiple customer network Multiple location network Multiple location network Load balancer navigation Load Balancer planningLoad Balancer prerequisites TCP Load Balancer requirements High-scale and high availability conﬁguration Redundancy with Load Balancers Capacity planning Nortel Application SwitchIncoming Load Balancer Capacity planning navigation SIP CTI TR/87 services requirementsOC 2007 client requirements Load Balancer capacity requirements Planning and engineering Mediation server requirements Signaling Server requirementsSIP CTI TR/87 example OCS Proxy and MCM capacity requirements Call Server requirementsMaximum call rate Usage General requirements navigation General requirements Operating System Requirements Server topology Mediation Server hardware requirements Hardware Hardware RequirementsOCS Proxy server hardware requirements Back end database for a small to medium Enterprise pool Virtual ServerBack end database for a large Enterprise pool Ofﬁce Communicator client requirements Storage SIP access portTrunks Trafﬁc ﬁgures Traffic CCS Traffic Erlang Number of ports Inputs Description Traffic CCS Traffic Erlang Number of ports Port use Basic Client Conﬁguration Security Signaling and media encryption Signaling security Dial Plan considerations Signaling security with TLSComputer SIP Calls Phone RCC or TR/87 Calls Number formats supported by Ofﬁce Communicator Signaling and media pathsDialstrings International Format Numbers Outside North America format North American format Outside North America Within North America Telephony Gateway and Services navigation Telephony Gateway and Services planningInternational format numbers for SIP Gateway and SIP CTI Systems, platforms, and applications Redundancy CapacitySIP routing SIP routing Feature Interactions Computer 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 diagram Nortel applications Other systems, call servers Gateways CDR Competitors Third party applications Campus redundancy Single node RedundancyGeographic redundancy Branch Ofﬁce redundancy MG 1000B/SRG SIPCTIStop all command Command Description Call Forward state changes Feature Interactions of RCC Feature Operation Description Feature Operation Description Client considerations LCS 2005 and OCS 2007 coexistenceConverged Ofﬁce functionality LCS 2005 and OCS 2007 coexistence Migration planning from LCS 2005 to OCS Default conﬁguration parameters Parameter Default valueMCM 2.0 to MCM Load balancer considerations Prerequisites Determine your deployment options User experience Phase DescriptionMigration process Phase Description User experience Functionality Description of Migration Phases Step Action Migrating users from LCS to OCS Uniﬁed Messaging OCS 2007 users using CallPilotUniﬁed Messaging navigation End CallPilot conﬁgurations For Converged Ofﬁce users using a Nortel telephone For Converged Ofﬁce users not using a Nortel telephone OCS 2007 users using UM 2007-integratedUniﬁed Messaging 2007 integrated Option SA DN For Converged Ofﬁce users using a Nortel telephone Uniﬁed Messaging 2007 non-integrated OCS 2007 users using UM 2007-non-integrated SA DN PCA Cfna Signaling with integrated Voice Mail Signaling integrated Signaling with non-integrated Voice Mail Signaling non-integrated Planning and engineering Installation Installation and conﬁguration ﬂow Installation navigation OCS 2007 installation preparation and deployment OCS 2007 installation preparation and deployment ﬂow chart OCS 2007 component installation CS 1000 and Signaling Server installationInstalling the CS 1000 system Installing the Signaling Server Active Directory Prerequisite OCS 2007 information Ofﬁce Communications Server OCS 2007 Enterprise Pool OCS Proxy server installation Installing the OCS Proxy server Load Balancer installationInstalling the Load Balancer Select Network Connections Installing MCM MCM installationPrerequisite MCM information Select Create a new account Conﬁguration Active Directory conﬁguration Conﬁguration ﬂow chart Active Directory Microsoft Ldap server User properties Deﬁning users Click 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 Voice Voice Properties conﬁguration Load Balancer conﬁguration Enabling dual forking-by user Enabling dual forking-globallyStep Action Click Forest and then Properties Host Authorization and Routing conﬁguration OCS conﬁguration procedures Conﬁguration of Static RoutesApplying policy Opening Ofﬁce Communications Server Ofﬁce Communications Server Front Ends For an example, see Routing tab Routing tab Opening the Computer Management console Conﬁguring host authorization for the OCS Proxy Ofﬁce Communications Server Management Console Click the Host Authorization tab Edit Authorized Host OCS Front End OCS Mediation OCS Application Servers Pool Host Authorization CTI TLS SIP CTI TLS OCS Conﬁguring a Mediation Server Mediation Server conﬁguration Click the Next Hop Connections tab MCM 3.0 conﬁguration MCM architecture Example 2 Incoming calls to Ofﬁce Communicator Example 1 Outgoing calls from Ofﬁce CommunicatorMCM architecture MCM management console MCM Direct conﬁguration 138 Conﬁguration MCM menu options MCM conﬁguration window SPS Network topology ﬁelds Configuration field Description Mediation routing table Following Element Manager SIP URI MAP Element Manager SIP URI MAP Get SIP URI Get phone Enabling replication to the Global Catalog Replicating 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ﬁguration Conﬁguring the Codec Call Server conﬁguration Codec conﬁguration Loss Plan conﬁguration Dialing plan to route to MCM Dialing Plan conﬁguration to route to MCM Marp Conﬁguring the Personal Call Assistant Prompt Response Description Screen output 156 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ﬁguration DNS conﬁguration SIP Trunk conﬁguration SIP Gateway conﬁguration window STRI/STRO WNK WNK Sigo ESN5 Domain naming SIP Trunk Domain name Conﬁguring the SIP Trunk Domain name URI Mapping Element Manager Signaling Server Properties SIP URI Map SIP GW Clid Parameters SIP Gateway Clid Parameters conﬁguration Parameter Area Code Parameter Country CodeParameter Subscriber / Number of Digits to strip Parameter Subscriber / Preﬁx to insert NRS conﬁguration Ofﬁce Communications Server Service Domain CDR conﬁguration Remote Call Control conﬁguration Step Action Go to the Ofﬁce Communicator menu RCC and PBX integration on OC client CS 1000 conﬁguration Enable integration with your phone systemConﬁguring the AML Type Adan LD 17 Conﬁgure AML Link Prompt Response Description Conﬁguring a station Conﬁguring the SIP CTI TR/87 ISM limitLD 22 ISM Limit printout LD 11-Twinning a station Prompt Response Description Considering Madn Multiple Appearance DN Signaling Server conﬁguration TR/87 Node conﬁguration Node parameter conﬁguration SIP Gateway conﬁguration SIP Gateway parameter conﬁguration 180 Conﬁguration SIP CTI Services conﬁguration settings SIP CTI Services settings Parameter Service EnabledParameter Customer Number Parameter International Calls As National Parameter Maximum Associations Per DN SIP CTI Dial Plan preﬁxes Parameter Dialing Plan SIP CTI Clid conﬁguration parameters Scenario 2 SIP CTI Dial Plan = UDP Scenario 1 SIP STI Dial Plan = CDPParameter Calling Device URI Format Parameter Subscriber/Number of Digits to strip Parameter Home Location CodeParameter Subscriber/Preﬁx to insert Parameter National/Number of Digits to strip North American Clid manipulation Non-North American SIP CTI conﬁguration example Non-North American Clid Manipulation Conﬁguring the SIP URI Map Conﬁguring CDR SIP Info message Normalizing Ofﬂine Recommended Normalizing phone numbers Creating Normalization rules Normalizing using the Address Book Service Example Result Adding a new Normalization ruleAdding a new normalization rule Step Action Normalization rule example for UDP dial plan Company phone number normalization rules for CDP Refresh Address Book on the client Refresh Address Book on the server SIP Routing and Redundancy conﬁguration OCS 2007 users using UM 2007 in integrated modeRedundancy conﬁguration Option 1 adding user Alias as Exchange UM Adding user Alias as Exchange UM Conﬁguring a basic mailbox for the UM user User 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 Communication Server IntroductionMCM Tools Signaling Server OAM Level CLI Commands Patches and upgradesRemote Call Control TTY SIP CTI Operational Measurements for SIP CTI Signaling Server Expert Level CLI Commands Polling message with IE type Checking Telephony Gateway conﬁguration Checking Telephony Gateway SIP Gateway conﬁguration Problem Lack of memory on Signaling ServerChecking Remote Call Control SIP CTI conﬁguration Checking Remote Call Control conﬁguration Symptom SIP CTI services does not come upSolution SIP Dialog not established Solution 2 Conﬁrm Fqdn and the IP address are correct Solution 1 Check conﬁguration parameters in ADSIP CTI service is down Screen output example for SIP CTI status Reconﬁgure SIP CTI service Solution 1 Check the Global Catalog content manually MCM not synchronizing new users in AD Cache modeLD 48, check the Elan status on the Call Server Solution 2 Access permissions for the AD object properties Checking the Global Catalog content manually Select User objects in the ﬁeld Apply onto Accessing permissions for the AD object properties OC client not registered Enable Replicate this attribute to the Global CatalogPop-up not displayed Call Forward is cancelled by Ofﬁce Communicator Delay for a SIP Gateway callSolutions Two pop-ups are displayed Capturing traces and logs Ofﬁce Communicator disconnecting from the networkCommunication Server 1000 traces AML traces on the Call Server SIP CTI only SIP CTI traces on the Signaling ServerSIP CTI trace in PDT Prompt Response Description SIP Gateway trace in PDT Prompt Response Description SIP Gateway traces on the Signaling Server Example of screen output for SIP Gateway trace MCM logs SIP and Debug Activating MCM loggingMCM logs MCM Event log MCM log ﬁle output Resetting MCM debug trace Step Action Resetting MCM debug traceOCS logs Event Viewer window OC logs Activating OCS logsEnabling OC logs Step Action OCS debugging tool Turn on Logging and Windows Event Logging OC client start-up debugging Signaling Server information Check Case checklistsNo PBX connection for OC client Call Server information Check MCM conﬁguration information NRS conﬁguration information CheckCheck OCS conﬁguration information Active Directory conﬁguration information Check Tracing information Check Overview Contents Message sequence SIP Info message with ECMA-323 content Telephony Gateway and Services call ﬂowCall ﬂow 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 Flow Remote Call Control Session Establishment through SRS Supported features Supported features Supported by Standard Edition Appendix B Conﬁguration Examples Overview of lab setup Setting up the lab Collecting required data Checking the Call Server conﬁguration Conﬁguring the Call ServerRequired Information Record your information For example Prt LD 22--check for licenses Prompt Response DescriptionSlt LD 20-SIP Trunk conﬁguration Prompt Response Description LD 22-MSCONV package Prompt Response Description Type RDB Cust Rout DES SIP Tktp TIE Npidtblnum LD 21-SIP Route conﬁguration Prompt Response Description LD 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 Description Screen 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 Description Checking the conﬁguration of the Signaling Server Signaling Server checklist Fqdn of the OCS 2007 Front End server DNS conﬁguration on the Signaling Server SIP GW Settings SIP URI Map SIP CTI Services Conﬁguring Network Routing Service NRSChecking NRS conﬁguration Step Action Signaling Server and MCM Endpoints status on NRS Routing Entry Active Directory user conﬁguration Checking the settings of Active Directory user conﬁguration General user properties Communications properties User Options Checking the MCM installation and conﬁguration MCM Application MCM Gateway Endpoint conﬁguration Overview of general lab set-up Enterprise EditionMCM Conﬁguration screen OCS Enterprise Edition General Overview Collecting Data for Enterprise EditionMicrosoft Active Directory Required information Record your For example Information OCS OCS Management Console OCS Management Console Identifying the active default applications Step Action OCS Default Applications RunningDetermining the exact Fqdn of the pool Default applications General tab settings Security/Certiﬁcates General settingsChecking the conﬁguration of Certiﬁcates Checking the conﬁguration of Host Authorization Host AuthorizationChoose the Host Authorization tab Front End server Certiﬁcate Routing Host Authorization for Front End serverChecking that Routing is correctly conﬁgured Routing for Enterprise Pool Conﬁguring DNS Click on the Service Location SRV tabChecking that DNS is correctly conﬁgured Select sipinternaltls Sipinternaltls SRV records Host a record for the Pool Active Directory conﬁguration User Advanced Settings Installing and conﬁguring MCM RTC Server Local Group Checking that MCM is correctly installed and conﬁgured RTC Server Application group MCM conﬁguration Conﬁguring NRS Checking that the Signaling Server is correctly conﬁguredChecking that NRS is correctly conﬁgured MCM endpoints Routing Entries for Endpoints Normalizing Phone Numbers Appendix B Conﬁguration Examples Appendix C Abbreviations CDP OCS IPSec Pstn Xpec VoIP Appendix C Abbreviations Page Nortel Communication Server