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!

IP500 4.0.7 Embedded VM, NO NIGHT Greeting?!

Status
Not open for further replies.

r6wraith600

IS-IT--Management
Sep 14, 2006
124
CA
This may be in relation to this post.....

However I am bring forth the question differently I think. Voicemail is on Full AA and nothing fancy. Using the time profile and creating 3 groups (day, afternoon, night) and the appropriate times (not over lapping).

The day works, the afternoon works, but the night does not play (*813) and the VM results by playing ONLY the Menu Options (*814).

I tried EVERYTHING and not matter what I did the night when flagged or the time being changed to allow the proper call sequence to take place, it did not work.

Am I the only one experiencing this? Or am I not handling the time profile properly? OR should I just wait till 4.1 is out in a month or so?
 
This is some great feedback guys!!!!

There are some comments I would like to make and ask as well.

As for the 1 minute gap, if you read the Avaya help file it is very clear that during a time that is not defined it defaults to the first profile greeting. That's why the drop down menu's provided allow the proper selections, as noted by Plat Guy. So for that one minute it will play the first greeting. This I tested.

AZJeepGirl
"Closed M-F 12:00AM to 7:59AM
M-F 4:30PM to 11:59PM"

Please explain to me the need to overlap these two times on the same day. Does this VM not recognize the "next day" switch over?

We have always gotten it to play the 814 option. We have as well deleted and manually recreated the short codes and rebuilt the VM AA from the ground up, same result.


As noted by JustinTMI, this is what we set.

"Monday to Friday 8:00AM to 12:00PM (Morning)
Monday to Friday 12:00PM to 4:30PM (Afternoon)
Monday to Friday 4:30PM to 8:00AM (Night)"

I even tried JUST a night only greeting in the first spot
and flipped the IPO to the night time proper hours and STILL it would not play the first part of the greeting "good evening".
 
This is probably the most straight forward thing to so that I have seen yet I can't find a reason why it doesn't play the 813 message when forced to. I would rather just play 814. I set up as well a scenario so that I knew the profiles were right for this test. I set and day and only a night and it worked perfectly for the day but when night comes around it just plays the 814 portion.

 
I would rather just play 814" Should have been "IT" would....
Wish I could edit post in this forum.
 
Still hoping for an answer......anyone else have any experience with this?
 
Your night should be
12:00am to 8:00am M-F
4:30pm to 11:59pm M-F
12:00am to 11:59 S-S
 
I'm not gonna test it so I take your word for it that it doesn't work. Assuming that it isn't, I would set up a second aa and use an incomming call route with a night destination as a completly different aa as the one that plays the day and afternoon greeting. In other words, I would have the destination field go to the first aa that had time profiles in it to play the morning and afternoon greetings. At night I would have the night fallback and appropriate time profile go to a shortcode to play another aa that played the night greeting.
 
Your night should be
12:00am to 8:00am M-F
4:30pm to 11:59pm M-F
12:00am to 11:59 S-S"

MrBob622 this makes much more sense to me for night time. We will give that a shot, if not Ronromano's is another option.

I am sure think there is "bug" in 4.0.7 that will surface but it doesn't seem like a lot of people have piles of experience with the Embedded VM as it is. Not my first choice for sure, but you would think the Avaya would have tested such a simple feature to ensure it works properly.
/end frustrated rant :)

Thanks guys and gals for all the feedback, it's much appreciated!
 
Did you find a solution? I am having the exact same issue on embeded with ip 406 it's driving me crazy & my customer is getting pissed.
 
I think I will create a second AA called night,record the night greeting and menu in *824 point the phantom user via sc to the night AA. voila should work.
 
This is not a bug. By design there is only the standard greeting option when using the Embedded Voicemail. This is something I came across with the IP400 and after searching through the help and engineering docs, it was clear that there is only one greeting option available.

How I got round it was rather simple. You can assign a night service profile to the incoming call routes.

- Create a time profile to include your out-of-office hours. This time profile will be a negative to your office hours ie 00:00 -> 07:59 and 18:00 -> 23:59 Mon to Fri and 00:00 -> 23:59 Sat,Sun
- Create an Out-of-hours user but do not assign it to physical extension. This means when you ring out-of-hours, it will just ring through to vmail.
- On the incoming call route, set the Night Service Profile to use the time profile you created.
- Set the Night Service Destination to the out-of-office user you created.
- Create the required short codes to access the Out-of-hours user’s vmail, set the greeting for this user “Our office are now closed, please ring… leave a message…” and bingo, you have two different greetings. :)

Bit poor of the Embedded Vmail if you ask me, but that is how I have got round the problem.

Good Luck!!
 
Just to follow up I sent my config to my Avaya Rep and he was going to test it in the lab. I tried the second AA as well but had the same results.

Paganatron....I will look into your comment however I had no problems getting it to play the Morning and Afternoon which is 2 greetings technically. It was the 3rd greeting that I was trying to make work.

When it's an option in the program we shouldn't need "a work around" in my opinion. Hopefully we will see a fix in 4.1 coming soon.
 
Ok I split up my night time profiles like we used to have to do before 3.2 and the issue has been resolved.

In stead of night M-F 4:31PM to 7:59 AM I had to change it to M-F 4:31 PM to 11:59 PM M-F 12:00 AM to 7:59 AM. Hope this helps some pore bastard out there.


As stated above, in this same post.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top