Philips SOPHO Call@Net User manual

1
PREFACE
This manual is valid for SOPHO Call@Net (previously known as SSW 810), running on all
ISPBX models of the SOPHO iS3000 Series. All of these systems will further be referred to as
"ISPBX".
LICENSING AGREEMENT
The licensing agreement for an ISPBX determines which facilities are available. It is therefore
possible that a facility described here will not work on a specific ISPBX, even though it has
been correctly configured. Check the relevant license agreement to determine what is
available.
GENERAL NOTE
Fully Integrated Networks (FINs) are only supported by the iS3070/3090!

2
1. INTRODUCTION
The primary function of ISPBX is to provide facilities to make voice communication between
telephone sets possible. In most cases these telephone sets are normal analogue sets where
the speech signal is transformed into an analogue electrical signal and transferred over a 2 wire
twisted pair to the ISPBX, where it is converted into a 64 kbps digital signal. This signal is
switched in digital form to the required destination. The digital signal is then converted back
to analogue form and sent to the destination telephone set. Here the analogue electrical signal
is translated back into an audible signal.
The ISPBX can be connected to other PBXs or to the public switched telephone network with
analogue trunk or tie lines. A speech connection between telephone sets in different PBXs (or
PSTN) uses these trunk or tie lines.
A connection can be made using the ISPBX, from one digital set to another. The same sort of
telephone exchange facilities are then offered for digital connections. Various kinds of
peripherals can be connected.
It is not necessary to install a dedicated data network on a plant for the transfer of digital
information. The digital peripherals can be connected to the ISPBX using the existing
telephone wiring. Alternatively, digital connections can be used.
1.1. DATA COMMUNICATION
For the transfer of digital information between two digital parties, terminals or peripherals, the
same facilities are available as for voice communication. The ISPBX provides a transparent
path between two ports and the terminals determine what kind of information is transferred
between the terminals and if necessary what type of protocol is used between them.
1.1.1. Data Communication within the ISPBX
A digital connection can be established using analogue lines by using modems. A modem is
connected to an Analogue Line Circuit (ALC) instead of a normal analogue telephone set. The
connection between two data parties is established as if it was a normal speech call. The ISPBX
is not aware that a digital connection has been made.
A purely digital connection is made by connecting the digital peripheral to a Data Terminal
Adaptor which is in turn connected to a Digital Line Circuit (DLC) or a Digital Trunk and
Extension (DTX). A Data Terminal Adaptor is a SOPHO-SET, SOPHO-LAM or LAM. Each
digital peripheral is connected to a port identified by a directory number (DNR). Peripherals
can make contact with each other by dialling the required DNR and if the devices are

3
compatible (regarding the communication protocol) a connection between the devices can be
established. The connection is circuit switched, a continuously established connection
between two data parties.
Without the modem higher communication speeds between two internal data parties can be
obtained as the modem is often the limiting factor in data communication.
In larger systems, different ISPBX units are connected using 2 Mbps digital inter-unit links and
the network acts as if it is one large PBX. The users are not aware of the separate units in the
system. This applies both for voice and for data communication.
The terminals in the fully integrated network of these units can be located within one physical
location. In this case all units are located on the same premises (interconnected via short 2
Mbps inter-unit lines). Such a network of terminals can be called a Local Area Network (LAN).
It is also possible that the units are located further apart (interconnected via leased 2 Mbps
lines through the PSTN for instance) and that the terminals are spread over the entire ISPBX
network. In such a case the network of terminals can be called a Wide Area Network (WAN).
1.1.2. Data Communication over an Analogue Route
A modem connection can be established over an analogue trunk or tie line to a data party
located in another PBX or in the PSTN. The analogue trunk or tie line is connected to an
Analogue Trunk Unit (ATU).
If the data party is connected via a modem to an ALC, then a data call to an ATU can be
established as if it was a normal voice call. An outgoing call is made by dialling the trunk access
code to the required destination and if necessary the external number of the data party. The
dialled digits are transferred over the line in the form indicated by the bundle properties. An
incoming call can be directly connected to the ALC after analysing the incoming number.
Operator assistance can be useful for setting up the call, since this type of data call is
established using a speech connection. After the connection between the two parties is
established the modems are inserted at both sides and the data transfer can take place.
If a data party is connected to a DLC, then conversion is required to enable data to be
transferred over the analogue trunk line. A modem must therefore be inserted between the
DLC and the analogue trunk line. This is accomplished using a Modem Line Unit (MLU) or a
SOPHO-LAM P375.
If a trunk or tie line is dedicated for data calls then a modem can be permanently connected
to the line.

