IP phones connect to the wrong CLAN

[stevea2Z]

Ok guys, can someone help me out? I have a 8720 R 3.1.2 with 10 Clan boards. I want one building to connect with a specific CLAN board and the other building to connect with another CLAN. How can I make this possible. The situation now is that the phones of building A connects with the clans for building B. How can I change this ?

Second question, date/time format? The customer wants it in 24 hours format instead of AM/PM It isn't in the terminal options, where it was before. Anyone an idea ?

 

[adscott]

My amature opinion on how to register phones to different CLAN cards would be to set the DHCP options differently per subnet. Hopefully you have different subnets/vlans per floor and building. If so then the DHCP properties would hand out the IP of the CLAN depending on the gateway the request came from.

My first post i am trying to learn this stuff so let me know if I am wrong guys.

 

[bsmo]

Steve,

Check out

http://support.avaya.com/elmodocs2/comm_mgr/r3/netw-region-tutorial-cm30-1005.pdf

This documents explains in detail how network regions work and how to configure.

 

[rjblanch]

We currently have the network regions set up for our CLAN's and the one thing that we have noticed is that occassionaly, some IP Endpoints will register to a CLAN not in the same region.

Has this happened to anyone else??

Regards..

 

[nknook]

We currently have the network regions set up for our CLAN's and the one thing that we have noticed is that occassionaly, some IP Endpoints will register to a CLAN not in the same region."

This is correct behaveour. When registering, IP phones in a particular region recieve an alternate gatekeeper list (=CLAN's). This list also contains CLAN's in other regions that have a "direct WAN" connection with the native region of the IP phone.
If the CLAN(s) of the native region are too busy (which is determined by ACM), the phone will register on an alternate CLAN, and this CLAN may be in another (direct WAN connected) region.

A solution may be to use ghost regions, and this is were I double bsmo's advise to read the network-region tutorial. It's very good.

 

[stevea2Z]

Thanks guys, The network regions has solved the issue.

 

[rjblanch]

Thanks nkook, that is correct, but unfortuantely we have an intervening region set up due to running a MPLS network, and the intervening is there to control bandwidth into each of the regions...

None of our endpoint regions are directly connected and I know that this issue has bugged Avaya for a while, so I guess I will keep asking them if they have come up with an answer.