I have a few issues I've been seeing with TMS/C-series codecs and the touch panel.
The first issues we have been seeing issues with the directory on the touch panels. It started with phonebooks disappearing, usually searching the directory would still provide results but without searching the list would just be empty.
The second issue is that TMS seems to loose random endpoints. TMS shows them as offline, "No HTTP response" or "No SNMP response". The reality is that the endpoint is online and has a new IP. If I manually input the new IP in TMS, all is well for a while.
In both of those cases, I've looked at the codec and noticed that references to Phonebook server and external manager point to the FQDN of my TMS server. I have manually changed on the codec and update all tempates on TMS to use IP instead of FQDN hoping to fix the issue. The problem is the IPs I enter manually on the codec revert back to the FQDN at some point, I'm not sure where this is coming from. I'm hoping someone can shed some light on that.
The last issue is that the touch panels seem normal to touch, however not only is the directory empty the self view and camera controls do not work. If you try to make a call, a message is displayed saying the call can't be placed. The touch panel still thinks it's paired to the codec and vice versa. If you unpair it using the menu on the touch panel and use a remote control, the codec works perfectly. Repair it and you're back to not working. We have added a second account to these codecs for use with pairing the remote so that we don't have to give users our administrator password. The account was given Admin and User roles, this has been working fine. Now, seemingly out of the blue I had to add the audti role to this account in order to solve the last issue. Without that role, the touch panel would pair but would be in the same state I just described. Once the audit is added it works.
If anyone can shed any light on any of these issues I'd be very greatful!
I guess you are using DHCP for your endpoints which can make it hard for TMS to keep track of the system, what is the TMS tracking the system by? IP/MAC/Hostname?
You see that the phonebooks / external manager uses FQDN, this address is coming from the TMS and its the address you have typed in the "Network settings" in TMS. if you remove the FQDN and only leave the IP TMS will push the IP only. FQDN is preffered so if that is typed in then that is the address TMS will set.
This might be related to your phonebook issue if the endpoints cannot resolve the FQDN the phonebook will dissappear . TMS pushes these address every now and then on a fixed interval.
The last touch issue you have someone else might have a good answer to that.
We are using DHCP and tracking in TMS by MAC. Just to note, we are only seeing this issue on C series endpoints, MXP endpoints are behaving normally.
I do have the FQDN field set, I will remove it over the weekend to see if the helps resolve our issues. Why is FQDN preferred? All of my endpoints should be able to resolve the FQDN, is there a way to do a NSLOOKUP from an endpoint? I'd like to try that during on a codec that isn't working.
I do believe this is all realated so I hope removing the FQDN helps!
Sometimes you want to use Wireshark to capture packets On Cisco Meeting Server to troubleshoot and investigate video call issues, quality issues, or may be Expressway integration, WebRTC Connections, or why not, understand how the communication and the ca...
When we talk about Stun Protocol used for NAT traversal in voip environment, the common term used when talking about the Type of NAT that is compatible with Stun is “Full Cone NAT”, then when we explain why Turn Protocol is developped to replace Stun Prot...
From X8.11 of Cisco Expressway, a new concept of load balacing based on priority and weight instead of the round robin for better load balancing and probe is added to prevent the Cisco Expressway-C to sollicit a webbridge when it is down.Assume all ...
Local Zone: This is a collection of all devices that are registered with Cisco Expressway. The local zone is divided to subzones. These subzones include the automatically crated default subzone and up to 1000 manually configured subzones. In additio...
Datacenter virtualization is the process of employing virtual hardware for designing, developing, and implementing the datacenters. It is often used as an umbrella term that entails different categories like application virtualization, server virtua...