4
If the trunk or tie line is to be used for both voice and data then another procedure must be
followed. Modems are grouped into a pool and are switched into a connection when required,
i.e. when a data call is in progress.
1.1.3. Data Communication over a Digital Route
A data connection can be established over a digital trunk or tie line to a data party located in
another PBX or in the PSTN. The digital trunk or tie line is connected to a Digital Trunk Unit
(DTU).
If the data party is connected via a modem to an ALC, then the external party must also have
a modem connection. The modem's modulated carrier signal is digitised by the ALC and are
transferred over the digital route as `voice' samples. Incoming and outgoing data calls can be
allowed without further requirements.
If a data party is connected to a DLC, then an outgoing data call is established by dialling the
trunk or network access code of a digital route. The connection between the DLC and the
DTU is made directly. An incoming call can be directly connected to the DLC after analysing
the incoming number.
In this way a fully digital connection between the calling data party and the destination data
party in different networks is possible.
If the external data party in the opposite network is connected via an analogue line to the
external network, a modem must still be used. By means of compatibility check modem pool
dialling is possible as described in the part above.
1.2. TEXT COMMUNICATION
The ISPBX offers a transparent path through a network (once a path has been established
between two ports, the data that is transferred between the ports is not processed). Text can
therefore be transferred as analogue or digital signals.
1.3. IMAGE COMMUNICATION
The ISPBX offers a transparent path through a network (once a path has been established
between two ports, the data that is transferred between the ports is not processed). Images
can therefore be transferred as analogue or digital signals.
1.4. BOUNDARIES, OPTIONS, TIMERS
For some facilities, certain boundaries, options or timers are important. These parameters are

5
mentioned in the concerning subjects in this manual together with an indication if it is network
(NE) or local (LO) data. More information about these parameters can be found in the Second
Line Maintenance Manual.
The boundaries are assigned a value during the projecting of the unit via the PEuu.POM file.
When the value of a boundary, timer or option must be changed, this can be effected via a new
projecting with an adapted PEuu.POM file.
Most of the options and timers can be changed in an operational system using the second line
maintenance command EXSUBC sometimes activated by a hot-start. Boundaries can almost
never be changed in an operational system because a change in a boundary results in a new
partition of the CPU memory.
For more information: see Facility Implementation Manual; Networking and Routing.

6
2. DATA COMMUNICATION WITHIN THE ISPBX
The ISPBX acts as a data network `infrastructure' for the interconnection of end user
terminals, peripherals and host computers. Transparent analogue or digital connections are
established between digital peripherals in much the same way as a voice connection is
established between two telephone sets. The end user terminals may use any protocol for
information transfer, provided the path has the capacity for the transmission.
Since the connection between two ports is established for the duration of the data call, this
network acts as a Circuit Switched Data Network (CSDN).
A data connection is established, in general terms, as follows:
- The calling party dials the DNR of the required destination. Dialling can be either from the
DTE keyboard, from the SOPHO-SET, SOPHO-LAM or LAM, automatically under
control of a software program or from a telephone set if a modem is used.
- The ISPBX uses the dialled information to determine the destination, using number
analysis. A facility such as `hot line' may also be used to determine the destination.
- The ISPBX checks if the connection is allowed. This involves checking traffic class of the
caller, the IBSC of the caller and the BSPT of the destination and the compatibility value
connection allowance.
- The called party is rung.
- The called party answers. Answering can be either from the DTE keyboard, from the
SOPHO-SET, SOPHO-LAM or LAM, automatically under control of a software program
or from a telephone set if a modem is used.
- If the two DTEs are compatible then data transfer can take place.
- After data transfer (or even during data transfer), either party may break the connection.
This can be either from the DTE keyboard, from the SOPHO-SET, SOPHO-LAM or LAM,
automatically under control of a software program or from a telephone set if a modem is
used.
If the two DTEs are not located in the same unit, then the data is transferred between the two
involved units over one or more inter-unit links.
The ISPBX supports V.24 and X.21 interfaces for connecting DTEs. The interface is used to
transfer information from the DTE to the CPU for establishing the path to the destination port
and to transfer the user-information through the network after the connection is established.
Glossary
- DTE means Data Terminal Equipment, which can be a data terminal, printer, Personal
Computer, or any similar piece of equipment.

7
- DCE means Data Circuit terminating Equipment, which can be a modem or one of the
range of Philips SOPHO-SET, SOPHO-LAM or LAM.
A DTE can be connected to the ISPBX using one of the following connections:
- The DTE can be connected to an Analogue Line Circuit (ALC) via a modem. In this case
the modem is the DCE.
ISPBX (ALC) - MODEM - DTE
In this case the ISPBX does not know that a DTE is connected; it is only an extension with
a DNR assigned. Such a DTE can make data calls by sending dial information to the ALC.
The ISPBX establishes a transparent `analogue' speech channel with another ALC with a
modem connected. After answering a normal modem-modem connection is available.
The characteristics of the modem determine the interface type between DTE and
modem, the dialling and answering capabilities (for the call set-up and clearing) and the
actual data transmission of user-to-user information (during the data transfer phase). The
analogue part of the connection is often a limiting factor.
- The DTE can be connected to a Digital Line Circuit (DLC) via a SOPHO-SET, SOPHO-
LAM or LAM. In this case the SOPHO-SET, SOPHO-LAM or LAM is the DCE.
ISPBX (DLC) - SOPHO-SET, SOPHO-LAM or LAM - DTE
The DTE is identified by a DNR. Data is passed between DTEs in a transparent channel.
The fully digital connection offers additional opportunities.
The DTE is not connected directly to the digital line circuit but to a DCE. This can be a
SOPHO-SET, SOPHO-LAM or LAM. The type of DCE determines the interface type
between DTE and ISPBX network, the dialling and answering capabilities (for the call set-
up and clearing) and the actual data transmission of user-to-user information (during the
data transfer phase).
The most common interface type between the digital line circuit and the DTE is V.24.
Most information in this chapter will be dedicated to this type of interface. Most
information will also be valid for the X.21 interface. In a special part in this chapter the
special X.21 information will be discussed.
If an internal data party wishes to be connected to a party in a special type of data network
and the ISPBX does not support the interface type then a gateway is required. Such a gateway
can be connected to a DLC.
2.1. CONNECTING A DTE TO AN ALC
Digital peripherals can be connected to ISPBX using conventional analogue connections. This
type of digital communication uses modems. The ISPBX does not know there is a digital
terminal connected to the ALC and there is also no need to know. A transparent path between
ALCs can be established irrespective the type of information transferred over the connection;

