I have a VG248 running 1.1(2.1.5). I keep getting errors in the Event log that it is unregistering (each port that is). CM shows the box as "unknown." But each port is registered with CM (there are only 8 configured). The log on the 248 shows that ports register and successfully unregister. Is this normal? Is this the way the VG248 works, registering and unregistering ports on a per call basis? This is used for AMIS integration. Any ideas?
This doesn't sound normal to me. Usually, I only see ports unregister/re-register if network connectivity, CM, or the VG248 has gone down. The ports should stay registered. You didn't mention what version of CM you have. Have you tried installing the latest software for the VG248 (version 1.2.1)?
It is CM ver 3.2.2c. I haven't tried installing the latest ver yet. In Main View,Diagnostics,Event log,View recent, it shows the output below, it does this constantly. Only the first 8 ports have directory numbers:
12122 16:05:49 29s I SCCP 3 Unregistering from CallManager
12123 16:05:49 4 I SCCP 3 Unregistered successfully from CallManager
12124 16:05:49 8 I SCCP 3 Registering with CallManager
12125 16:05:49 3 I POTS 3 Clear MWI
12126 16:05:49 223 I SCCP 3 Registered successfully with CallManager
The ports/box will be registered all the time and it is not per call basis. You check for errors on mainmenu-->display-->network statistics and check for any discard packets..also my question for you is does all the ports have DNs?
Ok, can you check if the speed is matching on both the switch and the vg248 eth interface and also check if its full/half duplex both sides. Even if this is good then you will have to check the CM tracefile..
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.