Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Embedded Voicemail Remote Access

Status
Not open for further replies.

Nick473

IS-IT--Management
Feb 12, 2008
5
I need help setting up access to voicemail remotely through the auto attendant. I am new to this so I hope I don't sound too ignorant about this. First of all I followed the directions in the Avaya white papers that I have read. I went to each user that needs remote access to voicemail and gave them an access code. I then went and created a short code to collect voicemail as laid out in the avaya white paper. once I was through with this, I mapped a number in my auto attendant to go to the new short code. For example, Button 8 was supposed to go to *99 via a normal transfer. When I click ok, it gives me an error and says that it can not find a hunt group or extension for *99. It is an IP Office 500 with embedded voicemail. I am running version 4.0 of the Manager software.
 
Yes, Manager says its an error, but did you send the config to the system to enjoy the fact that it will work.
 
easy, much easier than you think:

set up a ddi to ring destination: Voicemail

That's it!

Each user much have a voicemail passcode set in the manager, or they can set it themselves through the prompt, or even easier through the Visual Voice key you have programmed on each phone.

When the system answers, enter mailbox, enter passcode.

 
I did send the config to the box and it does not work at all. It told me that it was an invalid option.
 
Ok, you said setup a ddi to ring to it. I will need more information that this. I am very green at this and need a white paper or something. What is a ddi? I know what DID is. They only have 2 analog lines coming into the system.

Thanks.
 
apologies, if you have analogue you can't point a ddi to the voicemail. You could set 1 of the trunks just for voicemail access but I can't see them wanting this option can you???
 
No, both of the analog lines are used to accept incoming calls. It is not a big office. We are talking about 5 people who need this access. I just don't have a clue of how to set it up. I have called avaya and they can't give me any help. This is kind of my last resort.

Thanks.
 
Works on my system a treat, something else is missing.
 
If you were setting this up new out of the box, how would you do it?
 
By the book as always. I'll set it up again just to prove it again since I was asked to test this last week and did so. 8 hours to go and I'll be back in front of a rack of systems again.
 
Follow the Remote Mailbox Access document from the knowledgebase. Once you have your *99 set up, in your AA set an action to normal transfer and point it to the SC *99, this will allow access to the VM system and request the user ext and pw.
 
5 hours to remember to do it, 15 minutes to do it, no problems.

Short Code *98/?/Voicemail Collect
Auto Attendant 0/Normal transfer/*98

Dial *98 on system, "Please enter your mailbox number"
Put in a external call (BRI line routed by Incoming Call Route to the auto attendant) - press 0 = "Please enter your mailbox number".

And all other others work.

I would suspect the same people who put a warning into Manager also put a stop into the core without realising what they were doing. My Manager (IPO4.1) doesn't give any warning so they've fixed that and probably made a fix in the core also. Maybe you need to go to a different 4.0 release.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top