I've got a problem with CDR logging with my CallManager 3.1 publisher. When we try to see CDR table by doing:
Start->Programs->Microsoft SQL Server 7.0->Enterprise Manager
and select CDR table, we get an error message:
"The SQL Server <servername> is not known to be running. Are you sure you wish to connect?"
If we choose "OK" and force to select CDR table, we find no new calls are recorded to the table. If we check the SQL Service, however, the service is indeed running. We tried bunch of things like: start/stop SQL server, enable/disable CDR and update, restarting CCM server itself, etc. But nothing seems to work. After giving it up and started searching for a web for any solution, we end up with finding new calls are started being recorded. So it seems no solution is there but we need to wait enough time for CCM server to get happy to start cooperating with its SQL services.
Has anybody got any idea/solution for this problem???
We have 1xpublisher, 1xsubscriber(primary), 1xsubscriber(secondary). So a phone call should be processed by either primary or secondary, depending on which one was available when the phone was registered. And the CDR database exists on publisher. We have checked the eventlog on our primary CCM and found SQLServerAgent event: "The process could not connect to Distributor ''". So it looks like primary CCM failed to contact publisher. But why?
As for the error message on Enterprise Manager, we found a few posts on microsoft newsgroup:
Usually when you get the cannot connect to distributor on the sub that means you may have a name resolution problem or the sqlsvc users password is different on the pub than on the sub. The password should be the same for all of the servers in a cluster. Did you ever mess with this users password?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...