IBM Lotus Notes/Sametime Integration with Nortel Communication Server ACE SAS Fundamentals NN

Transcription

1 NN

2 Document status: Standard Document issue: Document date: 23 August 2010 Product release: 1.1 Job function: Fundamentals Type: Technical Document Language type: English. All Rights Reserved. While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks. CONTAINS Runtime Modules of IBM Lotus Sametime Software Developer's Kit Copyright IBM Corporation All Rights Reserved. CONTAINS software developed by the Apache Software Foundation All other trademarks are the property of their respective owners.

3 Contents New in this release 6 Features 6 Click-to-call 6 Telephony presence 6 Other changes 7 Fundamentals 8 SAS Manager 8 Dialing plan for telephony service 8 Device number provisioning 9 Users add preferred devices 9 Users make calls by entering a number 9 Sametime Server configuration impact 9 ACE SAS 10 Direct Mode SAS adapter 10 Telephone devices 10 Default office telephone device 10 Preferred device 11 SAS Installer 11 Sametime Meeting service interruption 12 Presence plug-in 12 Planning and Engineering 14 CS 1000 and SAS network deployment 14 Scalability, load balancing and redundancy 16 Requirements 16 Sametime Server OS 16 Sametime client OS 16 Sametime Server and Sametime Connect versions 16 Sametime Advance 17 Sametime Server hardware platforms 17 Supported directories 17 ACE Presence Plug-in version 17 Licensing 17

4 - 4 - Contents Capacity 17 SAS capacity 18 CS 1000 capacity 18 CS 1000 signaling and Call Server configuration for TR/87 18 Network Routing Service configuration 19 SAS limitations 20 SAS installation 22 Installing SAS on the Sametime Server 22 Upgrading SAS 23 Reinstalling SAS Add or Remove Programs 24 Reinstalling SAS SAS Installer 25 Uninstalling SAS Add or Remove Programs 27 Uninstalling SAS SAS Installer 27 Sametime Server and directory commissioning 29 Configuring the user default office telephony device 31 Creating Sametime policy groups with telephony feature enabled 32 Assigning users and user groups to Sametime telephony policy groups 35 Configuring user business card information 36 Disabling voice chat 38 Configuring Meeting Services to enable Sametime telephony services 39 Creating a Notes policy group 39 CS 1000 commissioning 42 SAS Manager commissioning 44 Configuring SAS without NRS (NRS mode none (Direct)) 44 Configuring SAS with NRS (NRS mode SPS) 48 Configuring Trace 51 Plug-in updates management 53 Configuring the Sametime Server to automatically push plug-ins 53 Locating the URL for the site that contains the Nortel plug-ins 55 Backup and restore 56 Backing up SAS configuration data 56 Restoring SAS configuration data 57 Maintenance 59 Trace files management 59 Monitor status 59 Events 61 SAS Installer events 61 SAS events 63 SAS Manager events 66

5 - 5 - Contents Troubleshooting 68 SAS installation issues 68 Out of disk space 68 Fatal error 68 Locked file deletion 69 Environment requirement not met 69 Rollback 69 Sametime client data corruption 69 Other issues 69 No telephony presence icon 70 Unable to call another Sametime Connect user 70 SAS does not start 70 Configuration changes are not applied 70 Unable to retrieve telephony information for a user 70 Presence information does not appear 70

6 New in this release This is the first release for Nortel (NN ). Features (page 6) Other changes (page 7) Features See the following sections for information about features: Click-to-call (page 6) Telephony presence (page 6) Click-to-call With the integration of Nortel Communication Server (CS 1000) Release 6.0 with Lotus Sametime Standard you can use Click-to-call from Lotus Notes and from the Sametime Connect client. Only Lotus Sametime clients are supported. For more information, see the following sections: Fundamentals (page 8) Planning and Engineering (page 14) Sametime Server and directory commissioning (page 29) SAS Manager commissioning (page 44) Telephony presence Through Lotus Sametime and CS 1000 integration, the telephony presence feature is available to online Sametime users. The Sametime Server retrieves users telephony device presence information from the CS 1000 switch, and then provides the information to all the Sametime watchers. For more information, see the following sections: Fundamentals (page 8) Planning and Engineering (page 14) Sametime Server and directory commissioning (page 29) SAS Manager commissioning (page 44)

7 - 7 - New in this release Other changes This section describes changes that are not feature-related. Revision History August 2010 Standard This document is issued to support Nortel ACE SAS Release 1.1. This document includes the following new sections: Configuring Meeting Services to enable Sametime telephony services (page 39) Creating a Notes policy group (page 39) Sametime client data corruption (page 69) November 2009 October 2009 Standard This document is issued to support Nortel ACE SAS Release 1.1. Standard This document is issued to support Nortel ACE SAS Release 1.1.

8 Fundamentals This chapter describes basic administrative information about Nortel Agile Communication Environment (ACE) Server Agent for Sametime (SAS). Navigation SAS Manager (page 8) Dialing plan for telephony service (page 8) Sametime Server configuration impact (page 9) ACE SAS (page 10) Telephone devices (page 10) SAS Installer (page 11) Presence plug-in (page 12) SAS Manager The SAS Manager is part of the SAS installation. The SAS Manager is a graphical user interface that administrators use for SAS configuration and to monitor the status of various running network services. Administrators can also use trace data collected from SAS Manager for diagnostics and trouble shooting activities. After the SAS installation is complete, start the SAS Manager to configure the SAS component. You can use Windows Remote Desktop Connection (RDC) to access the SAS Manager remotely. For more information about how to configure RDC client access to the server, see the Microsoft help documentation. Dialing plan for telephony service Dialing plan considerations apply to the following scenarios: Device number provisioning (page 9) Users add preferred devices (page 9) Users make calls by entering a number (page 9)

