Introduction   This document describes the configuration steps to configure backup device in Unity connection 9.x     The Disaster Recovery System (DRS), which can be invoked from, provides full data backup and restore capabilities. The Disaster Recovery System allows you to perform regularly scheduled automatic or user-invoked data backups.     DRS restores its own settings (backup device settings and schedule settings) as part of the platform backup/restore. DRS backs up and restores drfDevice.xml and drfSchedule.xml files. When the server is restored with these files, you do not need to reconfigure DRS backup device and schedule.       The Disaster Recovery System includes the following capabilities:     •     A user interface for performing backup and restore tasks.     •     A distributed system architecture for performing backup and restore functions.     •     Scheduled backups.     •     Archive backups to a physical tape drive or remote SFTP server.     The Disaster Recovery System contains two key functions, Master Agent (MA) and Local Agent (LA). The Master Agent coordinates backup and restore activity with Local Agents.       Managing Backup Devices     Before using the Disaster Recovery System, you must configure the locations where you want the backup files to be stored. You can configure up to 10 backup devices.       Perform the following steps to configure backup devices.     Step 1   In Cisco Unity Connection Administration, in the Navigation list, click Disaster Recovery System, and click Go.        Note:-   When a Cisco Unity Connection cluster is configured, we recommend that you back up the publisher server and, optionally, the subscriber      server.   The Disaster Recovery System Logon window displays.     Step 2   Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified Communications Operating System Administration.     Step 3   Navigate to Backup > Backup Device. The Backup Device List window displays.     Step 4   To configure a new backup device, click Add New.     Step 5   To edit a backup device, select it in the Backup Device list. Then, click Edit Selected.   The Backup Device window displays.     Step 6   Enter the backup device name in the Backup device name field.        Note:-  The backup device name may contain only alphanumeric characters, spaces ( ), dashes and underscores (_). Do not use any other      characters.     Step 7   Choose one of the following backup devices and enter the appropriate field values in the Select Destination area:     •     Tape Device- Stores the backup file on a locally attached tape drive. Choose the appropriate tape device from the list.          Note:- Be aware that if you are logged in through a VMware virtual machine, you cannot back up on a tape. This is because the tape device option        is disabled for VMware users.     •     Network Directory-Stores the backup file on a network drive that is accessed through an SFTP connection.Enter the following required information:          –     Server name: Name or IP address of the network server          –     Path name: Path name for the directory where you want to store the backup file          –     User name: Valid username for an account on the remote system          –     Password: Valid password for the account on the remote system          –     Number of backups to store on Network Directory: The number of backups to store on this network directory.   Note:-  You must have access to an SFTP server to configure a network storage location. The SFTP path must exist prior to the backup. The account that is used to access the SFTP server must have write permission for the selected path.     Step 8   To update these settings, click Save.     Note:-  After you click the Save button, the DRS Master Agent validates the selected backup device. If the user name, password, server name, or directory path is invalid, the save will fail.     Step 9   To delete a backup device, select it in the Backup Device list. Then, click Delete Selected.   Note:-  You cannot delete a backup device that is configured as the backup device in a backup schedule.   Related Links Unity Connection Disaster Recovery ... View more

    Introduction   This document describes the reasons of Agent not ready with the reason code.     Agent Not Ready Reason codes     There are reports that show the codes agents select when entering Not Ready state, that calculate the percentage of time spent in the Not Ready state, and that show specific Not Ready reasons based on the time range you specify. These reports help you identify whether agents are taking the appropriate number of breaks and whether their breaks are the appropriate length.Some reports display both the text of the reason code (if configured) and the corresponding number. For example, if an agent enters Not Ready state and selects "Break" as the reason code,and if you have configured text for this code in Configuration Manager, reports display "Break [1]". Other reports display the numeric Not Ready reason code only.If an agent's total login session is not included in the specified time range (for example, the agent was still logged in at the end of the time range), an asterisk (*) appears next to the agent's name in the report to indicate that data for that agent is not complete for the range. For Unified CC, in addition to Not Ready reason codes that you define, there are predefined Not Ready reason codes for situations in which the agent is made Not Ready automatically by the software. The following table describes these predefined Not Ready reason codes.   Predefined Not Ready Code Description   Reason Code Description 50001 The CTI OS client disconnected, logging the agent out.Note: This reason code is converted to a 50002, so 50001 does not display in the agent log out records. 50002 A CTI OS component failed, causing the agent to be logged out. This could be due to closing the agent desktop application, heartbeat time out, a CTI OS Server failure, or a CTI OS failure. 50003 Agent was logged out because the Unified CM reported the device out of service. 50004 Agent was logged out due to agent inactivity as configured in agent desk settings. 50005 For a Unified CCE deployment where the Multi Line Agent Control is enabled in the peripheral, and the Multi Line Agent Behavior is configured to impact agent state, the Agent will be set to not ready with this code while talking on a call on the Non ACD line. 50010 The agent did not receive multiple consecutive calls routed to him/her. The system makes the agent Not Ready automatically so that 50010 additional calls are not routed to the agent. By default, the number of consecutive calls missed before the agent is made Not Ready is 2. 50020 Agent was logged out when the agent's skill group dynamically changed on the Administration & Data Server. 50030 If an agent is logged in to a dynamic device target that is using the same dialed number (DN) as the PG static device target, the agent is logged out. 50040 Mobile agent was logged out because the call failed. 50041 Mobile agent state changed to Not Ready because the call fails when the mobile agent's phone line rings busy. 50042 Mobile agent was logged out because the phone line disconnected while using nailed connection mode. 50041 The agent's state was changed to Not Ready because the call fails when the agent's phone line rings busy. 32767 The agent's state was changed to Not Ready because the agent did not answer a call and the call was redirected to a different agent or skill group. 20001 - applicable if you are using the Cisco Agent Desktop Places the agent in the Not Ready state first before forcefully logging them off. 20002 - applicable if you are using the Cisco Agent Desktop Forces the logout request; for example, when Agent A attempts to log in to Cisco Agent Desktop and Agent B is already logged in under that agent ID, Agent A is asked whether or not to force the login.   If Agent A answers yes, Agent B is logged out and Agent A is logged in. Reports would then show that Agent B logged out at a certain time with a reason code of 20002 (Agent B was forcibly logged out). 20003 - applicable if you are using the Cisco Agent Desktop Not Ready for logout.   If not already in the Logout state, request is made to place agent in the Not Ready state. Then logout request is made to log the agent out. Supervisor Not Ready This code is reserved. Supervisor Logout This code is reserved. -1 Agent reinitialized (used if peripheral restarts). -2 PG reset the agent, normally due to a PG failure. -3 An administrator modified the agent's extension while the agent was logged in.       By default, predefined Not Ready reason codes do not have associated textual reason codes.They appear as numbers in reports. If you want to see a textual code for these Not Ready reason codes, enter the predefined Not Ready reason code into the Reason Code List tool with the related text. For example, you might want to label the 32767 Not Ready reason code "Redirection on No Answer".   Note:   • To report on Not Ready reason codes, ensure that the reporting of agent event detail data is enabled on the PG with the Cisco Unified CM peripheral. This is enabled by default.         Related Links Configure Auto Logout for CAD       ... View more

    Introduction   This document describes the reasons of Agent logout with the reason code.     Agent Logout Reason codes     Agent Logout Reason codes are defined in the agent desktop software and appear in historical reports as their numeric equivalent, with no text code. For example, if reason code 1 equals "end of shift" and the agent selects that reason for logging out, the report displays "1".In addition to the codes configured at the desktop, some codes are generated automatically whenthe agent is logged out by the software. The table below describes these predefined Logout Reason codes, which are available for both Unified ICM and Unified CC.   Predefined Logout Reason Code Description   Reason Code Description -1 The agent reinitialized due to peripheral restart. -2  The PG reset the agent, normally due to a PG failure. -3  An administrator modified the agent's extension while the agent was logged in. 50002                         A CTI OS component failed, causing the agent to be logged out. This could be due to closing the agent   desktop application,heartbeat time out, a CTI OS Server failure, or a CTI OS failure. 50003                                The agent was logged out because the ACD reported the agent's device as out of service. 50004                        The agent was logged out due to agent inactivity as configured in agent desk settings. 50020                              The agent was logged out when his/her skill group assignment dynamically changed. 50030                              The agent was logged out when his or her skill group assignment dynamically changed on the           administration & DataServer.     50040                         The mobile agent was logged out because the call failed. 50042                              The mobile agent was logged out because the phone line disconnected when using nailed connection mode. 20001 -applicable if   you are using the Cisco Agent Desktop   The agent's state was changed to NOT READY. 20002 - applicable if           Cisco Agent Desktop              Forces the logout request; for example, when Agent A attempts to login to Cisco Agent Desktop and Agent B is already logged in under that agent ID, Agent A is asked whether or not to force the login.If Agent A  answers yes, Agent B is logged out and Agent A is logged in. Reports would then show that Agent B logged  out at a certain time with a reason code of 20002 (Agent B was forcibly logged out).Note: Cisco Unified Mobile Agent is the only exception, where CAD will not allow you to log out a login name/ID that is  already in use.     20003 - applicable if           you are using the Cisco Agent Desktop Not Ready for logout.               Reports that show Agent Logout Reason Codes   These are some reports that contain information on Agent Logout reason codes:   • Unified IC Agent Real Time All Fields   • Unified IC Agent Not Ready Detail   • WebView agent03 (Agent Media Logout Status Report)   • WebView agteam03 (Agent Team Media Logout Status Report)   • WebView agtper03 (Agent Peripheral Media Logout Status Report)       Related Links Configure Auto Logout for CAD       ... View more

    Introduction   This document describes the various licensing options in Cisco Unified Communication 9.0   Cisco offers a variety of software licensing options to meet customer needs, regardless of the business size, the way employees work, and the tools they need. Cisco Unified Communications 9.0 licensing includes:-     • Cisco Unified Workspace Licensing (UWL): Cisco Unified Workspace Licensing provides the most popular bundles of Cisco Collaboration applications and services in a cost-effective, simple package. It includes soft clients, applications server software, and licensing on a per-user basis. Cisco Unified Communications Software Subscription (UCSS) is required to enable access to major software upgrades.     • Cisco User Connect Licensing (UCL): A per-user based license for individual Cisco Unified Communications applications, that includes the applications server software, user licensing, and a soft client. Depending the type of device and number of devices that you require, User Connect Licensing is available in Essential, Basic, Enhanced, and Enhanced Plus versions. Cisco Unified Communications Software Subscription (UCSS) is recommended to enable access to major software upgrades.     Cisco Unified Workspace Licensing     With Cisco Unified Workspace Licensing, your organization can flexibly meet business needs by procuring a broad range of Cisco Collaboration applications and services on a per-user basis at a "better together" bundled price. It provides the opportunity to deliver a consistent set of Cisco Collaboration applications to a larger portion of your users, helping organizations maximize the potential of collaboration.   Cisco Unified Workspace Licensing is available in two primary editions:-   Standard Edition: Built on the reliable Cisco Unified Communications Manager platform, this edition includes call control, voice messaging, and unified clients. Instant messaging and presence are also included and may be deployed as a 1-year subscription in the cloud or as a perpetual license on premises. Business Edition: Refers to Standard Edition on Cisco Unified Communications Manager Business Edition 6000 and is equivalent in functionality to Cisco Unified Workspace Licensing Standard Edition. Professional Edition: This edition includes all features in the Standard Edition plus WebEx Meetings, the WebEx Social Enterprise Collaboration platform, and contact center capabilities. You can deploy each WebEx solution as either a 1-year subscription in the cloud or as a perpetual license on premises.     Cisco Unified Workspace Licensing can help you:-     Improve the value of a unified workspace:     – Offers multiple workspace applications at a more affordable initial cost   – Lowers total cost of ownership (TCO) through a consistent per-user price point that includes: server software, license and soft clients   – Enables organizations to easily and cost-effectively adapt to changing employee or end-user needs     Maximize the potential of collaboration:     – Provides a consistent set of applications across the organization to increase overall employee productivity   – Includes instant messaging and presence for the entire organization. Can be deployed as a 1-year subscription in the cloud or as a perpetual license on premises, further reducing implementation time and costs   – Allows you to deploy each WebEx solution in Professional Edition as either a 1-year subscription in the cloud or as a perpetual license on premises     Flexibly meet your business needs:     – Simplifies the way you acquire and manage licensing, service, and support   – Flexibly deploys applications to meet your evolving operational and business needs   – Offers an open platform that integrates with other line-of-business applications.   Cisco User Connect Licensing Cisco User Connect Licensing for Cisco Unified Communications Manager is available in the following options :     Essential UCL and Basic UCL: These are user-based licenses for individual Cisco Unified Communications products. Each includes applications server software and user licensing for a single device supported by the Essential UCL or Basic UCL level of functionality. These licenses also provide on-premise Instant Messaging clients and presence software for the entire organization.   Enhanced UCL and Enhanced Plus UCL: These are user-based licenses for individual Cisco Unified Communications products that support Cisco's entire portfolio of user devices and include the ability to use a soft phone on your desktop (Windows and Mac) and mobile devices. They each include a soft client, applications server software, and user licensing. Enhanced UCL includes unified communications applications for a single device, whereas Enhanced Plus allows for two devices. These licenses also provide on-premise Instant Messaging clients and presence software for the entire organization.     Cisco User Connect Licensing for Cisco Unity Connection is available in the following option:     Basic Messaging (Voicemail): The Basic Messaging license includes rights to one Cisco Unity Connection user. The user has advanced voicemail access Internet Message Access Protocol [IMAP], unified messaging, phone, and web) and voice recognition. (If you are using voice recognition, you must order SpeechConnect ports separately.)     Related Links   https://supportforums.cisco.com/message/3702587#3702587 Drive to 9 Community Tech-Talk-Simplified Cisco Unified Communications Manager 9.x Upgrade Procedures ... View more

      Introduction   This document describes the login issue of CUMA client which uses client configuration SOAP interface.         CUMA client which uses the Client Configuration SOAP interface of CUP is denied login.     Condition   This condition occurs after a fresh install or upgrade to Cisco Unified Presence Release 8.6.1.       Steps to resolve the error     During a maintenance widow, the Cisco Unified Presence Administrator must run the following commands from the command line interface of the publisher node:     run sql update soapclienttypes set versioncheckrequired='f' where clienttype='CUMCCLIENT'     To restart service on all nodes in the cluster including the publisher node, enter the following command:     utils service restart Cisco UP Client Profile Agent     Newly added users cannot login over soap following DB restart     Users who were newly assigned to the system, or who were assigned to a new node cannot login via CUPC.     On attempting to assign the user, an error shows in the EPASSoapxxxx.log file like:-     2010-01-19 12:00:08,638 FATAL [Thread-176] soap.TTLoginDbMgr - PrepareStatement failed 2010-01-19 12:00:08,638 FATAL [Thread-176] soap.TTLoginDbMgr - java.sql.SQLException: System or internal error java.sql.SQLException: System or internal error java.net.SocketException: Broken pipe   The service "A Cisco DB" was restarted, without the service "Cisco UP Client Profile Agent" being restarted.     Workaround for this issue   Restarting the "Cisco UP Client Profile Agent" should fix the problem. As most of the CUP services rely on the Database, it is not advisable to restart the "A Cisco DB" service. If the DB needs to be restarted, it is best to restart the entire server.     Related Links Troubleshooting CUPS               ... View more

      Introduction   Any Cisco Unified Mobility Advantage client which uses the Client Configuration SOAP interface of Cisco Unified Presence is denied login.     Condition   This condition occurs after a fresh install or upgrade to Cisco Unified Presence Release 8.6.1.       Steps to resolve the error     During a maintenance widow, the Cisco Unified Presence Administrator must run the following commands from the command line interface of the publisher node:     run sql update soapclienttypes set versioncheckrequired='f' where clienttype='CUMCCLIENT'     To restart service on all nodes in the cluster including the publisher node, enter the following command:     utils service restart Cisco UP Client Profile Agent     Newly added users cannot login over soap following DB restart     Users who were newly assigned to the system, or who were assigned to a new node cannot login via CUPC.     On attempting to assign the user, an error shows in the EPASSoapxxxx.log file like:-     2010-01-19 12:00:08,638 FATAL [Thread-176] soap.TTLoginDbMgr - PrepareStatement failed 2010-01-19 12:00:08,638 FATAL [Thread-176] soap.TTLoginDbMgr - java.sql.SQLException: System or internal error java.sql.SQLException: System or internal error java.net.SocketException: Broken pipe   The service "A Cisco DB" was restarted, without the service "Cisco UP Client Profile Agent" being restarted.     Workaround for this issue   Restarting the "Cisco UP Client Profile Agent" should fix the problem. As most of the CUP services rely on the Database, it is not advisable to restart the "A Cisco DB" service. If the DB needs to be restarted, it is best to restart the entire server.     Related Links Troubleshooting CUPS               ... View more

    Introduction   This document describes the issues with Phone View and steps to troubleshoot.The Phone View feature is supported only with Cisco Unified Communications Manager phone system integrations.The Phone View feature may not function correctly outside a firewall or through a VPN router.   The Phone View feature allows users to see search results on the LCD screens of their Cisco IP phones when they use the Find Message or the Display Message menu. When Phone View is enabled, Cisco Unity Connection users can search for the following types of voice messages:-   • All new messages • All messages • Messages from a particular user • Messages from all outside callers • Messages from a particular outside caller   Phone View works only with Cisco Unified Communications Manager phone systems, and only with certain Cisco IP phones.   Issue 1:- Application User Is Configured Incorrectly     The problem may be caused by the incorrect configuration of the application user on the Cisco Unified Communications Manager server.     To Verify the Configuration of the Application User follow the steps below:-     Step 1     In Cisco Unified Communications Manager Administration, on the User Management menu, click Application User.     Step 2      On the Find and List Application Users page, click Find.     Step 3      Click the user ID of the application user that is used by Phone View.     Step 4      On the Application User Configuration page, under Application User Information, click Edit Credential.     Step 5      On the Credential Configuration page, confirm that the following check boxes are checked:     User Must Change at Next Login Does Not Expire     Step 6      Click Save.     Step 7     In the Related Links box, click Back to User and click Go.     Step 8     On the Application User Configuration page, under Application User Information, in the Password field, reenter the password.     Step 9     In the Confirm Password field, reenter the password.     Step 10    Under Device Information, in the Controlled Devices field, confirm that the devices that are associated with the application user account are                correct.     Step 11    Click Save.     Step 12    On the System menu, click Enterprise Parameters.     Step 13    On the Enterprise Parameters Configuration page, under Phone URL Parameters, in the URL Authentication field, confirm that the URL is                correct.     Step 14   If you made any changes, click Save.     Issue 2:- User Phone Configuration Is Not Correct     One possible cause may be that the configuration on the user phone is not current. You can reboot the phone so that it reloads the configuration from the Cisco Unified CM server.     Another possible cause is that the user phone is not supported. See the "Requirements for Cisco Unity Connection Phone View" section of System Requirements for Cisco Unity Connection Release 7.x.     Issue 3:- Phone System Integration Is Configured Incorrectly     The problem may be caused by the incorrect configuration of the Cisco Unified CM phone system integration in Cisco Unity Connection Administration.     Do the following procedure to Verify the Configuration of the Cisco Unified Communications Manager Phone System Integration     Step 1      In Cisco Unity Connection Administration, expand Telephony Integrations, then click Phone System.     Step 2      On the Search Phone Systems page, click the name of the phone system.     Step 3      On the Phone System Basics page, under Phone View Settings, confirm that the Enable Phone View check box is checked.     Step 4      In the CTI Phone Access User Name field, confirm that the name of the application user in Cisco Unified CM Administration is correct.                    Note that the name of the application user is case-sensitive.     Step 5      In the CTI Phone Access Password field, reenter the password of the application user in Cisco Unified CM Administration.     Step 6      Click Save.     To Verify the Configuration of the User     Step 1      In Cisco Unity Connection Administration, expand Users, then click Users.     Step 2      On the Search Users page, click the name of the user.                     Note If the user does not appear in the search results table, set the applicable parameters in the search fields at the top of the page, and                 click Find.   Step 3      On the Edit User Basics page, on the Edit menu, click Phone Menu.     Step 4     On the Phone Menu page, under Finding Messages with Message Locator, confirm that the Enable check box is checked.     Step 5      Confirm that the Enable Phone View check box is checked.     Step 6      Click Save.   Related Links Phone View ... View more

    Introduction   This describes concept of dial-peer and steps to debug dial-peer.   Cisco IOS uses two types of dial-peers. They are defined as:-   Plain old telephone systems (POTS) dial peer—These define the characteristics of a traditional Telephony network connection. The POTS dial peer maps a dial string to a specific voice port on the local router/gateway. Normally, the voice port connects the router/gateway to the local public switched telephone network (PSTN), private automatic branch exchange (PBX), or telephone.   Voice-Network dial peers—These define the attributes of a packet voice network connection. Voice-Network dial peers map a dial string to a remote network device.   Different technologies used by dial peers are explained here:-   Voice over IP (VoIP) - The dial peer is mapped to the IP address, Domain Name System (DNS) name, or server-type of the destination VoIP device that terminates the call. This applies to all VoIP protocols such as H.323, SIP, and Media Gateway Control Protocol (MGCP). Voice over Frame Relay (VoFR) - The dial peer is mapped to the data-link connection identifier (DLCI) of the interface from which the call exits the router. Voice over ATM (VoATM) - The dial peer is mapped to the ATM virtual circuit for the interface from which the call exits the router. Multimedia Mail over IP (MMoIP) - The dial peer is mapped to the e-mail address of the Simple Mail Transfer Protocol (SMTP) server. This type of dial peer is used for Store and Forward Fax (on-ramp and off-ramp faxing).   Syntax of a pots dial-peer     dial-peer voice <tag> pots destination-pattern <number> port <port #> <other configurable options>     tag is a numeric value that has locally significant only. destination-pattern <number> - number needed to route a call (valid characters are 0-9, A-D, *, #, . , T). port <port#> - voice-port where the call is sent once a destination-pattern is matched. <Other configurable options> application <ivr application>     Note - Pots peers strip the pattern that is match and forwards the rest.   Example   dial-peer voice 123 pots                            dial-peer voice 123 pots     destination-pattern 2..   ===>                  destination-pattern 2     port 1/1/0                                               port 1/1/0     prefix 2                                                  prefix 2     Note:- the above 2 peers are functionally equivalent.     Wild-cards - A dot (.) is used to represent any single digit to be collected ex. 2…. Would match any extension in RTP.   T - used for variable length dialing - Gateway will continue to collect digits until the inter-digit timeout expires - can incorporate a terminating character with:‘dial-peer terminator x’ globally, where x is any DTMF tone.     Matching rules for Outbound dial-peer   For call routing, dial-peers are matched solely on destination-pattern using the following rules:-   1. Most exact longest match.   2. Preference is used as tie breaker.   Note: If variable length dialing is *NOT* used!   Example 1: dialpeer           destpat               preference             session-target 1                      4085271048             0 (highest)               voip1 2                      408527....                0                             voip2 3                      408527....                1 (lower)                  pots 1 (interface) 4                       ..........                    1                            0:D (interface) 5                       ..........                    0                            voip3 So, if the called number is 4085271048, the order of attempts will be 1,2,3,5,4.   Example 2:   dial-peer            destpat             preference 1                          408527....             0 2                          4085271048          1 3                          4085271...            0 And the number dialed is 4085271048, the order will be 2, 3, 1.   Note that digits matched supercedes precedence.   If variable length dialing is used, then dial-peer matching changes slightly for calls where the DNIS is received one digit at a time (i.e. not PRI):   • The first match is taken regardless of the number of digits explicitly matched if “digit T” is not used. • Longest match is still followed if all destination-patterns have “digit T”   Example - Variable length dial string   Example 1: dialpeer              destpat             preference             session-target 1                        4085271048             0                                 voip1 2                        408…                      1                                 voip2 3                        408…                      0                                 voip3     So, if the called number is 4085271048, the  order of attempts will be 3 then 2. a nd only 408527 will be collected by the router.  Peer 1 will never be used.  If the call is an inbound ISDN call with called party=4085271048, then peer 1 will be matched.   Example 2: dialpeer              destpat                 preference             session-target 1                        408527104.T                  1                         voip1 2                        408…T                          0                         voip2 So, if the called number is 4085271048, the  order of attempts will be 1 then 2.     Matching rules for inbound VoIP peers   For peers where the call leg (VoIP) matches the dial-peer type (VoIP):   1. if the type is matched, associate the called number with the ”incoming called-number <string>”   2. else if the type is matched, associate calling-number with       ”answer-address <string>”   3. else if the type is matched, associate calling-number with       ”destination-pattern <string>”   4. else match PID=0     Answer-address: config option under a dial-peer that is used to match the ANI of the call to the <string> in the config command.   Incoming called-number: config option under a dial-peer that is used to match the DNIS of the call to the <string> in the config command.   Peer ID 0 (PID=0)   Peer ID 0 is an un-configured dial-peer used for inbound matching only.  The matched inbound peer defaults to PID=0 if no other inbound peer is found based on matching criteria.PID=0 has a default configuration that cannot be changed.   Example for inbound voip peer   Output of “debug voip ccapi inout”:   Example 1 - No voip peers:   *Mar  2 01:19:50.561: cc_api_call_setup_ind (vdbPtr=0x815CAA28, callInfo={called=200, calling=100, fdest=1 peer_tag=0}, callID=0x816AAEC0)   Example 2: - dest-pat only   dial-peer voice 1234 voip destination-pattern 1.. session target ipv4:10.1.1.1     *Mar  2 01:22:14.089: cc_api_call_setup_ind (vdbPtr=0x815CAA28, callInfo={called=200, calling=100, fdest=1 peer_tag=1234}, callID=0x816AAEC0)       Example 3: - overriding with answer-address   dial-peer voice 1234 voip destination-pattern 1.. session target ipv4:10.1.1.1   !   dial-peer voice 9876 voip answer-address 100   *Mar  2 01:28:03.173: cc_api_call_setup_ind (vdbPtr=0x815CAA28, callInfo={called=200, calling=100, fdest=1 peer_tag=9876}, callID=0x816AAEC0)     Example 4: - overriding answer-address with incoming called number   dial-peer voice 1234 voip destination-pattern 1.. session target ipv4:10.1.1.1 ! dial-peer voice 9876 voip answer-address 100 ! dial-peer voice 5678 voip incoming called-number 200     *Mar  2 01:29:11.089: cc_api_call_setup_ind (vdbPtr=0x815CAA28, callInfo={called=200, calling=100, fdest=1 peer_tag=5678}, callID=0x816AAEC0)     PID 0 for inbound voip peers has the following configuration:     any codec   ip precedence 0   vad enabled   no rsvp support   fax-rate voice   PID 0 for inbound pots peers has the following configuration:     no ivr application   Related Links Understanding dial-peers dial peer location https://supportforums.cisco.com/thread/2188482 ... View more

    Introduction   This document describes the steps to configure IPPM and troubleshooting issues.IPPM allows users to see presence status and send/receive text messages from their desk phone.  Configuring IPPM takes place on both CUPS and CUCM.  For users to use IPPM they must be CUP enabled in the CUCM licensing capabilities assignment.   Configuration   On the CUPS:   Go to Application > IP Phone Messenger > Settings. Set IPPM Application Status to ON and e nter the Cisco IP Phone Messenger configuration settings Enter an Application Username and password. Click Save.     On the CUCM:   Go to Device > Device Settings > Phone Services. Click Add New. Enter Phone Messenger for the Service Name and ASCII Service Name. Set the Service URL to:     http:// <cups server>:8081/ippm/default?name=#DEVICENAME# Click Save. Go to Device > Phone. Click on a phone from the find list. Go to the Related Links drop down menu Select Subscribe/Unsubscribe Services. Select Phone Messenger, from the Select a Service menu. Click Next. Click Subscribe. Click Save.   Now from your phone you should be able to press the services button and see Phone Messenger.  If you click on it you’ll be asked for a login name and password.    Tip:- You can also use the System Dashboard to view enabled Cisco IP Phone Messenger users in Cisco Unified Presence. Select Diagnostics > System Dashboard.     Troubleshooting   Issue 1:- Add Contact Failure   Error message "No UserID matches the extension you entered. Press OK to enter another extension, or Cancel to contact list."   You must enter a valid extension number of a contact within your organization.   Issue 2:- Multi-login Alert   Error message "You are currently logged in from other phones. Press Yes to log out of other phones (recommended for security reasons). Press No to leave other phones logged in."   Incoming messages will show on all your other logged-in phones in addition to this phone. Press OK to go to the main menu.   You are attempting to log into Cisco IP Phone Messenger on more than one phone. Although this is supported, you should be aware that all instant messages will appear on each phone. This might be a privacy concern.     Issue 3:-Refresh Interval   Error message"Invalid refresh interval. Enter a number between 7 and 3600."     You cannot enter an interval outside the given range (in seconds).     Issue 4:-Session Timer   Error message"Invalid session timer. Enter a number between 1 and 9999.''   You cannot enter an interval outside the given range (in minutes).   Issue 5:-Invalid Message Identifier   Error message ''You were trying to retrieve a message that had been deleted from the EPAS server. Press Ok or Exit to return to IP Phone Messenger main menu.''   If you are logged into more than one phone at a time, Multi-login state. Was deleting messages on one phone and attempting to view one on another.   Related Links IP Phone Messenger settings ... View more

    Introduction   This document describes CLI tools and commands on Unified Communications Operating System.The Command Line Interface (CLI) tool is used to execute CLI commands on the Unified Communications Operating System and help diagnose and troubleshoot problems with the CAD services.     Executing CLI Commands   The CLI tool framework automatically loads when the user logs into the Unified Communications Operating System as an administrator.   To execute CLI commands:-   1. Log into the Unified Communications Operating System as an administrator. CLI starts. 2. At the admin prompt, type the desired CLI command.   CLI Command Syntax     Pathkey, Key, and Value are mandatory fields and case sensitive. If a key or value contains spaces, enclose the string with double quotes. For example:                set uccx cad prefs SiteSetup "LDAP Host 5" "cal lab.lab.com"           NOTE: All commands are case sensitive.   CLI Commands       Command Description show uccx cad license usage     Displays the available and used license information. help <command>          Displays the description of the command.   Example: help utils service list utils service list     Displays the status of all services running on the Unified Communications Operating System. utils uccx dump  packets <Capturefile.cap> <Time interval>     Copies active span-based monitoring packets into the specified file.   • <Capturefile.cap>: Name of the file into which the packets must be copied. The file must have a CAP extension. • <Time interval>: Captures the packets for the specified time. The value for time interval must be in seconds.   NOTE:  Make sure the time interval specified is less than 180 seconds. If the time interval is longer than 180                          seconds, the process continues without stopping, leading to more memory and space usage.   Example: utils uccx dump packets capturefile.cap 5           Preferences     Commands Description show uccx cad prefs <pathkey> Displays key value pairs for the specified preferences file.   Example: show uccx cad prefs SiteSetup set uccx cad prefs <pathkey> <key> <value> Sets the key value pairs with a new value.   • Pathkey: Name of the CAD service’s preferences. • Key: The name of the key that you want to set with a new value. • Value: Specify a new value.   Example: set uccx cad prefs SiteSetup "LDAP Host 5" 0       Recordings     Commands Description show uccx recordings allowed Displays the maximum amount of disk size allowed for recordings. show uccx recordings space Displays the total size of all the recording files. utils uccx recordings purge <size in MB> <cutoff da Deletes the specified size of recording files on or before the cutoff date. No recordings newer than the cutoff date will be purged.   • Size in MB: Value must be a positive real number. • Cutoff date: Value can be any recognizable date as specified by the Unix system date command.   Examples: utils uccx recordings purge 4.005 10/28/2011 20:56:33 utils uccx recordings purge 50 2 weeks ago         LDAP utilities Command Description utils uccx ldap recover Recovers the LDAP database from an inconsistent state. utils uccx ldap archive Displays the path of LDAP transaction log files that are currently not used. utils uccx ldap stat Displays the statistics of the LDAP database. utils uccx ldap checkpoint Inspects and clears all LDAP database transaction logs and exits. utils uccx ldap index Regenerates the LDAP service indices based on the current LDAP database.   Stop the LDAP service in the Unified CCX Serviceability page before executing this command. utils uccx ldap search   <base DN value> [filter]   [attribute]     Displays information from the specified directory name in LDAP.   • Base DN value: The directory name. • Filter and attribute: Optional. Filters the specified directory name by these criteria.   Example: utils uccx ldap search "ou=Agents,lcc=Call Center 1,ou=Company,o=Calabrio Communications" "empID=dactuser1" utils uccx ldap add <ldifFile>     Adds entries in the LDAP database according to the format in the specified LDIF file.   • <LDIF File>: The LDIF file name. Stop the LDAP Monitor service in the Cisco Unified CCX Serviceability page before executing these commands.   Examples: utils uccx ldap add adp_add.ldif utils uccx ldap modify <ldifFile> Modifies entries in the LDAP database according to the format in the specified LDIF file.   • <LDIF File>: The LDIF file name. Stop the LDAP Monitor service in the Cisco Unified CCX Serviceability page before executing these commands.   Examples: utils uccx ldap modify ldp_mod.ldif utils uccx ldap delete <ldifFile Deletes entries in the LDAP database according to the format in the specified LDIF file.   • <LDIF File>: The LDIF file name. Stop the LDAP Monitor service in the Cisco Unified CCX Serviceability page before executing these commands.   Examples: utils uccx ldap delete cdp_del.ldif utils uccx ldap cat <ldifFile>     Copies all LDAP contents into the specified LDIF file.   • <LDIF File>: The LDIF file name.   Stop the LDAP Monitor service in the Unified CCX Serviceability page before executing this command.   Example: utils uccx ldap cat ldp_list.ldif utils uccx ldap modrdn   [add] [file <ldifFile>] |   [DN RDN]     Modifies the specified relative directory name in the LDAP database.   • add: Optional. Adds a new relative directory name in LDAP. If this option is not specified, it replaces the existing directory name with the new one.   • file <ldifFile>: The LDIF file name. The LDIF file must contain two lines, where:   The first line contains the existing directory name The second line contains the new relative directory name   Or   DN RDN: DN is the existing directory name and RDN is the new relative directory name.   You must provide parameters to either the [file <ldif file>] or DN RDN fields.   Example: utils uccx ldap modrdn file /tmp/ldap_add.ldif     Debugging log threshold, number, size, and alert preferences     Command Description show uccx cad log <pathkey> Displays the specified CAD service’s log configuration details.   Example: show uccx cad log slapd set uccx cad log <pathkey> <type> <key> <value> Sets debugging log threshold, number size, and alerts for debug or log files for the specified CAD application.   • Pathkey: Name of the CAD service's configuration file. • Type: The type of logging you want to set with the specified key value pairs. The types are debug or log. The additional type xslt can be set only for Bars CLI. • Key: The name of the key you want to set for the log threshold. The keys are Threshold, Size, and Files.   NOTE:  The Threshold key is used only with the debug type. You cannot set the Threshold key for Bars CLI. • Value: The values for Threshold can be one of the following: OFF, DEBUG, CALL, TRACE, and DUMP.   The value for Size and Files must be an integer. The value for Alarm must be either Enable or Disable.   Examples:   Threshold: set uccx cad log LRMService debug Threshold CALL   Size: set uccx cad log LRMService log Size 10   File: set uccx cad log LRMService debug Files 25   Alarm: set uccx cad log EEMServerJava log Alarm Enable   Restart, start, and stop CAD services   Header 1 Header 2 utils service restart <CAD service> Restarts the specified CAD service.   Example: utils service restart Cisco Desktop LDAP Monitor Service utils service start <CAD service> Starts the specified CAD service.   Example: utils service start Cisco Desktop Sync Service utils service stop <CAD service> Stops the specified CAD service.   Example: utils service stop Cisco Desktop LDAP Monitor Service       Related Links   Troubleshooting Agent in CAD ... View more

        Introduction   This document describes the troubleshooting step when C isco Unified Presence user does not receive a popup when Microsoft Lync or Microsoft Office Communicator user adds the user to their contact list     Cisco Unified Presence user does not receive a popup when Microsoft Lync or Microsoft Office Communicator user adds the user to their contact list   Resolution   Follow the below procedure to resolve this issue   1. If a valid availability state is shown, check whether Cisco Unified Presence is configured to automatically approve subscription requests from users within the local presence domain. If this feature is enabled, Cisco Unified Presence automatically approves the request without a popup to the Cisco Unified Presence user.   2. Otherwise, if " Status Unknown " or " Presence Unknown " is shown for the contact, perform the remaining troubleshooting steps as required.   3. Ensure that the Cisco UP SIP Proxy and Cisco UP SIP Federation Connection Manager services are running on each Cisco Unified Presence server.   4. Ensure that Partitioned Intradomain Federation is enabled on each Cisco Unified Presence cluster.   5. Check that the Partitioned Federation Routing mode applies to the chosen deployment. Advanced Routing is supported only in single-cluster Cisco Unified Presence deployments.   6. If TLS encryption is configured, use Wireshark or an equivalent monitoring tool to verify that the TLS handshake is successful.   7. If TLS encryption is configured but the TLS handshake is failing, verify that FIPS is enabled on Lync/OCS/LCS servers.   8. Ensure that a static route that points to the routing Cisco Unified Presence server is configured on each Lync/OCS/LCS Standard Edition server or Enterprise Edition pool.   9. Ensure that each Cisco Unified Presence server is resolvable by Domain Name Service (DNS) from the Lync/OCS/LCS deployment.   10. Ensure that a Lync/OCS/LCS Host Authorization entry exists for the Cisco Unified Presence server that is sending the SIP NOTIFY message.   a. At the very least, there must be an IP address entry for each Cisco Unified Presence server. b. If TLS encryption is configured, a second FQDN entry is also required for each Cisco Unified Presence server.   11. Ensure that the Cisco Unified Presence Access Control List (ACL) allows requests from all Lync/OCS/LCS servers/pools. If there is an ACL issue, the following entry appears in the SIP Proxy logs of the routing Cisco Unified Presence server: ACL - upstream not trusted - need to authenticate.   12. If this is a multicluster Cisco Unified Presence deployment, ensure that inter-cluster peering is correctly configured.   a. Select Cisco Unified Presence Administration > Presence > Inter-Clustering on the publisher node of the cluster that contains the designated routing Cisco Unified Presence node.   b. Ensure that the list of inter-cluster peers includes a peer for the cluster on which the Cisco Unified Presence user is provisioned and that the number of Associated Users for that peer is greater than 0.   c. Select the inter-cluster peer to validate the Inter-cluster Peer Status.   d. Ensure that there are no errors highlighted.   Cisco Unified Presence user does not appear in Microsoft Lync or Microsoft Office Communicator address book   Resolution       1. Ensure that a full synchronization by the Lync/OCS/LCS Address Book Service has taken place since the Cisco Unified Presence user was migrated from Lync/OCS/LCS. This synchronization happens nightly by default.   2. Request the Microsoft Lync or Microsoft Office Communicator user to sign out and sign in to trigger a download of the new address book. By default, it may take Microsoft Office Communicator more than an hour to download the new address book from Lync/OCS/LCS.   3. If the Cisco Unified Presence user was previously a Microsoft Lync or Microsoft Office Communicator user, ensure that the Cisco Unified Presence user still has their old Lync/OCS/LCS SIP URI populated in Active Directory (msRTCSIP-PrimaryUserAddress).   4. If the Cisco Unified Presence user was not previously a Microsoft Lync or Microsoft Office Communicator user or if their old Lync/OCS/LCS SIP URI has been cleared from Active Directory, you must manually populate the Active Directory msRTCSIP-PrimaryUserAddress field to ensure that the Cisco Unified Presence user appears in the Microsoft Lync or Microsoft Office Communicator address book. You must enter sip:<user's uri> in the msRTCSIP-PrimaryUserAddress field.   TLS handshake errors between Cisco Unified Presence and Lync/OCS/LCS   Resolution   1. Verify that FIPS is enabled on each Lync/OCS/LCS server.   2. Verify that Lync/OCS/LCS has been configured to listen for mutual TLS connections on port 5061.   3. Verify that the Cisco Unified Presence Application Listeners have been configured such that the Presence Peer Authentication Port is set to 5061.   4. Verify that the Cisco Unified Presence certificate is signed by the same certificate authority as the Lync/OCS/LCS server.   5. Verify that none of Lync/OCS/LCS or Cisco Unified Presence certificates have expired.   6. Verify that the Lync/OCS/LCS certificate is configured for both Server Authentication and Client Authentication.   • Such certificates have an OID value of "1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2" • If the certificate is configured for Server Authentication only, it has an OID value of "1.3.6.1.5.5.7.3.1"   7. Verify that the Cisco Unified Presence TLS Peer Subjects list contains the Subject Common Name (CN) used in certificates provided by Lync/OCS/LCS during TLS handshaking.   8. Verify that the Cisco Unified Presence TLS Peer Authentication TLS Context is configured correctly and that all TLS Peer Subjects have been selected.   Cisco Unified Presence unable to route Interdomain Federation requests through Lync/OCS/LCS deployment   Resolution   1.          Verify that the Lync/OCS/LCS deployment is correctly configured for Interdomain Federation. To do this, ensure that Microsoft Lync or Microsoft Office Communicator users can federate.     2.          Ensure that the Cisco UP SIP Proxy and the Cisco UP SIP Federation Connection Manager are running on each Cisco Unified Presence server.     3.          Ensure that Cisco Unified Presence is configured for Interdomain Federation to the foreign domain and that Direct Federation is enabled.     4.          Ensure that a static route is configured on Cisco Unified Presence for the foreign domain and that the static route points to Lync/OCS/LCS.     5.          Ensure that the foreign domain is included in the Cisco Unified Presence Access Control List (ACL).     Related Links Troubleshooting CUPS     ... View more

      Introduction   This document describes the steps to resolve the login failure after converting LDAP Synchronized user to local user.     On an LDAP synchronized system, After an LDAP Synchronized user is converted to a Local user from Cisco Unified Communications Manager 9.0(1), users will experience login failures from   1) Cisco Unified CM IM & Presence Administration   2) Cisco Unified CM IM & Serviceabilty Administration   3) Cisco Unified Personal Communicator   4) Cisco Jabber   5) Third Party XMPP Clients   6) All externally supported interface that requires user authentication (except PAWS API)   Prerequisites:-   As described in the problem, the user should be   1) Converted from an LDAP Synchronized user to Local user   2) System should be enabled for LDAP Authentication   2) Should be Cisco Unified Communications Manager 9.0(1) release   Steps to resolve the error     Re-sync the user from Active directory.   1) If the user was not deleted from within the same Organisation Unit of Active directory , perform a resync following the below mentioned procedure.   2) If the user was deleted from Active directory, recreate the user with the same details within the same Organisation Unit as before & perform a resync following the below mentioned procedure.   Resolve the problem by performing a manual sync and refer "Perform Full Sync"     Resolve the problem during a scheduled synchronisation ------------------------------------------------------------------------------ If the issue is non-critical & the system is configured for scheduled re-sync, refer "LDAP Directory Synchronization Schedule"   LDAP Directory Synchronization Schedule     Perform Sync Just Once     If you want to perform synchronization of the data in this LDAP directory with the data in the Cisco Unified Communications Manager database only once, check this check box.     Perform a Re-sync Every     If you want to perform synchronization of the data in this LDAP directory with the data in the Cisco Unified Communications Manager database at a regular interval, use these fields.   In the left field, enter a number. In the drop-down list box, choose a value:     •hours   •days   •weeks   •months     Cisco Unified Communications Manager can synchronize directory information every 6 hours, which is the minimum value allowed for this field.   Note:- This field remains active only if you do not check the Perform Sync Just Once check box.     Next Re-sync Time (YYYY-MM-DD hh:mm)   Specify a time to perform the next synchronization of Cisco Unified Communications Manager directory data with this LDAP directory. Use a 24-hour clock to specify the time of day. For example, 1:00 pm equals 13:00.   Related Links CUCM Ldap directory ... View more