Manuals / Nortel Networks / Computer Equipment / Server

Nortel Networks NN43001-121 manual Appendix B Conﬁguration Examples

Models: NN43001-121

1 304

Download 304 pages 15.62 Kb

Page 296

296Appendix B Conﬁguration Examples

If the Telephone Number is normalized to the Line URI format, you can use the "Click to Call" feature to show the caller’s user name when the Address Book Service is available.

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 296

Nortel Networks NN43001-121 manual Appendix B Conﬁguration Examples

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 Ofﬁce Communications Server 2007 features Other changesDecember Revision HistoryJanuary How to get help Getting help from the Nortel web siteGetting help through a Nortel distributor or reseller Prerequisites Introduction navigationIntroduction Component overview navigation Converged OfﬁceConverged Ofﬁce component overview Enterprise Voice Enterprise Voice components OCSOCS 2007 Voice components Media Gateways Core routing server componentsMediation Server CS 1000 and OCS 2007 logical network elementsSignaling and Media path between the OC client and CS Remote Call Control with SIP CTI TR/87 Example of RCC with SIP CTI TR/87Telephony Gateway and Services Remote Call ControlConverged Ofﬁce component overview Personal Call Assistant Dual forking examplePersonal Call Assistant PCA service Access Edge Server OCS 2007 snap-inMultimedia Convergence Manager CDR data collectionSIP CTI TR/87 Protocol Call Appearance pop-up windowIP diagram page 31 depicts the IP protocol information SIP diagramIP diagram Hardware Load BalancerOfﬁce Communicator Documentation ReferencesDocumentation References Technical document Content Primary audience Planning and engineering navigation Planning processNetwork conﬁguration Small network Medium network Small network conﬁgurationLarge network Medium network conﬁgurationMultiple customer network Large network conﬁgurationMultiple customer network Multiple location network Multiple location networkLoad Balancer prerequisites Load Balancer planningLoad balancer navigation Load Balancer requirements TCPRedundancy with Load Balancers High-scale and high availability conﬁgurationIncoming Load Balancer Nortel Application SwitchCapacity planning SIP CTI TR/87 services requirements Capacity planning navigationOC 2007 client requirements Load Balancer capacity 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 General requirements navigationServer topology Operating System RequirementsOCS Proxy server hardware requirements Hardware RequirementsMediation Server hardware requirements Hardware Virtual Server Back end database for a small to medium Enterprise poolBack end database for a large Enterprise pool Ofﬁce Communicator client requirementsTrunks SIP access portStorage Inputs Description Trafﬁc ﬁgures Traffic CCS Traffic Erlang Number of portsTraffic CCS Traffic Erlang Number of ports Basic Client Conﬁguration Port useSignaling and media encryption SecuritySignaling security Computer SIP Calls Signaling security with TLSDial Plan considerations Phone RCC or TR/87 Calls Signaling and media paths Number formats supported by Ofﬁce CommunicatorDialstrings International Format NumbersNorth American format Outside North America formatWithin North America Outside North AmericaTelephony Gateway and Services planning Telephony Gateway and Services navigationInternational format numbers for SIP Gateway and SIP CTI Systems, platforms, and applicationsSIP routing CapacityRedundancy Feature Interactions SIP routingComputer call Planning and engineering Telephony Gateway and Services planning Planning and engineering Remote Call Control with SIP CTI Simple network diagram Supported systems, platforms, and applicationsOther systems, call servers Gateways Nortel applicationsCDR Third party applications CompetitorsGeographic redundancy Single node RedundancyCampus redundancy SIPCTIStop all command Command Description Branch Ofﬁce redundancy MG 1000B/SRGFeature Interactions of RCC Feature Operation Description Call Forward state changesFeature Operation Description Converged Ofﬁce functionality LCS 2005 and OCS 2007 coexistenceClient considerations LCS 2005 and OCS 2007 coexistence Default conﬁguration parameters Parameter Default value Migration planning from LCS 2005 to OCSMCM 2.0 to MCM Load balancer considerationsPrerequisites Migration process User experience Phase DescriptionDetermine your deployment options Phase Description User experience Description of Migration Phases FunctionalityMigrating users from LCS to OCS Step ActionOCS 2007 users using CallPilot Uniﬁed MessagingUniﬁed Messaging navigation EndFor Converged Ofﬁce users using a Nortel telephone CallPilot conﬁgurationsUniﬁ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 OCS 2007 users using UM 2007-non-integrated Uniﬁed Messaging 2007 non-integratedSA DN PCA Cfna Signaling with integrated Voice Mail Signaling with non-integrated Voice Mail Signaling integratedSignaling non-integrated Planning and engineering Installation Installation navigation Installation and conﬁguration ﬂowOCS 2007 installation preparation and deployment OCS 2007 installation preparation and deployment ﬂow chart CS 1000 and Signaling Server installation OCS 2007 component installationInstalling the CS 1000 system Installing the Signaling ServerPrerequisite OCS 2007 information Active DirectoryOCS Proxy server installation Ofﬁce Communications Server OCS 2007 Enterprise PoolLoad Balancer installation Installing the OCS Proxy serverInstalling the Load Balancer Select Network ConnectionsPrerequisite MCM information MCM installationInstalling MCM Select Create a new account Conﬁguration Conﬁguration ﬂow chart Active Directory conﬁgurationActive Directory Microsoft Ldap server Deﬁning users User propertiesClick the Conﬁgure button 116 Conﬁguration Enable Remote call control Enable Enterprise Voice and PBX integration Enable both RCC and Enterprise Voice Ofﬁce Communications Server conﬁgurationLoad Balancer conﬁguration Voice Properties 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 For an example, see Routing tab Ofﬁce Communications Server Front EndsRouting tab Conﬁguring host authorization for the OCS Proxy Opening the Computer Management consoleOfﬁce Communications Server Management Console Click the Host Authorization tab Edit Authorized Host Host Authorization OCS Front End OCS Mediation OCS Application Servers PoolCTI TLS SIP CTI TLS OCS Mediation Server conﬁguration Conﬁguring a Mediation ServerMCM 3.0 conﬁguration Click the Next Hop Connections tabMCM architecture MCM architecture Example 1 Outgoing calls from Ofﬁce CommunicatorExample 2 Incoming calls to Ofﬁce Communicator MCM Direct conﬁguration MCM management console138 Conﬁguration MCM menu options MCM conﬁguration window Network topology ﬁelds Configuration field Description SPSMediation routing table Following Element Manager SIP URI MAP Element Manager SIP URI MAP Get SIP URI Enabling replication to the Global Catalog Get phoneReplicating attributes to the Global Catalog Network dial plan Configuration field Description MCM 3.0 conﬁguration Telephony Gateway and Services conﬁguration Enable phone integration on the clientCall Server conﬁguration Conﬁguring the CodecLoss Plan conﬁguration Codec conﬁgurationDialing Plan conﬁguration to route to MCM Dialing plan to route to MCMConﬁguring the Personal Call Assistant MarpScreen output Prompt Response Description156 Conﬁguration Caller ID table conﬁguration Following is a portion of the screen output Home LOC and Home NPA conﬁguration DNS Server conﬁgurationSIP Trunk conﬁguration DNS conﬁgurationSIP Gateway conﬁguration window STRI/STRO WNK WNK Domain naming Sigo ESN5Conﬁguring the SIP Trunk Domain name SIP Trunk Domain nameElement Manager Signaling Server Properties URI MappingSIP URI Map SIP Gateway Clid Parameters conﬁguration SIP GW Clid ParametersParameter Country Code Parameter Area CodeParameter Subscriber / Number of Digits to strip Parameter Subscriber / Preﬁx to insertOfﬁce Communications Server Service Domain NRS conﬁgurationCDR conﬁguration Remote Call Control conﬁguration RCC and PBX integration on OC client Step Action Go to the Ofﬁce Communicator menuConﬁguring the AML Enable integration with your phone systemCS 1000 conﬁguration LD 17 Conﬁgure AML Link Prompt Response Description Type AdanLD 22 ISM Limit printout Conﬁguring the SIP CTI TR/87 ISM limitConﬁguring a station Considering Madn Multiple Appearance DN LD 11-Twinning a station Prompt Response DescriptionSignaling Server conﬁguration Node parameter conﬁguration TR/87 Node conﬁgurationSIP Gateway parameter conﬁguration SIP Gateway conﬁguration180 Conﬁguration SIP CTI Services conﬁguration settings Parameter Customer Number Parameter Service EnabledSIP CTI Services settings Parameter Maximum Associations Per DN Parameter International Calls As NationalSIP CTI Dial Plan preﬁxes SIP CTI Clid conﬁguration parameters Parameter Dialing PlanParameter Calling Device URI Format Scenario 1 SIP STI Dial Plan = CDPScenario 2 SIP CTI Dial Plan = UDP Parameter Home Location Code Parameter Subscriber/Number of Digits to stripParameter Subscriber/Preﬁx to insert Parameter National/Number of Digits to stripNon-North American SIP CTI conﬁguration example North American Clid manipulationConﬁguring the SIP URI Map Non-North American Clid ManipulationConﬁguring CDR SIP Info message Normalizing phone numbers Normalizing Ofﬂine RecommendedNormalizing using the Address Book Service Creating Normalization rulesExample Adding a new Normalization rule ResultAdding a new normalization rule Step Action Normalization rule example for UDP dial planCompany phone number normalization rules for CDP Refresh Address Book on the server Refresh Address Book on the clientOCS 2007 users using UM 2007 in integrated mode SIP Routing and Redundancy conﬁgurationRedundancy conﬁguration Option 1 adding user Alias as Exchange UMConﬁguring a basic mailbox for the UM user Adding user Alias as Exchange UMUser 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 Introduction Communication ServerMCM ToolsRemote Call Control Patches and upgradesSignaling Server OAM Level CLI Commands TTY Operational Measurements for SIP CTI SIP CTISignaling Server Expert Level CLI Commands Polling message with IE type Checking Telephony Gateway SIP Gateway conﬁguration Checking Telephony Gateway conﬁgurationLack of memory on Signaling Server ProblemChecking Remote Call Control SIP CTI conﬁguration Checking Remote Call Control conﬁgurationSIP CTI services does not come up SymptomSolution SIP Dialog not establishedSIP CTI service is down Solution 1 Check conﬁguration parameters in ADSolution 2 Conﬁrm Fqdn and the IP address are correct Reconﬁgure SIP CTI service Screen output example for SIP CTI statusLD 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 Checking the Global Catalog content manually Solution 2 Access permissions for the AD object propertiesAccessing permissions for the AD object properties Select User objects in the ﬁeld Apply ontoPop-up not displayed Enable Replicate this attribute to the Global CatalogOC client not registered Delay for a SIP Gateway call Call Forward is cancelled by Ofﬁce CommunicatorSolutions Two pop-ups are displayedCommunication 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 traces on the Signaling Server SIP Gateway trace in PDT Prompt Response DescriptionMCM logs Example of screen output for SIP Gateway traceMCM logs Activating MCM loggingSIP and Debug MCM log ﬁle output MCM Event logResetting MCM debug trace Resetting MCM debug trace Step ActionOCS logs Event Viewer windowActivating OCS logs OC logsEnabling OC logs Step Action OCS debugging toolOC client start-up debugging Turn on Logging and Windows Event LoggingCase checklists Signaling Server information CheckNo PBX connection for OC client Call Server information CheckNRS conﬁguration information Check MCM conﬁguration informationCheck OCS conﬁguration information Active Directory conﬁguration information CheckTracing information Check Contents OverviewMessage 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 Remote Call Control Call Flow Call Forward call ﬂow by OC clientSupported features Remote Call Control Session Establishment through SRSSupported features Supported by Appendix B Conﬁguration Examples Standard EditionSetting up the lab Overview of lab setupCollecting 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 22-MSCONV package Prompt Response Description LD 20-SIP Trunk conﬁguration Prompt Response DescriptionLD 21-SIP Route conﬁguration Prompt Response Description Type RDB Cust Rout DES SIP Tktp TIE NpidtblnumLD 11-TN conﬁguration Prompt Response Description Tnb 152 0 0 LD 21-Conﬁrm PCA is activated Prompt Response Description LD 21-Conﬁrm PCA for SIP Gateway Prompt Response DescriptionScreen output shown here may differ depending on the setup Iapg Aacs no Itna no Dgrp Mlwulang 0 Mlng ENG Dndr LD 87-Conﬁgure DSC for PCA Prompt Response Description Flen DSP LSC Rrpa no RLI Ccba no NPA NXXSignaling Server checklist Checking the conﬁguration of the Signaling ServerDNS conﬁguration on the Signaling Server Fqdn of the OCS 2007 Front End 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 Checking the settings of Active Directory user conﬁguration Active Directory user conﬁgurationGeneral user properties Communications properties Checking the MCM installation and conﬁguration User OptionsMCM 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 OCS Required information Record your For example InformationOCS Management Console OCS Management Console Determining the exact Fqdn of the pool OCS Default Applications RunningIdentifying the active default applications Step Action General tab settings Default applicationsChecking the conﬁguration of Certiﬁcates General settingsSecurity/Certiﬁcates Host Authorization Checking the conﬁguration of Host AuthorizationChoose the Host Authorization tab Front End server CertiﬁcateChecking that Routing is correctly conﬁgured Host Authorization for Front End serverRouting Routing for Enterprise Pool Click on the Service Location SRV tab Conﬁguring DNSChecking that DNS is correctly conﬁgured Select sipinternaltlsSipinternaltls SRV records Active Directory conﬁguration Host a record for the PoolInstalling and conﬁguring MCM User Advanced SettingsChecking that MCM is correctly installed and conﬁgured RTC Server Local GroupRTC 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 Normalizing Phone Numbers Routing Entries for EndpointsAppendix B Conﬁguration Examples Appendix C Abbreviations CDP IPSec OCSPstn VoIP XpecAppendix C Abbreviations Page Nortel Communication Server