9 - 9 - Fundamentals Device number provisioning Use one of the following formats to provision the device number for a user s default office telephone in the directory: CDP dialing plan numbers (for example, 1234) UDP dialing plan numbers (for example, ) For UDP, the location code is required. CDP or UDP numbers must be qualified by phone context that you configure in the SAS Manager. All users provisioned in the directory for SAS must use the same dialing plan format. For example, if you use CDP, the dialing plan format for all users must be CDP; if you use UDP, the dialing plan format for all users must be UDP. Users add preferred devices Users can add preferred devices other than their default office telephone device, for example, another office phone or mobile phone. The format of the phone number for the new device must be either E.164 international format or another format dialable from the CS 1000 switch (for example, dialable from their office telephone). ACE SAS uses SIP trunks to the CS 1000 to communicate with these additional preferred devices. Users make calls by entering a number Users can make calls by entering a number in the Sametime Contact Search box. The number entered must be in either E.164 international format or another correctly prefixed format dialable from the user s office telephone. The following list provides some examples: Public international: or Public National: Public Local: CDP: 1234 UDP: Sametime Server configuration impact To implement SAS, you must perform some configuration on the Sametime Server or directory, including the following tasks: Configure users default telephone devices in the Domino directory or the external Lightweight Directory Access Protocol (LDAP) directory (if applicable). For more information, see Configuring the user default office telephony device (page 31).

10 Fundamentals Create Sametime Domino policy groups that have the telephony feature enabled (for Notes or Sametime Connect client, or both) and assign users and user groups to these Sametime telephony policy groups. You must configure the Sametime Domino user policies that specify users telephony capabilities on SAS Manager. Only the users who have these policies assigned have telephony access to the CS 1000 network. This configuration reduces unnecessary CS 1000 network attempts from unauthorized users. LDAP deployments require comparable configuration in SAS Manager. For more information, see Creating Sametime policy groups with telephony feature enabled (page 32) and Assigning users and user groups to Sametime telephony policy groups (page 35). Configure users business card information in the Sametime Server. For more information, see Configuring user business card information (page 36) ACE SAS ACE supports unified communication (UC) desktop integration with third-party communications systems. As a telephony platform, ACE enables third-party call control and telephony presence services on the Sametime Server. ACE SAS is a component that runs on the Sametime Server. To serve different customer requirements, there are two variants of SAS (referred to as adapters). While the two adapters and related architectures provide different feature sets, the end-user experience for Click-to-call and presence is similar for both. Attention: Currently, only Direct Connect adapter is supported. Direct Mode SAS adapter Direct Mode SAS connects the Sametime Server and CS 1000 switch directly through SIP and SIP CTI protocols, without adding intermediate software or hardware components. It is a cost effective, entry level solution for Click-to-call and telephony presence with the CS Telephone devices When a user places a call from the Notes or Sametime Connect client, the user's preferred device (telephone) makes the call. Default office telephone device Configure users default office telephone devices in the Domino directory or LDAP server (if applicable). The directory pushes the default device to the user's Sametime Connect client. For Multiple Appearance Directory Number (MADN), the Multiple Appearance Directory Number Redirection Prime (MARP) terminating number (TN) is the default office telephone device.

11 Fundamentals Attention: You cannot use a SIP device as the default office telephone device. When a user places a call with the default office telephone device, the audio path is automatically established (also referred to as click to dial). Remote Call Control enables origination of the call from that device. The on-hook path configuration of the device defines whether it uses headset or hands-free operation. For phone types that do not support hands-free (for example, M3905 or i2001), the speaker is the on-hook path regardless of the on-hook path configuration. In the absence of a microphone, only half-duplex is supported. If no speaker is available, the caller must pick up the phone. Preferred device Users can also add additional telephone devices to their preferred device list on the Sametime Connect client, such as other internal telephone numbers or external numbers such as mobile phones. For more information, see Nortel ACE SAS Click-to-Call and Telephony Presence for IBM Lotus Notes- Sametime User Guide (NN ). To establish a call with a preferred device, (other than the default office telephone) the client prompts (alerts) the device to go off-hook. For example, if you use your office phone, the called party gets a notification window (optional). If the called party clicks Accept, the called party s phone rings, and you can hear the ringback tone from your office phone. a phone that you added to Sametime Connect yourself, after the called party clicks Accept, your phone will be ringing first. Once you pickup your phone, the called party s phone starts ringing. SAS Installer The SAS Installer covers the file installations for the Direct mode adapter, as well as the SAS Manager. SAS components must reside in the same location as the IBM Sametime installation. Because all target folders are relative to the Domino/Sametime home directory, you cannot choose the installation directory. After the installation, you must run the SAS Manager to make SAS functional. SAS Installer provides an option to open the SAS Manager automatically at the end of installation.

12 Fundamentals The SAS Installer features downgrade protection, which uses the version number (standard major.minor.build format, for example, 1.0.1) of the SAS Installer. The SAS Installer checks for an existing SAS installation on the Sametime server, and then compares the version of the existing installation to the installer version to determine how to proceed: Downgrade prevention: If the installer version is older than the existing installation version, the installer aborts the installation and displays the following message "A later version of Nortel ACE SAS is already installed." Minimum version number required: The SAS Installer defines a minimum version number required for the upgrade. If the installed version is older than the minimum version number, the installer aborts the upgrade. In this case, you must uninstall the old version completely, and then run the installer again. Reinstall: If the installer version matches the version of the existing installation, the installer performs a reinstall (repair installation). Upgrade: If the installer version is newer than the existing installation version, the installation proceeds. The SAS Installer removes all existing files silently, and then installs new files. Because the contents of the configuration file can change during an upgrade, Nortel recommends that you run the SAS Manager after the upgrade is complete. For more information about messages that can appear during an installation or upgrade, see SAS installation issues (page 68). Sametime Meeting service interruption Old files to be removed during upgrade or uninstall can be in use by Sametime services. Windows prevents file deletion if the file is in use by a process. To free up files, you must stop these services in advance. The SAS Installer stops the Sametime Meeting service during an upgrade or uninstall, and restarts it again after the upgrade is complete. During an upgrade, users experience Sametime Meeting service interruption. Presence plug-in SAS presence support requires the installation of a Sametime client plug-in. There are two ways to install the presence plug-in: Sametime Server push: You must create an update site and configure the Sametime server to push client plug-ins to users client PCs. For more information, see Plug-in updates management (page 53). Sametime Client pull: Users must enter the URL for the plug-in update site in their Sametime client. You must provide the URL for the update site. For more information about how to configure the client to pull updates from the

13 Fundamentals update site, see Nortel ACE SAS Click to Call and Telephony Presence User Guide (NN ). SAS Direct mode uses only the telephony presence plug-in, which is the only plug-in required on client PCs. Attention: Currently, only SAS Direct Mode is supported. The available presence states are: None Idle Off Hook/Alerting Busy

