Created by: Roshin Thovarai on 14-06-2010 07:54:08 AM Hello,
We are currently using TMS Management API to collect Information on Tandberg Endpoint details and status. Would like to know the following details.
- What is the level/extent of QOS/Latency/ Packet loss/ Jitter data that TMS collects from the n/w or devices? - Is there a TMS API or any other way we can get this information either from TMS or Tandberg Endpoints directly ? - What are the Mibs supported by C90,C60 Codecs and Codian devices?
Thanks,
Roshin Cisco
Subject: RE: TMS API for QOS Replied by: Torgeir Johansen on 14-06-2010 08:41:47 AM Roshin,
I'll try to answer your questions, if you need more information, just ask :
- data regarding jitter/packet loss etc. are sent from the endpoints and collected in TMS at call end, typically represented as aggregated data (# of packet lost) or median/mean data (jitter level). The level of support and type of data is of course dependant of the endpoint type. Ie. for the Calypso endpoint range we collect audio and video jitter levels, audio and video duration loss levels, audio and video packets lost and audio and video packets dropped
- As of now, we have no supported public API for showing the mentioned data from TMS other than in the Reporting -> Network -> Packet Loss Log page in TMS. It is possible to probe the endpoints directly for these numbers after call end using the CUIL interface. For instance, for a Calypso (F software only) endpoint, you can either post a XML command over HTTP to the endpoint, or using telnet/ssh probe values like: ** AFTER the call is disconnected the CUIL command "xhistory Call [1..20]" will generate a report covering the mentioned jitter and packet drop/packet loss
- I'm not sure about which MIBS we use for the C series/Codian devices. If no one from the endpoint team replies this, I can certainly find out.
Regards,
Torgeir
Subject: RE: TMS API for QOS Replied by: Roger Boe on 14-06-2010 09:34:50 AM
Torgeir Johansen:
Roshin,
- I'm not sure about which MIBS we use for the C series/Codian devices. If no one from the endpoint team replies this, I can certainly find out.
Regards,
Torgeir
I'm able to provide an answer for the Codec part.
We don't support any corporate MIBs on the C-series codecs. So there is no possibility to get information from SNMP regarding packet loss, calls etc. We only support the basic standard functionality in SNMP V2:
We only support these OID's (described in RFC1213): 1.3.6.1.2.1.1.1 1.3.6.1.2.1.1.2 1.3.6.1.2.1.1.3 1.3.6.1.2.1.1.4 1.3.6.1.2.1.1.5 1.3.6.1.2.1.1.6 1.3.6.1.2.1.1.7
(sysDescr, sysObjectID, sysUpTime, sysContact, sysName, sysLocation, sysServices) No support for traps.
We have moved away from SNMP in favour of HTTP/S traps. The SNMP protocol has a lot over weaknesses and security issues, which we don't have when using HTTPS.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
