Siemens Saturn Iie Epabx General Description Manual

							SATURN IIE EPABX 
General Description A30808-X5130-AllO-l-8918 
Issue 1, May 
1986 
Figure 6.15 Two-Wire E&M Trunk (TMBA-2) Printed Circuit Board  
						

							SATURN IIE EPABX 
General Description A30808-X5130-AllO-l-B918 
issue 1, May 1986 
Figure 6.16 Four-Wire E&M Trunk (TMBA-4) Printed Circuit Board 
6-22  
						

							SATURN IIE EPABX 
General Description A30808-X5130-AllO-143918 
Issue 1, May 
1986 
Figure 6.17 Central Office Trunk (TMBM) Printed Circuit Board  
						

							SATURN IIE EPABX 
General Description A30808-X5130-AllO-I-8918 
Issue 1, May 1986 
Figure 6.18 Direct Inward Dialing Trunk (TMIE) Printed Circuit Board  
						

							SATURN IIE EPABX A30808-X5330-AllO-l-8918 
General Description Issue 1, May 1986 
SECTION 7.00 SATURN IIE ANCILLARY EQUIPMENT 
7.01 Service Terminal. A keyboard/printer data terminal 
equipped with an RS-232-C interface may be used to input 
maintenance and administrative commands to the system. 
The terminal is primarily used to enter data into the system 
for processing CMU procedures. The CMU procedures are 
used to make changes to the customer memory portion of 
the system memory, such as adding a station or trunk, chang- 
ing a station’s extension number or class of service, or ad- 
ding features to the system. The system memory contains all 
of the data relating to the programmable features and options 
the customer can select, arrange, and rearrange. The SATURN IIE System can also be provided with the Re- 
mote Customer Memory Update feature, which permits the up- 
dating process to be initiated from a remote (off-premises) 
location. This feature utilizes a modem that is built into the Re- 
mote Access Unit/Ports (RAUP). Changes to the customer 
memory can be completed through either local or long-distance 
trunks, tie trunks, or any SATURN IIE station. The requirements 
for the remote data terminal are specified in the Siemens prac- 
tice, SATURN IIE EPABX Customer Memory Update Proce- 
d.ures. Information pertaining to the use of such a data terminal 
for CMU changes is also included in that practice. 
The administrative procedures can be performed during nor- 
mal system operation with no interference to normal call 
processing. The CMU procedures are easy to use and pro- 
vide plain English prompting for the benefit of the user. The 
new data that is entered is then recorded on the floppy disk 
(by means of a “save” command) as a permanent record for 
system backup purposes. An example of an administrative 
CMU procedure is shown in Figure 7.00. Besides the modem port, the system provides three ports for 
data terminals (one on the CIOP, two on the RAUP) In addi- 
tion to the administrative functions described above, the sys- 
tern also compiles data pertaining to Station Message Detail 
Recording (SMDR) and traffic through the system. The SMDR 
and/or traffic data may be outputted via another port(s) to 
another printer/terminal or to an independent reporting sys- 
tern for post-processing. 
USER INPUT: 
)ADD COSASSN 
I 
User inputs the command (ADD) and keyword for Class-of-Service Assignment (COSASSN) 
SYSTEM PROMPT: 
CLASS OF SERVICE NUMBER (O-31) = 
System prompts the user for the class of service (COS) number to be assigned. 
USER INPUT 
CLASS OF SERVICE NUMBER (O-31) = 5 
User inputs “5” to indicate COS 5 is being assigned. 
SYSTEM PROMPT 
CLASSMARK ASSIGNMENTS = 
System prompts the user for the feature classmarks to be assigned to COS 5. 
USER INPUT: 
CLASSMARK ASSIGNMENTS = HKFLSH FWDALL FWDTONTWK PARK 
User inputs the classmarks to indicate the features to be assigned to COS 5. ‘(In this example, the following features 
are assigned: Hookflash, HKFLSH; Call Forwarding 
- All Calls, FWDALL; Call Forwarding to Public Network, 
NVDTONTWK; and Call Park, PARK. Hookflash is required to be assigned for certain features, including Call Park.) 
SYSTEM PROMPT: 
ALLOWED TRUNK GROUPS (O-31) = 
I 
System prompts the user for the trunk group numbers to which COS 5 is to be allowed access. 
USER INPUT: 
ALLOWED TRUNK GROUPS (O-31) = 3 
User inputs the trunk group number to which COS 5 is to be allowed. (In this example, only trunk group 3.) 
Figure 7.00 Example pf Administrative CMU Procedure  
						

							SATURN IIE EPABX 