14 Planning and Engineering This chapter describes planning and engineering requirements for Agile Communication Environment (ACE) Server Agent for Sametime (SAS). Navigation CS 1000 and SAS network deployment (page 14) Scalability, load balancing and redundancy (page 16) Requirements (page 16) Licensing (page 17) Capacity (page 17) CS 1000 signaling and Call Server configuration for TR/87 (page 18) Network Routing Service configuration (page 19) SAS limitations (page 20) CS 1000 and SAS network deployment A Sametime Server community can connect to a CS 1000 network through SAS. There are two ways SAS can connect to a CS 1000 network. SAS can connect directly to the CS 1000 Signaling server (for more information see the figure SAS direct connection to CS 1000 without NRS (page 15)), or through the Network Routing Service (NRS) to the CS 1000 signaling server (for more information, see the figure SAS deployment with NRS (page 15)). The calls that initiate from the Notes or Sametime Connect clients are trunk call requests to the CS If SAS connects directly to the CS 1000 Signaling server, the signaling server manages the call control requests only for the users that are logged onto the Sametime Server that hosts the SAS component.

15 SAS direct connection to CS 1000 without NRS Planning and Engineering SAS deployment with NRS With a Sametime cluster, an NRS must proxy the requests from all of the Sametime Servers to the CS If NRS (SPS) is deployed, configure SAS in the NRS as a gateway endpoint.

16 Planning and Engineering In a scenario where the users reside on different CS 1000 Servers, through NRS routing, SAS ensures that the user's home CS 1000 is always contacted. The calls originate from the user's home CS 1000, which ensures the proper application of any RPL (Restriction Permission List) rules. Scalability, load balancing and redundancy You can achieve Sametime scalability and redundancy by adding more Sametime Servers to the same Sametime Server community. Install each Sametime Server in the Sametime Server community that serves the CS 1000 users. You can choose to either use multiple home Sametime Servers or use Sametime Server clustering. With the home Sametime Server approach, the Sametime Servers share information and can support all users. Users are always logged into the their home Sametime Server, which the Sametime administrator assigns. If the home server goes down, you must assign another home server to the users of that home server. While this approach serves scalability requirements, it does not adequately serve redundancy requirements. With the Sametime Server clustering approach, a user can log on to any Sametime Server in the cluster. The cluster dynamically load balances logon requests across the Sametime Servers and if one server fails, the other servers process the requests. Load balancing and failover in the cluster is accomplished primarily through a rotating DNS system or IBM Edge Server. The rotating DNS system or WebSphere Edge Server fronts the clustered servers for load balancing. As each client connects, the rotating DNS system or Edge Server distributes the client connections evenly to the servers in the cluster. Requirements The following sections describe the requirements for the ACE SAS solution. Sametime Server OS SAS runs on Microsoft Windows 2003 Standard or Enterprise Edition, Service Pack 2 (SP2) on the same machine as the Sametime Server. Sametime client OS The presence plug-ins are supported on Microsoft Windows XP Professional SP2 or better, Microsoft Windows 2000 Pro SP4 or better, and on Microsoft Windows Vista. Sametime Server and Sametime Connect versions Sametime Server Standard is supported. Sametime Connect Standard Client is supported.

17 Planning and Engineering Support is not available for Lotus Notes Client with embedded Sametime Connect Client Sametime Advance Sametime Advance runs on a separate server, but requires Sametime Standard to run, therefore, a minimum of two servers is required). Sametime Advance provides additional functionality that is not available with Sametime Standard (for example, persistent chat rooms and other collaboration tools). All Sametime Advance customers also have Sametime Standard. SAS connects to the Sametime Standard server. If a Sametime Advance server is in the network, the basic SAS functionality continues to work with Sametime Standard server. Sametime Server hardware platforms For more information, see the Sametime Server Installation and Administration Guide. Supported directories The Domino directory, Domino LDAP directory, and external LDAP directories (such as Microsoft Active Directory) are supported. Only one root LDAP server (Domino, AD or other), which is aware of all user data is supported. ACE Presence Plug-in version The ACE 2.0 Presence Plug-in is supported, which aligns with Sametime Connect and Lotus Notes Licensing The CS 1000 requires the following Incremental Software Management (ISM) licenses: ISMs per device for TR/87 and AST. This covers calls made with the default office telephone device that is acquired and monitored by SAS by TR/87. ISMs for SIP Trunk Access Ports to support the call volume (two ports per call). This covers calls made with a preferred device, other than the default office telephone device, by SAS over SIP. You can obtain an IBM bundle, which contains the requisite licenses, from the ordering tool. Capacity The following sections discuss system capacity.

18 Planning and Engineering SAS capacity Because SAS resides on the same platform as the Sametime Server, the capacity of SAS depends on the hardware platform, on which the Sametime Server runs. For different server platforms, you can measure the capacity by using standardized sets of relevant benchmarks available from Standard Performance Evaluation Corporation (SPEC). For example, for a server that has SPECint_rate2000 value of 18.6, the maximum number of calls achieved is 10,000 calls per hour. Therefore, the supported number of calls per hour = (10,000 x SPECint_rate2000 of the server) / This is subject to limitations from the Sametime Server. In our testing, the maximum achieved is 10,000 calls per hour. The number of users that the system can support depends on the usage (the number of calls per hour per user). For example, assuming five calls per hour per user, the test platform can support 2000 users. CS 1000 capacity This integration solution requires CS 1000 Release 6.0 signaling server and call server. For a single Signaling Server, the maximum number of SIP CTI (TR/87) users is For the Call Server, the number of supported users depends on the CPU and platform type supported in Release 6.0. CP PIV: up to users (IP+TDM) CP PM: up to users (IP+TDM) CP PM Co-Res (SIP lines): up to 1200 IP Users (800 Unistim and 400 SIP) TDM CP PM Co-Res (no SIP lines): up to 1000 IP Users (Unistim) TDM' For more information about CS 1000 capacity numbers, including the breakdown, see the CS 1000 documentation suite. CS 1000 signaling and Call Server configuration for TR/87 Application Module Link (AML) is the main interface that supports call control requests from SIP CTI clients between the Signaling Server TR/87 FE application and the CS For detailed information about how to configure the AML link, see the CS 1000 documentation suite.

