Recently, I upgraded OXE release from R6.2 to R9.0 (h1.301.34). After system upgraded, the 4037 IP Phone cannot startup. It ran at Phase 6 (UA Signaling Error) and then reset. The CPU7 and the defected IP Phone was put at different subnets. It seems that some UDP ports are blocked by the router/firewall. Anyone knows what is the different on UDP ports between R6.2 and R9.0.
Ethereal log is attached for your study.
IP of defected 4037 IP Phone: 137.189.27.60 MAC:00 80 9F 3B F5 0F
Main Role IP: 137.189.108.63
CPU-A: 137.189.108.61
CPU-B: 137.189.108.62
4037 IP Phone cannot startup after upgraded from R6.2 to R9.0
-
spring
-
smileyman
-
freedom
Do you still have a lanpbx file available on your system?
check with 'lanpbxbuild'
If not, create one automatically using 'lanpbxbuild -auto' or do it by hand.
Does the set have a DHCP address or a static address?
Check if the set receives the correct TFTP address and Callserver address.
Does the set have the correct settype in the management?
If you use the set out/in prefix on IPtouch 8 series sets, the settype will change to an IPtouch 9 serie set!
As soon as you do an update with this settype in the database, an ip-phone might not be able to become operational.
You have to change the settype to 8-series before it will work.
Not sure if this problem is also there for 4037 sets.
check with 'lanpbxbuild'
If not, create one automatically using 'lanpbxbuild -auto' or do it by hand.
Does the set have a DHCP address or a static address?
Check if the set receives the correct TFTP address and Callserver address.
Does the set have the correct settype in the management?
If you use the set out/in prefix on IPtouch 8 series sets, the settype will change to an IPtouch 9 serie set!
As soon as you do an update with this settype in the database, an ip-phone might not be able to become operational.
You have to change the settype to 8-series before it will work.
Not sure if this problem is also there for 4037 sets.
-
JoelO
