Call Server IP Administration

[fishnoob]

Can't remember this for the life of me!

We had a power outage just earlier and the phones went into Discover mode after the power came back on, however it was having DHCP troubles and not connecting to the call server configured in the 242 DHCP option.

It then cycled through some VERY old CLAN IPs that no longer exist. The IPs are NOT int he 46xx or 96xxsettings file either.

Can anyone shed some light on this basic info on how to change this?

Thanks in advance!

 

[wpetilli]

It can be old/cached information. Once all the DHCP troubles were fixed, did you try another reboot?

 

[kyle555]

CM tries to load balance registrations across all CLANs administered in the same network region.

If those "ip-interfaces" for those old CLANs are still in CM and in the same region, that'll explain why phones are trying to register to them in the absence of a settings file or DHCP scope telling them to do so.

 

[montyzummer]

You need to look at the agl list document , this will explain how CM provides information to the phones and the exact behaviour in cert aim setups , you ultimately have many different configuration items that you can set but you need to understand the big picture , I'm sure the paper is called Avaya aura communication manager alternate gatekeeper list ,... Or very similar Google it ... Also read the network connectivity in communication manager document again if it's not that it's very similar name

APSS (SME)
ACSS (SME)
ACIS (UC)