CCM adds "_1" to Device Name when configuring an H.225 Trunk

[ewaizel]

My question is WHY?

Did any of you had this problem and managed to avoid it?

If for example, the device name is "ABCDE", CCM will send "ABCDE_1" as the H.323 ID when registering into the Gatekeeper. In my case the registration is being rejected. This is not the value the Gatekeeper was expecting.

[mmelbourne]

I believe a trunk is configured for each of the CallManagers in the CallManager Group to which the trunk is assigned, for resiliency purposes.

[ewaizel]

mmm interesting.

So if I also have a subscriber server it will use "_2"?

Is this something that can be configured?

[mmelbourne]

That's what my setup here does. I was slightly surprised too, but the IP addresses of the devices are those of the Publisher and Subscriber.