4412D Phones Shutting Off

[Rappy]

Hi everyone!

I have a remote office connected via IP VPN to the main branch. Main branch is ipo 412 running 3.2.69. Remote is ipo 406 V1 running 3.2.69. Problem is at remote branch with 2 digital expansion units. The users connected to both units are seeing their phones shut off completely. All their phones are 4412D's. The users having these issues are on 2 separate units. Avaya came out to replace the 406 and the PRI card. The uptime on the 406 is over 48 hours. it is not rebooting. I am attaching logs from the device as i have captured them. The device is grounded properly to a ground. the units do not seem to shut off or power cycle when the phones die. The phones can then be powered back on by unplugging them and plugging them back in. I have not made any changes to the unit since this started to happen. I have not made any configuration changes to the unit since this issue was reported. Your help is greatly appreciated as always.

the error message seen below "Cause=18, No user responding/No response from remote device" can be found for every extension exhibiting this problem:
3212252mS CMExtnRx: v=318, p1=3
CMPhoneStatus
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
Product Unknown
Cause=18, No user responding/No response from remote device
3212262mS CMExtnRx: v=322, p1=6
CMPhoneStatus
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
Product Unknown
Cause=18, No user responding/No response from remote device
3212272mS CMExtnRx: v=331, p1=9
CMPhoneStatus
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
Product Unknown
Cause=18, No user responding/No response from remote device
3212282mS CMExtnRx: v=313, p1=10
CMPhoneStatus
Line: type=NoLine 0
Call: lid=0 i d=-1 in=0
Product Unknown
Cause=18, No user responding/No response from remote device

Beets? Yes! Ask me how I feel about Beets! I like Beets!

 

[Rappy]

using a spare ip office 406 and a digital expansion unit, i have been able to duplicate the issue. The lab is as follows:

ip office 406- connected to power, using expansion slot 2- connected to DS 16 using the Avaya cable provided (someone called it a TDM cable?!)

ip DS 16- using single expansion slot connected to ip office
4412D phone- plugged into DS 16 port 9

experiment- after the phone has a display, the TDM cable is then removed from the DS 16; the phone keeps its display but the voicemail light blinks; after plugging in the TDM cable back into the DS 16, the display goes out and the voicemail light blinks; the phone comes back after about 5 seconds;

repeating the process twice yields the same results

Repeating the process a third time causes the phone's display to go out completely; unplugging and plugging the phone back in causes the display to return

The DS were replaced and the issue has been resolved.


Beets? Yes! Ask me how I feel about Beets! I like Beets!