Set NightService actually puts hunt group to Out-of-Service

[MikefromMB]

Hey everyone,

It seems that when we put our Night Service on, it actually sets it to "Out-Of-Service" and it does not do it automatically according to the time profile. For example, when pressing the button 'Set Hunt Group Night Service' for my Group 100, the status on the phones show OG rather than NG, where O = Out of Service, N = Night Service and G = Group member.

This is my environment:

Server: Avaya IP Office 9.1.7.0 build 163
Phones: Avaya 9608
DayAA = A group with 1 user called PhantomDayAA
NightAA = A group with 1 user called PhantomNightAA
Time Profiles:
--Open = M-F, 8 to 5
--Closed = M-F, 5:30pm to 7:30am + Sat & Sun (set such that it gives a 30 min window pre- and post- "Open")


Programming:

The main group (Group 100) has OVERFLOW set to Group mode going to the DayAA group (I don't think anything here is an issue, but including it fyi). It also has the FALLBACK as Day Service Time Profile = None, Out-of-Service Destination = DayAA, Night Service Destination = NightAA.

Our front desk phone has a programmed button of 'Set Hunt Group NightService' for Group 100 which, as mentioned above, when activated actually sets the status to OG rather than NG. Coming in during the Closed time profile still shows it as OG.

I don't know why my night service seems to default to the out-of-service setting. The Out-of-service goes to DayAA, which is good during the day, but I want my Night Service to go to NightAA.

I'm not sure how this happened, but I need my Night Service back.

Can anyone help me, please?

Thanks.

 

[intrigrant]

O = "Out Of Hours" which is used for both NightService as well as for Out Of Service.
N = "Do Not Disturb"

Sometimes it helps to red a manual now and then...
I did not read any further as my brain is overheated right now

 

[amriddle01]

It's never said N for nightservice, always O regardless of it being OOS or NS, don't use an icon on the phone as a definitive troubleshooting tool, test it

 

[MikefromMB]

Thanks for this information. It corroborates what someone else has pointed out to me in the documentation (which I did not have access to at the time). I was mis-informed and I apologise for the inconvenience I may have cause.

Again, thanks for the help, and sorry about my little ID10T problem.

Mike