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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

centralized voicemail auto attendant

Status
Not open for further replies.
Feb 27, 2006
40
US
We have recently deployed a small site onto an existing customer's site. The SCN seems to be working fine, the two sites are able to dial eachother, and the users at the remote site are able to reach voicemail, etc.

The only problem I am having is with the remote site's auto attendant. They want a very basic setup and I can't get it to work correctly. They want all incoming calls from 8-5 answered by a hunt group, during the day, if no one from the group answers, they want the calls sent to the auto attendant. After 5, they want all calls sent to the auto attendant.

I set the incoming call route up to go to the hunt group, and set the hunt group's voicemail box to point to the auto attendant in VM PRO. I've done this a million times for customers w/o SCN and it works perfectly...

In this remote site's case, in call status, i can get the call to hit voicemail, but it's going to the "Welcome to IP Office, please enter your extension" prompt instead of voicemail... Originally, I couldn't even get it to stay in voicemail, it looked as if the main site was sending the calls back to the remote site.

Is there something specific I need to program at the main site to get this working correctly?
 
Are you doing this via the hunt group night service or directly from the incomming call route??

If the times are set in stone, I would do it from the ICR

Set up time profile as per requirments (remember times are opposite to when programming for a hunt group n/s)

Night Service destination VM:MODULE NAME

Should work a treat.

Jamie Green

IPO ACA:Implement


Fooball is not a matter of life and death-It is far more important!!!!
 
I have the scheduling set up using voicemail pro. That isn't the problem, I can't get the calls to reach voicemail at all... I can't even get all calls to hit an auto attendant.

Is there something I need to program on the Main site's switch to get the calls to stay in VM from the remote site?
 
You didn't make it clear if the hunt group is in the main site or remote. Did you set up a short code to allow the remote site to call the huntgroups in the main site? Did you set up a short code that matches a shortcode on the main site so calls could be passed?
 
The hunt group is on the remote site, and yes a shortcode was created on the main site for the hunt group.

The remote site also has it's own trunks.
 
If you don't program anything into VM Pro for the H/G does it go to M/B when not answered??

Are users M/B's working correctly??

Can you access the hunt group M/B to listen to messages (via short code or Manager)??

Is the Hunt Group name and number unique from other groups and user within the SCN?? Are all users and groups unique??

Is voicemail setup as Centralised voicemail with a destination of the IP line to the Main Site??

Jamie Green

IPO ACA:Implement


Fooball is not a matter of life and death-It is far more important!!!!
 
Are you trying to get it to go V/M on a Leave action or Q'ing??

Remote sites don't get Q'ing on 3.2. They do on 4.0.

Jamie Green

IPO ACA:Implement


Fooball is not a matter of life and death-It is far more important!!!!
 
Remote Queue messages on 4.0 ??

That will only happen if the huntgroup is on main site and you have the Distributed Group license so remote users can logon the main sites group, doesn't it?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top