19 Planning and Engineering ISM for SIP CTI TR/87 defines the number of TNs that you can configure with the T87A Class of Service (CLS). In addition to the T87A CLS, you require AST ISMs to identify the controlled line itself as an AST DN. For more information, see the CS 1000 documentation. TR/87 control of a DN key can be supported on IP, digital, and analog stations (but not SIP phones). A T87A CLS is required to allow a TN to support the SIP CTI application. The AST prompt is used to configure which DN key on the TN is controlled or monitored by the SIP CTI application. You can configure a maximum of two keys per TN as AST keys. If you employ call control in a MADN environment, you must be aware of the following station configuration issues: If multiple TNs exist in a MADN group, configure T87A CLS and AST only on the MARP TN. Remote Call Control service requests sent by a Sametime user (for example, Make Call), always apply to the device defined as the MARP TN. For Single Call Ringing (SCR) keys, telephony presence updates represent all TNs within a MADN group. Therefore, when user answers a call on a wireless station SCR key on a non-marp TN, the telephony status shows "Busy". For Multiple Call Ringing (MCR) keys, telephony presence is supported only for the MARP TN within a MADN group. Therefore, when a user answers a call on a wireless station MCR key on a non-marp TN, the presence status does not show "Busy". Only calls answered on the MARP TN affect the telephony presence status of that Sametime user. Network Routing Service configuration Configure SAS as a gateway endpoint in the Network Routing Service (NRS) Manager, as shown in the following figure. SAS currently supports only static endpoints.

20 Planning and Engineering NRS configuration for SAS SAS limitations The following list describes the limitations for ACE SAS: A SIP device cannot be a user's default office telephone device for initiating remote call control calls. However, users can add SIP devices to their preferred device lists for making SIP calls. Only two-party Click-to-call is supported. Multi-party click to conference or web conference through telephone device is not supported. Telephony presence is only available for online users. Because of a Sametime Client limitation, Sametime users can only initiate one Click-to-call at a time. If a party is not using their default office telephone device, they must hang up the call from their telephone. Ending the call from the Sametime Client is not supported in this scenario. After SPS fail-over, Sametime support applies to new calls only. Preexisting active calls remain active; however, Sametime presence and hang-up are no longer maintained for those calls Support is not available for Outlook Client integration with Sametime Connect. Support is not available for Instant Meeting. Support is not available for call control to use the Sametime/Notes client to answer a call, place the call on hold, or transfer the call.

21 Planning and Engineering You can use the Sametime Connect dial pad to enter digits to dial a call, but you cannot use it during the call for transfers, IVR, Messaging, or any other DTMF use. Support is not available for SRTP, or SIP TLS.

22 SAS installation This chapter provides procedures for installing and uninstalling ACE SAS on the IBM Sametime Server. Navigation Installing SAS on the Sametime Server (page 22) Upgrading SAS (page 23) Reinstalling SAS SAS Installer (page 25) Uninstalling SAS Add or Remove Programs (page 27) Uninstalling SAS SAS Installer (page 27) Installing SAS on the Sametime Server Run the SAS Install Wizard to copy all required files into the proper destination directories on the IBM Sametime Server, create a program group and shortcut, create and update registry entries, and create or modify environment variables for ACE SAS. Prerequisites Download the SAS Installer package. Ensure that the Sametime Server is installed. Ensure that the volume, in which SAS is installed, contains a minimum of 500 MB of free space. Procedure steps Step Action 1 Run the SAS Installer package. 2 On the Welcome window, click Next.

23 SAS installation 3 Read the Nortel License Agreement. 4 Choose whether to proceed. Choose to Print the license agreement. Accept the license agreement and proceed. Cancel the installation. Do this Click Print. Select the check box beside I accept the terms in the licensing agreement and then click Install. Click Cancel, and then click Yes to confirm that you want to cancel the installation. The Install button is not available until you accept the license agreement. 5 Optional: In the exit dialog window, ensure that the check box beside Launch SAS Manager after installation. is selected. This step runs the SAS Manager and makes SAS functional. 6 Click Finish. --End-- Upgrading SAS Upgrade SAS to install a newer version of the software on the IBM Sametime Server. Prerequisites Download the SAS Installer package. Ensure that SAS is installed. Ensure that the volume, on which SAS is installed, contains a minimum of 500 MB of free space. Procedure steps Step Action 1 Run the SAS Installer package. 2 On the Welcome window, click Next. 3 Read the Nortel License Agreement. 4 Choose whether to proceed.

24 SAS installation Choose to Print the license agreement. Accept the license agreement and proceed. Cancel the installation. Do this Click Print. Select the check box beside I accept the terms in the licensing agreement and then click Install. Click Cancel, and then click Yes to confirm that you want to cancel the installation. The Install button is not available until you accept the license agreement. 5 Optional: In the exit dialog window, ensure that the check box beside Launch SAS Manager after installation. is selected. This step runs the SAS Manager and makes SAS functional. 6 Click Finish. Reinstalling SAS Add or Remove Programs Reinstall SAS to repair the installation by replacing missing or corrupt files, shortcuts, and registry entries. Prerequisites Ensure that you have the installer package. Ensure that SAS is installed. Ensure that the volume, on which SAS is installed, contains a minimum of 500 MB of free space. Procedure steps Step Action 1 Open the Windows Control Panel. 2 From Control Panel, open Add or Remove Programs. 3 From the list of installed programs, select Nortel ACE SAS Version <x.x.x>. The x.x.x is the version number. 4 Click Click here for support information. 5 Click Repair. --End--

25 SAS installation Job aid: The following figure illustrates how to start the repair process from the Add or Remove Programs utility. Add or Remove Programs Support Info Reinstalling SAS SAS Installer Reinstall SAS to repair the installation by replacing missing or corrupt files, shortcuts, and registry entries. Prerequisites Ensure that SAS is installed. Ensure that the volume, in which SAS is installed, contains a minimum of 500 MB of free space.

26 SAS installation Procedure steps Step Action 1 Run the SAS Installer package. 2 Click Repair. 3 To confirm that you want to reinstall SAS, click Repair. 4 On the exit window, click Finish. --End-- Job aid: The following screen shot shows the installation package Repair option. Installation package Repair option

