IP Phones stuck on Discovering after IP Office server edition reboots

[Abdul Wahab Waheed]

Hi Everyone, I've faced this same issue at 2 sites. For whatever reason, if the ip office server edition gets a reboot; all the ip phones (16xx, 96xx) get stuck on discovering... when they power up. But if we manually restart them they boot up normally and the extension starts to work. I thought it had to do something with the DHCP Scope but the option 242 is enabled as the phones are getting proper IP Address, also i checked the 46xxsettings.txt file and it is configured correctly as well.
My question is that why is it necessary to manually restart the ip phones? is there any other work around for this?

 

[Okkie26]

Are they in resilience mode?

 

[Abdul Wahab Waheed]

No. The issue occurred in two different projects. They are not linked together but i faced a same issue at both the projects

 

[derfloh]

Do you have a packet trace where you can see what the phone does?

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[MrFooF]

did you give time to phones to get on resilience system ?

I remember testing whole, it took 5 minutes to get whole system resilient

 

[Abdul Wahab Waheed]

@derfloh I haven't tried the packet tracer yet. I believe it has to do something with the network configuration but i'm not sure what could be the problem.
@MrFooF yeah I left them overnight but still they were stuck at Discovering... but if i simply reboot them manually they start to work within a min.

 

[MrFooF]

Is the DHCP service provided from IPO ?

If not, did you enter all the servers IPs ?
If it is, did you activate the resilience on link between both servers ?

 

[Abdul Wahab Waheed]

DHCP is provided from their network and not from the IPO and yes, all the IPs are entered.
Sorry if i confused you. I had the same issue at two different projects, completely unrelated to each other. But the setup is same, both have IPO Server Edition with IPO Expansion unit. IPs are being given through their own network's DHCP Server and not from IPO.

 

[MrFooF]

I'm really on a DHCP issue.
Can you give the option 176 & 242 text you configured ?
(I prefer to use IPO as DHCP on a voice VLAN, usefull to apply QoS, for example...)

 

[derfloh]

A PCAP trace would show you if the phone sends DHCP requests and if it get any (valid) answer.

If DHCP works, the phone should get some files and then try to connect to the call server.

You should see everything in the trace and can get hints how far it comes and if there's something wrong, I.e. With the DHCP options.

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/