|
|
Joined: Oct 2013
Posts: 30
Member
|
OP
Member
Joined: Oct 2013
Posts: 30 |
I have an IWATSu ICON phone system. 130 phones in a k-12 environment. Phones are in vlan 5 in the 10.77.80.0/23 network and data in the default vlan in the 10.77.64.0/23 network. DHCP is controlled/provided at the State level. They have option 43 on the root scope to tell the phones to go to vlan 5 and 10.77.80.5 as the gateway to the Phone Switch. I have changed the mbu, the csu and one other card I dont remember the name of to no avail. PROBLEM: Every morning the phones reset 5 times each between 8am-10am. The rest of the day they are fine. Nothing outrageous on the error log other than the resets.
The wireshark on the mbu however indicates IP addresses from the 10.0.7.0 network. The mac addresses for the 10.0.7.0 in the wireshark are associated with an IWATSU phone. The mac addresses do not show up however in any of my switches. It seems that the phones are holding the 10.77.80.x address and it seems that the phone system is pushing the 10.0.7.0 addresses as well. Is this causing the confusion?
Is there somewhere that the phone switch can hold on to a previous IP scheme and it is mixing it up with my new scheme? Where is the 10.0.7.0 coming from? I have poured over the icon program and cannot find the 10.0.7.0 in the program.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Oct 2013
Posts: 30
Member
|
OP
Member
Joined: Oct 2013
Posts: 30 |
We did resolve this issue. The phones do reboot sometimes, but that could be something else on the network. The main resolution that fixed this for us was VLANning. We were in on large broadcast domain. While we cant technically confirm this was the issue as I had network experts indicating that the phones should be able to handle this, they could not. We split the entire network up into 12 different vlans and have the phones in one of their own. The phones have not acted as before since 2013. They are stable. Let me know if you have any questions.
|
|
|
|
Joined: Jan 2017
Posts: 1
Member
|
Member
Joined: Jan 2017
Posts: 1 |
This is an old thread, but I'll throw my 2 cents in just in case someone else has an Iwatsu reboot issue..
We had a big reboot problem after upgrading to Ver 12 to get the receptionist console capabilities.
After going through and tearing out every network monitoring device i had (SNMP apparently makes these things reboot), we installed VLANS for network endpoints, workstations, phones, cameras etc. (apparently, excessive broadcasts make these things reboot). We ran new cat6 to each desk for a dedicated phone connection (apparently too much traffic from a tethered workstation will make these things reboot).
Long story short, I went through the network and took care of all of the things that the Iwatsu engineers said would make these things reboot,
Our problem ended up being some strange network issue that was solved by a switch reboot and a full phone system reboot. All of the IWATSU phones were flapping ports on a cisco switch trunk in one of the connected buildings. After a reboot, they got their act together and we've had no more phone reboots.
|
|
|
|
|
|
|
:
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
Forums84
Topics94,287
Posts638,786
Members49,767
|
Most Online5,661 May 23rd, 2018
|
|
|
|
|