I hope I hear from Mike Poole on this one... I recently replaced an old Avaya Merlin legend with a single cabinet Opt 11C (Succession 3.0) w Call Pilot 2.5 that I had in storage. Everything is working beautifully, needed no changes to dial plan (had same DID range), trunk routes, etc. Built new voice mail boxes for the extensions, which all work...the only thing that doesn't work is the MWI light at the top of the phone. It will not indicate when new messages are received. I have read as much as possible on here...tried adding the two keys that turn on and off the light to test...the light works then...but only during the test. All ACDN's are acquired as they should be. There was no DN, ACDN, or CDN changes. ELAN and CLAN are working. All Call Pilot services in Services in the NT 4.0 CP Server are started...including Call Pilot MWI service. The MWI DN in a users VM box matches their extension, which is on Key 0 and marped to that set. All are set as SCR...no multi-appearances of any DN on Key 0. No VM box has any one else's DN in it. I am stumped. Can RPL's play a part of this in Call Pilot? When rebooted, the following errors appear in the event browser of CP...
"Event from [] , Event: ID=25, Description: Dialogic Event Management system initialisation failed. This means that one of the necessary stages of the startup of the CT Server has failed. The CT Server will not start. You should try again to start the CT Server. If that fails. contact Dialogic Tech Support. ." and "MWI [] NBosa_Call ServiceThread:Notification Client is not functioning. Rc=102, MaxRetry=0"
At the same time, these messages, in this order, appeared in the alarm monitor of CP..."Fault Manager cannot display messages on Hex Display. rc = 65535", and "Bad message handle", and "Event from [] , Event: ID=6008, Description: The previous system shutdown at 3:38:31 PM on 6/2/14 was unexpected. .", and "Cannot open process associated with service CallPilot MWI Service, rc=87", and "Failed to make TCP network connection, rc = 203", and "NBosa_Call ServiceThread:Notification Client is not functioning. Rc=102, MaxRetry=0", and finally "Event from [] , Event: ID=25, Description: Dialogic Event Management system initialisation failed. This means that one of the necessary stages of the startup of the CT Server has failed. The CT Server will not start. You should try again to start the CT Server. If that fails. contact Dialogic Tech Support. .". Again, everything IS working...except that pesky MWI light on all the phones. Suggestions? I will try to get back and check this post regularily, but in case... dweiss@ryland.com works too for responses! Thanks all!!
"Event from [] , Event: ID=25, Description: Dialogic Event Management system initialisation failed. This means that one of the necessary stages of the startup of the CT Server has failed. The CT Server will not start. You should try again to start the CT Server. If that fails. contact Dialogic Tech Support. ." and "MWI [] NBosa_Call ServiceThread:Notification Client is not functioning. Rc=102, MaxRetry=0"
At the same time, these messages, in this order, appeared in the alarm monitor of CP..."Fault Manager cannot display messages on Hex Display. rc = 65535", and "Bad message handle", and "Event from [] , Event: ID=6008, Description: The previous system shutdown at 3:38:31 PM on 6/2/14 was unexpected. .", and "Cannot open process associated with service CallPilot MWI Service, rc=87", and "Failed to make TCP network connection, rc = 203", and "NBosa_Call ServiceThread:Notification Client is not functioning. Rc=102, MaxRetry=0", and finally "Event from [] , Event: ID=25, Description: Dialogic Event Management system initialisation failed. This means that one of the necessary stages of the startup of the CT Server has failed. The CT Server will not start. You should try again to start the CT Server. If that fails. contact Dialogic Tech Support. .". Again, everything IS working...except that pesky MWI light on all the phones. Suggestions? I will try to get back and check this post regularily, but in case... dweiss@ryland.com works too for responses! Thanks all!!