In duplex ICM environment, if logger on side A fails and router on side B fails, side B will obviously be removed from service and call routing will coninue uninterrupted on side A. But databases on both sides will be out of date as both loggers are not in service (as per SRND). When the nodes will come up, what about the data during downtime? will it be recoverable and accessible in databases?
"will it be recoverable and accessible in databases?"
How could it be? Both loggers are down.
The Router has pulled the configuration into memory when it started up, so under this unusual scenario, your call center will continue to run, but historical data cannot be held in memory for long. Updates on the half-hour come from the PG, the Router saves to memory and requests the Logger to write to the database. It cannot. I'm guessing that when the next half-hour update comes, it will overwrite the previous. Data will be lost.
Ok, it's now clear that Historical Database updates itself through 'replication' process exists both at AW and Logger. The process 'updateAW' is responsible to update the configuration in central database located at Logger.Whereas the 'rtclient' of AW communicates with 'dbagent' process of Router whereas the 'dbworker' process of Router access the central controller.
My question is, is 'dbagent' dependent or relate anyhow on 'dbworker' process? if the Logger goes down, can't 'dbagent' update the AW with real time feed directly? Which process is responsible to update the awdb?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...