SNMP call manager 6.x

Does anybody has any information of using CCM 6.0 MIBs

could you let us know what exactly you need from
CCM 6.x mibs ?

Similar Messages

Snmp traps with Call Manager 4.13

Anyone being able to get snmp traps from Call Manager 4.13 to work. I can walk the MIB and get snmp cold start traps but no Call Manager specific traps

There is a possibility that the CCM service controls this trap and thus cannot send a trap until it is up. This is an issue seen in many devices not just CCM. CCM supports only certain traps.Refer the following URL for more information
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803f52e1.html#wp1041935

Call Manager - SNMP - Call InProgress

Hi there,
I would like to know if somebody have the OID for call InProgress in Call manager,
I'm running
6.1.1.2000-3
with snmp v3
also, do you have the CPU % OID ?
thanks a lot : )

See this post.
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=General&topicID=.ee6c82b&fromOutline=&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cc26b08
Jesse

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

Connectivity Issue between ASA 5520 firewall and Cisco Call Manager

Recently i have installed ASA 5520 firewall, Below is the detail for my network
ASA 5520 inside ip: 10.12.10.2/24
Cisco Switch 3560 IP: 10.12.10.1/24 for Data and 10.12.110.2/24 for Voice
Cisco Call Manager 3825 IP: 10.12.110.2/24
The users and the IP phone are getting IP from the DHCP server which configured on cisco 3560 Switch.
the Default Gateway for Data user is 10.12.10.2/24 and
for the voice users is 10.12.110.2/24
now the problem is that the users is not able to ping 10.12.110.2 call manager. please if somebody can help in this regard. i will appreciate the prompt response against this issues.

Actually i don't wana to insert new subnet and complicate the nework. i need a simple way to solve the problem. below is the details for the asa 5520 config.
ASA Version 8.2(1)
name x.x.x.x Mobily
interface GigabitEthernet0/0
nameif inside
security-level 99
ip address 10.12.10.2 255.255.255.0
interface GigabitEthernet0/1
nameif outside
security-level 0
ip address x.x.x.x 255.255.255.252
object-group service DM_INLINE_SERVICE_1
service-object tcp-udp
service-object ip
service-object icmp
service-object udp
service-object tcp eq ftp
service-object tcp eq www
service-object tcp eq https
service-object tcp eq ssh
service-object tcp eq telnet
access-list RA_VPN_splitTunnelAcl_1 standard permit Inside-Network 255.255.255.0
access-list RA_VPN_splitTunnelAcl standard permit Inside-Network 255.255.255.0
access-list inside_nat0_outbound extended permit ip Inside-Network 255.255.255.0 10.12.10.16 255.255.255.240
access-list inside_nat0_outbound extended permit object-group DM_INLINE_SERVICE_1 10.12.10.16 255.255.255.240 Inside-Network 255.255.255.0
access-list inside_nat0_outbound_1 extended permit ip Inside-Network 255.255.255.0 10.12.10.16 255.255.255.240
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
mtu mgmt 1500
ip local pool VPN-Pool 172.16.1.1-172.16.1.30 mask 255.255.255.0
ip local pool VPN-Users 10.12.10.21-10.12.10.30 mask 255.255.255.0
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-641.bin
asdm history enable
arp timeout 14400
global (inside) 2 interface
global (outside) 1 interface
nat (inside) 0 access-list inside_nat0_outbound_1
nat (inside) 1 Inside-Network 255.255.255.0
route outside 0.0.0.0 0.0.0.0 Mobily 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http Mgmt-Network 255.255.255.0 mgmt
http Inside-Network 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map outside_map interface outside
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
crypto isakmp policy 30
authentication pre-share
encryption 3des
hash md5
group 2
lifetime 86400
telnet Inside-Network 255.255.255.0 inside
telnet timeout 5
ssh Inside-Network 255.255.255.255 inside
<--- More ---> ssh timeout 5
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
group-policy RA_VPN internal
group-policy RA_VPN attributes
dns-server value 86.51.34.17 8.8.8.8
vpn-tunnel-protocol IPSec
split-tunnel-policy tunnelspecified
split-tunnel-network-list value RA_VPN_splitTunnelAcl
username admin password LPtK/u1LnvHTA2vO encrypted privilege 15
tunnel-group RA_VPN type remote-access
tunnel-group RA_VPN general-attributes
address-pool VPN-Users
default-group-policy RA_VPN
tunnel-group RA_VPN ipsec-attributes
pre-shared-key *
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect netbios
inspect rsh
inspect rtsp
inspect skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect tftp
inspect sip
inspect xdmcp
service-policy global_policy global
prompt hostname context
Cryptochecksum:e5a64fa92ae465cd7dabd01ce605307d
: end

