Call Coverage

Calls routed to the night extension using Night Station Service follow the coverage path of the night extension under all coverage criteria except Send All Calls.

If a night extension has a coverage path in which Cover All Calls is administered, all attendant-seeking calls redirect to coverage. Changes to the protocol for handling DID-LDN calls (that is, forwarding attendant-seeking calls on or off premise from the night extension) do not work.

Call Forwarding All Calls

Calls redirected to the attendant through Call Forwarding All Calls do not route to the DID-LDN extension.

Inward Restriction

Inward-restricted phones can be administered for Night Station Service. Night Service features override Inward Restriction.

Night Console Service

Do not provide Night Console Service with this Night Station Service.

Remote Access

A Remote Access extension can be specified as the Night Station extension on an incoming, non-DID, trunk group.

Tenant Partitioning

Each tenant may have a designated night-service station. The system directs calls to an attendant group in night service to the night-service station of the appropriate tenant (when a night attendant is unavailable). When someone places an attendant group into night service, all trunk groups and hunt groups that belong to tenants served by that attendant group go into night service. In this case, the system routes incoming calls to the night-service destination of the appropriate tenant.

Each tenant can have its own LDN night destination, TAAS port, or night attendant.

Timed Reminder

Timed Reminder calls returning to a console that has been placed in Night Service and has an assigned DID-LDN night extension is not redirected to the DID-LDN night extension. Rather, they are dropped.

Trunk Answer from Any Station

TAAS and Night Station Service can both be assigned within the same system, but cannot be assigned to the same trunk group.