The field definitions for CMR are in the same document as CDR field definitions: http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_2/4_2_1/cdr421.htm#wp34650 Guides for other CallManager versions can be found here: http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/ Just check out the Call Detail Record Definition document for the particular version of CallManager that you are interested in. The dateTimeStamp field of CMR is in the same format as the timestamp fields from CDR (such as dateTimeOrigination, dateTimeConnect) etc, so you can search on that field, and the directoryNumber field contains the extension that the CMR record is for. You can relate the CDR and CMR using the globalCallID_callManagerId and globalCallID_callId fields though you may want to use the timestamp fields as well if you need to be exact, since those fields are reset when CallManager resets, so they aren't unique within the table/database. ... View more

It sounds like the insert service can't find the CDR database. Check the CDR settings in Enterprise Parameters - there are settings there to configure how CDR is handled, where it is stored, etc. Maybe the CDR UNC path was changed for some reason and is wrong? ... View more

The admin username is CCMAdministrator (in my experience), and the password for CCMAdministrator is set during installation. You should be able to log into the console and use the CLI to change the password. ... View more

Did you enable CDR on both CallManagers? In Serviceability check the CDR Enabled flag for each of your two CallManagers and make sure it is set to "true". If CDR is enabled on both CallManagers: Are there csv files building up in your C:\Program Files\Cisco\CiscoCDR (not sure if that's the exact directory name offhand, but it's close!)? If so, perhaps your CDR Insert service is not enabled? The CDR Insert service reads CSV files sent from the subscribers in CSV format and inserts them into the CDR database. ... View more

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. ... View more

Yes, when a user is defined with the super-provider flag, that user has access to all phones. Note that there are some differences when connecting as a super-provider. First, you can't enumerate through the terminals - you need to know the device name and use createTerminal() rather than getTerminal(). Cisco says this is to be less resource-intensive when using super-providers. Your code can detect if you're connected as super-provider with something like the following: // detect connection type (super-provider or regular) boolean superProvider; CiscoProviderCapabilities provCap = (CiscoProviderCapabilities)provider.getCapabilities(); if (provCap != null && provCap.canObserveAnyTerminal() == true) { superProvider = true; } else { superProvider = false; } // Now that you know your connection type, use one // of two methods to get the terminal (assuming deviceName holds the name of the device) String deviceName = "SEP00304502ECDE"; CiscoTerminal targetTerminal; if (superProvider) { targetTerminal = provider.createTerminal(deviceName); } else { targetTerminal = (CiscoTerminal) provider.getTerminal(deviceName); } So the super-provider functionality is quite useful, but there are some things to watch out for. Note that createTerminal is provided by CiscoProvider, and the above code assumes that the provider variable is of type CiscoProvider. ... View more

Please see your original post for a reply: http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=IP%20Communications%20and%20Video&topic=IP%20Telephony&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddae02a ... View more

A DN starting with 'b' designates a conference bridge (i.e. 'b' for Bridge). You should only see these numbers in the finalCalledParty field (though you may see it in originalCalledParty as well, in some instances). When you see this type of number (starting with a 'b') in the finalCalledParty field, that means that this call record identifies the extension or phone number in the callingPartyNumber field calling into a conference bridge for a conference call. This is quite common, and nothing to be worried about. See the following document for additional information on CDR fields: http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_1/4_1_3/cdr413.htm From the above CDR specification, this section: http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/4_1/4_1_3/cdr413.htm#wp61027 discusses conference calls. Note the 'b' in the conference bridge portion. ... View more

I agree with Stephan - you'll need to explore the Lotus Notes APIs to find out what's available. One protocol that is likely to be available is LDAP, and another may be JavaMail. Of course, you'll also want to learn how to create Cisco IP Phone applications - follow Stephan's link and get the SDK to get familiar with Cisco IP Phone development. You'll probably want to obtain the Lotus Notes java library, though if you find out where that is, let me know! My guess is that it is obtained from a Lotus Notes install, much like Cisco's jtapi.jar is obtained from downloading a plug-in from CallManager. Here are some links that might be of use: Here's IBM's Lotus Developer page: http://www-128.ibm.com/developerworks/lotus This site has API examples for notes, though written in C: http://www.nsftools.com/tools/apisamples.htm Using Lotus Notes with Eclipse to manage and run your Java programs: http://www-128.ibm.com/developerworks/lotus/library/notes-eclipse/ Introduction to the Java Mail API (see second paragraph of second page where the author discusses how to adapt the example to Lotus Notes) http://www.javaworld.com/javaworld/jw-06-1999/jw-06-javamail.html jGuru JavaMail FAQ Home Page: http://jguru.com/faq/home.jsp?topic=JavaMail&page=3 devx.com: A Lotus Quick Tour http://www.devx.com/ibm/Article/19939 ... View more

There is no way to remove the globe icon that I am aware of - the globe signifies that it is an XML Service (like a WWW icon or something along those lines) as opposed to a speed dial button... Too bad we don't have control over that (at least, I am not aware of any way to control that behaviour, my guess is that it's built into the phone's firmware). ... View more

This is somewhat unrelated to the discussion, but may be somewhat relevant in any case :) I recall talking to a Cisco engineer about the new video capabilities where the Cisco vidcam connected to the PC would only work when the pc was connected to the phone via the phone's PC port, and that this created some sort of special relationship between the pc and the phone. I don't know if it communicated with the phone via CDP or what (that's just a wild guess). I never looked into the details or thought much of it, but thought it was interesting and I'd be interested to hear what others might have heard/experienced along these lines... (I have not yet played with the video cam with CallManager, not sure if others have and have any experiences to share in this regard?) ... View more

Unless you need the name of the "speed dial" beside the line/feature button, you could consider adding one or more instances of a service to the line/feature buttons. You would need to change the phone button template to add one or more service URLs to the phone so that services can be assigned to those line/feature buttons. Then, when the user selects that line/feature button, it calls your service, which can make a call on behalf of the user using jtapi. This way the number that is called can be dynamically determined, as you mentioned you wanted. Of course, the name of the service ("custom speeddial" or whatever) will always be listed beside that line/feature button, but at least you can customize what happens when the user presses that button at run-time... http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803edaff.html ... View more

What happens if you try calling the service from a web browser? You should see a bunch of Cisco XML, such as CiscoIPPhoneText or CiscoIPPhoneMenu, etc. So when you press the services button, you get some type of raw XML, such as: ... Is that correct? What is the URL of your service URL? What is the URL for your IDLE URL? If they are .xml files, then you probably have to add the .xml mime type to the CCMCIP virtual directory in IIS Manager, and map .xml to text/xml. ... View more

I think managing SoftKey:Exit, SoftKey:Cancel, and Cisco's service history stack are a bit of a voodoo :) I would suggest using SoftKey:Exit instead, and see if that works better for you... ... View more