CDR Access

[s.casper_2]

We are trying to read our CDR records via ODBC. We are using the default read Userid and password but appear to be not authenticating. Here is the error we receive:

SQLSTATE '28000'

SQL Server Error 18456

[Microsof][ODBC SQL Server Driver][SQL Server]Login failed for user 'CISCOCCMCDR"

Any ideas? We are using MLA but I would think that should have no effect on the ODBC login.

Thanks!

[aaronw.ca]

The default username and passwords (read and read/write) are no longer available in CCM 4.0+, which might be why you are having problems if you are using a 4.0 or newer installation. SQL authentication is disabled by default in CallManager 4.0 and 4.1, and only windows authentication is available.

You can re-enable mixed-mode authentication so you can use SQL authentication again, but you will have to create your own login, as the default accounts are no longer available.

This link might provide additional details:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801f9f33.shtml

and the CDR specification, though you probably already have that:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_usage_guide09186a0080405548.html

[s.casper_2]

Thank you for the response. We are on 4.1.3.

Under SQL Enterprise Manager/Security/Logins I see

the Windows Group - Built-in/Administrators.

For this group under the Database Access tab Permit is selected for all data bases. In the Permit in Database Role window only Public and db_owner are selected. Should any others be selected such as db_datareader?

[aaronw.ca]

What computer are you running query analyzer on and trying to connect to the CallManager database with? Are you connecting from the CallManager itself? Or from another computer on the network?

If you are running from CallManager itself, then you should be able to connect. Just change the authentication to Windows Authentication (and not SQL authentication). It won't ask you to enter a password, and you should be able to connect without any problems.

If you are running from another computer on the network, then it gets more complicated. Is the CallManager part of a domain? Is the computer you're connecting from part of the same domain? If not, you may want to re-enable SQL authentication, and use that. Cisco doesn't recommend having a CallManager join a domain, though Cisco also doesn't recommend re-enabling SQL authentication, so either way you're going against a recommendation, but that can't be helped. Choose the solution that works best for you in your environment.