registration issues with vcsc

[hgraniteworks]

Hi Guys,

we seem to be having issues with our mps when trying to register to our vcsc via h232. we seem to be experiencing the same issue with two seperate system controller blades. Mps registers no problem on sip. the vcsc keeps reporting that there is a conflict, even if we de-register all the devices the vcsc still reports the same issue.

any help is appreciated.

thanks

[hgraniteworks]

Further testing has established that Mps can register no problem to ipvcr int ernal gk but when we try to register to the vcsc, the vcsc rejects any h323 registrations from the mps, sip registers no problem. The ipvcr also registers to the vcsc on h323 and sip registers instantly once configured. Any help will be greatly appreciated.

[awinter2]

Shazad,

although doing this is more likely to work around rather than resolve whatever issue you are having, you could try setting VCS Configuration > Protocols > H323 > Registration conflict mode to 'Overwrite' instead of 'Reject'.

- Andreas

[Tomonori Taniguchi]

MPS may attempt register to VCS in two different types while registering as H323 device.

One for Endpoint and other is Gateway.

Static conference will register as “Endpoint” and this number can’t overlap which will cause conflict registration.

Personal conference prefix, Dial-in conference prefix, etc. will register as a “Gateway” and this number can be duplicate with other device for load balancing the call.

I’d recommend to take ‘syslog 3’ on MPS or/and diagnostic log from VCS (also xconfig from MPS) to identify what alias and which device are trying to register with conflict alias.