96XX phones won't get their files from a http server, only the IPO despite custom settings. 2

[tac84]

Hi guys,
I've just been experiencing a strange one. I have a mix of 9611G, 9608G and some 9630G/9640G handsets.
In Manager, I have the phone file server type set to 'Custom' and the IP address in the HTTP field. I've had no issues with this for ages. My 9611G/9608G handsets get their files from the correct file server with no problems however all of a sudden, the 96XX phones only obtain their files from the IP Office (Memory Card) even though all of their files are on the file server too. On the 96XX handsets in the CRAFT menu under Addresses, HTTP notes the correct file server however HTTPS lists the IP Office IP Address. On my 9611G/9608G the HTTPS server is 0.0.0.0

This has only started happening recently but I can't pinpoint exactly when.

Any ideas why the 9630G/9640G phones go straight to the memory card even with the phone file server type set to custom? I just find it strange that the newer IP phones (9611G/9608G) go straight to the file server but the older ones don't.

Any suggestions would be greatly appreciated

Thanks, Tim
Adelaide, Australia

 

[derfloh]

The 9611/9608 load a 96x1Hupgrade.txt while the 9630/40 load 96xxupgrade.txt.

Probably the needed text file is missing.

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/

 

[tac84]

Thanks for your reply @derfloh.
Yes definitely have these files on the file server. On the display of the 96XX handsets when they boot, the IP addresses that display are the same as the IPO which is what would happen if the phone file phone file server type was set to 'Memory Card' yet the IP address that display on the 96X1 handsets is the correct file server.

These used to work perfectly. I know that I had to play around with security certificates on the IPO when I was using a 1140E SIP phone. Could the problem have something to do with security certificates? That is the only change I can think of since the last time the 96XX phones talked to the file server perfectly...


Thanks, Tim
Adelaide, Australia

 

[tac84]

Hi all, unfortunately this problem still exists...any ideas or suggestions?

Thanks!!

Thanks, Tim
Adelaide, Australia

 

[Travis Harper]

If you point a web browser to

http://yourserver/46xxsettings.txt

Depending on the web server, it could be permissions issue.

Are you able to tail the logs on the web server while a phone boots?
When the phone boots, do you see a 200 OK, or a 404?

If you regenerated the certs, you will need to regenerate a cert for the web server as well.

Travis

 

[tac84]

@Travis Harper

Hey Travis
Thanks for looking at this one.
When the phone boots, the 96XX phones go straight to the IPO IP Address, they don't even display the http server address, yet the 9611G/9608G do exactly what they're meant to do by getting their files from the http server with 200 OK.

When you say re-generate a cert for the web server, do you mean install the new IPO Certificate on the computer acting as the http server? Or is there something else I'm meant to do in the Security settings page...

Just can't work out why the 9611G/9608G phones have no trouble at all and all of a sudden the 9640G or 9650C won't play..



Thanks, Tim
Adelaide, Australia

 

[teletechman]

HTTP notes the correct file server however HTTPS lists the IP Office IP Address. On my 9611G/9608G the HTTPS server is 0.0.0.0
You set this with your scope option 242 add tlssvrv=xxx.xxx.xxx.xxx(file server address) and see if it pulls the file.
Mike

 

[bahmonkeys]

Yes setup Option 242, this will point all IP phones to the location of the phone system which has all the .bin files for the phones firmware. Don't go messing with 46xxsettings.txt

 

[tac84]

Thanks everyone for your help, turns out there was another DHCP server accidentally on which was causing the issue!

Thanks, Tim
Adelaide, Australia

 

[Westi]

Thanks for letting us know what it was Tim

Resolutions get pink

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019

 

[tac84]

Cheers @Westi

Thanks, Tim
Adelaide, Australia