Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: PC77375 on October 25, 2019, 09:48:20 AM

Title: Issue with MWI lamps
Post by: PC77375 on October 25, 2019, 09:48:20 AM
Running MiVoice Business 8.0 SP3 PR2(clustered) on ISS with Virtual Nupoint Build: 18.3.0.105.01

Just started having issue with MWI lamps. PBX continuously logs the following:

Source      Call Control - Software
Description      SWERR unexpected cp return code, OFFSET 2:$336, PC: $5854E0 LOG_ID: dpnhciorg#50, PROCEDURE: dpnhciorg_handle_virtual_reply, SEVERITY: cp_minor PID: ($5, $3D2)

Source      MiXML_CM
Description      CConnectionManagerServerEx::TerminateClientConnection: Terminate accept message sent to remote client IP <X.X.X.X:49517>, AppName <NuPoint>.

Mitel support has only suggested PBX reboot so far.  I have rebooted the ISS and the Virtual Nupoint. MWI lamps will work for a short time, then stop. Running lights test from Nupoint, I am able to light my lamp but not turn it off. Restart Nupoint service by entering offlin config mode and activating, MWI lamps will work again. They will begin to fail in a few hours. Has anyone seen this behavior? I wish their logs were more friendly.
Title: Re: Issue with MWI lamps
Post by: johnp on October 25, 2019, 07:08:34 PM
This sound similar to the 19 version .101 where the msg queue on nupoint fails
Title: Re: Issue with MWI lamps
Post by: PC77375 on October 26, 2019, 08:26:54 AM
This sound similar to the 19 version .101 where the msg queue on nupoint fails
Is there a documented resolution for this? Upgrading is not an option, it’s standalone Nupoint and that seems to be the latest version.


Sent from my iPhone using Tapatalk
Title: Re: Issue with MWI lamps
Post by: PC77375 on November 13, 2019, 08:54:16 PM
Figured it out. It was a bad extension locking up the MWI process. Disabled MWI for that extension and restarted Nupoint...not a problem since.


Sent from my iPhone using Tapatalk
Title: Re: Issue with MWI lamps
Post by: mandinga92578 on March 24, 2023, 09:15:56 AM
How did you find out which extension was locking up the MWI for the system?