We have a few Edge95 systems in one of our offices. They are running the F9.3 PAL. The VCS is registering it apparently, but the system is stating that it failed to register on the gatekeeper due to alternates. On the VCS the system looks to be registering with 4 seperate E.164 Alias. However I cannot determine in the Edge 95 codec where that is being set.
This is the error -
Cause=H.235.5 Checksum failed
Can someone please point me in the right direction to set the systems to have only 1 E.164 alias.
VCS's are running at X7.2, pending the upgrade to X7.2.2.
I should have stated that there are 3 systems in the office. One is connecting just fine, while the other two are showing a rejection on the endpoint and in TMS, although the VCS-C shows them registered. All the endpoints are running the same Software version F9.3 and all are on the same subnet.
The fact that the endpoint gives a reject and the VCS-C shows a registration is a bit concerning.
Here are some screen shots -
Gatekeeper setting from TMS -- >
Registration on VCS-C
What concerns me and I am not sure where it is configured on the Edge95 is the multiple alias's that the VCS-C seems to pick up from the endpoint, as the line above indicates.
And from the Endpoint configuration -
The multiple alias is set to off and I am not sure where else it could be pulling alias's from.
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.