Upgrade to 4.1.3 changed access to CDR/SQL

[d.anthony.hadley_2]

Anyone know about a third party CDR accounting app called MTS tabsit? The customer recently upgraded from CallManager 3.3.3 to 4.1.3 sr3a. Now they can't log in to the CM with this application, they get a SQL login error. They tried using the windows login but that didn't work. The SQL passwords are the same as before. What else could have changed during the upgrade? Thanks.

[Rob Huffman]

Hi d.anthony,

Have you checked out this section of the post installation/upgrade tasks for 4.1.3?

After you upgrade Cisco CallManager, the database name automatically increments; for example, from CCM0300 to CCM0301. Third-party CDR software may have SQL triggers that are hard coded to the original database name. The triggers may point to the previous database name and cause all CDR flat files to write to the BAD directory on the publisher database server.

From this doc:

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

Hope this helps!

Rob

Please remember to rate helpful posts.........

[aaronw.ca]

In addition to Rob's point (a valid one, though using triggers on CallManager databases is not recommended by Cisco), the change from SQL authentication to Windows authentication may be causing problems, especially if you upgraded from a CallManager version prior to 4.0 (such as 3.x).

An error such as:

"Login failed for user 'sa'. Reason: Not associated with a trusted SQL server connection."

is usually indicative that the application is trying to log in with SQL Authentication but the SQL Server is only configured to use Windows Authentication.

See also:

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

and

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=IP%20Communications%20and%20Video&topic=IP%20Phone%20Services%20for%20Developers&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dd97a4f/0#selected_message

You will likely need to either re-enable Mixed-mode authentication (which allows SQL Authentication in addition to Windows authentication), which is not recommended by Cisco, or else change the way the 3rd party software connects to CallManager and have it use Windows authentication rather than SQL authentication.

[jbarcena]

"In order to make administration of Cisco CallManager 4.0 easier, authentication has changed from 'SQL Server and Windows' to a 'Windows Only' authentication. In the past, a separate account and password was required in order to access the SQL database on the Cisco CallManager server after the initial Windows logon to the server. In Cisco CallManager 4.0, you only need to logon to Windows in order to gain access to the SQL database. This was done so users would not have to remember their SQL Server system administrator (SA) passwords after their initial install"

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