Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: sunspark on December 03, 2020, 07:13:08 PM
-
Hello fellows,
Do you know where the ip address of the call server is located except in the lan configuration, the network elements, the trunks icp networking and the msl / dhcp? I have upgraded + changed the ip address , and the phones are still trying to contact the old ip address of my call server. In option 125 I have the new ip address, and I reset factory all phoned, but they are still trying to contact the old address.
Any idea
-
Make sure there's no static settings on the phone. Static settings will override DHCP.
-
Make sure there's no static settings on the phone. Static settings will override DHCP.
as said in my post :i reset to factory all phones so no static ip address.
-
Then you need to double check your networking, if DHCP is set to send the phones to the correct server IP and they're still going to the wrong one, your DHCP isn't working correctly.
-
Then you need to double check your networking, if DHCP is set to send the phones to the correct server IP and they're still going to the wrong one, your DHCP isn't working correctly.
my dhcp is set correctly, i can see in the pcap boot squence the option 125 with the good call server ip
-
Then I don't know what to tell you, DHCP should be pointing the phone to the server IP in the DHCP option, unless there's a static setting overriding it. What if you put the correct IP in as a static setting on a phone?
-
Then I don't know what to tell you, DHCP should be pointing the phone to the server IP in the DHCP option, unless there's a static setting overriding it. What if you put the correct IP in as a static setting on a phone?
already tried, after reboot, the phone change the static call server / Tftp setting to the old ip address, seems like a bug.
i've tried with 53xx phones , i don't have the same behavior
the issue only with 69xx phones.
-
the problem is solved by updating the 69xx firmware.
-
the problem is solved by updating the 69xx firmware.
What firmware were you on, and what did you update to?
-
the problem is solved by updating the 69xx firmware.
What firmware were you on, and what did you update to?
From 1.4.0.80 to 1.5.2.24