Voicemail Ports calling main number

[goulbout]

Hello There,

We are having a problem with our voicemail ports. Our main extension (Operator ext.) keeps receiving calls from the voicemail ports. When the call is picked up it announces that a user (Random users) has voicemail. This is really confusing.

Can you shed any light?

Thanks

[Mattmayn]

What rel. is the controller running?

I assume the voicemail is the embedded voicemail?

[ralph]

There is a bug in earlier software.  There is a patch available.  Better thing to do is upgrade.

Ralph

[goulbout]

The release we're using is : 8.0.8.8
Yes it is embedded voicemail.

Thanks for the replies.

[jimtora]

If your calls are coming from the voicemail ports than it could also mean that programming was done for voicemail notification. Is this occurring to (0) operator only? Try leavinhg a msg for another extn and see if this occurs as well.
Here is what you can do to confirm the previous responses.
First backup you 3300, as well as voicemail and call history.
Do an upgrade of your current version to a stable version. Once this has been done check to see if the problem persists.If it doesn't than their was a bug. If it still does then check you VM settings for notifications to Operator (0).

good luck

[ralph]

This sounds like the bug I'm aware of but the software version doesn't match.   I looked online to find the knowlege base article but couldn't find it.   Below is the text of the readme doc provided by Mitel with the patch to "fix" the problem..

Ralph





This is a temp. patch for p.140570 to address the issue of Voicemail boxes dialling 0,
instead of calling pager number

This patch contains the following files

-stopdial0.o
-readme.txt which provides instructions how to apply




Before begining, in the shell, enter 'cd "/sysro"'
Then enter 'pwd'
You should see /sysro in the results.


Procedure to apply this path on Rel 7.0, 7.0 UR1, 7.0 UR2 and 7.0 UR3.


Step 1: Manually ftp all of the above file(s) into 3300 as follows:

On your PC, open a DOS prompt and do the following action on DOS ( or cmd) prompt.
Change to the folder that include stopdial0.o

e.g. If your folder is c:\patch, TYPE: cd c:\patch

Start the ftp session and perform tasks as follows:
TYPE: ftp <ip address of the controller>
      Enter your ESM username and password to login
TYPE: binary
TYPE: hash

TYPE: put stopdial0.o       
Type: bye


Step 2: Load the patch in RAM ( not require to reboot)
On RTC shell ( maintenance/serial port)
i.e At --> prompt

Type: ld < stopdial0.o



Step 3: To fix corruption:
The user has 3 options:
  1. stopdial0
        this one cleans all mailboxes right away and then set up the
        automatic 1:30 AM  schedule
  2. stopdial0 "nosched"
        this one cleans all mailboxes right away and skips making a schedule
  3. stopdial0 "schedonly"
        this one does not cleans mailboxes right away. The scheduled 1:30 AM run
        will do it.


On RTC shell, Mitel recommends to type:

Type: stopdial0 "noshced"         ##Comment : this is to check and fix immediately


Once you confrim the fix, you can
Type: stopdial0 "schedonly"      ##comment: This is for preventive measure



Note: If the system reboots, you need to repeat step 2 and Step 3 (if required)

[hsearson]

A client of ours had this problem where the receptionist would recieve calls from the voicemail ports. They did have an ACD group which were forwarding calls to the next agent. It turns out that in the 'always forward' option we had to put the ACD path there so calls will be requeued when an agent hits their forward key.  Is it possible the same scenerio can happen?  Maybe a user does not have their forwarding set and it is defaulting back to 'o'.

[v2win]

Are the trunks analog or digital?

[hsearson]

On the switch I work on it's digital. The console gets calls from voicemail ports and when she picks up it's the audio of voicemail prompts.  I disabled on hook dialing on the Voicemail COS but that does not work either.