Config Archive for Call Manager

Hello,
It give me the attahced error fo r config archive for call manager.

The supported devices page shows each supported device, and what features are supported:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html

Similar Messages

Phone License for Call Manager express

Dears ,
Is the phone license required for Call manager express or the license on the voice gateway enough for operating the phones ?
Regards,

Hi Ian,
I think I may have given you some bad info here. Sorry about that
Right to Use Feature Licenses
The following licenses do not Cisco software activation and you can begin using the features upon receipt of the Right to Use Notification
Feature License Name
Prerequisites
License Types
CME
IP Base & UC
Feature (Counted)
SRST
IP Base & UC
Feature (Counted)
VXML Gateway
IP Base & UC
Feature (Counted)
CUBE
IP Base & UC
Feature (Counted)
Land Mobile Radio
IP Base & UC
Feature
You should be good to go. But a quick note to
[email protected]
would be a fair idea.
Cheers!
Rob

Need to take MIB File for Call Manager

Hi,
Can anyone help me how to take MIB file for Call Manager. We have a cluster of 6 CUCM servers (1 pub + 5 Sub). we need this MIB file for monitoring purpose. If you need anyother information regarding this please let me know.

Hi
Below MIBs are supported in CUCM. Refer the link attached for details. Btw which Version are you running ?
•CISCO-CCM-MIB
•CISCO-CCM-CAPABILITY
•CISCO-CDP-MIB
•CISCO-SYSLOG-MIB
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/managed_services/cisco_mibs.html
Thanks.

7975 firmware for call manager express

i would like to add 7975 phone to call manager express.
where do I get the firmware for 7975 for cme?
i tried from software.cisco.com but it's for call manager only.

Hi pranavluhar,
check this link cme-153-3Mv2.rar (in 10.0 option).There is a 7975 version for CUCME.
Hope this helps.

Config archive for Cisco 4404 WLC devices