27 SAS installation Uninstalling SAS Add or Remove Programs Uninstall SAS to remove it from the IBM Sametime Server, after it is no longer required. Prerequisites SAS is installed. The volume in which IBM Domino/Sametime is installed, contains a minimum of 500 MB of free space. Procedure steps Step Action 1 Open the Windows Control Panel. 2 From Control Panel, open Add or Remove Programs. 3 From the list of installed programs, select Nortel ACE SAS Version <x.x.x>, and click Remove. The x.x.x is the version number. Attention: In the event of a fatal error during the removal process, a popup window reports "Fatal error during installation". The error triggers a rollback, which restores the system to the original state. --End-- Uninstalling SAS SAS Installer Uninstall SAS to remove it from the IBM Sametime Server, after it is no longer required. Prerequisites SAS is installed. The volume in which IBM Domino/Sametime is installed, contains a minimum of 500 MB of free space.

28 SAS installation Procedure steps Step Action 1 Run the SAS Installer package. 2 Click Remove. 3 To confirm that you want to uninstall SAS, click Remove. 4 On the exit window, click Finish. --End--

29 Sametime Server and directory commissioning You must perform several configuration tasks to commission the Sametime Server and directory. Prerequisites for Sametime Server and directory commissioning Ensure that IBM Domino Server, IBM Sametime Server, and Nortel ACE SAS are installed. Sametime Server and directory commissioning tasks Complete the following tasks to commission the Sametime Server and directory. To navigate to each task, see Navigation for Sametime Server and directory commissioning tasks (page 30).

30 Sametime Server and directory commissioning Sametime Server and directory commissioning tasks Navigation for Sametime Server and directory commissioning tasks Configuring the user default office telephony device (page 31) Creating Sametime policy groups with telephony feature enabled (page 32) Assigning users and user groups to Sametime telephony policy groups (page 35) Configuring user business card information (page 36) Disabling voice chat (page 38)

31 Sametime Server and directory commissioning Configuring the user default office telephony device Configure users default office telephone devices in the Domino directory or LDAP server (if applicable), to make this information available to the Sametime application. Prerequisites Be familiar with dialing plan considerations. For more information, see Dialing plan for telephony service (page 8). Ensure that the deployment uses Domino directory. Attention: Deployments that use LDAP require comparable configuration. Detailed steps depend on the user interface provided by the LDAP directory in use. In SAS Manager, the Telephone Attribute identifies which LDAP directory attribute stores the user's default office telephone device. Procedure steps Step Action 1 To start the Sametime Administration console, open a Web browser and enter the following URL: You must specify the fully qualified domain name (FQDN) for the Sametime Server in the browser address bar. 2 Log on as an administrative user. 3 In the top navigation pane, click People & Groups. 4 In the left navigation pane, expand the Domino Directory. 5 Expand People. 6 Click by Organization. 7 In the Directory pane, click the corresponding link for the user. 8 Click Edit Person tab. 9 Select the Work/Home tab. 10 Select the Work tab.

32 Sametime Server and directory commissioning 11 In the Office phone box, type the number for the default office phone, in the appropriate format. 12 To save the changes, click Save & Close. --End-- Creating Sametime policy groups with telephony feature enabled By default, telephony policy is disabled. To permit the use of telephony features, such as Click-to-call and telephony presence, you must enable telephony policy for the users. Nortel recommends that you create a separate policy group or groups, for telephony. You must enable telephony policy for each client (standalone Sametime Connect client and Sametime Connect client integrated with Lotus Notes). Prerequisites The deployment uses Domino directory. Procedure steps If the deployment uses an LDAP directory, comparable configuration is required. Use the data to identify which users are telephony enabled. Detailed steps depend on the user interface provided by the LDAP directory in use. In SAS Manager, the Telephony Search Filter identifies the search filter to use to identify the users with telephony enabled. Step Action 1 To start the Sametime Administration console, open a Web browser and enter the URL: You must specify the fully qualified domain name (FQDN) for the Sametime Server in the browser address bar. 2 Log on as an administrative user. 3 In the navigation pane, click Administer the Server. 4 In the navigation pane, click Policies. 5 On the Policies page, click New. 6 In the Name box, type SAS Policies.

33 Sametime Server and directory commissioning 7 In the Community Services section, in the Allow telephony row, select the option for Contact lists and instant messaging only. 8 For Sametime Connect only configuration, go to Step For Lotus Notes integrated with Sametime Connect only: In the Integrated Sametime Connect section, for the Allow all Sametime Connect features to be used with integrated clients policy, select the Yes check box. 10 To save the changes, click OK. 11 In the navigation pane, click Configuration, Meeting Services. 12 Ensure that the Allow people to schedule a telephone conference call for a web conference. A telephony service provider is required. check box is selected. You must restart the server for the changes to take effect. --End-- Job aid: The following figures show the enabled telephony policy for both the Sametime Connect client, and the Lotus Notes integrated Sametime Connect client. Telephony policy for Sametime Connect Client

34 Sametime Server and directory commissioning Telephony policy for integrated clients

35 Sametime Server and directory commissioning Assigning users and user groups to Sametime telephony policy groups After you create telephony policies, which have telephony features enabled, you can add either individual users or user groups to the policy group. Newly added users, user groups, or policy changes take effect after system reboot or based on the following refresh intervals (defined in Community Services): Directory refresh interval (minutes): Group policy refresh interval. Configuration refresh interval (minutes): User rules assignment refresh interval. Prerequisites Ensure that you have created the telephony policies. Ensure that the deployment uses the Domino directory. Procedure steps Step Action 1 To start the Sametime Administration console, open a Web browser and enter the following URL: You must specify the fully qualified domain name (FQDN) for the Sametime Server in the browser address bar. 2 Log on as an administrative user. 3 In the navigation pane, click Administer the Server. 4 In the navigation pane, click Policies. 5 On the Policies page, select the policy to which you want to assign users (for example, SAS Policies). 6 Click Assign Users. 7 In the Directory pane, from the Directory menu, select the directory. 8 In the User pane, select a user, and then click Add. 9 To save the changes, click OK. --End-- Procedure job aid The following figure shows a selected telephony policy and the Assign Users button.

36 Assign users Sametime Server and directory commissioning Configuring user business card information Configure the information that appears on a user s business card to use the details from the directory. Prerequisites Ensure that each user's default office telephone device field is correctly mapped to the corresponding Domino or LDAP directory attribute. Procedure steps Step Action 1 To start the Sametime Administration console, open a Web browser and enter the following URL: You must specify the fully qualified domain name (FQDN) for the Sametime Server in the browser address bar. 2 Log on as an administrative user. 3 In the navigation pane, click Administer the Server. 4 In the navigation pane, expand Configuration and then click Business Card Setup. 5 From the Select list, select an attribute, which you want to appear on the user s business card, and then click Add >>. 6 From the Selected list, select any attribute, which you do not want to appear on the user s business card, and then click << Remove.

