hi, i am trying to access to the sql data base, but i dont see the sql query analyzer installed, but i clearlly see SQL server running, how can i check the DB? and normally which login and password does cisco use to connect to it?
As a follow-on to installing Microsoft SQL 2000 to get management tools: You cannot install this using standard Microsoft SQL Server media. You must use the customized version that is available as a Cisco part number for CCX. Your partner can provide you a quote on this.
It is definitally not advisable do anything not explicitly documented. The Historical Reporting Administrator and Developer Guide provides available options to you. If you are running MSDE, your management tool options are the CLI commands. If you want Enterprise Manager and other related tools, you will need to order the full SQL Server SKU. You need to consider CCX as a "black box" appliance. Starting in 8.0, all of the rules will be enforced by transitioning to the sealed Linux OS model.
CCX uses Windows Authentication using the local Administrator account to interact with SQL locally. Changing to mixed mode will break CCX unless you are running 7.0(1)SR4 or higher; even then it is not recommended.
Remember that if you "go off the reservation" and do something that is not documented, you are not supported by Cisco or any sane partner for that matter. No TAC support, nothing.
If you are not using the historical reporting features of CCX then I question why. This is a significant reason for buying the product, especially with CCX over IP IVR. You may want to review the Historical Reports User Guide again to see if there is useful reporting data for you.
Do you think all the data an organization needs to report on about a phone call is covered in Historical Reporting?
Some organization, like ours, also use internal applications to track data about specific phone calls. We like to have reports that integrate both systems. In order to facilitate this, we do a nightly extract from the CCX database to our own reporting database. This accomplishes a couple of things.
1. All report data is in one database making it easier to create reports and ad-hoc queries.
2. It's typically not wise to allow users to run ad-hoc queries and such against production databases. Because we extract the data, we keep the CCX database "on task".
Turning on mixed-mode authentication is documented and does work. Interestingly enough our Historical Reporting still works as well even though we don't use it and were told they wouldn't.
I am definitely not stating that the canned HR reports provide every useful data point or representation of what happened in CCX. What I was saying is that mixed mode was known to break CCX until 7.0(1)SR4 and that there is a documented process (DTS export) for doing this.
I was also cautioning against deviating beyond anything that Cisco documents because it will eventually break. When Cisco tells you that you are on your own because of what you did, that's a bad day and I have seen customers in that position. Band aid workarounds to product limitations are not worth doing IMO.
I fully agree with Jonathan. It is a suck position to be in when you get kicked in the face by TAC because you didn't do it exactly as they describe. (On the flip side, TAC hasn't been overly useful, for me anyway, with regards to UCCX).
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...