I have a customer with many TP endpoints (EX90, MX300, C40/60, CTS500, CTS1300, CTS3000/3200, TX1310, TX9000 and TX9200). My network management server is pulling call detail records directly for each endpoint with the exception of the TX line of endpoints.
I know that the TX endpoint line is the successor of the CTS endpoint line and I believe is still MIB driven as well. I know that the CTS endpoint latest code via CCO is v.1.9.7(33). But I have also noticed on CCO that there is a 6 series, e.g. v6.0.3(33), v126.96.36.199, etc.
My question is, do the TX Series endpoints strictly deploy to the v6.X code and, if so, are the TX endpoints MIB driven, e.g. CISCO-TELEPRESENCE-CALL-MIB.
I am trying to figure out how to pull call detail from the TX endpoints...
Your attached link did not assist with my inquiry. Why would CTS endpoint respond to a specific OID, ctpcLocalSIPCallId, for example...and the TX endpoint not responding at all. I have SNMP access to both types of endpoints.
So there is no other MIB changes or additions for the TX endpoint line? The latest MIB CISCO-TELEPRESENCE-CALL-MIB, dtd
I just did an snmpwalk on my TX9000 in a call with a CTS3000 and they looked fairly similar (including ctpcLocalSIPCallId, .188.8.131.52.184.108.40.206.6220.127.116.11.1.11). The TX9000 is running 1.9.x right now however, it could be an issue with TX6 code.
Also do you have SNMP enabled on the TX9000? If I recall correctly, CTSs have SNMP v2c enabled by default, TX endpoints have SNMP disabled by default. Can you upload the output of an snmpwalk on a CTS vs. TX?
Tyler, in the CLI of a TX9200...I have attached 'show version' as well as 'utils service list'. SNMP service is RUNNING state. I am in the CTS Admin for the TX9200 for the first time...maybe the customer just enabled SNMP...just starting my discovery process with these devices. Things seem to be OK.
To get you up to speed since I created this post...Call Detail is now being collected...minor code issue. Not the endpoint issue.
I will reach out if there are any other issues that I see moving forward...thx.
It's possible that SNMP_Srvr was killed due to a memory issue. Sometimes it dies if something is wrong with the monitoring tool (ie too many SNMP gets too quickly). How often are you doing SNMP gets? Can you upload a set of logs so we can look at the memory? Specifically the sysm logs would tell us if that's what killed the process.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...