Day and night with Automated Attendant

[mrbi1310]

Hi All

I have using ISDN trunk and Automated Attendant funcation, and now my customer want to use calender
- From 8hAM to 17hPM when customer call-in will hear voice guide and press extension + operator
- From 17h01PM to 7h59AM when customer call-in will routing direct to hungting group

Please help how to config

[mrbi1310]

Hi All

The currently, the system work with: when customer call-in will hear voice guide and press extension + operator
but i have config with schedule on Entity incoming call but not work, please advise

[murraya]

double post?

[mozsert]

Hi mrbi310
For example DID number xxyy100 would go to AA

Follow these steps,
write an entry to Public numbering plan Attendant call xxyy100 - xxyy100 0
write an entry to Resticted numbering plan Attendant call xxyy100 - xxyy100 0
In time range 1st line for all days: 8hAM to 17hPM - Normal/Opening hours - Attgrp 1
In time range 2nd line for all days: 17PM to 8AM - Res/Closing hours - Attgrp 2
Create a virtual extension and divert it to Hunt group
In attendant groups 1st line: put all VM ports
In attendant groups 2nd line: put virtual extension
clear 'inhibition time range' flag from subscriber features of VM ports/virtual extension/hunt group members

I hope these helps you.

[murraya]

hi, I think that is for OXO but ths is for OXE.
looks like my eariler post is not there so sorry thought it was a double post.
if your ddi goes to AA access then create a entity with time switching set in incoming state hours.
in the AA access assign the entity created then point day and night destinations to different tress then leafs.
hope that helps.

[mrbi1310]

Hi

I have done to take feature work
- we need create double AA with 02 access, and create day and night in Entities
- Create entities with routing for day//night

THanks

[murraya]

you can do that i.e send DDI to entity call (incoming state hours set) with day and night different AA accesses
or
send call to aa access directly and set day/night catagory to different AA trees. assign the entity (with incoming state hours set) to the AA access.

the second way means you only use 1 Access (you only have 8 per caller catagory so are presious sometimes)