General Description A30808-X5130-AllO-l-8918 
issue 1, May 1986 
SYSTEM PROMPT 
TOLL CODE REST LIST NUMS (O-19) = 
System prompts the user for the toll code restriction list(s) to apply to COS 5. 
USER INPUT: 1 
TOLL CODE REST LIST NUMS (O-19) = 7 
User inputs the toll code restriction list(s) to which COS 5 is to be allowed access. (In this example, only toll 
code 
restriction list 7.) 
SYSTEM PROMPT 
RESTRICTED ACD GROUP NUMS (O-63) = 
System prompts the user for the ACD group number(s) from which COS 5 is restricted from accessing. 
USER INPUT: 
RESTRICTED ACD GROUP NUMS (O-63) = 
User does not wish to assign a restricted ACD group at this time, therefore no entry is made. (“Enter” 
key is depressed 
to obtain next prompt or response.) 
SYSTEM PROMPT: 
RESTRICTED STATION COS’S (O-31) = 
System prompts the user for the station class of service number(s) from which COS 5 is restricted from accessing. 
USER INPUT: 
RESTRICTED STATION COS’S (O-31) = 
User does not wish to assign a restricted station COS at this time, therefore no entry is made. (“Enter” key is depressed 
to obtain next prompt or response.) 
SYSTEM RESPONSE: 
ADD STNCOS 83-01-03 11:41:47 
CLASS OF SERVICE ADDED 
System acknowledges addition of the new class of service, followed by the calendar date (January 3, 1983) and the 
current time (11:41:47). 
USER INPUT 
) SAVE CUSTDATA 
User inputs the command (SAVE) and the keyword for Customer Data (CUSTDATA) to save the changed data to the 
floppy disk. (In the event of a system restart, the system reloads automatically from the floppy disk. Therefore, any 
changed data that has not been “saved” must be reentered.) 
Figure 7.00 Example of Administrative CMU Procedure (Continued)  
						

							SATURN IIE EPABX A30808-X5130-AllO-l-8918 
General Description Issue 1, May 1986 
7.02 Attendant Console. The attendant console, shown in 
Figure 7.01, is a desk-top unit with which the attendant 
processes calls, using pushbutton keys and an alphanumer- 
ic display. It is 46.99 cm (18.5 in.) wide, 13.08 cm (5.15 in.) high, 
and 26.47 cm (10.42 in.) deep. A maximum of twelve atten- 
dant consoles can be provided in the SATURN IIE System. 
A telephone handset is furnished with the console. An op- 
tional headset may be substituted for the handset. Both tone 
and visual indicators alert the attendant to incoming calls. The 
level of the tone signal may be controlled by a volume con- 
trol located at the front edge of the console. 
The attendant console provides switched-loop operation, with 
single-loop appearance to simplify call handling. The advan- 
tages of stored-program processing allow the attendant to 
have complete information about calls directed to the con- 
sole. The attendant has complete control over calls directed 
to the console and a number of other features by means of 
the preset and programmable console keys and the display. 
The attendant console is microprocessor-controlled, and con- 
tains a codec/filter for voice analog/digital conversion. The 
console receives its required power from the main system, 
which can be up to a distance of 610 cable meters (2,000 ca- Connections to the console are made through industry- 
standard, modular, connector-ended cables that provide voice, 
control signals, and power. A standard two-pair cable is used 
to make the connection from the SATURN IIE System to a 
modular jack located near the console. 
The upper portion of the console contains the display sec- 
tion, which gives the attendant the necessary information to 
correctly identify the call being serviced. The display section 
includes a 40-character, alphanumeric vacuum-fluorescent 
display. The following types of indications are provided by the 
display: 
a. Time of day 
b. Station numbers of calling and called parties 
c. Class of service of calling station 
d. Busy/idle/out-of-service status 
e. Intercept information 
f. Call queuing lengths (This information is presented to 
the attendant automatically between the servicing of 
ble feet). calls.) 
Figure 7.01 SATURN Attendant Console  
						

							SATURN IIE EPABX A30808-X5130-AllO-l-8918 
