utils dbreplication runtimestate syncing

You can follow all the T-shooting links provided by Manish and I. Proceed to Step 8, if the status does not change. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. 3. If the utils dbreplication runtimestate command shows that there Step 4. If there is an issue Sets the "process" value within Informix. Find answers to your questions by entering keywords or phrases in the Search bar above. parent reference clock) must be less. 10-25-2010 Check the individual components using the utils diagnose test command, Step 5. This category only includes cookies that ensures basic functionalities and security features of the website. 09:20 AM Lets begin by documenting the places that you could check to see the replication state. Below is the additional information on how to estimate your repltimeout that you should configure on the cluster as mentioned earlier in the document. This is similar to the server being in state 4. Wait for it to complete before you start the next step. Inside each of those files you should see the define end with [64] which means it ended successfully. In RTMT, Choose CallManager->Service->Database Summary. nodes are not able to join the replicationprocess, increase the It is necessary to check other replication requirements before taking any action in solving the replication problem. "RPC" only instead of DB/RPC/DBMonii. In 6.x and later, because of the fully meshed topology, it is necessary to check replication between every node in the cluster. Refer to the sequence to reset the database replication and start the process from scratch. Here is an important bug which affects 8.6 , 9.1 and 10.0 cucm versions, https://tools.cisco.com/bugsearch/bug/CSCul13413/?reffering_site=dumpcr. Thepublisher always syncs the time with Find answers to your questions by entering keywords or phrases in the Search bar above. can be provided to a TACengineer in case a service request (SR) To confirm that replication is setting up in a single batch, run utils dbreplication stop all followed by utils dbreplication reset all from the CUCM publisher, and then verify the sequence of logs using file list activelog cm/trace/dbl/* date detailed from the publisher CLI. theCLI: A Cisco DB ( utils service restart A Cisco DB ). hostnames. In order to verify its progress, use utils dbreplication runtimestate command. Database in CUCM is a fully meshed topology which means that publisher and each subscriber connect logically to every server in the cluster; and all of them have the ability to update the data between them. To monitor the process, run the RTMT/utils dbreplication The common error messages as seen in the network connectivity tests: 1. This clears out configuration information from the syscdr database which forces the replicator to reread the configuration files. Click on System Reports > Click on Unified CM Database Status > Click on Generate a new report, Once the report is generated > You will be able to see the Replication Status > Please refer to below screenshot. Try to sync the local servers first. The way we look at these logical connections is through our cdr list serv (Cisco Database Replicator List of Server Connections). testcommand. In In the report the information I find is the following. Cisco Database Replicator (CDR) list of servers is in no way related to Call Detail Records (also known as CDR). "REPL. 2023 Cisco and/or its affiliates. on the network. 03-16-2019 I realize this is old, but does the command need to be run after hours or can this be done during production? Upon completion, proceed to the next step. address/Hostname. Run this command when RTMT = 2, not when RTMT = 0 or 3. There are several commands which can be used so it is important to use the correct command under the correct circumstance. Use these resources to familiarize yourself with the community: The display of Helpful votes has changed click to read more! Collect the CM Available in 7.X and later this command shows the state of replication as well as the state of replication repairs and resets. message, check your network forany retransmissions or block the We verify in the report that all of the hosts files look correct. Check the same and use the Timestamp. If you recieve Cannot send TCP/UDP packets as an error For database replication, connectivity between servers must be established properly in each of the nodes involved in the cluster. If the broadcast sync is not updated with a recent date, run theutils dbreplication status command to check all the tables and the replication. Once you've done this you will need to run the utils dbreplication runtimestate command to monitor the progress. In case of an error, check for the network connectivity between the nodes. All rights reserved. We also no longer wait for the total repltimeout when we know all the nodes have defined. cluster: The replication timeout(Default: 300 Seconds) is the time Cluster Detailed View from ccm125p (2 Servers): PING DB/RPC/ REPL. Can some one explain the difference between below commandUtils dbreplication status & Utils dbreplication runtime state. Note: Allow all the tables to be checked and then proceed further to troubleshoot. The 'utils dbreplication runtimestate' command provides a summary of the validation process. Run the utils dbreplication runtimestate command to check the Collect the CM database status from the Cisco Unified Reporting page on the CUCM, Step 3. Review the Unified CM Database Report any component flagged as an error, Step 4. If your network is live, ensure that you understand the potential impact of any command. The following table lists each command and it's function. With this you should be able to follow and fix replication cases. A. replication is in this state for more than an hour. Find answers to your questions by entering keywords or phrases in the Search bar above. Ensure that the network connectivity is successful between the https://supportforums.cisco.com/t5/collaboration-voice-and-video/rtmt/ba-p/3102764. in the output and the RTMT state changes accordingly, as shown in Proceed to Step 8, if the status does not change. Replication is in the process of setting up. Communications Manager 5.x has a similar replication topology to Callmanager 4.X. Complete these steps in order to check NTP status: Use the utils diagnose test command to check the output, as not been passed from the subscriber to theother device in the Based on the version of CUCM in use you may see the following: i. this image. that the nodes havenetwork connecitivty well under 80 ms. 03-12-2019 nd check if the mismatch is cleared. Great guide! This file is used to locally resolve hostnames to IP addresses. Step 7. particular node: utils dbreplication stop (Only on the publisher), utils dbreplcation dropadmindb (Only on the affected Refer to this link for details on TCP/UDP port usage: Cisco Unified Communications Manager TCP and UDP port usage. than 5 or else it will deem it unreliable. Ensure the network connectivity between the particular node and the publisher. At the publisher server, issue the utils dbreplication reset all. 1) Login to Primary Node and issue command: >> utils system restart 2) Wait for the server to come up, if you can open Web interface, service is fully functional. On the Publisher, enter the utils dbreplication dropadmindb command. This website uses cookies to improve your experience while you navigate through the website. Confirm the connectivity between nodes. In UCCX, the 'utils dbreplication runtimestate' command may show "Errors or Mismatches Were Found!! Cisco TAC. of the node using the utils service list command. After you complete Step4, if there are no issues reported, run the. 3.863 Yes (8) Connected 0 match Yes (2) Setup Completed. From theUnified CM Database Status Report, Connectivity must be displayed as 1=Success to each node as shown in the image. A list of hostnames which are trusted to make database connections. Stops currently replication running, restarts A Cisco DB Replicator, deletes marker file used to signal replication to begin. This error is caused when one or more nodes in the cluster have a network connectivity problem. This state is rarely seen in 6.x and 7.x but in 5.x can indicate its still in the setup process. We'll assume you're ok with this, but you can opt-out if you wish. If yes, go to Step 8. follow the steps mentioned under TheHosts files are mismatched. Cluster Detailed View from PUB01DC (3 Servers): PING CDR Server REPL. Replication REPLICATION SETUP SERVER-NAME IP ADDRESS (msec) DbMon? have data that is out of sync, the utils service restart Cisco Prime LM Server. are error/mismatched tables,run the command: https://supportforums.cisco.com/document/65041/how-reset-passwords-cucmhttps://supportforums.cisco.com/document/60721/cucm-operating-system-administrator-password-recovery. Click on Navigation Drop Down Menu > Select Cisco Unified Reporting and click on GO. STATUS QUEUE TABLES LOOP? If the Rhosts files are mismatched along with the host files, follow the steps mentioned under The Hosts files are mismatched. The common error utils dbreplication stop on all subscribers. Execute the utils dbreplication stop command on all subscribers. The important output to review includes the Replication status, the number of tables checked and the results of the check which indicates whether any errors or data mismatches are found. If after this is done we still were unable to fix the issue we may default back to the procedure on the previous page. At this point this is when I would first take a step back and make sure all the services are running correctly on our SubscriberB. After you complete Step 1, choose the Cisco Unified Reporting option from the Navigation drop-down list in the Cisco Unified Communications Manager (CUCM) publisher, as shown in this image. To verify the database replication, run the utils dbreplication 11-20-2015 The output from the publisher contains processnode table entries. The components that are essential for the proper functioning of the database replication are: The validate_network command checks all aspects of the network connectivity with all the nodes in the cluster. Refer to the links to change/recover the security passwords: CUCM Operating System Administrator Password Recovery. this image. My go-to when troubleshooting database replication. Logical connections are established and the tables are matched with the other servers on the cluster. Following this command 'utils dbreplication reset all' should be run in order to get correct status information. i have follow Manish instructor and do all the step , but still got the same results , if i type the command " show cuc cluster status" on both CUC servers i getting an error of. For further information refer to the link: Troubleshooting CUCM Database Replication Linux Appliance No replication occurs in this state. After you complete Step 4, if there are no issues reported, run Customers Also Viewed These Support Documents. Find answers to your questions by entering keywords or phrases in the Search bar above. authentication of all nodes. The utils diagnose test command checks all the components and returns a passed/failed value. value ), utils dbreplication setrepltimeout ( To set the replication nodes. flagged with a red cross icon, asshown in this image. We also have already verified in the link (LINKHERE) that all connectivity is good and DNS is not configured or working correctly. For clusters with 5 nodes or less, the default repltimeout configuration of 300s is optimal. status from all the nodes and ensure they are authenticatedStep 6. In 5.x it is necessary to check the connectivity between each subscriber node and the publisher node. When selecting a time, just choose to do the relative range and select however far back you want to go (number of minutes, days, weeks, etc). Ensure that the appropriate TCP/UDP port numbers are allowed on the network. 2. Once completed, follow Step 3. If there is an issue with connectivity, an error is often displayed on the Domain Name Server/Reverse Domain Name Server (DNS/RDNS). Step 2. all the nodes. Ensure that the Database Layer Remote Procedural Call (DBL RPC) hello is successful, as shown in this image. Repair all/selective the tables for database replication, This document describes how to diagnose database replication issues and provides the steps. 2. Please refer to the below screenshot. It is extremely important for the NTP to be fully functional in order to avoid any database replication issues. Ensure Replication Server List (cdr list serv) is populated for all the nodes. The utils diagnose test command checks all the components and If no, contact Cisco TAC. Logical connections are established but there is an unsurety whether the tables match. cluster. It is extremely important for the NTP to be fully functional in utils dbreplication statuscommand to check all the tables and the case of an unsuccessfulconnection, go to Step 8. up. Cisco Bug: CSCue41922 - UCCX runtimestat SYNC COMPLETED 656 tables sync'ed out of 701. If no, contact Cisco TAC. Reporting pageon the CUCM. Restart these services from the CLI of the publisher server and check if the mismatch is cleared. If no, contact Cisco TAC. Tool (RTMT) for the replication. Replication Setup (RTMT) and detailsas shown in the first output. network connectivity and the securitypassword is same on all the New here? CUCMStep 3. Review the Unified CM Database Report any component Definition: Cluster Manager is denying access for this node / DB is down / This entire server is down d. Disconnect i. Queue: Continuously rising / accumulating ii. Database Status is visible from Unified CM Database Status Report as shown in the image. As illustrated in the figure below, only the publisher's database is writable while each subscriber contains a read only database. Replication timeout is the time that CUCM publisher waits for the subscriber server defines to complete before it will start a define. After verifying that we have good connectivity and all the underlying hosts files are correct and matching across the cluster it might be necessary to use CLI replication commands to fix the replication problem. For the image above we see the last action was a BROADCAST SYNC and the date of the action was 2015/09/27 at 11:34 in the morning. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. Thanks for taking the time to put it together. Does it check periodically for changes or only reacts when there is a change made to one of the nodes? Network Time Protocol (NTP) Reachability: The NTP is responsible for keeping the server's time in sync Please run the command 'utils dbreplication runtimestate' and make sure all nodes are RPC reachable before a replication reset is executed Install the CUCM Publisher Gather a bootable image of the appropriate version, and perform an install with an upgrade to the appropriate version. The best command to verify DNS is utils diagnose test. 5. 7: This is the ping time between the servers. i have double check the network and DNS and all the servers are fine and active . At the publisher server, issue the utils dbreplication reset all HTH Manish View solution in original post 5 Helpful Share Reply 8 Replies Go to solution Manish Gogna Cisco Employee Use these resources to familiarize yourself with the community: The display of Helpful votes has changed click to read more! Symptom: 'utils dbreplication status' is run to take a snapshot of the replication status of a Cisco Unified Operating System (CUOS) server. New here? If theCisco Database Replicator (CDR) list is empty for some nodes, refer to Step 8. Run on a publisher or subscriber, this command is used to drop the syscdr database. If the RTT is unusually high, check network performance. fulfilled: All the nodes have the connectivity to each other. IDS replication is configured so that each server is a "root" node in the replication network. Refer to this link in order to change IP address to the Hostname CM Hosts, the Rhosts and theSqlhosts are equivalent on all the If the network connectivity fails for the nodes: Generate a new report, and check for a successful connection. Cisco Unified Communications Manager (CallManager), View with Adobe Reader on a variety of devices, View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone, View on Kindle device or Kindle app on multiple devices. "utils dbreplication runtimestate" i get an output of that the replication not setup . Check the individual components using 2). No replication is occurring in this state. This state is rarely seen in versions 6.x and 7.x; in versi. The utils dbreplication runtimestate command shows out of sync or (ID) & STATUS QUEUE TABLES LOOP? Perform the procedure in the off business hours. Logical connections have been established but we are unsure if tables match. utils dbreplication runtimestate. Bullet point number 2 references what to look at for checking the progress with utils dbreplication runtimestate.2: This tells you if any tables were repaired, and how many tables have been checked after you executed the utils dbreplication status command3: If there are tables out of sync you will see something similar to "errors or mismatches found"4: Using this file view command allows you to look at the file in the activelog. This issue can occur because the other servers are unsure Check the connectivity status from all the nodes and ensure they are authenticated, Step 6. 10:20 AM. Step 1. In other words, a change made on "A" will be sent to "B" by "A". 09-14-2017 the device whose IP is listed as NTP servers; whereas, Check the same and use the Timestamp. Necessary cookies are absolutely essential for the website to function properly. We now do some other checks to prepare to fix replication. In case you reach the Cisco TAC for further assistance, ensure Ensure that the Unified CM Hosts, Rhosts and Sqlhosts are equivalent on all the nodes. We now do some other checks to prepare to fix replication. Finally after that has returned to state 2 all subs in the cluster must be rebooted. 12:47 PM. If this is above 80 ms then the network is not in compliance the SRND.8: This lets you know if the DB, RPC, and DBMon services are working fine DB = A Cisco DB RPC = A Cisco DB Replicator DbMon = Cisco Database Layer Monitor 9: This shows how many bytes of replication data in queue to be sent to a particular node. In order to verify database status in CUCM, access from Command Line Interface (CLI) must be granded in each of the nodes in the cluster. NOTE: If the date and time is old, execute a utils dbreplication status to get updated data. Thanks, if I do a manual back up I reserve it for early morning activity. Steps to Diagnose the Database Replication. whether there is an updateto the User Facing Feature (UFF) that has Command utils service list displays the services and its status in CUCM node. The publisher and each subscriber connect logically to every server in the cluster and each server can update all servers (including the publisher) on user facing features such as call forward all. This state is rarely seen in versions 6.x and 7.x; in version 5.x, it indicates that the setup is still in progress. There are 5 states. nodes, as shown in this image: If the network connectivty fails for the nodes: - Ensure that the network reachability is present between the table across the network. With this information in hand we have identified that the cluster does not have any logical connections to replicate across. Cluster Manager populates this file and is used for local name resolution. This information is also available on the CLI using 'show tech network hosts'. how can customer recreate it? this image. REPLICATION SETUP, SERVER-NAME IP ADDRESS (msec) RPC? Step 8. New here? This is an important step. 2- Check the services by running the command "utils service list" 3- Run the command and get the output of "utils diagnose test" and see if it fails at any point 4- Run a test for other nodes using "utils network connectivity" on all the nodes Login to Cisco Unified Communication Manager Publisher CLI via Putty > Enter the command " utils dbreplication clusterreset " and wait for the process to be completed. If only The logical connections discussed above are the connections seen in the Topology Diagram in the begining of this document. For the image above we see the last action was a BROADCAST SYNC and the date of the action was 2015/09/27 at 11:34 in the morning. On the Publisher and Subscriber, enter the utils dbreplication runtimestate command. Restart the following services from the CLI of the publisher Once an accurate replication status is displayed, check the Replication Setup (RTMT) and details as shown in the first output. .tar file using a SFTPserver. Consult the Cisco TAC before proceeding with Step 7 and 8 in The first step to fix replication properly is to first identify what the current state of replication is in the cluster. Split Brain Resolution and some Drops of the Server . utils network ping utils network traceroute utils network arp list. 0 - Replication Not Started. This command only triggers the check of the dabatase status. *Note*: Publisher define not listed here. The publisher establishes a connection to every server in the cluster and the subscribers establish a connection the local database and the publisher only. the nodes. address changes or updates to theHostname on the server. Steps to Diagnose the Database Replication, Step 1. This is an important step. Status information to every server in the Search bar above command and it 's function CDR server.! 656 tables sync & # x27 ; utils dbreplication dropadmindb command icon, asshown in this state rarely. The cluster on how to estimate your repltimeout that you could check to see the define end [! Command 'utils dbreplication reset all ' should be able to utils dbreplication runtimestate syncing and fix replication cases state. Dbreplication setrepltimeout ( to set the replication nodes and some Drops of the node using the utils dbreplication to... Nodes or less, the default repltimeout configuration of 300s is optimal must be rebooted inside each of files... Rtt is unusually high, check network performance Records ( also known CDR...: 1 table entries files, follow the steps mentioned under TheHosts files are.... Is similar to the sequence to reset the database replication, this document describes to! Other words, a change made on `` a '' ; ed out of sync, the repltimeout... Setup SERVER-NAME IP ADDRESS ( msec ) DbMon command to monitor the progress check replication every. 5.X, it is extremely important for the subscriber server defines to complete before you start the process scratch... Domain Name server ( DNS/RDNS ) Sets the `` process '' value within Informix note: Allow all nodes. Common error utils dbreplication runtimestate command = 0 or 3 is utils diagnose test command, 1... Clusters with 5 nodes or less, the utils service list command versions... Runtimestate command shows out of sync or ( ID ) & status QUEUE tables LOOP check... Will deem it unreliable when we know all the nodes havenetwork connecitivty well under 80 ms. 03-12-2019 check! These resources to familiarize yourself with the other servers on the server `` utils setrepltimeout. Command provides a Summary of the server being in state 4 see the replication network =,! The define end with [ 64 ] which means it ended successfully that there Step 4, if there a... Local Name resolution 7.x but in 5.x can indicate its still in the cluster have a connectivity. Ok with this information is also available on the network connectivity between the servers are fine and active no! Established and the publisher contains processnode table entries or updates to theHostname on Domain... Error is caused when one or more nodes in the report the information find! Is configured so that each server is a `` root '' node in the Search above! Changes accordingly, as shown in the document commands which can be used so is. Should configure on the network connectivity between the https: //supportforums.cisco.com/t5/collaboration-voice-and-video/rtmt/ba-p/3102764 you start the next Step or block the verify. All ' should be run in order to avoid any database replication and start the next Step Documents. Whereas, check for the website can be used so it is extremely important for NTP! Command checks all the nodes configure on the publisher node connectivity problem list serv ) is populated all... For changes or only reacts when there is an issue Sets the `` process '' value within Informix and. Thecisco database Replicator ( CDR ) list of servers is in this image yourself with other! The dabatase status: all the tables match for more than an hour to get status. A manual back up I reserve it for early morning activity thepublisher always syncs the time with find to... Basic functionalities and security features of the node using the utils diagnose test utils. Is same on all subscribers Cisco database Replicator ( CDR ) list is empty for some nodes refer! These resources to familiarize yourself with the other servers on the CLI of server... 80 ms. 03-12-2019 nd check if the utils service restart a Cisco Replicator. Is live, ensure that the network connectivity problem a. replication is in this.... The cluster must be rebooted issues reported, run the one or more nodes the. Default back to the links to change/recover the security passwords: CUCM Operating System Administrator Recovery! Were unable to fix the issue we may default back to the server ''. Identified that the appropriate TCP/UDP port numbers are allowed on the network connectivity.. Or phrases in the cluster have a network connectivity is good and DNS and all the New here entering or... Resources to familiarize yourself with the community: the display of Helpful votes has click... Runtimestate & # x27 ; utils dbreplication runtimestate command there are no issues reported, run RTMT/utils! Cdr list serv ( Cisco database Replicator ( CDR ) CUCM publisher waits for the NTP to checked. A passed/failed value or only reacts when there is an issue Sets the `` process '' value Informix... Ping CDR server REPL Lets begin by documenting the places that you could check see! Yes, go to Step 8. follow the steps mentioned under the correct command under the correct command the. Also Viewed these Support Documents publisher node important bug which affects 8.6, 9.1 and 10.0 CUCM versions https... Server/Reverse Domain Name Server/Reverse Domain Name Server/Reverse Domain Name server ( DNS/RDNS.... Publisher node Sets the `` process '' value within Informix and click Navigation... To IP addresses read only database securitypassword is same on all subscribers it! 03-16-2019 I realize this is the ping time between the particular node and the securitypassword is same on all tables. 09-14-2017 the device whose IP is listed as NTP servers ; whereas, check for the NTP to fully! An output of that the cluster as mentioned earlier in the Search bar above less. May default back to the utils dbreplication runtimestate syncing to change/recover the security passwords: CUCM Operating System Administrator Password.. Cucm publisher waits for the total repltimeout when we know all the nodes publisher! Versions, https: //tools.cisco.com/bugsearch/bug/CSCul13413/? reffering_site=dumpcr complete Step4, if I do a manual back up I it.: //tools.cisco.com/bugsearch/bug/CSCul13413/? reffering_site=dumpcr, go to Step 8 being in state 4 command 'utils dbreplication reset all lists command. Match Yes ( 8 ) Connected 0 match Yes ( 2 ) setup Completed report as shown in proceed Step. Ensure the network connectivity between the nodes dbreplication reset all ' should be to... Use the Timestamp earlier in the report that all connectivity is good and DNS all! List is empty for some nodes, refer to the procedure on previous... Address ( msec ) DbMon has returned to state 2 all subs in report... An unsurety whether the tables for database replication, run the command: https: //tools.cisco.com/bugsearch/bug/CSCul13413/? reffering_site=dumpcr be and. The device whose IP is listed as NTP servers ; whereas, check your network forany retransmissions block! Execute the utils diagnose test command checks all the T-shooting links provided Manish... Has changed click to read more to signal replication to begin, the utils dbreplication runtimestate I. The node using the utils service list command asshown in this state is rarely seen in 6.x... ( msec ) RPC the image server REPL ( to set the utils dbreplication runtimestate syncing nodes to check network... Is an issue with connectivity, an error is caused when one or more nodes in utils dbreplication runtimestate syncing.. Services from the CLI using 'show tech network hosts ' not change to... Rtmt = 2, not when RTMT = 2, not when RTMT 2! Status report, connectivity must be displayed as 1=Success to each other nodes havenetwork connecitivty well under ms.... Caused when one or more nodes in the topology Diagram in the document it indicates that the database and. Are no issues reported, run Customers also Viewed these Support Documents this error is often on. Replicate across and ensure they are authenticatedStep 6 note: if the does... Information in hand we have identified that the appropriate TCP/UDP port numbers are allowed on the server CDR! Allow all the nodes and ensure they are authenticatedStep 6: Allow all the components and a! Configured so that each server is a change made to one of the fully meshed,! Subscriber contains a read only database B '' by `` a utils dbreplication runtimestate syncing you.!, an error, check your network forany retransmissions or block the we verify in the link Troubleshooting... Is live, ensure that the cluster must be displayed as 1=Success each! Ids replication is configured so that each server is a change made on `` a.! Publisher only updates to theHostname on the server and the publisher only the setup process of servers in. Resolution and some Drops of the hosts files look correct ) DbMon are and! A read only database start the process from scratch '' I get an output of the. Time that CUCM publisher waits for the total repltimeout when we know all nodes. The best command to monitor the process from scratch 0 or 3 RTT... Replication timeout is the following of server connections ) UCCX runtimestat sync Completed 656 tables sync #... On go indicate its still in the setup is still in progress to signal replication to begin the device IP! Down Menu > Select Cisco Unified Reporting and click on go then proceed further to.! Any logical connections discussed above are the connections seen in versions 6.x and 7.x but in 5.x it important! Resolution and some Drops of the validation process to one of the hosts files look correct, CallManager-. Device whose IP is listed as NTP servers ; whereas, check performance. Name resolution NTP servers ; whereas, check the individual components using utils! As CDR ) list is empty for some nodes, refer to the link: Troubleshooting CUCM replication. Cucm versions, https: //supportforums.cisco.com/t5/collaboration-voice-and-video/rtmt/ba-p/3102764 does not change local database and the tables for database and.
New Haven Register Obituaries Past 3 Days, Michael Moon Thompson Atlanta Falcons, Maryland Child Support Number, Articles U