37 Sametime Server and directory commissioning 7 Repeat Step 5 and Step 6 until the Selected list contains only the attributes that you want to appear on the user s business card. Attention: You must include the Telephone attribute in the list of selected attributes. 8 In the Attribute value column, type the corresponding directory attribute for each of the attributes that appear in the Selected list. Attention: For Domino Directory, the Telephone attribute must be OfficePhoneNumber. For LDAP, the Telephone attribute must be the same value as the Telephone Attribute configured in SAS Manager. 9 To save the changes, click Update. --End-- Procedure job aid The following figure shows an example of business card configuration for a user, with mapping to attribute values in the Domino directory. The Telephone attribute must be selected and mapped to OfficePhoneNumber in the Domino directory. If you use an external LDAP server, you must map the Telephone attribute to the corresponding LDAP directory attribute. For detailed information about how to configure and check business card configuration in Domino directory or an external LDAP server, see the Sametime Server Installation and Administration Guide.

38 Sametime Server and directory commissioning Business card configuration Disabling voice chat Voice chat is a peer-to-peer chat utility that enables computer to computer calling only. The Call feature enables calls to any phone. In order to prevent the confusion of getting voice chat mistaken for CS 1000 calls, you can disable voice chat on the Sametime Server. Procedure steps Step Action 1 To start the Sametime Administration console, open a Web browser and enter the URL: You must specify the fully qualified domain name (FQDN) for the Sametime Server in the browser address bar. 2 Log on as an administrative user. 3 In the left pane, select Policies.

39 Sametime Server and directory commissioning 4 In the right pane, under Sametime default polices, clear the Allow client-toclient voice call check box. Voice chat is no longer available in the client. --End-- Configuring Meeting Services to enable Sametime telephony services Enable Sametime telephony services for Meeting Services to have the phone icon appear in the menu bar for users. Procedure steps Step Action 1 To start the Sametime Administration console, open a Web browser and enter the URL: You must specify the fully qualified domain name (FQDN) for the Sametime Server in the browser address bar. 2 Log on as an administrative user. 3 In the left pane, select Configuration, Meeting Services. 4 In the right pane, select the Allow people to schedule a telephone conference call for a web conference check box. --End-- Creating a Notes policy group Create a Notes policy group to assign to users of telephony services. If Notes policies already exist, you can reuse the existing policies, or create new policies. Prerequisites You have access to the Domino Administrator Client.

40 Sametime Server and directory commissioning Procedure steps Step Action 1 Log on to the Domino Administrator Client. 2 In the navigation pane, click Domino Directories. 3 In the navigation pane, expand <yourdomain> Directory. <yourdomain> represents the actual name of your Domain. 4 From the directory tree for your domain, select Policies, and then click Add Policy. 5 Define the new policy namespace and description. 6 From the directory tree for your domain, select People. 7 From the list of users in the directory, select a telephony services user. 8 Right-click on the selected user and choose Assign Policy. 9 From the Policy list on the Assign Policy Option dialog, select the name of the new policy. 10 Open the user s profile to verify that the correct policy (for telephony services users) is assigned. --End-- Procedure job aid The following figure shows a newly-created policy called GroupA (description: Telephony Enabled User Group). Domino policy group The following graphic shows the GroupA policy group assigned to a user s profile.

41 Sametime Server and directory commissioning Domino policy group assigned to a user

42 CS 1000 commissioning This chapter contains information about CS 1000 configuration tasks for Nortel Agile Communication Environment (ACE) Server Agent for Sametime (SAS) deployments. Prerequisites for CS 1000 commissioning Ensure that the deployment includes CS 1000 Release 6.0. Ensure that SIP CTI configuration, including AML, is complete. CS 1000 commissioning tasks Complete the following tasks to commission the CS 1000 for ACE SAS. To locate more information about any of the tasks, see Navigation for CS 1000 commissioning (page 43).

43 CS 1000 commissioning CS 1000 commissioning Navigation for CS 1000 commissioning Configure SAS as a gateway endpoint on the NRS. Perform this task only if the deployment uses the Network Routing Service (NRS). SAS supports only static endpoints. For more information about how to configure a gateway endpoint on the NRS, see the CS 1000 documentation suite. Configure SAS as the Proxy Server in the Virtual Trunk Gateway Perform this task only if SAS connects directly to the CS For more information about how to use Unified Configuration Management Element Manager (UCM - EM) to complete this task, see the CS 1000 documentation suite.

44 SAS Manager commissioning This chapter describes how to configure SAS. Prerequisites for SAS Manager commissioning Ensure that ACE SAS is installed. Navigation for SAS Manager commissioning Configuring SAS without NRS (NRS mode none (Direct)) (page 44) Configuring SAS with NRS (NRS mode SPS) (page 48) Configuring Trace (page 51) Configuring SAS without NRS (NRS mode none (Direct)) Configure SAS Direct mode for a deployment without NRS. Procedure steps Step Action 1 Open the SAS Manager. 2 Select the Configuration tab. 3 In the SAS Mode section, select the Direct Connect option. 4 In the CS 1000 section, from the NRS Mode list, select None (Direct). 5 Type the values for the CS 1000 SIP GW IP Address, Phone Context, and UDP Access Code parameters. 6 In the SIP section, for SIP Transport, select a transport option. 7 In the SIP Port box, type the number for the SIP port. 8 In the Directory section, from the Directory Type list, select the directory type (Domino or LDAP).

45 SAS Manager commissioning 9 If you selected Domino in Step 8, go to Step If you selected LDAP in Step 8, click LDAP Configuration. 11 In the LDAP Configuration window, configure the parameters for LDAP. 12 Click OK, and then go to Step In the Domino User Policy box, type the names of the user policies that have telephony features enabled. Example: PolicyGroups=/GroupA,/GroupB 14 To save your changes, click Apply. For all configuration changes to take effect, you must reboot the Sametime Server. --End-- Variable definitions Variable NRS Mode CS 1000 SIP GW IP Address CS 1000 SIP Service Domain Definition NRS (Network Routing Service) mode supports a Direct connection with the CS 1000 (no NRS) or SPS. The node IP address of the CS 1000 SIP Gateway. The SIP service domain of the SIP Gateway in SIP URI format. Example: interop.com Phone Context SAS uses phone context to qualify a Sametime user's telephone number when sending requests to the CS If you use the CDP numbering plan, specify the corresponding CDP phone context. If you use the UDP numbering plan, specify the corresponding UDP phone context. The phone context must match the corresponding phone context that is configured and used on the CS Example: cdp.udp UDP Access Code SIP Transport The access code prepended to dialed numbers, for the UDP dialing plan. TCP and UDP are supported SIP transport methods. SIP Port The default SIP port is (1 of 3)

