A T1 line carries twenty-four 64 kbps-voice channels at 1.5 Mbps, and can be used as a public or private line. Voice is digitized by Pulse Code Modulation (PCM).
1.
Channel Type
[LCOT/GCOT/DID/TIE/OPX] The T1 card supports five different channel types to provide connection at minimum expense. One of the five channel types can be assigned to any one of the T1 card's 24 channels individually, according to usage rates and customer needs.
2.
T1 Features
The following table shows the features available for each channel type:
A single line telephone (SLT) which is installed off site can perform as if it were installed locally. The SLT makes and receives calls through the PBX. An extension number can be given to the OPX, and extension data such as Class of Service (COS) is also applied.
[Example]
(5) ANI
Automatic Number Identification (ANI)
Receives the caller's number from a T1 line.
When the ANI number is received, it can be treated the same as a Caller ID number. (→ 1.3.2 Caller ID)
Conditions
•
If a T1 line is used as a public line, the channel type depends on the contract with the telephone company.
A ring tone is sent through an external pager (loudspeaker) when an incoming call is received. Any extension user can answer the call.
Conditions
•
Hardware Requirement: A user-supplied external pager
•
Floating Extension Number A floating extension number can be assigned to an external pager (default: 600). An external pager is accessed by dialing its floating extension number.
•
Pager Volume It is possible to change the volume level of an external pager through system programming.
Tenant service is a cost-effective method of providing PBX services to different offices or companies located in the same building, while using only one PBX.
1.
Tenant Configuration
1.1.
Tenant Members
Extensions are assigned to a tenant indirectly; they are assigned to extension user groups, and these extension user groups are assigned to tenants. An extension can belong to only one extension user group and an extension user group can belong to only one tenant, therefore an extension can belong to only one tenant. (→ 1.7.1 GROUP FEATURES)
1.2.
Time Service
Time modes are used by many PBX features to determine how they will function during different times of day (→ 1.17.5 Time Service). The start and end times of each time mode (day/lunch/break/night) for each day of the week are programmed in a Time Table. Each Time Table has a number which corresponds to the tenant number of the tenant it serves. (Tenant 1 uses Time Table 1, etc.)
[Example of Tenant Configuration]
2.
System Management
Each of the following system management items can be assigned to each tenant.
ARS Mode: Determines under which circumstances Automatic Route Selection (ARS) operates for calls made by the tenant's extensions — either when a call is made using the Idle Line Access method, or when any CO Line Access method is used. (→ 1.3.15 CO Line Access). The ARS mode for each tenant can also be programmed to be the same ARS mode assigned to the entire PBX, or turned off. (→ 1.1.3 ARS (Automatic Route Selection)) → 2.12.6 [6-6] Tenant—ARS Mode
c)
Audio Source for Music on Hold: Determines the audio source for the Music on Hold heard by the tenant's callers. Either a tone or a specific background music (BGM) number can be used. The audio source for each tenant can also be programmed to use the same audio source used for Music on Hold assigned to the entire PBX. (→ 1.11.4 Music on Hold) → 2.12.6 [6-6] Tenant—Music On Hold
Through Class of Service (COS) programming, it is possible to:
1.
Prevent extensions of one tenant from calling extensions of another tenant. (Tenant-to-Tenant Call Block)
2.
Limit the trunk groups which can be used by the extensions of each tenant. (External Call Block)
3.1.
Tenant-to-Tenant Call Block
Using Internal Call Block, certain features, such as making intercom calls, can be restricted based on the COS assigned to extensions. (→ 1.9.14 Internal Call Block) Well-planned COS programming can prevent extensions of one tenant from:
–
Calling an extension or doorphone which belongs to another tenant
–
Picking up calls ringing at extensions belonging to another tenant (→ 1.3.7 Call Pickup)
–
Retrieving calls being held by another tenant (→ 1.3.3 Call Hold)
[Programming Example: Internal Call Block]
In this example:
Internal Call Block is employed to block calls between certain tenants.
Each extension in a tenant is assigned a COS that is not assigned to extensions which belong to another tenant.
a)
Extensions in Tenant 1 are either COS 1 or 2. They can make calls to extensions in Tenants 1, 2, and 3.
b)
Extensions in Tenant 2 are either COS 3 or 4. They can make calls to extensions in Tenants 1 and 2, but not 3.
c)
Extensions in Tenant 3 are either COS 5 or 6. They can make calls to other extensions in Tenant 3 only.
3.2.
External Call Block
If multiple tenants are using the PBX, the External Call Block feature should be programmed to control which COS numbers are allowed to access which trunk groups. By preventing certain COS numbers from accessing certain trunk groups, each tenant can be given its own trunk groups which no other tenant can access.
[Programming Example: External Call Block]
In this example:
External Call Block is employed to prevent tenants from accessing all trunk groups except the ones designated to them. Each extension in a tenant is assigned a COS that is not assigned to extensions which belong to another tenant.
a)
Extensions in Tenant 1 are either COS 1 or 2. They can access trunk groups 1 and 2.
b)
Extensions in Tenant 2 are either COS 3 or 4. They can access trunk groups 3 and 4.
c)
Extensions in Tenant 3 are either COS 5 or 6. They can access trunk groups 5 and 6.
Conditions
•
The following features used by incoming call distribution (ICD) group are determined by the tenant number assigned to them (→ 1.9.1 ICD GROUP FEATURES):
–
The Music on Hold heard by a caller while waiting in a queue.
–
The Time Table used by the ICD group to determine the current time mode. An overflow destination and Queuing Time Table can be assigned for each time mode.
An extension can be preset to ring at a certain time, to act as a wake-up call or reminder. This feature can be programmed to activate only once, or daily. If the user answers the alarm call, a prerecorded voice message will be heard. If a message is not assigned, a special dial tone (dial tone 3) will be heard. Timed reminders can be set in one of two ways:
•
By the extension user, from his or her own extension (Timed Reminder).
•
Remotely, by the hotel operator (Remote Wake-up Call).
Conditions
•
Be sure that the PBX clock is set to the correct time.
•
Only one timed reminder can be set for an extension at a time. Setting a new reminder clears the previous reminder. If both the extension user and the hotel operator set a timed reminder for the same extension, the timed reminder that was set most recently is effective.
•
Programmable Time The Alarm Ringing time, the number of alarm repeat times, and Interval time are programmable through system programming.
•
To use the voice message feature: An MSG card is required and a message must be recorded. An extension assigned as a manager can record messages. (→ 1.12.2 OGM (Outgoing Message)) A different message can be assigned for each time mode (→ 1.17.5 Time Service).
Time modes are used by many PBX features to determine how they will function during different times of day. For example, incoming calls can be directed to sales staff during the day and to a Voice Processing System (VPS) at night, extension users can be prohibited from making long distance calls during lunch time, etc.
There are four time modes—day, lunch, break, and night. The start and end times of each time mode are programmed for each day of the week in a Time Table. Each Time Table has a number which corresponds to the tenant it serves, i.e., Tenant 1 uses Time Table 1, etc.
1.
Time Service Switching Mode
The current time mode can switch automatically to another time mode at the preprogrammed time assigned in the Time Table. It is possible, however, to switch time modes manually.
Whether time modes are normally switched manually or automatically is determined through system programming. Each tenant is assigned a switching mode.
Time Mode Switching
Description
Condition
Automatic
The current time mode will switch automatically to another time mode at the time programmed in the tenant's Time Table, and can be switched manually by pressing the Time Service button or by dialing the Time Service Switch feature number.
The current time mode (day/lunch/break/night) and the switching mode (automatic/manual) can be switched manually by an extension assigned as a manager, or by an extension whose Class of Service (COS) is authorized.
Manual
The current time mode will switch only when the Time Service button is pressed or when the Time Service Switch feature number is dialed.
2.
Time Table
Each tenant has a Time Table that is used when the tenant is in Automatic Time Service Switching mode. Each Time Table has four basic modes—day, lunch, break, and night—and also provides for multiple "breaks", such as morning breaks and afternoon breaks, and multiple "days", such as the morning shift and the afternoon shift following lunch.
A tenant's Time Table is programmed to control when each time mode starts (and therefore, ends) and can be programmed separately for each day of the week.
Each Time Table has a number which corresponds to the tenant number of the tenant it serves. (Tenant 1 uses Time Table 1, etc.)
[Programming Example: Time Table]
[Visualization of Time Schedule for Tenant 1]
Note that in this example, the day mode (Day 2) resumes automatically when the break mode (Break 1) ends.
[Visualization of Time Schedule for Other Tenants]
Note that time modes can be arranged as they are needed (for example, night mode can occur in the morning and afternoon, if necessary) and not all time modes need to be used in a tenant's time schedule.
Also note that Tenant 4's Break 1 is followed by the night mode because no end time is programmed for the break.
Destination of calls that are overflowed while waiting in a queue for an available agent of an incoming call distribution (ICD) group (→ 1.9.5 ICD Group Features—Overflow)
The DID Table can be programmed to direct calls to a different destination for each time mode based on the number dialed by the caller. Calls can, for example, be directed to an ICD group during the day mode, or to the Voice Mail (VM) service of a VPS during the lunch and night modes.
Explanation:
A CO line call with the DID number "123-4567" is received at 20:00.
1)
The call will be handled by Time Table 1.
2)
The current time mode is "night" (shown in "Programming Example: Time Table", above).
3)
The call is directed to extension 150, which is a floating extension number used by the VPS (programming not shown here).
[Programming Example: DIL Table]
The DIL Table can be programmed to direct calls to a different destination for each time mode based on the CO line receiving the call. Calls can, for example, be directed to an ICD group during the day mode, or to the Voice Mail (VM) service of a VPS during the lunch and night modes.
Explanation:
A call is received at 20:00 on CO line 01.
1.
The call will be handled by Time Table 1.
2.
The current time mode is "night" (shown in "Programming Example: Time Table", above).
3.
The call is directed to extension 150, which is a floating extension number used by the VPS (programming not shown here).
4.
Holiday Mode
The PBX can also accommodate 24 different holidays. The start and end date of each holiday can be programmed, and all holidays are assigned a single time mode. For example, if the "night" mode is assigned as the time mode for holidays, and a holiday begins December 31st and ends January 1st, all PBX features will use their "night" settings from 0:00 A.M. on December 31st until 0:00 A.M. on January 1st.
5.
Time Service Button
A flexible button can be customized as one of the following Time Service buttons:
a)
Day/Night button
b)
Day/Night/Lunch button
c)
Day/Night/Break button
d)
Day/Night/Lunch/Break button
These buttons can be used to switch the current time mode: pressing the Day/Night button will toggle between the day and night modes, for example.
Each Time Service button will display the current time mode using a different light pattern or color, as shown below.
Light Pattern
Current Time Mode
Off
Day
Red on
Night
Green on
Lunch
Slow green flashing
Break
Slow red flashing
Holiday
Note
Pressing a Time Service button will change the current time mode only if the COS assigned to the extension is authorized to do so or if the extension is assigned as a manager. All other extension users can press this button on their proprietary telephones (PTs) to display the current time mode.
Conditions
•
The start times of the following time modes can be specified through PC programming as well as PT programming.
–
Day 1 and 2
–
Lunch
–
Night
The start and end times of the following break modes can be specified through PC programming only.
–
Break 1
–
Break 2
–
Break 3
Note that if an end time is programmed for a break, the day mode will start or resume at this time, as shown previously in "Visualization of Time Schedule for Tenant 1" example. If no end time is programmed, the break will continue until the start of the next time mode, as shown in Time Table 4 in "Visualization of Time Schedule for Other Tenants".
•
Time Service Switching Mode (Automatic/Manual) Button Any flexible button can be customized as the Time Service Switching Mode (Automatic/Manual) button.
Each COS is assigned a TRS level for each time mode; level 1 grants the highest level of authorization, allowing all CO line calls to be made, and level 7 grants the lowest level of authorization, prohibiting all CO line calls from being made. TRS levels 2 through 6 are used to restrict calls by combining preprogrammed Denied and Exception Code Tables, explained below.
Each COS can also have a separate TRS level applicable to calls made using System Speed Dialing.
A TRS check is applied each time a dialed number is sent to a CO line after an extension user goes off-hook and seizes a line.
[Flowchart]
Denied Code Tables
Denied Code Tables are preprogrammed lists containing the first few digits (leading number) of telephone numbers which may not be called. All outgoing CO line calls made by TRS level 2 through 6 users are compared to at least one Denied Code Table, and when the leading number of a dialed telephone number (not including the CO Line Access number) matches an entry found in the applicable table, the call is denied.
There are five Denied Code Tables. Each table applies to a corresponding TRS level as well as the level(s) preceding it, as explained below.
Exception Code Tables
Exception Code Tables are preprogrammed lists of leading digits or complete telephone numbers which are checked against every dialed number prohibited by a Denied Code Table. When a user dials a number prohibited by a Denied Code Table, it is compared to at least one Exception Code Table. If the dialed number matches an entry found in the applicable Exception Code Table, the call is permitted.
There are five Exception Code Tables. Each table applies to a corresponding TRS level as well as the level(s) preceding it, as explained below.
This allows extension users to use System Speed Dialing to make CO line calls which are normally prohibited by the TRS level of their assigned COS. If, for example, a user's TRS level is 7, that user normally cannot make any CO line calls. However, if the same user's TRS level for System Speed Dialing is level 1, the user can make a CO line call to any number stored in System Speed Dialing.
TRS Level
The TRS level is determined by the telephone codes set in the Denied Code Tables and Exception Code Tables. As shown in the table below, the Denied Code Tables for the higher levels are applied to all levels below it, and the Exception Code Tables for the lower levels are applied to all levels above it.
[Usage Example] Using this method, certain outgoing CO line calls (e.g., international/cellular phone/long distance) can be restricted as in the example below:
Restricted
Allowed
Level 1
No restriction
Level 2 (Boss)
•
International Calls
•
Countries where Clients are Located
•
Cellular Phone Calls
•
Long Distance Calls
•
Local Calls
Level 3 (Secretary)
•
International Calls
•
Cellular Phone Calls
•
Boss's Cellular Phone
•
Long Distance Calls
•
Local Calls
Level 4 (Operator)
•
International Calls
•
Cellular Phone Calls
•
Long Distance Calls
•
Local Calls
:
:
:
In this example, a level 1 user can make any CO line calls. A level 2 user can make international calls to the countries where clients are located, and can also make cellular phone/long distance/local calls. A level 3 user cannot make international/cellular phone calls apart from to the boss's cellular phone, but can make long distance/local calls. A level 4 user cannot make any international/cellular phone/long distance calls, but can make local calls.
To set TRS as in the example above, it is necessary to program the Denied Code and Exception Code Tables as follows:
TRS Settings for Each Level Through system programming, it is possible to select a different method of TRS. With this method, each level has its own separate set of denied codes and exception codes, which are only applied to that level. → 2.13.5 [7-5] Miscellaneous—TRS Table Mode for Level N (N=2_6)
[Usage Example] Using this method, it is possible to restrict certain CO line calls (e.g., international/cellular phone/long distance) on a department basis, as follows:
Restricted
Allowed
Level 1
No restriction
Level 2 (Engineering)
•
International Calls
•
Country where Factory is Located
•
Cellular Phone Calls
•
Long Distance Calls
•
Local Calls
Level 3 (Overseas Sales)
•
Cellular Phone Calls
•
Company Cellular Phone
•
International Calls
•
Long Distance Calls
•
Local Calls
Level 4 (Accounting)
•
International Calls
•
Long Distance Calls
•
Cities where Clients are Located
•
Cellular Phone Calls
•
Local Calls
:
:
:
In this example, a level 1 user can make any CO line calls. A level 2 user can only make international calls to the country where the factory is located, and can also make cellular phone/long distance/local calls. A level 3 user can only make cellular phone calls to the company cellular phone, and can also make any international/long distance/local calls. A level 4 user cannot make any international calls or most long distance calls, but can make long distance calls to cities where clients are located, cellular phone calls and local calls.
To set TRS as in the example above, it is necessary to program the Denied Code and Exception Code Tables as follows:
Denied Code Tables
Exception Code Tables
Level 1
Not Programmable
Not Programmable
Level 2
011
Leading number to deny international calls
011xx
Leading number for country to be allowed
Level 3
1123755
Leading number to deny cellular phone calls
1123755xxxx
Number for cellular phones to be allowed
Level 4
011
Leading number to deny international and long distance calls
1315
Long distance numbers for states/cities to be allowed, and leading number of cellular phones
1530
1
1123755
:
:
:
Conditions
WARNING The software contained in the TRS feature to allow user access to the network must be upgraded to recognize newly established network area codes and exchange codes as they are placed into service.
Failure to upgrade the on-premise PBXs or peripheral equipment to recognize the new codes as they are established will restrict the customer and the users of the PBX from gaining access to the network and to these codes.
KEEP THE SOFTWARE UP TO DATE WITH THE LATEST DATA.
•
TRS checks are performed for all calls made by:
–
Any CO line access (Idle Line Access, Trunk Group Access, S-CO Line Access)
–
Automatic Route Selection (ARS)
•
The PBX can also be programmed to perform a TRS check for numbers that contain non-digits ( or #). By default, the PBX ignores ("No Check") any non-digits that are dialed, which is useful in preventing unauthorized calls which could possibly be made using certain telephone company exchanges. → 2.13.5 [7-5] Miscellaneous—TRS Check for Dial "* #"
TRS ignores the code and checks the remaining digits.
Number dialed is not a CO line call, so TRS does not check the number.
TRS checks the entire number.
Special Carrier Access Code
TRS ignores the code and checks the remaining digits.
TRS checks the entire number.
TRS checks the entire number.
•
ARS If ARS is applied to a dialed number, TRS will check the user-dialed number, not the modified number produced by ARS. You do not need to program ARS-modified numbers in any of the TRS Tables. Additionally, when using ARS, TRS will ignore the Host PBX Access code or Special Carrier Access code.
•
Dialing Digit Restriction during Conversation TRS can also limit the number of digits which may be dialed by an extension user while the user is engaged on a received CO line call. If the number of dialed digits exceeds the limit, the line will be disconnected. → 2.13.5 [7-5] Miscellaneous—Dial Digits Limitation After Answering—Dial Digits
If no disconnection is chosen, the TRS check will also be performed after the Inter-digit time expires.
–
If disconnection is chosen, the line will be disconnected when the CO line Inter-digit time expires. This also prevents EFA from being used.
This setting applies to all CO lines.
•
When one of the following features is used, the TRS level of the extension can be temporarily changed. If two or more of these features are used simultaneously (Dial Tone Transfer is used while the extension is locked, for example), the TRS level of the feature with the highest priority is applied for the duration of the call. The numbers below (1 through 4) indicate the priority of each feature, with 1 having the highest priority, and 4 having the lowest.
TAFAS Answer
or #). By default, the PBX ignores ("No Check") any non-digits that are dialed, which is useful in preventing unauthorized calls which could possibly be made using certain telephone company exchanges.