You can get the total available ports and their modes with device.query, then do some calculations…
With current versions of MCU (API version 2.8) there isn’t a direct way of getting these information via the API. However it is possible to get port usage information by doing some calculation.
You can use ‘participant.enumerate’ command with filter ‘connected|connecting’ to get all active participants on the MCU. Then you can count the number of videoTxCodec(not none) /audioTxCodec(not none) /contentTxCodec(not none) in ‘currentState’ struct to get all the ports used.
You then need to compare the number of audioTxCodec and videoTxCodec, if the number of audioTxCodec is greater than the number of videoTxCodec it means there are audio-only participants.
But the TMS Bridge Utilization Report does not separate between video and audio only calls.
As we use our 4520 bridges for phone conferences also, this would be very helpful if Cisco could update the reports for that szenario also.
And to enhance the missing API calls, we have this problem also. Compared to a simple API calls about MCU resources its a huge amount of API calls and calculating to get all MCU resources because its no so easy as it seems. For example to calculate the right video port usage you must look if a video codec is in use, if there is H.239 or streaming in use. And, calculation of that depends also from "Media port mode" settings.
Thanks Adam. This is definitely one way to do it. Are there any plans for the API to contain a more direct query of this information? It just seems odd that it provides totalVideoPorts but then no subsequent totalVidePortsInUse or something of the like. Likewise, totalAudioPortsInUse, totalContentPortsInUse, etc could be used..
Because of this issue, we are currently using the Status--->> Conferences screen and doing an HTML "screen scrape" to pull the Ports in use information directly from that page. As wew know that page could change in future version, we would like to see this information available through the API.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...