Hi everybody.
My 96xx phones are exhibiting some odd behavior. If they are logged out, after 60 secs, they go into discovery mode (cycle through the gateway IP addresses). Once they do that, you have to restart the phone in order to get the login screen again.
I started doing some research and found that some examples have the tag VLANTEST on the dhcp scope on option 242. This cycling/timeout issue is a big problem because the students who handle tier 1 support on my contact center (AACC 6.2) need to logout and login during shift changes. If the timer reaches 60 seconds, the phone start discovery. What I did was add the VLANTEST =120 field on the DHCP scope (for both data and voice scopes), but the phones (after reboot) still go to discovery mode after 60 seconds.
I should add that this happens ONLY when the phones have a privately addressed IP (10.14.x.x). When they get a public address (69.x.x.x, which is non QoS’d) this does not happen.
Any ideas?
Thanks for your help.
My 96xx phones are exhibiting some odd behavior. If they are logged out, after 60 secs, they go into discovery mode (cycle through the gateway IP addresses). Once they do that, you have to restart the phone in order to get the login screen again.
I started doing some research and found that some examples have the tag VLANTEST on the dhcp scope on option 242. This cycling/timeout issue is a big problem because the students who handle tier 1 support on my contact center (AACC 6.2) need to logout and login during shift changes. If the timer reaches 60 seconds, the phone start discovery. What I did was add the VLANTEST =120 field on the DHCP scope (for both data and voice scopes), but the phones (after reboot) still go to discovery mode after 60 seconds.
I should add that this happens ONLY when the phones have a privately addressed IP (10.14.x.x). When they get a public address (69.x.x.x, which is non QoS’d) this does not happen.
Any ideas?
Thanks for your help.