Night service adjustments.

[BoskerTheArkite]

I have an IP 406 DS 4.2.(11), and for some reason it has started going to night service at 17:00 instead of 18:00, as it's supposed to. It's only doing this on Tuesdays. Other days work as planned.
I have looked at VM Pro and Tuesday looks just like every other week day. I changed it to 18:01 to see if that would kick it in the pants, but it didn't seem to do any good. I have looked at the hunt groups on Tuesday, after it went to Night service and none of them were directed to night service. Help!
Thanks

 

[amriddle01]

Manager doesn't show the groups as in Night Service if it's done via time profile, it only shows if done via a code,button or using Manager. So check the groups time profile and/or system time

http://www.ipoffice.tel

 

[CarGoSki]

Detail the call flow.

PRI to incoming call route to group to auto attendant etc..

You probably have an additional timer on ICR or group.

 

[BoskerTheArkite]

amriddle, I assume you're talking of hunt groups, I couldn't see anything looking suspicious under fallback. I don't quite understand where to look for 'system time'. Where is that?

 

[tlpeter]

Bosker, soes the group have a time profile set under the tab fallback?
If yes then follow Amriddle post.

It does not show "nightservice", it just follows that path.


BAZINGA!

I'm not insane, my mother had me tested!

 

[BoskerTheArkite]

Night service is not checked and is actually darkened out on every hunt group.

 

[tlpeter]

But is there a time profile assigned?


BAZINGA!

I'm not insane, my mother had me tested!

 

[BoskerTheArkite]

Sorry, I mis communicated, Time profile is not checked and is darkened on each hunt group.

 

[tlpeter]

Is it a group on a remote IPO?
Normally those settings can not be grayed out but when it is a group that is configured on a different (scn) IPO then it could the problem.


BAZINGA!

I'm not insane, my mother had me tested!

 

[BoskerTheArkite]

I assume you're asking about another IP office system. This is the only one.
Also, when I said "not checked" I should have said it shows as a grayed out "<None>".

 

[tlpeter]

OK so the time profile option is grayed out.
This means that there is no time profile configured on the ipo itself.


BAZINGA!

I'm not insane, my mother had me tested!

 

[BoskerTheArkite]

So, why come on Tuesdays, does it go to night service early?
I've seen lots of June bugs, but I'm thinking this in a Tuesday bug.

 

[amriddle01]

If there is no time profile someone is doing it manually 1 hr early, or VM pro is doing bit of generic action config

http://www.ipoffice.tel

 

[BoskerTheArkite]

In VM pro Tuesday looks just like every other week day.
I clicked on the NightAA module then I clicked up on top on the icon saying "contition editor" and then the week planner. There my week days all look the same with the exception of where I changed tuesdays time to go to night service to 18:01 instead of 18:00, just to see if I could bump it into behaving.

 

[BoskerTheArkite]

Back in Manager, under line, I selected my PRI group where I see nothing helpful.
Under Incoming Call Route, I see the last 4 numbers in my main number pointing to what looks like a short code for "MainAA".

 

[BoskerTheArkite]

That should read "last 4 digits of my main incoming number".

 

[amriddle01]

You are confusing matters saying it is going into night service when it isn't, time based routing in VM Pro is not night service, are you saying it is the conditions in vm pro that are faulty

http://www.ipoffice.tel

 

[BoskerTheArkite]

I have an icon on VM Pro client, under "modules" that says "Night AA" and I assumed that was night service.
I really have no idea why my calls are going to night service an hour early, maybe it's a VM Pro trouble or maybe it's an IP Office Manager problem.
I wish I was smart enough to figure it out.
I appreciate all of your help.

 

[amriddle01]

Night AA is just a name someone gave that module, it doesn't have anything to do with night service per se, which is where groups are put into night service state by a button/code or time profile, hence the confusion. It's got to be a VM thing if that's what alters the routing based on time of day, do the effected calls route through that module only? if so the issue must be the condition being tested in that module. Do you ever make changes on the server using remote desktop?

http://www.ipoffice.tel

 

[BoskerTheArkite]

I am making the changes via a remote.
Holidays have another route module, but it's completely different.
Those are the only two.