IP Office 500v2 11.1.2.1.0 build 3 DHCP not assiging phones the sip proxy settings 1

[JimFed]

My own internal IP office has a real SSL cert assigned and I am using TLS on the J179 phones. I have never been able to get my phones to auto configure
I am using the default 46xxsettings.txt file and if I use the IP Office for DHCP with the setting Avaya phones only the phones will get a IP but not configure the SIP proxy settings. If I setup the phones to use DES the phones auto configure and work fine. If I manually configure them they work fine.
I have even taken my phone system off the network and plugged new switch directly into the phone system with one brand new J179 connected and it will get IP but not the Sip Proxy settings. The configuration for DHCP is super easy. I am 30 year network tech but I can not get this to work. I have IPOSS on the system but they wont help me because it never worked. Wondering if anyone else is having this issue or seen it. I setup these all the time for customers and they work but they are not using TLS. I am using TLS as I have techs working from home and we only allow their IP to connect to our system. There are no vlans on my network as we only have 10 phones. I do have an AT&T Sip trunk coming in on Lan2 and my phones are configured on LAN1 that is the only non standard thing.

 

[critchey]

Are the phones grabbing the 46xxsettings.txt file? It sounds like the HTTP server is not being set in the phone so it never grabs the file which it needs to get the SIP proxy. You can verify if it grabs the file via monitor.

The truth is just an excuse for lack of imagination.

 

[Ekster]

The 46xxsettings file is what delivers the phone's proxy settings, this is accessed by HTTP/HTTPS. You say you have a "real" SSL Cert on the system, so I assume you have the certificates FQDN set in the LAN VoIP domain settings? If so, you need to make sure there is a DNS setting on your network that resolves the FQDN to the IP500's IP address, otherwise the system will reject HTTP requests using the FQDN. When an HTTP request is made, the IP500 will query it's configured DNS server and check the FQDN matches its IP address, if it does not find a match it will reject the request.

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet

 

[critchey]

Pink for Ekster that is the answer I pretty much guarantee it.

P.S. "I have IPOSS on the system but they wont help me because it never worked." What kind of nonsense is that? You can't get support for something you never had working? smh

 

[IPOLackey]

they wont help me because it never worked." - More like they wanted a PO for them as they saw it as a setup issue rather than a fault... Had that a couple of times, even when its a upgrade that breaks something.

 

[JimFed]

I have valid Split DNS meaning internal dns points to the phone system internal ip address and external DNS points to firewall ip that is redirected to phone system. I have noticed that if I go to

http://ipoffice.domain.com/46xxsettings.txt

the site will not come up. If I go to

https://ipoffice.domain.com/46xxsettings.txt

the site comes up. I do have TLS enabled on the system. Phones work fine if I use DES to configure them or manually configure them.