8
voice or a modulated carrier with digital information.
The diagram below shows the connection of two DTEs using modems. Here a single unit
configuration is illustrated (one switching network). A connection made between units uses 2
Mbps inter-unit links between the switching networks.
Figure 2-1 Analogue Connection between Terminals within the ISPBX.
The end user terminal is a DTE Equipment (DTE). The modem is a Data Circuit Terminating
Equipment (DCE). A normal flat cable can be used for connecting both devices. By using two
compatible modems two devices with any type of interface can be connected. The type of
interface is of no interest as long as the ISPBX receives the call set-up information. For detailed
information on the functioning of an interface, such as V.24, see the data communication
literature.
The calling modem modulates the digital information from the calling data party on a carrier
and this modulated carrier is transferred through the `analogue' network in the speech band.
The receiving modem demodulates the incoming signal and the digital information is
transferred to the destination data party. The two modems must be compatible with each
other (use the same transmit and receive frequencies). In the case of full duplex
communication Frequency Division Multiplexing is used. The calling data party uses the low
frequency band (within the speech band) to send information while the called party uses the
high frequency band as backward channel.
Depending on the type of modem, call set-up may be done using a normal telephone set
(rotary dial or keytone), using keyboard dialling from the DTE or automatically under control
of the DTE software. For example, V.25bis commands or AT-commands can be used for call
set-up. The modem transfers the digits to the network as pulses or keytones. If a telephone
AD
DA
DTE
V.2 4
DTE
DCE
64 kbps
5404
CV0
Speech
Speech or modulated carrier Speech or modulated carrier
Compatible modems
C
V
0
C
V
0
:
a
ll
o
w
ed
5404
CV0
Speech
64 kbps
ALC
V.24
MODEM MODEMSN

9
set is used for call set-up then the modem is connected to the line after the connection has
been established.
A number of important points should be remembered to enable a modem-modem connection
to be established:
- A modem can be connected to any type of ALC.
- The ALC to which the modem is connected must be allocated a DNR.
- The destination DNR must be included in the appropriate dialling tree of the calling party.
- The traffic class of the calling party must at least have the same traffic class as the
destination number indicated in the dialling tree.
- The IBSC 14=`SOPHO speech' should be allocated to the DNR.
- The BSPT 14=`SOPHO speech' (or another voice BSPT) should be allocated to the DNR.
- The CV of the DNR must be created as voice (CRCVAL or CHCVAL) and assigned to the
DNR (CHAGCV).
- The compatibility value connection allowance between the CV of the calling and the CV
of the called party must be set to allowed (CHCVCA). For more information: see
Appendix A.
- No facility class mark inhibits the connection.
- The facilities offered by `data protection' prevent a break-in attempt by another extension
or operator. A break-in to an established modem connection could disturb the data
connection.
For more information on these mechanisms: see Facility Implementation Manual;
Management.
2.2. CONNECTING A DTE TO A DLC/DTX
A DTE can be connected to the ISPBX using a Digital Line Circuit (DLC) or Digital Trunk and
Extension (DTX) board and a DCE. The DCE is a SOPHO-SET, SOPHO-LAM or LAM.
The DLC-A, B, C, D or U is connected to a SOPHO-SET, LAM or PNT1 using a 2 wire, 2B+D
S0interface connection. This is a twisted pair connection over which two user (2B) channels
of 64 kbps and a signalling (D) channel of 16 kbps are transferred. An additional 8 kbps
synchronisation signal, makes the transmission speed 152 kbps. Existing twisted pairs (a-b
wires, as used for analogue telephones) can be used for these data connections; no new wiring
needs to be installed. The imperfections of the line are compensated for by using echo
cancelling techniques for the transfer of digital information.
The DLC-I or DTX-I is connected to a SOPHO-SET or SOPHO-LAM using a 4 wire, ISDN
2B+D S{inf0} interface connection.