Call Manager - Phone register & unregister

How can we be informed if a phone unregisters from call manager? Can we see it in the Real Time Monitoring Tool or snmp ?
Thanks

Wrong, there is still app log in any linux appliance.
You access it thru RTMT
HTH
java
if this helps, please rate

Hi Team, I wuold like to know if you have any app to make Firefox OS working with cisco Call Manager 10.5. Something like Cisco Jabber for Android or iOS.

I'm interesting on buying a Firefox Smart Phone, but
I would like to know if are any app to install on Firefox OS smart phone in order to work with cisco call manager 10.5.
Something like Cisco Jabber for Android o iOS.
Thanks,

Hi Itech,
If Cisco Jabber has a webapp, or mobile version of their website available, you should technically be able to access it through Firefox OS.
You may also search Firefox Marketplace for an alternative solution:
* [https://marketplace.firefox.com/]
- Ralph

Call Manager 8.0 to 9.1 upgrade

We are currently running Call Manager 8, UCCE 8, and CVP 8. ICM/CTI 8.
We would like to upgrade Call Manager 8 to 9.1 first before upgrading UCCE, CVP, etc., it could be months before these are upgraded.
Does anyone know or foresee any issues if UCCE, CVP, etc., are not upgraded right away after CM is upgraded?
Any comment is appreciated. Thanks.

Look at the UCCE compatibility matrix as you need the exact versions to find out whether they will work together, of ir you'll need a single window on which to upgrade all.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

Just downloaded Sales Call Manager App...I can't get it to work on either my Iphone 4S or My Ipad 2?

Downloaded the App Sales Call Manager. I can't get it to work on either my Iphone 4s or my Ipad2? Can anybody advise how to fix or even get back my money that i paid for it?

Contact the app developer for support. A link to their website will be in the apps description in the AppStore.

Upgrade Call Manager from 8.6.2 to 10.5

Hello All,
We are planning to upgrade a Cisco Call Manager Publisher node from 8.6.2 to 10.5. We want to install a new publisher on a new environment, but we are struggling with some questions.
If we install the Pub node 10.5 can we migrate the configuration from the 8.6.2 to 10.5? Do we need a special tool for this?
If above doesn't work, we can still migrate the existing call manager towards the new servers and start the upgrade, the only problem we face there is that we have to change the publisher's IP because we want to use a new ip addressing scheme.
Kr,
Yannick Vranckx

Your best bet is to use the new tool: cisco prime collaboration deployment. This fits perfectly into what you want to do here and can easily help you with all aspect of the migration including the ip address change. You can learn how to use the tool here..
https://www.youtube.com/watch?v=JzG4kz1_hL4

What are the essentials needed before upgrading from call manager 9.1.1 to call manager 9.1.2?

I recently tried to upgrade my call manager in a lab environment from 9.1.1 to 9.1.2 but failed. The error stated that connection had been lost after 2 hours into it. Connect using CLI. Any help would be greatly appreciated.
Steve

You mean via GUI??
What does the upgrade status via CLI says??

Call Manager Migration 7.1.5 to 9.1 / Trunking : ICT vs. SIP

Hello All,
Currently studying for CCNA Voice and have been asked by my current employer to upgrade CUCM 7.1.5 to 9.1.1. There has been a time frame put on the deployment however I want to dig pretty deep into the deployment to learn as much as possible. I am going to start by configuring a trunk between the 2 call manager clusters. from there I will add users to the new call manager and try to convert slowly to the new call manager instead of one big cutover. I will place a route pattern over the trunk so that cucm 9.1 will route through cucm 7.1 while I slowly convert users to the new system. I will then deploy directory numbers in a Staging partition that is not associated with any CSS. Once I have all users and phones configured on the new 9.1 call manager I want to use the bulk admin tool to change the staging partition to the working internal_PT production partition. The users will be imported from LDAP. My questions are, does this sound like a feasible plan? Is there any other difference between a SIP trunk and ICT besides the SIP and H.323 protocol? ( I prefer SIP from what I have read) and will having the same users on both boxes interfere with call processing, if these users and phones are not active yet?

Just for the record. I found the solution to my problem. Checking more logs I read this:
The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.
"/usr/local/cm/script/cm-dbl-ontape_backup-install RU PostInstall 9.1.2.11900-12 7.1.5.30000-1 /usr/local/cm/ /common/component/database /common/log/install/capture.txt " terminated. Exceeded max time (240)
The system will now halt.
So I accessed the Dissaster Recovery Section on CUCM and deleted the tape backup device that was configured there. After deleting it the upgrade went well.

Can't remove registered ephone in call-manager-fallback

This ephone and dn keeps registering so long as call-manager-fallback is not shutdown.
RTR001#show ephone registered
ephone-1[0] Mac:0FD4.9DA0.D415 TCP socket:[1] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 6/5 max_streams=1
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:7
IP:10.32.21.183 * 26602 SCCP Gateway (AN) keepalive 4 max_line 2 available_line 1 dual-line
port 2/0/21
button 1: cw:1 ccw:(0)
dn 2 number 4851 CM Fallback CH1 IDLE
Preferred Codec: g711ulaw
Lpcor Type: none
The MAC 0FD4.9DA0.D415 identifies port 21 on a Cisco VG224. After shutting down that voice-port, the ephone doesn't register when call-manager-fallback is enabled.

Well, that is one idea that I've already had, Linc, but I'm reluctant to use the "nuclear option" for obvious reasons. I'm actually wondering now if the Secure Cert / OD problem is affecting Profile Manager. See this thread: https://discussions.apple.com/message/23686348#23686348

Error in Cisco call manager

Hi, I just installed the IPCC exprss in my call manager publisher. No error during the instalation.
But I got a error message in even log.
Cisco desktop enterprise
type: Information
Event ID: 2
SS3101 setup monitor failed connection failed, end

Please make sure that the Jtapi and Rmjtapi service users are ok (users password must be consistant with what you have within CallManager)

CDR FIles in Call Manager version 7.1.5-30000

Good Morning:
I have a cluster of servers Cisco Call Manager version 7.1.5.30000; 01 Publisher and 02 subscriber. The publisher server passes CDR files to a call accounting application PC-SYSTEL on another server. At one point the CDR files are no longer spend the Call Manager to the application PC-SYSTEL
Call manager services are reviewed, the part of CDR Management in Cisco Unified Serviciability right. The only solution is doing a RESTART to PUBLISHER server, and then again go CDR files to the application PC-SYSTEL
Please anyone has any solution other than to give a RESTART PUBLISHER server, or is this the only way to restore this service.
Expect your news.
Thanks in advance for any ideas.
Regards.
Fernando.

Hi Fernando,
Please check the following.
(1) Confirm that the billing server is configured correctly (verify the IP address). From the Cisco Unified Serviceability page, navigate to Tools > CDR Management to view the billing server parameters.
(2) Check if you can ping the billing server from the Publisher. From the Publisher CLI, you can use the following command:
utils network ping a.b.c.d
where a.b.c.d is the IP address of the billing server
(3) Check if the FTP (or SFTP) service/software running on the billing server.
(4) Check if the billing server is running out of disk-space.
(5) Check if the CDR Respository Manager service is running on the Publisher. If not, start the CDR Repository Manager service.
(6) On the Publisher, check the 'preserve' and 'destinationX' (X can be 1, 2 or 3) directories for CDR flat files. For example: if transfer of CDR files to billing server is broken from Jan 6th, then use the following commands:
file list activelog /cm/cdr_repository/preserve/20110106
file list activelog /cm/cdr_repository/destination1/20110106
(if multiple billing servers are configuration, the location will be similar to above, but the corresponding directories will be named destination2, destination3). This location contains symbolic links to files under preserve. CDR Repository Manager service uses these soft-links to determine what files need to be transfered to billing server.
If you don't observe files in either the 'preserve' or the 'destinationX' locations for the specific date, then it means that problem does not reside on the Publisher. Either the CDR records were not generated by the server that handled the call or it could mean that CDR Agent service on that server could not transfer flat files to the Publisher. Was the 'CDR Enabled Flag is enabled in CallManager service' enabled on that particular date ? Is the CDR Agent service running on the node that handled the call ?
If you observe files in the 'preserve' directory for the specific date, try restarting the CDR Repository Manager service on the Publisher. If the file transfer to the billing server does not commence, then set the trace level for the CDR Repository Manager service to Debug, wait 10 minutes, download CDR Repository Manager logs via RTMT and engage Cisco-TAC for further troubleshooting.
HTH
Manish

SNMP call manager 6.x

Similar Messages

Maybe you are looking for