Telephone System Technical Requirements
The Systems shall be engineered and factory tested according to the specifications described or referenced within this article, and will include but not be limited to the following:
1. System Functional Requirements
a. Only new and unused equipment of the latest field-proven design in accordance with EIA-464 shall be provided. The selected CONTRACTOR shall be responsible for the compatibility of the interface equipment with any and all circuits provided by the local authority. This service may be in the form of either individual copper pair trunk lines or a trunked fiber optic interface such as an E-1. Refer to EIA-496 for interface requirements. The final interface requirement to telecom operator will be determined at a later date.
b. The system’s basic module should be capable for a 100 percent expansion in future, and shall be provided with 20 percent spare line cards.
c. The equipment will be mounted in industry standard 23-inch cabinets and shelves (provided by Others). They shall be free standing, structurally reinforced units equipped with tie down assemblies. Cabinets shall be of such a design to minimize RFI/EMI radiation in compliance with FCC regulations. Cabinets shall accept cables from either overhead ducting or under floor plenum.
d. The switching system shall be a fiber-distributed, fully featured digital switching system capable of providing PABX service for voice and data communications. It shall have stored program control, redundant CPU, and redundant critical subsystems. Additionally, it shall have self-diagnostic routines, modular design, and universal slot port architecture. The central call processing unit shall be located in the General Services Building Ground Floor Communications Room.
Peripheral units shall be connected to the central call processing unit via a single pair of single-mode fiber optic cable. Contractor shall assist in locating the peripheral units with a minimum of one peripheral unit per plant process unit located in the process unit Control Building. Phones shall be connected to the PABX via ports located on the peripheral units.
e. The trunk side of the PABX shall support trunk ports to the local exchange.
f. The PABX shall be capable of routing all calls to PSTN trunk lines, fiber optic or copper (See Section 3.1a).
2. Reliability Requirements
2.1 The PABX shall be designed and configured to incorporate stored program technology, internal scanning diagnostics, diverse routing, secure power, and environment sufficient to ensure overall call processing availability of at least 99.98 percent or better on an annual basis for the PABX.
2.2 The system software must be field-proven, and easily upgraded as new releases are available.
3. HCISS Requirements
3.1 Direct lines between the Telecom Company Central Office and plant buildings, as specified, shall be used to satisfy the High Commission on Integrated Security System (HCISS) requirement of a reduced land line system for a minimum period of twelve (12) hours as per HCISS SSD-12.
4 Remote Peripheral Resources (Networking)
The PABX shall be installed in a fiber-distributed configuration with CPU to peripheral connections achieved through single-mode fiber optic cable connections between the buildings being serviced. Therefore, the network peripheral modules shall allow for the physical distribution of operator consoles, analog/digital lines and trunk circuits via fiber optic cable pairs connected to the main CPU module without the need for an external multiplexed unit. It shall be possible to establish telephone calls within the network without a second dial tone or operator assistance.
5. Automatic Re-Boot
In the event of a system outage the system shall provide for an automatic re-boot of the operating system. The sequences, functions and events must return, intact, reflecting the
most recent up-dates.
6. Limitation on Terminal Equipment Placement
The PABX shall support the placement of analog or digital telephone sets and attendant console 1,200 feet or more from the peripheral module equipment.
7. Dual Tone Multiple Frequency/Pulse Operation
The system must support the use of DTMF signaling with conversion to dial pulse as required by connecting trunks.
8. Loop/Ground Start Operation
The system offered shall provide for loop start operation, either dynamically assignable or fully automatic from common hardware (trunk card). Universal programmable trunk cards
by port or multiple signaling should be used.
9. Self-Diagnostics
The systems shall contain a real time sweeping diagnostics program that will monitor key areas of system operation. The status of the system shall be available at the
maintenance service supervisor’s terminal.
10. Traffic Capacity and Grade of Service Requirements
The PABX system shall support the specified traffic volumes and provide, as a minimum, overall grade of service as defined below:
a. Total system capacity of 1000 Erlangs
b. Voice line average 16 Centi-Call Seconds (CCS) per port
c. Central Office line average 16 CCS per port
d. Telephone Directory – The system software shall be designed to allow for the identification of 1000 Telephone numbers.
e. 112 Trunk groups – Each trunk group can support up to 96 trunks and be capable of assigning different routes.
11. Grade Of Service
The PABX system shall provide the following defined grade of service:
a. Within the system, calls shall be virtually non-blocking
b. Blockage probability between a specific line and an idle out-going trunk shall be less than 0.01 percent (P=0.0001).
c. Blockage probability between a specific incoming trunk and line shall be less than 0.01 percent (P=0.0001)
d. Blockage probability to system service circuits, e.g., incoming receivers, senders, announcement, conference, tone and ringing circuits, shall be no greater than 0.1 percent (P=0.001)
e. Not more than 1 percent of all dial tone requests shall encounter a dial tone delay greater than 2 seconds in the busy hour.
f. The system shall connect a MF or DTMF receiver to an incoming trunk in such a way that not more than 0.5 percent of all attempts encounter a delay greater than 270 milliseconds for immediate-start trunk groups and 2.0 seconds for wink start or delay dial operation.
12 Networking Features
The CONTRACTOR shall state the standard and optional capabilities of the proposed PABX with regard to the following:
a. DPNSS- Digital Private Network Signaling System (DPNSS) Cassette
b. APNSS- Analog Private Network Signaling System
c. DASS2- Digital Access Signaling System Number 2
d. Automatic Route Selection or Least Cost Routing
e. Call back with queuing
f. Dialed Digit Translation – For forcing on-net calls dialed over off-net facility back to on-net and vice versa for network overflow over off-net facility with the least cost routing. A capability of translating at least 15 digits is required
g. Network speed calls with pauses for multiple switch access codes in the Tandem Tie Trunk Networking
h. Network Traffic measurement
i. Basic Voice and Data Calling (Category 1 and Category 2).
j. Distinctive ringing for off-plant versus intra-plant calls.
13 SYSTEM FEATURES AND FUNCTIONALITY
The CONTRACTOR shall indicate in their response showing the standards and options of system features and functions. The PABX system standard features and functions is not necessarily limited to the following:
Dialing Plan:
The selected CONTRACTOR in conjunction with the OWNER shall implement a Network Dialing Plan after the selected CONTRACTOR has completed station reviews at the complex.
14. System Features
a. Station-To-Station Calling – Calls shall be able to be placed between stations without attendant assistance within defined populations on the switch.
b. Direct Inward Dialing (DID) – The PABX shall provide DID feature for the direct completion of calls to defined station locations within the system without attendant assistance or dial an additional extension numbers.
c. Direct Inward System Access (DISA) – This feature allows users outside the PABX to access an extension without attendant assistance by dialing an additional 4 digit extension number after receiving a voice announcement.
d. Direct Outward Dialing (DOD) – The PABX shall provide for the placement of external calls without attendant assistance. This will be accomplished using a single digit followed by the external number.
e. Station Hunting – The PABX shall provide for calls that encounter a busy signal to be routed to pre-determined additional station locations in either a consecutive or non consecutive manner until an idle line is reached.
f. Call Forward-Busy – Calls to a system station position encountering a busy signal shall be automatically forwarded to a designated predefined destination.
g. Call Forward-No Answer – Calls placed to a specific station that are not answered after a predetermined period of time shall be redirected to a predefined second destination.
h. Direct Trunk Access – To support maintenance of the system, the ability to “dial access” a specific trunk based on class of service will be provided.
i. Flexible Plan – The PABX shall support the in-Kingdom nationwide numbering scheme for DDD, IDDD and network calling, with the “A” digit assignable to specific call routing.
j. System Level Intercept – In the event a call cannot be completed as a result of defined call restriction or dialing irregularities, the system shall be capable of routing to the following three destinations as defined by the System Manager
1. A reorder tone
2. System level recorded announcements
3. The attendant
k. Class of Service (COS) – The PABX shall provide conditional class of service markers, as defined by the system manager, at the station and trunk levels. Each Trunk/Line on the PABX shall be a definable COS.
1. Individual stations can be restricted to specific features and dialing areas.
2. Trunk groups can be marked to provide direct access to special service trunks and/or dedicated tie trunks.
3. Classes of services are as follows:
i. COS A: No restriction in features and able to make International long distance calls.
ii. COS B: No restriction in features and able to make long distance call within Kingdom
iii. COS C: No restriction in features and able to make local calls within Jubail area.
iv. COS D: Limited features and not able to make out-going trunk call.
l. Class Of Restriction (COR)- In the event of emergency status the PABX shall provide the capability to restrict all or some extensions from dialing outside of the
system.
1. COR A-Restrict all out-going trunk calls.
2. COR B-Restrict out-going trunk calls of COS B and COS C.
m. Dial Pulse/DTMF Conversion – The PABX shall provide for the conversion of dial pulse signaling to DTMF on either line or trunk ports of the system, if required.
The system shall be capable of automatically converting DTMF signals for transmission over rotary-dial-only trunks, if required.
n. Emergency Transfer Control – Under the control of the system manager predefined trunks or trunk groups shall be capable of being directed to specific station locations.
o. Line Lockout – In the event that a line is inadvertently left off hook, the system shall apply a reorder tone followed by a howler and then, after a period of time predefined by the system manager, take the line out of service.
p. Line and Trunk Ring Down (Direct Connect) – Once an associated “station” goes off hook, it will ring a defined station location on the system whether on a local
line or on a designated CO, FX, WATS or Tie trunk.
q. Tie Trunk Service – The PABX shall provide for a special trunk class of service that will, upon incoming seizure, cause the designated trunk to be terminated at a
specified station location on the system.
r. System Partitioning – The PABX shall be capable of being both line and trunk partitioned so as to provide for individual management of groups on the system.
As required, groups can have their own attendants and routing schemes in addition to assigned class of service features. System-wide administration and
control will override the groups.
s. Prompts and Tones – The PABX shall provide special prompts and tones to verify completed operations and conditions. In the case of recorded intercept, this will
be provided electronically rather than by tape. In conjunction with other features, the system will provide music on hold from a common source either within or
adjunct to the system.
t. Account Codes – Account codes identify the caller or called party on the station message recording record (SMDR). This information can then be used for client
billing. Account codes can be one to twelve digits long.
u. Call Detail Recording (SMDR/CDR) – The PABX shall provide, through a dedicated port, detailed call information, to include:
1. calling and called numbers
2. trunk identification
3. date
4. start time
5. account codes
6. authorization codes
7. duration on every call
The selected CONTRACTOR shall define in detail the interface proposed. The output of the SMDR/CDR shall be stored in an electronic storage device (PC) with a capacity for a minimum of 30 days of traffic.
v. Music on Hold – Music on hold provides a caller with pre-recorded music or a message during a hold period, giving a caller confidence that he has not been “dropped” while being held.
w. Traffic Measurement – The traffic measurement feature enables traffic data for the system to be accumulated over a user-programmable interval of time, and printed out as a traffic report, as required. Each report includes but is not limited to the following:
1. Peg counts of individual incoming, outgoing trunk groups, both way trunk groups, and DTMF Receivers.
2. Busy peg counts of outgoing trunk groups.
3. Usage of the foregoing attached items (format in CCS or Erlangs).
4. Maximum usage values of trunk groups and DTMF Receivers.
5. Operator activities (per console) such as calls answered, calls abandoned, and average waiting time values.
x. Toll Restriction – The PABX shall provide access restriction, assignable by COS to stations. Non-local calling or calling outside of a management-defined group of area codes shall be barred to stations so class marked. Stations that are toll restricted shall be capable of overriding this restriction on a per call bases by predialing one of several management defined account codes. A minimum of 10 codes shall be possible. There shall be no limitation to account codes.
y. Toll Fraud Prevention – The PABX system shall be equipped with the highest level of security design features for preventing unauthorized access by hackers attempting toll fraud and system sabotage. PIN codes for any Direct Inward System Application (DISA) and class of service restriction for access will be required.
15. Station Features
15.1 Call Hold – The user shall be able to place an existing call on hold and place a second call or respond to a Call Waiting prompt and return to the original call as
required.
15.2 Call Waiting – The user when on a call shall receive an audible prompt that a second call is waiting. Using the hold feature, the user shall be able to alternate
between calls or cancel either as required.
15.3 Call Forwarding – The user shall be able to route all incoming calls to a predetermined second station either on or off the system. Outward dialing from the station will not be affected. Call forwarding destinations are to be defined and limited by COS.
15.4 Call Transfer/Three-Way Calling – The PABX shall allow the user to place on hold an existing call, then originate a call to a third party. The user will be able to communicate privately with the third party prior to adding the original party. The user can complete the transfer by hanging up, even if the third party call is still in the ringing mode.
15.5 Call Conference – Unassisted from an attendant position, the properly classmarked station user shall be able to establish a multi-party conference connection with as many as eight (8) individual participants. Participants can be located either on or off the PABX.
15.6 Speed Calling – This feature shall allow the user to place a call, whether internal or external to the system, using an abbreviated dialing code as predefined by the user.
15.7 Call Pick-Up – A user shall, by dialing a defined code, pick up calls directed to other stations within a defined group.
15.8 Automatic Call Back (Queue) – When calling an extension and receiving a Busy tone, the caller shall have the option to dial a pre-defined code. The system will then monitor the called extension, and when the extension is on hook (free), the system will ring both parties. Callbacks (Queue) can also be used to queue for busy trunks and hunt groups.
15.9 Night Connect – During after hours operation, a night bell can be provided to a group of lines, allowing any station in the group the ability to dial a code and be connected to the call.
15.10 Station Camp-On – The PABX shall allow a calling station, upon receiving a busy signal from a station within the system, to queue for call completion once the busy condition clears. A distinctive camp-on tone shall be provided to both the calling party, to indicate queuing, and the called party, to indicate call waiting. This feature shall be assignable as a COS for both the called and calling parties.
15.11 Do Not Disturb – This feature simulates a busy condition at an extension when the user does not wish to be disturbed by calls. The feature can be set up and canceled from the required extension, remotely from another extension, or the operator console.
16. Switchboard Attendant Requirements
16.1 Automatic Attendant – Automatic Attendant feature shall work with the voicemail sub-system to provide for both operator overflow and an alternative answering point for routing calls. Routine calls made over a trunk can be handled by a recorded announcement, giving the caller information and calling instructions. The caller then has several options:
a. To terminate the call if the recorded information was sufficient to satisfy the inquiry
b. To dial an extension number given in the message to obtain further information
c. To dial “ 0 “ for operator assistance
d. To wait until the message is finished at which time the caller will be routed to the operator or a designated extension
16.2 Status Display – means of screen base terminal or digital display, call status information will be provided to the attendant. A LCD alphanumeric display Incoming Call Identification key/lamp pairs provides call status information to the attendant.
16.3 Directory Lookup – Operator has the ability to access the System Directory to display the system users on the console screen. Attendants shall be able to
perform “look-ups” by station number, name and related information.
16.4 Partitioning – Trunk groups as well as line groups will be assignable to attendant positions, with attendant positions being fully partitioned. When more than one attendant is assigned to a group, calls will be distributed in a uniform manner. Partitioning may be accomplished through Multi-Tenant software.
16.5 Attendant Outbound Dialing – Attendant positions shall be equipped with a pushbutton dial along with an Auto or Speed dialing capability for calling outbound from the attendant positions to locations within the PABX and on or off the network. Both direct station select and direct idle trunk select shall be provided.
16.6 Serial Calling – attendant shall be capable, upon the request of the calling party, of transferring the call to pre-selected locations. Upon completion of each
transaction, the call will be automatically routed to the next location. This will be done in sequence without further operator intervention.
16.7 Call Forward Initiation – attendant shall be able to place any station that is assigned to that position in a call forward mode from the attendants console.
16.8 Busy Override – attendant shall be able to “Override” an existing call on the system. This will be accomplished without disconnecting either party. Both parties shall receive a warning tone. Selected stations shall have the capability of being protected from this feature by class of service.
16.9 Attendant Controlled Conference – attendant shall be able to set up conference calls with up to 8 parties participating. The attendant will control the conference.
16.10 Attendant Queuing – Incoming calls to an already busy attendant position will be identified to the attendant but will continue to receive ring-back signaling. When
the first available line assigned to that loop is available the call will be connected.
16.11 Operator Call Hold and Retrieve – The operator may place any type of call on hold for further call handling. Those calls placed on hold will be queued and displayed on the console screen. Calls on hold will recall the operator after the “Hold recall Timer” has expired.
16.12 Class of Service Override – The attendant shall be able to override the class of service for any station location on a one-time per call basis. At the conclusion of the call the original class mark will apply.
16.13 Night Service – The attendant shall be able to place the PABX on Night Service which will redirect incoming calls after a predefined number of rings to an intercept night message or alternate answering point.
16.14 Operator Paging – Paging zones are available for use by the operator. These zones can be individually accessed, or can be all accessed simultaneously by the operator.
16.15 Speed Calling – The operator has access to the system speed call Directory.
17. Data Switching Features
17.1 The PABX system shall provide circuit switching of Analog (voice band) Data with capability to add Digital Data Information (E1) in the future. The system shall be capable of supporting at least 20 percent of system ports (lines and trunks) as circuit switched data connections. When the system is provisioned with 20 percent of system ports capable of supporting data connections, the system(s) shall be able to meet the grade of service requirements as defined in this Specification.
17.2 The PABX system shall be capable of providing the following capabilities and features:
a. Data Privacy – Properly class marked station lines, whether used for simultaneous or alternate voice and data, shall not be subject to intrusion by the attendant or system feature action. No user action shall be required to activate this feature. This class of service can be assigned from the system administrator only.
b. Modes of Transmission – The PABX system; switches, nodes, and terminals shall accommodate simplex, half-duplex, and full-duplex data transmission modes.
c. Computer Access – The PABX System with Telephony Applications Interface (MiTAI) shall allow Industry standard Pentium platform microcomputer access and perform industry applications programs.
18. Station Instruments
Multi Line analog instruments with conference call feature shall provide electronic features with programmable soft keys, message waiting light, speaker, adjustable ringer, pick-up and hold keys, and illumination to indicate station calls, wink hold, line busy or ringing. A display shall be furnished that provides rapid access to PBX features. These instruments shall be fully compatible with the PABX and station features as described in this document and all interconnecting networks and services.
19. System Interface Requirements
19.1. Trunks and Lines Circuits
PABX shall be equipped for a minimum of 75 DID external trunk lines and 75 DOD external trunk lines.
20. Station Line Circuits
20.1 The PABX shall be capable of providing the following station instrument interfaces:
a. Station Loop Limits – The System shall provide the specified service and meet defined quality and performance criteria on local line loops of at least 1200 ohms or more at a nominal -48 VDC excluding the stationequipment.
b. Long Loop Line ports provisioned with analog line cards and DS1 ports shall support loops of at least 1400 ohms (excluding station equipment) or more without use of repeaters.
c. Loop Start Signaling – The System shall provide loop start signaling, with battery and ground on the tip and ring conductors. The System shall detect loop closure from the station as a seizure. After seizure the System shall provide dial tone on the tip and ring as a start dial signal.
21. Trunk Circuits
The System shall be capable of interfacing and interacting with trunks using European industry standard protocols.
21.1 Standard Operation – The System shall be capable of collecting and analyzing all or a portion of digits dialed before signaling to trunk facilities.
21.2 E&M Trunk Signaling – The System shall be capable of providing 4-wire transmission E&M trunk circuits, both Type I and Type II.
21.3 Terminating Trunk Signaling – The System shall interface and be compatible with the following incoming trunk or the incoming portion of two-way trunk protocols.
21.4 Call for Service Timing – The System shall ignore any transient off-hook signals whose duration is less than 60 millisecond. Service timers will be set when the system is programmed.
21.5 Immediate Dial – The System shall be ready to receive pulsing within 60 to 270 milliseconds after receipt of a valid seizure. System dial timers will be set when the system is programmed.
21.6 Delay Dial – The System shall support a delay dial operation returning an offhook delay dial signal of at least 140 milliseconds, immediately after seizure recognition. Delay dial timers will be set when the system is programmed.
21.7 Busy Back on Incoming Trunks – Under software control the System shall be capable of returning an off-hook signal indicating the trunk is out-of-service.
21.8 Disconnect Control – Trunk-to-trunk calls shall be supervised by the System under calling party control supervision. The System shall disconnect on a software defined on-hook signal of between 40 and 700 millisecond. Disconnect timers will be set when the system is programmed.
21.9 Ground Start – The System shall provide ground inter-trunk signaling by applying a ground to ring side of the line to indicate an off-hook condition.
21.10 Originating Trunk Signaling – The System shall select, seize, signal, and supervise outgoing trunks using the following protocols:
21.10.1 Guard Timing – The System shall not seize an outgoing trunk until it has been idle for at least 750 milliseconds (programmable to 1.25 sec). Guard timers will be set when the system is programmed.
3.21.10.2 Immediate Dial – The System shall be capable of providing immediate dial operation on a per-trunk group basis, by providing an offhook seizure for at least 150 milliseconds followed by DP, MF, MFC or DTMF address signaling.
21.10.3 Wink-Start Operation – The System shall be capable of providing wink-start controlled out pulsing for trunks classes marked for this
operation.
22. One-Way DID Trunks
Preset class marked stations on the System shall receive incoming calls from the PSTN without attendant intervention.
23. Direct Inward System Access
Exchange lines will exist which return a dial tone to the incoming callers and allow callers to continue dialing an extension number without the operator assistance.
24. DOD Trunks
The System shall be capable of interfacing directly with one-way outgoing or two-way trunking using either ground or loop start signaling. Trunks shall be class marked to provide automatic identification of outward dialing, as required.
25. Digital Facilities
25.1 The System shall interface with the STC at a DS-1 or E-1 level utilizing associated signaling alarm and testing protocols.
25.2 The main PABX shall be capable of interfacing with remote peripheral units using the existing facility if any, like single-mode fiber optic backbone.
26. System Provided Tones
The System shall provide line signaling and supervision that conforms with EIA or equivalent standards. The audible signals shall be provided by the System.
Ringing
The System shall provide either industry standard 20 Hz, 2 second on 4 second off ringing to each line to line calls and 2 second on 2 second off ringing for calls originating external to the System or other as may be dictated by Saudi Telecom Company. Internal and external calls shall be indicated by a distinctive defined ringing pattern.
27. Signaling Formats
The System shall provide and accommodate the following line and trunk signaling:
a. Dial Pulse (DP)
b. Dual Tone Multi-frequency (DTMF)
28. Voicemail Sub-System
This section describes how the Voicemail sub-system shall be integrated with the PABX System. The Voicemail sub-system shall be a PC-based system. Use of standard, upgradable PC hardware is required. The selected CONTRACTOR shall provide a complete turnkey PC-based Voicemail subsystem, which includes a minimum of eight (8) hardware interface ports to the PABX. Voicemail software shall handle a mailbox capacity of 1200 or more, a minimum of 30 hours hard disk storage capacity, and 800 sets of user templates.
1. Integration
The sub-system shall be able to reproduce and understand the System signals used to report conditions, send commands to peripherals, and execute call control functions. This integration shall allow the Voicemail sub-system to send message waiting light signals to extension LEDs and route calls to proper message boxes.
2. Auto Attendant
The Voicemail sub-system shall incorporate an auto-attendant to answer incoming calls, play a short day or night message, let callers transfer to a department, enter extension or consult a company directory. The auto-attendant coordinates access to Voicemail and other System features (such as paging) in the absence of a human operator.
3. Hardware
The Voicemail sub-system shall be a stand-alone PC based system, which looks and mounts like the PABX hardware. The PC shall include all necessary components to be capable of meeting all functionality as required in this specification.
4. Features
The Voicemail sub-system should include but not be limited to the following features:
a. Full In-Band Integration
b. Multiple Language
c. Automatic Call Distribution (ACD)
d. ACD Silent Monitoring and Recording
e. Advanced Menu (Single or Multiple Key Activate Features)
f. Audiotext
g. Auto Copy (Mail Box Message Copy)
h. Auto Day/Night-1/ Night-2 Switching Mode
i. Direct Dial Inward for ACD
j. Call Screening
k. Custom prompt and recording
l. Date and Time stamping
m. Dial through during greeting
n. Digital Message On Hold (play advertising information)
o. Extension/Mailbox creation, editing and range selection
p. Future Delivery on a predetermined day of message
q. Flexible Extension/Mailbox length
r. Menu prompt recording through any touch tone telephone
s. Message retrieve, save, copy and delete
t. Message Waiting Lamps activation
u. Multiple or Single greetings
v. Multi Tenanting (Multiple PABX Connection)
w. Password protection
x. Personal Operator (Dialing *0 during the greeting can transfer a call to Attendant)
y. Programmable per port
z. Mailbox can be programmed to emulate an external Announcer and playback recorded message (greeting or company information)
aa. Relay Paging Access
bb. Remote telephone forwarding to voice mail
cc. Reports on numerous sub-system function and activities
dd. Scheduled Event, Automatic forwarding specific telephone to Voicemail at predetermined times and date.
ee. Simplified mailbox activation