I have VCS control and Expressway in production Assent and h460 are both active on the expressway, but inactive on control. Is this correct?
I assume you saw the "inactive" on a xstatus or on the https:///h323 page, right, or is it mentioned
somewhere else as well?
Maybe Andreas could follow this up an improvement request, as at least it can be confusing.
On a VCS-C it shows up in red letters (at least) on the h323 config page.
Maybe not showing it at all on the vcs-c might be handy as well, ....
In general h460 is one of the parts which makes the expressway an expressway.
If you would try for example to access the
https:///locallyregisteredendpoints page it would tell you that you lack a license.
h460 is one of the parts which makes the expressway the expressway.
So this "Inactive" this is nothing you need to worry about, that's the wanted behavior. And its
ok that h.460 is not used on the vcs-c (its not a bug its a feature :-)
If your firewall allows it and your VCS-E is set up for it you could try to register the endpoint
with h.460 to the VCS-E.
In general when having strange symptoms its worth checking that there is no NAT helper / Application
layer gateway or what ever in between the involved components and that the firewall ports are properly
configured and the traversal zone and search rules are properly set up.
Also reading release notes and possibly upgrading to the latest software versions.
The traversal zone has the options has two h323 options which I would try to play around in such a case:
"H.460.19 demultiplexing mode" and "Protocol" (has to be the same on vcs-c and -e).
Andreas: what are the use cases for these parameters?
Anyhow, its strange with the garbled sound.
J.House: Please rate the answers using the stars below the messages!