We have an OfficeServ 7200 system which I recently switched from a PRI to SIP trunk that has been notifying my voicemail box (I'm the admin) every day since. Each morning I have the "1 NEW VM MSG" message showing on my set display and the "message" key LED is on but when I log onto my voicemail there are no new messages. I'm assuming this is some kind of alarm but not sure what is causing it. Initially I thought it might have been because the PRI circuit was no longer active and the PRI trunk card was reporting this to the MCP which was sending the alarm - so I shut down the system and removed the PRI trunk card. This didn't make any difference as I'm still receiving the alarms. Any suggestions as to what might be causing this and how to stop it from happening would be appreciated. Thanks.
So when you log into the voicemail and enter your password you then get the no new messages prompt?And then does the display go back to normal time/date display and message light goes out?
So when you log into the voicemail and enter your password you then get the no new messages prompt?And then does the display go back to normal time/date display and message light goes out?
Correct for both. If I wait two days it will show 2 new messages waiting and so on but when I log onto voicemail it says "there are no new voicemail messages".
Very strange I could see it if there actually was a "short" message like a hangup but then there would be an actual message. But every day is strange Have you checked the activity logs to see if you can see anything? There must be something causing it
What do you mean by activity logs? The OS 7200 Alarm History (6.1.1) has nothing showing up that coincides with these daily alarms. On the voicemail system the "Display Error Log" shows the following two entries every day at 3:00 a.m. but nothing else that occurs daily:
NOTICE - Thu Feb 6 3:00:00 2020
Daily system maintainance
NOTICE - Thu Feb 6 3:00:56 2020
System maintainance complete
The voicemail user and activity logs don't show anything that is occurring daily. This problem definitely started right after we switched from the PRI to the SIP trunks but what exactly is causing it has me stumped. Thanks.
Just to rule out that this is part of the VM daily maintenance, I manually kicked that off and it completed without triggering the voicemail alarm so it's not related to that. Guess that isn't a surprise though as the PRI to SIP trunk migration shouldn't affect the VM system. It's got to be something coming from the MCP I think but have no idea what.
Your calling it a voicemail alarm but isn't this a voicemail message? Whatever is sending this message should show up in the port activity .
I guess I'm calling it a voicemail alarm as I assumed that's what it was since there isn't an actual voicemail message associated with the display and message light indicated message. Unfortunately, it happens overnight sometime so I'm not sure how to monitor the port activity unless I want to pull an all-nighter ;-).
Do you have a SVMI manual?You should be able to check the Operating Utilities port activity log and do a search
I looked through the port activity log for last night and nothing stands out. I see the following messages repeated all the time, all day long, every day:
=>NET 0:34.52.66 Admin error detected: (20,0) Connection reset
=>NET 0:34.52.66 Connection open
=>NET 0:44.52.00 Admin session connected
=>NET 0:44.52.00 Admin remote close detected
=>NET 0:44.52.00 Connection release
=>NET 0:44.52.00 Admin error detected: (20,0) Connection reset
=>NET 0:44.52.00 Connection open
=>NET 0:54.52.06 Admin session connected
=>NET 0:54.52.06 Admin remote close detected
=>NET 0:54.52.06 Connection release
=>NET 0:54.52.06 Admin error detected: (20,0) Connection reset
=>NET 0:54.52.06 Connection open
=>NET 1:04.52.67 Admin session connected
=>NET 1:04.52.67 Admin remote close detected
=>NET 1:04.52.67 Connection release
=>NET 1:04.52.67 Admin error detected: (20,0) Connection reset
=>NET 1:04.52.67 Connection open
=>NET 1:14.52.79 Admin session connected
=>NET 1:14.52.79 Admin remote close detected
=>NET 1:14.52.79 Connection release
=>NET 1:14.52.79 Admin error detected: (20,0) Connection reset
=>NET 1:14.52.79 Connection open
=>NET 1:24.52.47 Admin session connected
Well the activity log is supposed to show everything that happens in the system so I'm not sure why you can't see what's setting the light
I've seen this occur. Usually it's caused by 2 mailboxes having the same extension, so the 2nd mailbox keeps setting the mw light on the other extension.
This usually occurs when you manually didn't extension/mailbox numbers in the vm though (eg when changing the number plan from 3 to 4 digits, so you don't have to rerecord all greetings)
Going from pri to sip shouldn't cause this.
If it is this or will be hard to track down, you're going to have to manually check every number in every mbx and ext block to make sure they are correct.
I thought of that but it seems strange that it happens overnight and only 1 new message a night.You would think if that was the case it would happen at random times and during the day?
Thanks for the replies. I'll check the duplicate extensions on the mailboxes as I have no other ideas of things to check. If this situation would require the other mailbox to receive a voicemail every night, that's not definitely happening as we only have about 15 people on the system and usage is very low and definitely nothing going on overnight. As well, I would see this in the activity logs if there was a message being left for some other mailbox.
Is there the concept of system alarms that would show up this way or is this something completely unrelated and likely due to some problem with the voicemail system itself? Thanks.