Call Manager not classifying video endpoints correctly based off H245
Symptom: Intelligent bridge selection chooses a video conference bridge instead of an audio one when a audio conference resource should be selected.
Additionally, there is also a service parameter that influences how a conference bridge is selected:
"Allocate Video Conference Bridge for Audio-only Conferences When Video Conference Bridge Has Higher Priority
This parameter determines whether Cisco Unified Communications Manager chooses a video conference bridge, when available, for an ad hoc audio-only conference call when a video conference bridge has a higher priority than an audio conference bridge in the MRGL.
If an audio conference bridge has higher priority than any video conference bridge in the MRGL, Cisco Unified Communications Manager ignores this parameter.
it was really a helpful. in my scenario we have conductor and vTS, when we only choose vTS CFB then video conf call is working fine but when we add one more MRG of audio CFB for audio fallback purpose then all conf calls works as audio only. your mentioned service parameter change really did the job and now my conf initiated as video.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.