46 SAS Manager commissioning Variable Directory Type Domino User Policy Address (FQDN) Port Definition LDAP or Domino directory. This parameter is available only after you select Domino as the directory type. It specifies which Domino Directory User Policies have the telephony feature. Only users who are assigned to these policies can registered with the CS 1000 for Click-to-call and telephony presence. Configure the names of the policies in SAS Manager. The LDAP server address. You can specify either the IP address or Fully Qualified Domain Name (FQDN). The configured access port on the LDAP server. Valid port number range: Default: 389 (non-ssl), 636 (SSL) Login Username Login Password Telephone Attribute The log on user name that SAS uses to log into the LDAP server. Example: cn=administrator,cn=users,dc=yourcompany, dc=com The Login Password that SAS uses with the LDAP Login DN. The name of the attribute that stores a user's default office telephone device in the LDAP directory. Default: telephonenumber Telephony Search Filter The search filter for finding all telephony enabled users from the LDAP directory (no default). These are the users who can be registered with the CS Example: (&(objectclass=person)(your_telephonyflag=tru E)) Base Search DN The LDAP server base search DN. Example: dc=yourcompany,dc=com Enable Indicates whether to use SSL for LDAP access. If selected, by default the LDAP port (in the Server Port box) is port 639. If cleared, the port is 389. You can modify the port number manually after you enable or disable SSL. (2 of 3)

47 SAS Manager commissioning Variable SSL Keystore Path SSL Keystore Password Use Cache Sync Time Definition The location (directory) of the key store file that contains the SSL Certificates. Specifies the password SAS uses to access the key store file. Password characters appear as (*) characters. SAS looks up telephone numbers in the directory to support Click-to-call and presence. If enabled, SAS caches data to speed up user lookup. Select to enable caching. The time of day at which the cache synchronizes with the directory. (3 of 3)

48 SAS Manager commissioning Configuring SAS with NRS (NRS mode SPS) Configure SAS to use a SIP Proxy Server (SPS). Procedure steps Step Action 1 Open the SAS Manager. 2 Select the Configuration tab. 3 In the SAS Mode section, select the Direct Connect option. 4 In the CS 1000 section, from the NRS Mode list, select SPS. 5 In the corresponding boxes, type the values for the Primary NRS IP Address, and the Secondary NRS IP Address parameters. 6 From the SPS Mode list, select an SPS mode. 7 In the corresponding boxes, type the values for the SAS SIP Endpoint Address, Phone Context, and the UDP Access Code parameters. 8 In the SIP section, for SIP Transport, select a transport option. 9 In the SIP Port box, type the number for the SIP port. 10 In the Directory section, from the Directory Type list, select the directory type (Domino or LDAP). 11 If you selected Domino in Step 8, go to Step If you selected LDAP in Step 8, click LDAP Configuration. 13 In the LDAP Configuration window, configure the parameters for LDAP. 14 Click OK and go to Step In the Domino User Policy box, type the names of the user policies that have telephony features enabled. Example: PolicyGroups=/GroupA,/GroupB 16 To save your changes, click Apply. For all of the configuration changes to take effect, you must reboot the Sametime Server. --End--

49 SAS Manager commissioning Variable definitions Variable NRS Mode Primary NRS IP Address Secondary NRS IP Address SPS Mode SAS SIP Endpoint Address Definition NRS (Network Routing Service) mode supports Direct connection with the CS 1000 (no NRS) or SPS. The IP Address of the primary NRS server. Message flows between SAS and CS 1000 can go through NRS SPS. The IP address of the secondary NRS server, which provides redundancy. The SPS modes are: Proxy All SIP Messages, Proxy SIP messages and redirect SIP CTI messages, or Redirect all messages. You can configure SAS in the Network Routing Service (SPS) as a gateway endpoint. Configure the endpoint address in SIP URI format in SAS Manager. Example: SASServiceProvider@YourCompany.com, where SASServiceProvider is the static SIP endpoint name configured for SAS on the NRS, and YourCompany.com is there SIP service domain configured on the NRS. Phone Context SAS uses phone context to qualify a Sametime user's telephone number when sending requests to the CS If you use the CDP numbering plan, specify the corresponding CDP phone context. If you use the UDP numbering plan, specify the corresponding UDP phone context. The phone context must match the corresponding phone context that is configured and used on the CS Example: cdp.udp UDP Access Code SIP Transport The access code prepended to dialed numbers, for the UDP dialing plan. TCP and UDP are supported SIP transport methods. SIP Port The default SIP port is Directory Type LDAP or Domino directory. (1 of 3)

50 SAS Manager commissioning Variable Domino User Policy Address (FQDN) Port Definition This parameter is available only after you select Domino as the directory type. It specifies which Domino Directory User Policies have the telephony feature. Only users who are assigned to these policies can registered with the CS 1000 for Click-to-call and telephony presence. Configure the names of the policies in SAS Manager. The LDAP server address. You can specify either the IP address or Fully Qualified Domain Name (FQDN). The configured access port on the LDAP server. Valid port number range: Default: 389 (non-ssl), 636 (SSL) Login Username Login Password Telephone Attribute The log on user name that SAS uses to log into the LDAP server. Example: cn=administrator,cn=users,dc=yourcompany, dc=com The Login Password that SAS uses with the LDAP Login DN. The name of the attribute that stores a user's default office telephone device in the LDAP directory. Default: telephonenumber Telephony Search Filter The search filter for finding all telephony enabled users from the LDAP directory (no default). These are the users who can be registered with the CS Example: (&(objectclass=person)(your_telephonyflag=tru E)) Base Search DN The LDAP server base search DN. Example: dc=yourcompany,dc=com Enable Indicates whether to use SSL for LDAP access. If selected, by default the LDAP port (in the Server Port box) is port 639. If cleared, the port is 389. You can modify the port number manually after you enable or disable SSL. (2 of 3)