General Description Issue 1, May 1986 
In addition to the call data information listed above, the dis- 
play may also be used for both call data display and for dis- 
playing system status to the attendant (such as the system’s 
failure history) plus major and minor alarm indicators. 
The lower portion of the console contains a keyboard assem- 
bly that allows the attendant to process the various types of 
calls, initiate station and trunk calls, and access special fea- 
tures (such as conferencing, paging, and night service). All 
keys are nonlocking and have single built-in Light-Emitting 
Diode (LED) indicators that light steadily or flash to indicate 
a particular operating condition. A full explanation of the oper- 
ation of the attendant console is provided in the Siemens prac- 
tice, SATURN EPABX Attendant Console General Description 
and Operating Instructions. 
Eighteen keys on the attendant console are fully assignable 
by the customer to meet customized needs. The remaining 
sixteen keys are preset for the functions required in all sys- 
tems. These keys are labeled and assigned as follows: 
ANS Answer (System selects type of call: 
operator, incoming, or recall) 
ATT RLS Attendant release from all parties 
AUD ON/OFF Audible signal control - on/off 
BOTH Both source and destination party select 
DEST Destination party select TIME 
Time display 
INC Incoming call queue answer 
LOOPn Loop selection (Loop 1 through Loop 4) 
NIGHT Night operation 
OPR Operator call queue answer 
RCL Recall queue answer 
RLS Release of individual party 
SRC Source party select 
Calls requiring attendant assistance are directed automati- 
cally to one of three call identification keys. Each key has a 
corresponding holding queue that allows the attendant to 
select one of the three types of calls: incoming trunk calls; 
operator (“dial 0”) calls; or recalls (calls that have already been 
serviced by the attendant and for some reason have returned 
to the console for additional attendant assistance). By me- 
ans of an LED indicator, the call identification keys indicate 
to the attendant the type of call waiting to be serviced 
and thereby permit the attendant to process each call selectively. 
In addition to the above three keys, an “answer” key is provid- 
ed. This key can be used to answer waiting calls on a “first- 
in, first-out” basis. When the attendant uses the answer key, 
the longest waiting call (regardless of whether the call is in 
the incoming, operator, or recall queue) is presented to the 
console for servicing.  
						

							SATURN IIE EPABX A30808-X5130-AllO-l-B918 
