Night Service

During Night Service, calls that are normally routed to the Attendant are directed either to the customers Night number (LD 15) or to the trunks NITE DN (LD 14). Auto-attendant (Call-Pilot) time of day controllers are not affected, only attendant and trunk (NITE) calls.

• Options 11-81C are automatically in Night Service on power-up.
• Switching from Night to Day service requires an attendant console.
• Switch to Night from a console, or disable/enable all consoles (LD 32).
• Without an attendant console, the customer is in permanent Night Service.

Note: New customers created in LD 15 are initially in Day service, and will switch to Night service after a sys-load.

The assignment of Night DN's is optional, it is therefore possible to program a system with no night answering point - the caller would hear ringing, but their call would not be answered.

The Night DN may be defined as a multiple appearance DN (MADN) with multiple call arrangement (MCR). All sets assigned the DN should be in the same switch (node) - as is the case where there is only one Meridian telephone switch.

Setting of Night / Day Service is implemented at an Attendant Console:

• Toggle between Day and Night Service by pressing the [Shift] + [Day/Night O/C] (Sun/Moon) keys.
• Systems without an AODN (LD 15) can be put into Night Service by pressing the [O/C] key on all consoles. This busies out all the consoles and puts the system into Night Service. Pressing the [O/C] on any console will return the system to Day Service.

Note: LD 14 NITE DN's take precedence over the LD 15 NIT 1-4 DN. This includes internal calls or external calls on trunks that are not Auto-Terminated or Private (LD 16, AUTO=NO and PRIV=NO).

Types of Night Service

Three types of Night Service are provided which the customer can specify separately or in any combination:

• Selected Trunks to Selected Directory Numbers (DN's)
  In LD 14, trunks can be assigned to ring individual Night DN's during Night Service. A LD 14 NITE DN takes precedence over LD 15 NIT 1-4. If the LD 14 NITE DN is different to the LD 15 NIT DN, incoming trunk calls cannot be picked-up by dialing the "Trunk Answer From Any Station" code 1 + 4. TAFAS can only be used for calls to the LD 15 NIT 1-4 DN's.
• Night Answer Telephone
  All calls normally routed to the Attendant Console can be routed to one particular DN (Night Bell) when the attendant puts the system in Night Service. The NIT1 DN could terminate at phones or external bells and could be answered at any other phone by dialing the TAFAS code 1 + 4. LD 15: NIT1 xxxx (Night Answer point), TIM1 (if no time is entered, 24 hours is assumed).
• Night Service by Time of Day (NSTD)
  Allows the definition of up to four Night DN's (NIT1-4) with a time associated with each - start times must be in ascending order. Incoming calls can be answered using the TAFAS code 1 + 4.

Programming

Night Service for a customer:

• LD 15, CHG type NIT:

  NIT1 xxx...x, X	- the first night DN (enter X to remove).
  TIM1 0-23 0-59	- start time of first night service DN (hour and minute)
  :
  NIT4 xxx...x, X	- the fourth night DN (enter X to remove).
  TIM4 0-23 0-59	- start time of fourth night service DN (hour and minute)

Night Service DN for trunks:

• LD 14, CHG type COT:

  NITE xxx...x, X

  - Night Service DN for this trunk (enter X to remove)

Printing NIT data:

• In LD 21:

REQ: prt                           print in LD 21, change in LD 15
TYPE: nit    
TYPE NIT_DATA
CUST 0       
             
TYPE NIT_DATA
CUST 00      
NIT1 3600                          first night DN (enter X to remove)
TIM1         
NIT2                               second  "   " ...      
TIM2         
NIT3         
TIM3         
NIT4         
TIM4         
RPNS NO                            Recall With Priority During Night Service - (no) yes
ENS NO                             Enhanced Night Service - (no) yes

• Print COT trunks in LD 20, look for the NITE prompt.

REQ: prt                           print in LD 20, change in LD 14
TYPE: trk   
TN 8 0 2 0
:
RTMB 2 1                           Route/Member number
NITE 5555                          Night answer DN
ATDN 0                             Day     "    "   (if Route is AUTO YES)

Incoming Digit Conversion:

Separate day and night Incoming Digit Conversion trees can be assigned to a DID route. An NDNO tree can be used to redirect specific DID DNs to an alternate answer point during night service. Print the route data block (RDB) in LD 21, and check the following prompts:

REQ: prt                           print in LD 21, change in LD 16
TYPE: rdb 
CUST 0
ROUT 2
:
IDC YES                            YES = this route uses digit conversion
DCNO 0                             Day mode IDC tree number
NDNO 1 *                           Night mode     "    " 

An asterisk (*) next to DCNO or NDNO indicates the active tree, eg: whether the PBX is in day or night mode. Remember: a PBX without a console is always in night mode. Use LD 49 to print, add, change, or delete DID Incoming Digit Conversion (IDC) data.

Auto-terminating or Private trunks (LD 16, AUTO=YES or PRIV=YES) are not affected by Night or Day Service, and behave like Direct Inward Dial. Incoming calls are routed directly to the ATDN (LD 14) or PVR Key (LD 11), not to the Operator or Night DN's.

Attendant Overflow Position (AOP) allows calls to be automatically rerouted to a specified Attendant Overflow Directory Number (LD 15: ATT_DATA, AODN XXXX) when calls waiting to be answered have exceeded a defined threshold (AQTT), or an attendant is in the Position Busy state, but the system is not in Night Service.

Forwarding Consoles to CallPilot:

• In LD 15: NIT_DATA, set the NIT1 to the main CallPilot voicemail number (ACD).
• Add a Service Directory Number, with Service DN: 0 (or other console LDN), terminating at a night Application.
• In night mode, calls will forward to CallPilot. A console is never busy, so it can't use 'forward no answer' to re-route calls.

---