09-27-2011 04:15 AM - edited 03-21-2019 04:43 AM
Hello!
We made a few changes in our UC560 config related to dial peers and DIDs and since then, we are having a strange problem: four extensions go offline every 12-24 hours.
Here is what happens:
On 26 Sep at 20:47 I reboot one of our CP-521S phones, extension 111, before going home
2011-09-26 20:47:34 Local7.Info 192.168.10.4 460: 000468: Sep 26 19:47:47.263: %IPPHONE-6-REG_ALARM: Name=SEP00211BFCB2B3 Load=8.1.17 Last=Hard+Unknown
2011-09-26 20:47:34 Local7.Info 192.168.10.4 461: 000469: Sep 26 19:47:47.459: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-33:SEP00211BFCB2B3 IP:10.1.1.23 Socket:5 DeviceType:Phone has unregistered abnormally.
2011-09-26 20:47:34 Local7.Info 192.168.10.4 462: 000470: Sep 26 19:47:47.459: %IPPHONE-6-REGISTER: ephone-33:SEP00211BFCB2B3 IP:10.1.1.23 Socket:1 DeviceType:Phone has registered.
I check the phone - it works, there is a dial tone
On 27 Sep at 10:00 I come to work and the phone is dead, no dial tone. I ping then phone and it pings okay, I can connect connect to it over HTTP (see attached), but cannot make or receive calls. All calls go to voicemail.
I logon to our syslog server and see this:
2011-09-27 07:27:16 Local7.Info 192.168.10.4 305: 000302: *Sep 27 06:23:39.465: %IPPHONE-6-REG_ALARM: Name=SEP00211BFCB2B3 Load=8.1.17 Last=Hard+Unknown
2011-09-27 07:27:16 Local7.Info 192.168.10.4 319: 000316: *Sep 27 06:23:39.685: %IPPHONE-6-REGISTER: ephone-33:SEP00211BFCB2B3 IP:10.1.1.23 Socket:5 DeviceType:Phone has registered.
2011-09-27 07:27:16 Local7.Info 192.168.10.4 320: 000317: *Sep 27 06:23:39.709: %IPPHONE-6-REG_ALARM: Name=SEP00211BFCB2B3 Load=8.1.17 Last=Hard+Unknown
I have four phones with this problem. They have been all working okay for more than a year. I tried connecting phones to another port on the switch, changing phone sets etc - doesn't seem to make any difference. The problem is somehow related with extensions but I'm not sure how to troubleshoot it and would appreaiate any help.
09-27-2011 02:08 PM
Hey, had some weird issues a while back similar to this. To start check the firmware on the switches update to latest and see how you get on is what I would recommend to start with. Afterwards check the firmware on the phones.
HTH
Craig.
10-05-2011 04:56 AM
I have found something interesting, hopefully that will shed more light on this problem. Firmware is not the problem.
It appears that this problem has somethign to do with hunt groups. all phones in hunt group 1 experience this problem. so if I add a working phone to hunt group 1 - next day it will crash. here is my config
ephone-dn 18 dual-line
number 104 no-reg primary
pickup-group 1
label 104
description RECEPTION
name RECEPTION
call-forward night-service 514
call-forward noan 121 timeout 30
night-service bell
!
!
voice hunt-group 1 parallel
final 512
list 108,104,105,106,100
timeout 10
pilot 511
!
!
voice hunt-group 2 parallel
list 114,107,102,103,104
timeout 100
pilot 512
!
!
voice hunt-group 3 parallel
final 511
list 101,109,117
timeout 10
pilot 513
!
!
voice hunt-group 4 parallel
list 251,253,254,259
timeout 100
pilot 514
all phones in group 1 except 104 for some bizzare reason go offline every day in the morning. I can add any new phone to this group and it will crash too. If I remove a phone from that group - it always works.
I'm not even sure what's wrong with that hunt group.
10-05-2011 06:55 AM
Hello,
I am not sure exactly what is going on with those phones, but because of the timing you mentioned... 12/24 hours. It almost sounds like a DHCP issue, where the phones are not able to renew their IP addresses. You could test this by changing the lease time for DHCP addresses, to see if that is the case.
(I know that you said you can still ping the phone, and access the web interface, but because of the timing, DHCP is the only thing I can think of at this time.)
DHCP least time can be changed in CCA by modifying the DHCP pool. Lease time is listed there.
You can also use CLI to modify: conf t - ip dhcp pool phone - lease infinite.
Thank you,
Darren
10-05-2011 07:02 AM
Hello Darren
DHCP is not a problem. all phones have IPs, I can ping them and connect via HTTP, so they are connected to the phone system, I can see that runnign show ephone, but there is no dial tone. I can't make or receive calls. If somebody calls me, calls go to voicemail
If that was a DHCP issue, it would presumably affect all phoens regardless what hunt group they are in, whereas in my case I can add a working phone to group 1 and it will have this problem the next day
10-05-2011 03:12 PM
Hi Inventica,
What Software Pack are you currently running?
Cheers,
David.
10-06-2011 01:11 AM
I'm running 8.0.2.
I did a few tests yesterday
If I switch the phone system to night mode and have the following settings in my config:
ephone-dn 18 dual-line
number 104 no-reg primary
pickup-group 1
label 104
description RECEPTION
name RECEPTION
call-forward night-service 514
call-forward noan 121 timeout 30
night-service bell
voice hunt-group 1 parallel
final 512
list 108,104,105,106,100
timeout 10
pilot 511
voice hunt-group 4 parallel
list 251,253,254,259
timeout 100
pilot 514
Then as soon as I ring our main office number, all phones in hunt group 1, except 104 (Reception) - will die.
If I change
call-forward night-service 514
to, let's say an external phone number i.e. my mobile - everything works
call-forward night-service 07712345678
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide