Morning all,
This is a very odd issue and is currently being investigated by Avaya, to no avail.
Details ;-
Control Unit - IP500v2 (has been replaced)
Expansion Cards: VCM32 (has been replaced)/BRI8 (has been replaced), CombiATM4 (has been replaced), DS8 (has been replaced)
Releases Attempted: 7.0.36, 8.1 FP1, 8.1 FP1 (build 67)
Handsets have used the firmware from 7.0.36 plus those from 8.1 FP1
SD Card has been replaced and config re-programmed from scratch
We've enabled and also disabled Direct Media Path
Handsets use Call Appearence keys via the user's settings rather then User Rights (I've seen the latter can cause problems)
Issue occurs on 1608i/1616i WITHOUT bbms. The handsets with bbms seem to be recorded.
4 Port VM Pro, with Call Recording set to on, on 4 extensions (On NOT Mandatory) - these handsets haven't rebooted.
One handset at any given time will restart. However, it won't restart in a way that you'd expect an IP Phone would - it's like it loses power for less than a second. The users have base extensions and login users, when the phone restarts the user logged in does not get logged out from the handset.
Phones are connected to the LAN2 port and hence does not share the Cat5e network with the customers PC's/Network Devices. Phones are assigned an IP Address via the IP Office's DHCP setting and are powered using PoE switches (both have been replaced)
Customers network has been proven as OK via an independant Cat5e companies testing.
Wireshark traces show that the handset is "talking" to the IP Office control unit without issue, the IP Office/Handset respond to the keep alive requests just fine and then the handset "Disapears" for a few seconds and then comes back..
SSA shows nothing untorward and a monitor trace show's the following :-
92325983mS H323Evt: GK: Unregister endpoint SystemName_50f7dcdb40364ba2 for extension 322 reason 3
92325983mS CMExtnEvt: GPRoom8:322 ExtnFault now 1
Note I've edited the systemname section for confidentiality reasons! But in it's place was the name of the telephone system
It doesn't really show anything other than that to acknowledge a phone has restarted. If you go in to the h323 phone status section you can see a selection of handsets that have sufferent from the issue.
We have also deployed a few power bricks to see if there was something in the Cat5e network that could interupt the power, however those with power bricks have restarted since then. So really I believe we may have eliminated the following :-
Control Unit
Expansion Cards
PoE Switches
Customers Cat5e Network
Leaving potential issues with :-
IP Handset Firmware
Bugs in 7.0.36, 8.1 FP1, 8.1.67
VoiceMail Pro Call Recording - noted minor congestions here, am trying to get confirmation that the congestion count coincides with a handset restart
If anyone has come across any similar issues or has any suggestions I'd love to hear from you!
Many Thanks,
Rob
This is a very odd issue and is currently being investigated by Avaya, to no avail.
Details ;-
Control Unit - IP500v2 (has been replaced)
Expansion Cards: VCM32 (has been replaced)/BRI8 (has been replaced), CombiATM4 (has been replaced), DS8 (has been replaced)
Releases Attempted: 7.0.36, 8.1 FP1, 8.1 FP1 (build 67)
Handsets have used the firmware from 7.0.36 plus those from 8.1 FP1
SD Card has been replaced and config re-programmed from scratch
We've enabled and also disabled Direct Media Path
Handsets use Call Appearence keys via the user's settings rather then User Rights (I've seen the latter can cause problems)
Issue occurs on 1608i/1616i WITHOUT bbms. The handsets with bbms seem to be recorded.
4 Port VM Pro, with Call Recording set to on, on 4 extensions (On NOT Mandatory) - these handsets haven't rebooted.
One handset at any given time will restart. However, it won't restart in a way that you'd expect an IP Phone would - it's like it loses power for less than a second. The users have base extensions and login users, when the phone restarts the user logged in does not get logged out from the handset.
Phones are connected to the LAN2 port and hence does not share the Cat5e network with the customers PC's/Network Devices. Phones are assigned an IP Address via the IP Office's DHCP setting and are powered using PoE switches (both have been replaced)
Customers network has been proven as OK via an independant Cat5e companies testing.
Wireshark traces show that the handset is "talking" to the IP Office control unit without issue, the IP Office/Handset respond to the keep alive requests just fine and then the handset "Disapears" for a few seconds and then comes back..
SSA shows nothing untorward and a monitor trace show's the following :-
92325983mS H323Evt: GK: Unregister endpoint SystemName_50f7dcdb40364ba2 for extension 322 reason 3
92325983mS CMExtnEvt: GPRoom8:322 ExtnFault now 1
Note I've edited the systemname section for confidentiality reasons! But in it's place was the name of the telephone system
It doesn't really show anything other than that to acknowledge a phone has restarted. If you go in to the h323 phone status section you can see a selection of handsets that have sufferent from the issue.
We have also deployed a few power bricks to see if there was something in the Cat5e network that could interupt the power, however those with power bricks have restarted since then. So really I believe we may have eliminated the following :-
Control Unit
Expansion Cards
PoE Switches
Customers Cat5e Network
Leaving potential issues with :-
IP Handset Firmware
Bugs in 7.0.36, 8.1 FP1, 8.1.67
VoiceMail Pro Call Recording - noted minor congestions here, am trying to get confirmation that the congestion count coincides with a handset restart
If anyone has come across any similar issues or has any suggestions I'd love to hear from you!
Many Thanks,
Rob