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

Night Service not working after upgrade 1

Status
Not open for further replies.

KiraMcD

Technical User
Mar 30, 2004
22
US
Equipment: IP412

Recently upgraded from 1.3 to 4.0. Big jump. Most everthing's working (including some stuff that had never worked before: MOH, ring tones when calling another extension, etc.). What's no longer working is the Night Service. I did not set up the system (outside vendor) and was given next to no training, so please bear with me.

The Night Service is normally turned on at the receptionists desk via a button programmed *20*309#. Extension 309 is the Hunt Group for all incoming call routes. There is another Hunt Group called Night (ext. 111) and a User called NightAttendant (ext 112). I'm not clear what part these two play.

In VoiceMailPro, I have NiteAttend setup with all the forwarding options. I can listen to the recording when I dial 310 and it allows me to enter an extension, dial by name, etc.

Since the upgrade, when Night Service is turned on, callers hear the generic greeting for VM box 309. At least they can leave a message, but it's not what we want, obviously. Can any one tell me what I'm missing? I'm sure it something obvious, so don't be afriad to use a clue-by-four if you think it's warranted. ;-)

TIA,
KM
 
You can setup the button under Advanced - Set Huntgroup Night service then in the action field - pick your hg 309.

Make sure that the Night HG has vmail checked on and I'm not sure why there is a user set up in there - you shouldn't need that.

In VM Pro - setup a leave mail start point for the 309 hunt group to go to the module(s) for the automated attendant. You shouldn't need a start point for the night hg -since all calls were first directed to the 309 hg the identity of this group will follow thru to vmail.

 
I didn't start working on IPO until 2.1 so I might be way off but I would look at the night service fallback group for 309. It sounds like it should be set for 310. When you dial *20 it is putting 309 into night service so if there is no fallback you would get the generic greeting as you describe.
 
Who did the upgrade?? The Vendor or yourself????

Do all your Voice prompts sounds ok?? VM Pro has 2 modes Intuity mode and IP Office mode?? The prompts are very different and it can change the way thing like this work.

Are you in the correct mode. Dial *17 and see if it plays the prompts like it used to.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office


Fooball is not a matter of life and death-It is far more important!!!!
 
dphoneguy: The Advanced button programming didn't work. Now all calls ring through to her phone when the receptionist turns on the NS. I switched it back to the way it was. VM is turned on in the HG Night. I deleted the User 112 (I think it was a work around when we first got the system. We were using an outside service.)

ronron: I don't have the option of setting the NS fallback to 310. It is set to HG Night.

jamie: I did the upgrade; when it failed I called Avaya and they ghosted me, fixed a couple of things and got me up and running again. When I dial *17 I hear the regular voice mail recordings and all the button prompts work properly. When I dial 310 I hear the NS message that I recorded and all the button prompts work properly. My only modes were online or offline. I clicked Online and then clicked Save and Make Live. Still nothing.

dphoneguy: In VMPro there was a Leave Mail start point for Night but not for 309. I created one and voila! It's working! Thanks so very much!!

KM :-D
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top