51 SAS Manager commissioning Variable SSL Keystore Path SSL Keystore Password Use Cache Sync Time Definition The location (directory) of the key store file that contains the SSL Certificates. Specifies the password SAS uses to access the key store file. Password characters appear as (*) characters. SAS looks up telephone numbers in the directory to support Click-to-call and presence. If enabled, SAS caches data to speed up user lookup. Select to enable caching. The time of day at which the cache synchronizes with the directory. (3 of 3) Configuring Trace Perform the following procedure to customize the way SAS Manager collects and reports traces in the trace log files, for Direct Mode. Procedure steps Step Action 1 Open the SAS Manager. 2 Select the Trace tab. 3 In the Type section, click to select or to clear the SIP, Directory, and Debug check boxes, as required. 4 Optional: In the Dialable Number (DN) Filter box, type the DN, for which you want to capture trace data. 5 From the Number of Files (1 5) list, select the number of trace files to use for logging trace data. 6 From the File Size (5 20MB)list, select the size for each trace file. 7 Optional: To view a trace file, click Open Trace and then select a file to open. 8 To save your changes, click Apply.

52 SAS Manager commissioning Variable definitions Variable SIP Directory Debug Dialable Number (DN) Filter Number of Files (1 5) File Size (5 20MB) Definition If selected, captures all SIP messaging. If selected, captures all Domino or LDAP directory messaging. If selected, captures all SAS Debug-level logs. Refines the trace log to capture trace messages only for a specific DN. Specifies the number of trace files that SAS uses to store trace log data. After the last file reaches the maximum size, SAS continues to log data by overwriting the existing files, starting with the first file (SAS_trace_0_1.log). Specifies the maximum size of each trace log file in megabytes. After a file reaches the maximum size, SAS creates a new file to continue logging trace data.

53 Plug-in updates management This chapter describes how to configure the Sametime Server to manage updates for Agile Communication Environment (ACE) Server Agent for Sametime (SAS) plug-ins. Prerequisites Install SAS. See SAS installation (page 22). The SAS Installer installs the required Presence Plug-in files onto the Sametime Server. Commission the Sametime Server and directory. See Sametime Server and directory commissioning (page 29). Commission CS See CS 1000 signaling and Call Server configuration for TR/87 (page 18). Configure NRS for SAS. See Network Routing Service configuration (page 19). Commission SAS Manager. See SAS Manager commissioning (page 44). Navigation Configuring the Sametime Server to automatically push plug-ins (page 53) Locating the URL for the site that contains the Nortel plug-ins (page 55) Configuring the Sametime Server to automatically push plug-ins PrerequisitesPrerequisites You know the URL for the site that contains the Nortel plug-in files. You can use the procedure Locating the URL for the site that contains the Nortel plug-ins (page 55) to locate the URL.

54 Plug-in updates management Configure the Sametime Server to automatically upload (push) updated Sametime plug-ins to Sametime Connect clients. Procedure steps Step Action 1 To start the Sametime Administration console, in the address bar of your Web browser, enter the following: _server>/stcenter.nsf You must enter the fully qualified domain name (FQDN) for the Sametime Server. 2 In the navigation pane, click Administer the server. 3 In the navigation pane, click Policies. 4 On the Policies page, select the policy to use for SAS (for example, SAS Policies). 5 In the Sametime update site URL, type the URL for the site, which contains the Nortel plug-ins. 6 To save your changes, click OK. 7 To return to the main page, click the Sametime Lotus icon. 8 Log off from the Administration Console. 9 Restart the Sametime Server. --End-- Variable definitions Variable <Sametime _server> <sas_update_site> Definition The name of the server that hosts the update site The name of the update site.

55 Plug-in updates management Locating the URL for the site that contains the Nortel plug-ins The Nortel presence plug-ins are installed automatically as part of the SAS install process. You can use SAS Manager to locate the URL for the site that contains the plug-ins. Procedure steps Step Action 1 Open SAS Manager. 2 From the Help menu, choose About SAS Manager. 3 Click Presence Plug-in. --End--

56 Backup and restore This chapter provides the procedures that you require to back up and restore data for Nortel Agile Communication Environment (ACE) Server Agent for Sametime (SAS). Navigation for backup and restore Backing up SAS configuration data (page 56) Restoring SAS configuration data (page 57) Backing up SAS configuration data You can back up the SAS configuration data as part of your backup strategy. Procedure steps Step Action 1 Open the SAS Manager. 2 Point to Action, and then click Backup. 3 In the SAS Backup File dialog, browse to the location where you want to save the backup file. 4 In the File name box, type a name for the file. 5 Click Save. --End-- Job aid: The following images illustrate how to backup SAS configuration data.

57 Backup and restore SAS backup Save the SAS backup file Restoring SAS configuration data You can restore SAS configuration data as part of your recovery strategy. Prerequisitesfor restoring SAS configuration data Ensure that a backup file that contains previously backed up data exists.

58 Backup and restore Procedure steps Step Action 1 Open the SAS Manager. 2 Point to Action, and then click Restore. 3 In the SAS Backup File dialog, browse to the location of the backup file, and then select the file. 4 Click Open. --End--

59 Maintenance This chapter provides information about Agile Communication Environment (ACE) Server Agent for Sametime (SAS) maintenance. Navigation Trace files management (page 59) Monitor status (page 59) Events (page 61) Trace files management If you change the Trace configuration to reduce the number of files that SAS uses to capture trace data, SAS does not automatically remove the existing files. You can manually delete the files. For example, if you change the number of files from five to three, you can delete the SAS_trace_0_4.log and SAS_trace_0_5 log files. Monitor status Use SAS Manager to check the active configuration for SAS, and to monitor the status of SAS. After configuration, the SAS Manger Status tab displays the status of the SAS Component and various other network components. The status of the following components appears on the SAS Status tab: SAS Mode SAS State NRS Mode Primary and Secondary NRS For an example of the display, see the figure SAS Status tab (page 60). For more information about the valid status values, see the table Valid status values (page 60).

60 Maintenance SAS Status tab Valid status values Component SAS Mode Values Direct Connect Unknown SAS State Started Stopped Starting NRS Mode SPS None (direct) Primary NRS Healthy Standby Unknown Not Configured Not Responding Secondary NRS Healthy Standby Unknown Not Configured