Nodes are discovered properly, with the correct icon, and inventory updated.... but when we try to download config, we got:
*** Device Details for XXXXXXX ***
Protocol ==> Unknown / Not Applicable
Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS
Execution Result:
Unable to get results of job execution for device. Retry the job after increasing the job result wait time using the option:Resource Manager Essentials -> Admin -> Config Mgmt -> Archive Mgmt ->Fetch Settings
We have configured only HTTPS credentials, because others are not permited, isn't it?
Telnet through port 22 works fine (i have read about https://supportforums.cisco.com/message/3053616#3053616)

in dcmaservice.log:
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchive,1941,Sync Archive for 4 devices - Sync Archive
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchive,1955,Number of devices in fetch Q = 0
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,addToDeviceIdToReqIdMap,2289,Device Id 7 already in Q
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-7
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :6
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS101
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-10
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :7
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS102
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,addToDeviceIdToReqIdMap,2289,Device Id 6 already in Q
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-7
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :6
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS101
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-7
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :6
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS101
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-10
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :7
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS102
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveIfRequired,2055,Compared the device with running thread devices.Adding to Fetch Q
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,59,inside compareDeviceWithDevicesinRunningThreads method
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,60,Total running threads:5
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-7
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :6
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS101
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,65, Running Thread Thread-10
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,67,Device Id :7
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,compareDeviceWithDevicesinRunningThreads,68,Device Name :PEDRWLS102
[ Wed Sep 01 15:54:34 CEST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveIfRequired,2055,Compared the device with running thread devices.Adding to Fetch Q

MOH Sources for 2 800 #'s for call manager

Hey all,
How would i go about configuring 2 MOH sources for 2 different 800 numbers coming into call manager?
Im stuck at trying to find the location in call manager where the 800 numbers are configured?
Where abouts would you be able to see what incoming pri configurations are in call manager or am i looking in the wrong place.
Bascially, i want to use a different MOH source file for a second 800 number.
Thank you everyone!

What you translate is dependent on what the telco is sending you and the value configured for Significant Digits in the gateway configuration. If the telco sends you 10 digits and the Significant Digits field is set to All, then you would translate the entire 800 number.
For Unity, you configure MOH using the device pool of the Unity ports. You can configure the device pool under System -> Device Pool and assign the device pool to the Unity ports under Feature -> Voicemail -> Cisco Voice Mail Port. So, to have 2 different MOH sources for your 800 numbers, you would have to have 2 device pools assigned to 2 sets of voicemail ports and ensure that the numbers get translated to a hunt pilot that uses the proper ports.
Brandon

API for Call Manager Backup

Hello All,
Is there any API available to take the back up from Cisco Call Manager (ranging from the version of 4.0 up to 7.0). My aim is to develop an application either in .NET or Java to take the back up from the call manager and restore the same.
I could get some information on Cisco Back up utilities. But for the automation purpose I am looking for using API in application so that it can be triggered at the desired time automatically.
Thanks and regards,
Ram

Hi Ram,
You may want to post this question under "IP Telephony" community. This is where call manager questions are posted.
thanks,
Hitesh

Unfied Meetingplace for Call Manager Express??

Hi! I was told that Meetingplace express is being End Of Life, can you tell me if I can install the recommended Unified MeetingPlace for a new Call Manager Express 8.0install? If so, can use a use a MC7825 server and licenses but what licenses?!?! I'm a little lost here...
THANKS in advance

can you tell me if I can install the recommended Unified MeetingPlace for a new Call Manager Express 8.0install?
Yes with limitations per the SRND: http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/srnd/8x/confernc.html#wp1057454
If so, can use a use a MC7825 server
No. You need at least an MCS7835: http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Release_8.0_--_System_Requirements_for_Cisco_Unified_MeetingPlace_Release_8.0#Table:_Supported_Cisco_MCS_and_Third-Party_Equivalent_Servers_for_the_Application_Server
licenses but what licenses?
I hope you have UCSS coverage left on MPE. The problem is that MP8 and beyond are no longer stand-alone systems; they all require WebEx for the web conferencing. MP8 only provides audio/video conferencing. If you have a WebEx Node for MCS you also get an inside-the-firewall WebEx cloud attachment point for clients. A WebEx contract is required though. Remaining UCSS coverage should provide you that for free through the conclusion of the contract.
Oh, and MP8 starts at 200 ports. Most MPE customers probably are a better fit for straight-up WebEx MC.
http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Release_8.0_--_Licenses_for_your_Cisco_Unified_MeetingPlace_System

Acceptance Critria for Call Manager

Dears
I need a help for a template for acceptance critria for all function can be tested throgh the call manager

The supported devices page shows each supported device, and what features are supported:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html

What is the best cisco ip phone for call manager and ipcc practicals

Hi i have recently started my training on Cisco Call Manger and CCIE voice from a leading cisco voice training institute (http://networkerszone.com/), and am working on 7900 series phones, is there any other phone that i should use or this is fine.

Naval,
7900 phones are good enough for both CUCM & UCCE. UCCE however doesnt support all models of 7900 series, please refer UCCE Compatibility Matrix for supported phone models.
You may also use CIPC as agent phone.
GP.
Pls rate the post if it helps !!

Menu.asp for call manager express

i would like to have multiple services for phones with cme, but you can only enter one url for services with cme, has someone written a small menu.asp that you could point at, then would give you a selection of services to chose from, i.e weather, stock tick, etc

Hi Ian,
I think I may have given you some bad info here. Sorry about that
Right to Use Feature Licenses
The following licenses do not Cisco software activation and you can begin using the features upon receipt of the Right to Use Notification
Feature License Name
Prerequisites
License Types
CME
IP Base & UC
Feature (Counted)
SRST
IP Base & UC
Feature (Counted)
VXML Gateway
IP Base & UC
Feature (Counted)
CUBE
IP Base & UC
Feature (Counted)
Land Mobile Radio
IP Base & UC
Feature
You should be good to go. But a quick note to
[email protected]
would be a fair idea.
Cheers!
Rob

Microsoft Patches for Call Manager

HELP !!
Where do I find the "approved" Microsoft patches for CCM4.x please ?
Regards
Scott

Hi Scott,
You will need a valid CCO account (which I guess you've already got). Then just go to the support section on the Cisco website, choose "download software", then just specify your CCM version etc. and you will see all the patches available.
Cisco guarantees that they will release any critical operating system patch within 24 hours of the Microsoft announcement. Noncritical patches are rolled up into a monthly update.
Please rate if useful....

Call Manager 9.1 Active Directory Question(s)

Hello All!
Firstly let me establish that I am not an administrator of our VoIP system however I do manage the Server side of our network. We are in the process of planning an Active Directory upgrade and I'm having some difficulty getting a question answered about the requirements for Call Manager. We are at version 9.1 of Call Manager currently with our Active Directory version at 2003 R2. We are planning to upgrade to Active Directory version 2008 R2 (functional level) however we would like to use Server 2012 R2 as the OS for our AD servers. From a Microsoft standpoint this is a valid solution, it's built into Active Directory that you can run at different "functional levels" of AD on higher server operating systems. Any Call Manager applications that require a Windows operating system would run on whatever works for that (2003 or 2008 etc). Can we use Server 2012 R2 as the Domain Controller operating system while running at 2008 R2 functional level for Active Directory and still retain our Cisco support?

Hi Allen,
This is from Cisco site (you already may have seen this), though it talk about the directory services but it is specifically mentioned 2008. 2012 may work and specially as you are saying with functional level set to 2008 shouldn't have any issues. But Cisco have not tested that and you may get into support issues (if any).
Its completely tested and supported with CUCM 10.X
Version 9:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_0_1/ccmsys/CUCM_BK_CD2F83FA_00_cucm-system-guide-90/CUCM_BK_CD2F83FA_00_system-guide_chapter_010011.html#CUCM_TK_C4E65231_00
Configure LDAP directory
If you want to do so, you can add users from your corporate directory to the Cisco Unified Communications Manager database by synchronizing the user data to the database. Cisco Unified Communications Manager allows synchronization from the following directories to the database:
Microsoft Active Directory 2000
Microsoft Active Directory 2003
Microsoft Active Directory 2008
Microsoft Active Directory Application Mode 2003
Microsoft Lightweight Directory Services 2008
iPlanet Directory Server 5.1
Sun ONE Directory Server 5.2
Sun ONE Directory Server 6.x
OpenLDAP 2.3.39
OpenLDAP 2.4
Terry

Cisco Call Manager 9 ELM question

Hello everyone!
We start using ELM for Call Manager Licensing and I just can not understand they way it works. I am used to DLUs and can not undertand the new scheme
Just to make is clear:
We have
Enhanced (9.x) - Unified CM Available - 180 Installed
Does it mean we can register 180 IP phones?
And we also have
Used - 8, Required
What is meant by Required?
Thank you!

It means you are entitled to 180Enhanced UCSL users (users with up to 2 devices), you have 18 such users currently provisioned and 132 still available. This does not mean you can have 180 such devices, it means you can have 180 users with 2 devices such as phone or softphone assigned to them or any 79XX, 89XX, 99XX phones.
The 21 and 9 are basic (69XX phone) and essential (3905, 6901 phone), since you don't have any of these licenses, they are being borrowed from the upper tier.
HTH,
Chris

Call Manager/LMS 3.2 Integration

Hello,
I am building CiscoWorks LMS 3.2 from scratch and my two Call Managers come up as unreachable devices. I've done some searches and found plenty of Cisco documentation speaking about CDP settings for Call Manager but nothing that tells me where to view it or change it. Can someone tell me what menus I should be looking at in Call Manager in order to verify the SNMP settings?
Any other reason CiscoWorks would be unable to reach these CMs?
Thanks,
Mike

if the CallManager is marked "unreachable" it is not a problem with CDP. CDP is necessary to find the hardware - this step passed (because it is listed). The next thing that must work is SNMP reachabiliy and this fails. So either the Call Manager has no SNMP community configured or LMS does not know the correct community to use.
If both are ok, access-lists or firewalls are typically blocking SNMP traffic.
here is the documentation for the Call Manager that covers this
Simple Network Management Protocol Configuration
see the section Configuring SNMP Security

Config Archive for Call Manager

Similar Messages

Maybe you are looking for