General Description Issue 1, May 1986 
SECTION 8.00 STATION MESSAGE DETAIL RECORDING 
8.01 General. Station Message Detail Recording (SMDR) pro- 
vides detailed records of incoming and outgoing trunk calls. 
The SATURN System records all detail information for outgo- 
ing CO, WATS, FX and Tie trunk calls and incoming CO, WATS, 
FX and Tie trunk calls. Intra-switch, station-to-station, station- 
to-attendant, and attendant-to-station calls are not recorded. 
The SMDR program is resident in the system and can be ac- 
tivated/deactivated by the attendant on a per-trunk-group ba- 
sis. When activated, the SMDR program remains on-line and 
runs continuously until it is deactivated. While running, it pro- 
vides chronological reports of calls via one of the output port(s) 
of the RAUP or the TTY port on the CIOP 
The SMDR output device is assignable from the service ter- 
minal and this information is saved such that, if the system 
is reloaded, SMDR resumes operation automatically to its as- 
signed output port. 
The recording of calls is customer selectable on a 
per-incomingtrunk-group basis and on a per-outgoing-LCR- 
route-element basis, or on a per-outgoing-trunk-group basis 
if direct trunk group access is used. 
When a call detail recording buffer is not available and an 
internal or outgoing call is attempted, the call will be either 
blocked or allowed to proceed without recording, based on 
a system option flag (defined via a CMU procedure). Incom- 
ing calls are never blocked. 
8.02 Call Record Items. The call data items that are includ- 
ed in the SMDR report are described in below. An example 
of an SMDR printout is provided in Figure 8.00. 
a. Record Type. This single-character field precedes the 
Source Identity field and does not have a heading. The 
character indicates the record type as follows: “T” for 
call trace, and blank for voice call. 
b. Source Identity. This field identifies the originating (i.e., 
calling) party of the call on record. It includes the sub- 
scriber extension number for an outgoing call or the 
trunk group and trunk group member number for an 
incoming trunk call. 
The source identity is left blank for calls originated by, 
and not extended from, an attendant. 
c. Destination Identity. This data identifies the terminat- 
ing (i.e., answering) party of the call on record. It is the 
trunk group and trunk group member number of the 
trunk used for the outgoing call or the subscriber ex- 
tension number in the case of an incoming trunk call. 
The destination identity is left blank for incoming calls 
terminated at, but not extended (or transferred) from, 
an attendant, Special Night Answer Position (SNAP), 
Zoned Universal Night Answer (ZUNA), Assigned Night 
Answer (ANA), or Special Overflow Answering Posi- 
tion (SOAP). If the incoming call is extended (or trans- 
ferred) by the attendant, SNAP, ZUNA, ANA, or SOAP, 
the destination identity identifies the transferred-to- 
subscriber extension number or, trunk group and trunk 
group member number (i.e., trunk-to-trunk connection). d. 
e. 
f. 
h. Least Cost Route Selection Route Number. This data 
identifies the route member used to route the call. This 
field is blank for internal and incoming calls and out- 
going calls that do not utilize LCR (i.e., Direct Access 
trunks). 
Access Code. This data identifies the routing access 
code dialed by the user after going off-hook (and 
receiving internal dial tone). 
When speed calling is used, this field contains the ef- 
fective routing access code, rather than the speed call- 
ing access code. 
Dialed Digits or Called Number. These are the digits 
dialed by the user after dialing any routing access 
code. The number of digits may vary up to a maximum 
of 16. They may include, for example, in chronological 
order, either of the following: 
l International Gateway Code, plus country code. 
plus remaining digits for International Direct Dis- 
tance Dialing. 
l Prefix 0 or 1, plus area code (3 digits), plus Office 
Code (3 digits) plus Station Number (4 digits), i.e., 
up to 11 digits for domestic Direct Distance Dial- 
ing. Note that either prefix and/or area code may 
not be required for many local area calls. 
When speed calling is used, this field contains the ef- 
fective destination address rather than the speed call- 
ing access code and member number dialed by the 
user. 
When Least Cost Routing (LCR) is used, this field con- 
tains the effective address dialed by the user rather 
than those outpulsed as a result of the LCR outdial- 
ing rule. 
Authorization Code Index. (See Account Code/Authori- 
zation Code for the definition of “authorization code”). 
When an authorization code is entered and it is not 
“displayable” (i.e., is secret), a two-character index to 
the authorization code is listed in this field. A person 
with the proper authorization can use this index to ob- 
tain the full authorization code, and unauthorized per- 
sons are restricted from obtaining it. 
For some applications, such as for resale of services. 
a large number of authorization codes may be required. 
In such cases, if the index exceeds 99, the ” ** ” is 
printed in this two-character field. 
Starting Time of Call. This field indicates the time of 
day, in hours, minutes and seconds at which record- 
ing commenced. For incoming calls, this is the time 
at which the call is answered. For outgoing calls over 
trunks that return answer supervision, this is the time 
at which answer supervision is received. For outgoing 
calls over trunks not returning answer supervision, this 
is the end of outpulsing time incremented by a cus- 
tomer adjustable filtering time. (If the holding time does 
not exceed the filtering time, the call is not recorded.)  
						

							SATURN IIE EPABX 
