Content Server not registering to VCS

[Anthony Chan]

Have the 2nd generation of the TCS and running S5.2 firmware

for some strange reason it is not registering to our VCS

both units are on the same VLAN

suggestions?

Thanks

Anthony

[Martin Koch]

Check you config, restart the service reboot the server and then recheck your logs.

If you have enabled auth. Check that your clocks are in sync, if you use policies on the vcs check

That they are ok.

But most of the time a tics restart helps

Sent from Cisco Technical Support iPad App

[Jens Didriksen]

TCS Web GUI;

Management --> Configuration --> Site Settings: Gatekeeper Settings

should show you why it isn't registering.

[Anthony Chan]

this is what it says

I have 3 other TCS's they are registered properly but those were running S5.1 and S4.0 on the 1st generation hardware

have restarted the TCS server and still get the same results

[Anthony Chan]

found this error in the logs of the VCS:

i am assuming that I am using an already assigned alias?

[Jens Didriksen · Accepted solution]

Yup, that is correct - you need to look at the registrations listed on the VCS and find the offending alias(es), and either unregister these on the VCS itself, or, if they are correctly registered for another device, change the aliases on one of them.

The fact that it is a second generation box on 5.2 is neither here nor there as far as registrations are concerned.

cheers jens

[awinter2 · Accepted solution]

Anthony,

if the conflicting registrations stem from the same TCS, you might want to set 'VCS Configuration > Protocols > H323 >

Registration conflict mode' to 'Overwrite', as this should resolve the problem.

Make sure that you fully understand what this setting does before switching it though, as you might run into problems if it turns out that the conflicting alias originates from a different H323 device.

Hope this helps,

Andreas

[Anthony Chan]

thanks for all your help, found that the alias recording names were the same but strange that in the other TCS it never gave me that error but is now working

[Jens Didriksen]

The other TCS most probably registered first, so no conflict occured for that particular registration.