10
For more information: see Hardware configuration Manual and Maintenance Manual, part 3:
Board Interfaces and Strap Settings.
A number of important points should be remembered when making a connection between
DTEs connected to DLCs:
- A DTE can be connected to the DLCs as listed earlier.
- The DLC to which the DTE is connected must be allocated a DNR. In the case of a
SOPHO-SET, two DNRs must be allocated, one for the voice port and one for the data
port.
- The destination DNR must be included in the appropriate dialling tree of the calling party.
- The traffic class of the calling party must at least have the same traffic class as the
destination number indicated in the dialling tree.
- The IBSC 00=`64 kbps unrestricted' should be allocated to the data DNR.
- The BSPT 00=`64 kbps unrestricted' (or another data BSPT) should be allocated to the
data DNR.
- The IBSC 14=`SOPHO speech' should be allocated to the voice DNR of a SOPHO-SET.
- The BSPT 14=`SOPHO speech' (or another voice BSPT) should be allocated to the voice
DNR of a SOPHO-SET.
- The data port of the SOPHO-SET, SOPHO-LAM or LAM used in the connection must be
correctly programmed. Both sides of the connection must be compatible.
- The CV of the data DNR must be created as data (CRCVAL or CHCVAL) and assigned to
the DNR (CHAGCV). For a SOPHO-SET the CV for the voice DNR must be assigned as
voice.
- The CV of a data DNR can be used to download the data port parameters of the SOPHO-
SET, SOPHO-LAM or LAM. If this is required then the data port parameters are
downloaded to the DNR using DOWNLD.
- The compatibility value connection allowance between the CV of the calling and the CV
of the called party must be set to allowed (CHCVCA). For more information: see
Appendix A.
- No facility class mark inhibits the connection.
- Facility class mark FCM 12=`SOPHO-SET' must be allocated to the DNR of the DTE. For
a SOPHO-SET this must be done for both the voice and data DNRs. This indicates that
the ISPBX must send call progress information (for instance ringing, answered, called by,
call diversion address etc.), LED activation/de-activation signals and display information to
the SOPHO-SET, SOPHO-LAM or LAM. Call progress information is used, for example,
on the display of the SOPHO-SET, SOPHO-LAM or on the screen of the DTE.
2.3. DATA PORT
The data port of the SOPHO-SET, SOPHO-LAM or LAM acts as the interface between the

11
DTE and the ISPBX network and is therefore used as Data Circuit Terminating Equipment
(DCE). A normal flat cable can be used for the connection.
The full digital connection for data communication within a FIN is illustrated in figure Figure 2-
2 Full Digital Connection between Data terminals within the ISPBX.

12
Figure 2-2 Full Digital Connection between Data terminals within the ISPBX.
The data port takes care that the user data (and some control signals if required and possible)
is sent to the destination DTE. The conventions for the interface type only apply to the
DNR=5401
CV=3, Data
64 kbps user
channel in 2B+D line
64 kbps user
channel in 2mbps
USI / USO lines
DNR=5402
CV=3, Data
DNR=5403
CV=3, Data
DNR=5404
CV=3, Data
DNR=5405
CV=3, Data
DNR=5407
CV=3, Data
DNR=5406
CV=3, Data
DNR=5408
CV=3, Data
DNR=5301
CV=0,Speech
DNR=5302
CV=0,Speech
CV3 - CV3 : allowed
CV3 - CV0 : not allowed
V.24
V.24
LAM
DCE
SOPHO-LAM
DCE
SOPHO-LAM
DCE
SOPHOSET
DCE
SOPHOSET
DCE
V.24
V.24
V.24
V.24
V.24
V.2 4
2B+D 2B+D
64 kbps
64 kbps
64 kbps
64 kbps
64 kbps
64 kbps
DTE DTE
DTE
DTE
DTE
DTE
DTE
DTE
64 kbps
2B+D
2B+D
2B+D2B+D
2B+D
2B+D2B+D
DCE DCE
SN
SN
SN
SN
SN
DLC/
DTX-I
DLC/
DTX-I
DLC/
DTX-I
DLC/
DTX-I
DLCPNT-1
DLC/
DTX-I
DLCPNT-1
SN

13
interface between the DTE and the data port; NOT between the two DTEs.
Before a data call can be established, the data port must know if the DTE is ready to send or
accept data. Therefore the normal on-line operations must be performed (V.24: CT 108 and
CT 107 procedure; X.21: C and I procedure).
In the dialling phase the destination number is received by the DCE either from the keypad
(not for the LAM) or from the connected DTE (either from the terminal keyboard or from the
software program). The DCE transfers the number to the DLC-controller using a protocol-
message in the D-channel. The DLC-controller initiates a call set-up request to the PPU and
further to the CPU using the normal Internal Message Protocol (IMP).
For more information on the D-channel protocol: see Facility Implementation Manual;
Networking and Routing.
If the call is allowed (number analysis, traffic classes, CV allowances and facility class marks)
the ISPBX sends ringing current to the destination data port. The called data port receives a
string from the CPU with the calling party identification. If required this string can be passed
to the DTE.
If the called party answers the call, a transparent 64 kbps connection between the calling data
port and the destination data port is established. If the two ports are located in the same unit
only one switching network is involved. If the ports are located in different units, the 64 kbps
connection is established between two or more switching networks connected together by a
64 kbps timeslot in 2 Mbps inter-unit links. For full duplex communication a reversed path
from the called to the calling data port is also established. The calling data port receives a
message to inform the port that the call has been answered.
After the transparent connection is established, the ISPBX is not involved in the data call any
more until one of the data ports sends a message that the data call has finished. The ISPBX will
then break down the connection.
The set-up of the complete data port can be defined by of programming the interface
parameters. These include transmission speed and mode, separate signals of the interface
control, method of data rate adaption, method used for dialling and the character format.
Programming can be performed locally (using the keypad of the SOPHO-SET or SOPHO-
LAM or by using the keyboard of the DTE) or remotely (by downloading the data compatibility
value). The exact options available depend on the SOPHO-SET, SOPHO-LAM or LAM.
- DTE initiates activity.
If the DCE is idle (i.e. not busy with a data connection), the DTE is able to communicate
with the microprocessor of the DCE for dialling or data port programming. For local

14
programming of the data port from the DTE keyboard, the DTE must be on-line (for
instance, by setting the CT108 signal of the data port on).
The microprocessor of the DCE prompts the DTE for input that can be dial information
or a special command to enter programming mode. If keyboard dialling is selected then a
number or name can be entered for dialling. If V.25 bis or AT-command dialling is selected,
the microprocessor interprets the entered call set-up request and returns the result to the
terminal.
After the entry of dial information the microprocessor uses the D-channel protocol to
send the dial information towards the ISPBX. After the destination party has answered the
call, the data rate adaptor starts sending and receiving the frame pattern. After
synchronisation the microprocessor connects the DTE to the data rate adaptor and the
transparent DTE-DTE connection is established. If the user transmission rate is 64 kbps
no synchronisation phase is necessary and the terminal is switched to the data rate adaptor
when the opposite party has answered.
- ISPBX initiates activity.
The microprocessor of the DCE is able to communicate with the CPU using D-channel
messages. If an idle data party is called, the microprocessor receives a call set-up message.
If required, the calling party identification (part of the call set-up message) can be sent to
the DTE.
The incoming call can be answered automatically (DCE answers the call autonomously) or
manually (DTE answers the call). The data rate adaptor starts sending and receiving the
frame pattern. After synchronisation the microprocessor connects the DTE to the data
rate adaptor and the transparent DTE-DTE connection is established. If the user
transmission rate is 64 kbps no synchronisation phase is necessary and the terminal is
switched to the data rate adaptor when the opposite party has answered.
Note: If the data port supports synchronous communication, this only applies to the user - user
data transfer phase. The communication between the DTE and the DCE is asynchronous
and is used for programming and dialling the destination number. After the connection has
been set-up to the destination DTE the transmission mode can be switched over to
synchronous communication. If the DTE is not able to perform the switch-over the
connection set-up can be performed automatically using the hot line facility.
A schematic overview of the data port configuration and its place in the SOPHO-SET,
SOPHO-LAM or LAM is illustrated in the following figures.

15
Figure 2-3 Data port configuration within LAM 308 and LAM 309.
Figure 2-4 Data port configuration within SOPHO-LAM P375.
INTERFACE
CONTROL
INTERFACE
CONTROL
µP
ECHO
CANCELLER
2B+D
152 kbp
s
Keyboard dialling
Data port programming
LAMPS
MEMORY
DATA RATE
ADAPTION
DATA RATE
ADAPTION
64 kbps
B-channel
V.2 4
X.21
V.2 4
X.21
16 kbps
D-channel
64 kbps
B-channel
MULTIPLEXER
INTERFACE
CONTROL
µP
2B+D
152 kbp
s
Keyboard dialling
AT command dialling
V.25bis dialling
Data port pro
g
rammin
g
LAMPS &
DISPLAY
KEYPAD
MEMORY
DATA RATE
ADAPTION
64 kbps
B-channel
V.2 4
16 kbps
D-channel
MULTIPLEXER

16
Figure 2-5 Data port configuration within SOPHO-SET 308, S375 D, P375 D and P370 D.
2.3.1. Interface Control and Data Rate Adaption
There are two systems of data transfer:
•With Data Rate Adaption
If the transmission speed between the two DTEs is less than 64 kbps then the data rate
must be adapted. Also some of the control signals of the interface between the DCE and
the DTE can be transferred. The two DCEs use a frame structure to communicate with
each other. The user data and interface control signals are located in fixed positions within
that frame. The data rate adaption methods supported by SOPHO-SET, SOPHO-LAM
and LAM are summarised below.
INTERFACE
CONTROL
µP
ECHO
CANCELLER
2B+D
152 kbps
(
SOPHO-SET 308
and
S375 D only)
DATA RATE
ADAPTION
ANALOGUE
DIGITAL
CONVERTOR
AUDIO
INTERFACE
HANDSET
64 kbps
B-channel
V.2 4
16 kbps
D-channel
64 kbps
B-channel
MULTIPLEXER
LAMPS &
DISPLAY
KEYPAD
MEMORY
Keyboard dialling
AT command dialling
V.25bis dialling
Data port pro
g
rammin
g

17
Table 2-1 Rate Adaptation Methods.
First the two data ports try to synchronise using a synchronisation pattern in the frame
structure. If this pattern is detected without errors, then synchronisation is established.
Synchronisation must be achieved in both directions. Once synchronisation is established
the user-data and the interface control signals can be transferred between the two parties
and the 64 kbps transparent channel is available to the DTEs.
Each DCE receives the relevant interface signals (control signals and the user data) from
the DTE and inserts them into the correct frame position in the 64 kbps user channel. This
user channel is multiplexed by the DCE into the 152 kbps 2B+D line to the DLC. The
DLC-line interface demultiplexes the 64 kbps user channel from the 2B+D line and inserts
it in a timeslot in the 2 Mbps highway to the PSC/PMC. The 64 kbps signal is transferred
to the opposite DLC, via the PSC/PMC and the switching network (and, if necessary, inter-
unit links). The receiving DLC extracts the 64 kbps user channel from the 2 Mbps highway
and multiplexes it into the user channel of the 2B+D line to the destination DCE. The data
and control signals are extracted from the 2B+D line by the DCE and passed to the DTE.
A transparent digital path has thus been established between the two DTEs.
Data rate adaption is performed by a dedicated chip in ERGOLINE, SOPHO-SET,
SOPHO-LAM or LAM; for SOPHO-SET, SOPHO-LAM or LAM the OQ 1505 or the OQ
1509. A summary of the most important features of these chips is given below.
PROPRIETARY X.30 V.110
Synchronous sampling frequency: 96kHz - -
Bits per frame : 32 80 80
Data : 24 48 48
Synchronisation : 4 17 17
Synchronisation status : 1 - -
State of CT105 / CT109: 3 2 2
Speed : - 3 3
NIC : - 3 3
600/1200 bps synchronisation adaption: - 1 1
State of CT108 / CT107: - 4 4
Flow control (CT106): - 2 2

18
DATA OQ1505 OQ1509 Ergoline
Used in : LAM 308 SOPHO-SET S375
D
D340 with V.24 data
port
LAM 309 SOPHO-SET P375
D
SOPHO-SET 308 SOPHO-SET P370
D
MLU SOPHO-LAM P375
Data rate adaptions
supported:
Philips proprietary Philips proprietary
X.30 X30
V.110 V.110
Synchronous speeds
supported:
600 600
1200 1200
(bps) 2400 2400
4800 4800
9600 9600
19200 19200
38400 38400
48000 48000 48000
56000 56000 56000
64000 64000 64000
Asynchronous speeds
supported:
50
75
(bps) 110
150
200
300 300 300
600 600 600
1200 1200 1200
1200/75 1200/75

19
Table 2-2 Summary of Data Rate Adaptors.
•Without Data Rate Adaption
If the transmission speed between the two DTEs is 64 kbps, then the full data channel is
used for transferring user information; no control signals can be transferred. Since no
control signals are transferred no synchronisation can be applied. The DTEs themselves
must use some kind of frame structure to interpret the digital information.
The DCE receives the user-data from the DTE and inserts it in the 64 kbps user channel.
The user channel is multiplexed by the DCE into the 152 kbps 2B+D line to the DLC. The
DLC-line interface demultiplexes the 64 kbps user channel from the 2B+D line and inserts
it in a timeslot in the 2 Mbps highway to the PSC. The 64 kbps signal is transferred to the
opposite DLC, via the PSC/PMC and the switching network (and, if necessary, inter-unit
links). The receiving DLC extracts the 64 kbps user channel from the 2 Mbps highway and
multiplexes it into the user channel of the 2B+D line to the destination DCE. The data is
extracted from the 2B+D line by the DCE and passed to the DTE. A transparent 64 kbps
digital path has thus been established between the two DTEs.
2.3.2. Profiles
This feature is only available in the SOPHO-SET S375 D, SOPHO-SET P375 D and the
75/1200
2400 2400 2400
3600
4800 4800 4800
7200
9600 9600 9600
12000
14400
19200 19200 19200
38400 *) 38400
48000 *)
56000 *)
64000 *)
*) Speeds higher than 19200 are not supported by LAMs or SOPHO-SET
DATA OQ1505 OQ1509 Ergoline

20
SOPHO-LAM P375.
Two data ports are only able to communicate correctly with each other if they use the same
data port set-up. This is:
- Transmission mode (synchronous/asynchronous);
- Conversation mode (full/half duplex);
- Transmission speed;
- Data format (byte length, stop bits, parity);
- Terminal rate adaption method;
- Terminal rate adaption options (flow control, Network independent Clock).
Only in this case are the data bits and the control signals transmitted and received in the same
fixed positions in the frame structure.
It may be necessary for a DTE to be connected with other DTEs employing different data port
set-ups. The use of `data profiles' makes it possible to connect normally incompatible parties.
A data profile is a data port set-up that can be used for the duration of a single data call. The
profile is used to temporarily change the set-up of the local data port according to a set-up as
used by another remote DTE. A data profile contains a complete data port set-up.
Four profiles can be defined. A profile must also be allocated to an entry in the name directory
of the DCE.
When either an incoming call from or an outgoing call to another DTE is made, the DCE
automatically changes the data port set-up to that of the profile; the two data ports are
compatible.
When a call is initiated using the name directory and a profile is assigned to the name then the
data port set-up is adjusted according to the information in the profile. With an incoming call,
the DCE checks the received calling party identification. If the received number is stored in
the directory and a profile is assigned to it, then the data port set-up is adjusted according to
the information in the profile.
The information in the profile is only valid for the duration of one data call. After releasing the
call, the set-up of the data port is restored to the local programming as was used before the
profile changed the set-up.
More details on profiles are contained in the User Guide/Data Guide of the DCE.