General Description 
. 
A30808-X5130-AllO-l-8918 
Issue 1, May 1986 
i. Call Duration. Call duration is the elapsed time from 
the starting time of the call until the call is released. 
The duration is recorded in hours, minutes and se- 
conds with the leading zeros and colon suppressed 
for hours. 
If the system time of day is adjusted while recording 
is in progress, it will not affect the validity of the reported 
call duration. 
j. Special Identity. Whenever an attendant, SNAP, ZUNA, 
ANA, or SOAP is involved in answering an incoming 
trunk call, or whenever the attendant is involved in plac- 
ing an outgoing trunk call, or whenever LCR routes a 
call over an expensive facility or a specialized com- 
mon carrier, or whenever a call is forwarded to the pub- 
lic network, a special identity character is recorded. 
The following special identity characters are defined 
for this field: 
1-12 - Attendant Console 1-12 
S - SNAP 
Z L ZUNA 
A - ANA 
0 - SOAP 
E - LCR Expensive Facility 
F - Call Forwarding to Public Network 
6, C, D - LCR Specialized Common Carrier. Iden- 
tity of SCCs 0, 1, and 2, respectively. 
k. Account Code/Authorization Code. This field usually 
provides the account code data associated with the call 
record. However, if an authorization code is entered, 
and it is defined as “displayable” (i.e., the code is not 
secret), then this code is printed instead of the account 
code. 
An authorization code is a special security code (up 
to 6 digits) to allow an authorized subscriber to up- 
grade, for that call only, the class of service giving the 
user a special feature or otherwise unauthorized fa- 
cility. When an authorization code is required, it is 
usually entered after the access code and prior to di- 
aling the called number digits. Use of authorization 
codes include calls made from a restricted telephone 
using the Mobile Authorization Code feature and in- 
coming calls on Direct Inward System Access trunks. 
The account code data is either the standard (i.e., 
default) account code assigned for the station or the 
special account code entered by the station user or 
the attendant, if applicable, for the outgoing call; the 
standard account code assigned for the station is used 
in the case of an incoming calf. 
When a station accesses an LCR route element or a 
direct access trunk group not marked for special ac- 
count codes, the standard account code assigned to 
the station is recorded. If no account code is assigned, 
the field is left blank. 
Authorization codes will be prefixed by “#‘I to distin- 
guish them from account codes. 
I. Pooled Modem Group. Refer to Siemens practice OC 
II General Description and Feature Supplement. The following special considerations are applicable to 
the call data items: 
Station Call Transfer. A separate call record is 
generated each time a call is transferred by a sta- 
tion, except for incoming trunk calls transferred by 
a SNAP, ANA, ZUNA, or SOAP station, in which 
case the same call record is continued and a spe- 
cial identity character is recorded. 
Starting Time of DISA Call. On an incoming DISA 
call, an SMDR record shows the start time as the 
answer time of the destination, and not as the an- 
swer time of the DISA trunk. 
Attendant Controlled Conference. The source or 
destination identity for a party connected to an 
attendant-controlled conference is ‘ACC X” with 
“X” representing the conference circuit (l-8). “ACC 
X” appears as the source identity for parties called 
by an attendant and added to the conference. “ACC 
X” appears as the destination identity for parties 
who call into an attendant and are added to the 
conference. 
Meet-Me Conference. The source or destination 
identity for a party connected to a meet-me con- 
ference is “MMC X” with “X” representing the con- 
ference circuit (l-8). “MMC X” appears as the 
source identity for parties called by an attendant 
and added to the conference. “MMC X” appears 
as the destination identity for parties who dialed 
directly into the conference or call into an atten- 
dant and are added to the conference. Any account 
code applied to a meet-me conference must be en- 
tered by an attendant. 
Alternate Trunk Groups. If a trunk is accessed via 
direct trunk group access, the SMDR option to 
record or not record the call is based on the as- 
signment of the primary trunk group, even when 
an alternate route is selected. When LCR is used, 
the SMDR option is based on the LCR route ele- 
ment used. 
Station Hunting. The account code and destina- 
tion identity is that of the final (i.e., answering) 
station. 
Call Forwarding (internal). The account code is that 
of the forwarded (i.e., dialed) station and the desti- 
nation identity is that of the forwarded-to (i.e., an- 
swering) station. 
Call Forwarding to Public Network. When an in- 
coming trunk calls a station which is forwarded to 
the public network, two SMDR records are gener- 
ated: one showing the incoming trunk as the 
source ID and the forwarded station as the desti- 
nation ID; the other showing the forwarded station 
as the source ID and the out-going trunk as the 
destination ID. An internal station calling the for- 
warded station generates one SMDR call record 
showing the forwarded station as the source ID and 
the outgoing trunk as the destination ID. All records 
show the account code of the forwarded station. ’