Voicemail Calling Operator when Operator Transfers Call

[Sheps]

Hello,

New to Mitel and the 3300 ICP, and I have inherited the management from the previous administrator.  I was removing mailboxes which were no longer in use the other day and was mis-informed regarding a extension and deleted a mailbox which was still in use.

This was not a big deal as the user did not have any voicemail, and we just recreated the VM box.  However, since then, the voicemail has been calling the operator whenever the operator transfers a call to that extension and it goes to voicemail.

Calling on a Direct Dial number for that extension does not cause the voicemail ringback.  It is only when the call is being transferred from the operator extension for sure, and possibly any extension.

Any assistance on what I am missing would be appreciated.

I should add, there was a thread similar to this previously by someone else, and unfortunately the information contained within did not help.

[Mattmayn]

When the call comes back to the operator does it say anything like ringing you back or recall? If so it would be a timer in the COS. Another thing to look at is that the user could have programmed call forwarding on the set itself. To see if this is the case run the maintenance command "Locate Feature Extension (ext number)" and you will see any active features on that phone.

[Sheps]

Thanks for the response,

I have checked the active features and there are none.  Other users have the exact same COS and the VM does not call back the operator.

When the operator transfer to the extension, the call back from the voicemail system is actually the voicemail mailbox administration it seems asking for the password.

I also spoke with the user who has the operator extension and she mentioned that yesterday she had not transferred to the extension and the voicemail system called her again.

[ralph]

I'm assuming that you're using the embedded VM.

Edit the mailbox.  Look at "message notification"
The type should be 'extension'
the number should be blank.
Disable user access and set the Schedule to 'disabled'

Let us know how that works.

Ralph

[Sheps]

Thanks, it was the"schedule" not being set to disabled that did it.  Everything else was set as it should be.