
TD 92483GB
2008-06-05/ Ver. B
Installation and Operation Manual
UPAC- Unite Packet for Messaging and Alarm
98
F.1.3
Advanced parameters
F.2
Limitations in the Ascom Line Protocol
A line protocol message constists of the following records and separators:
<Addr/Message/Beepcode/PagFunc/NoOfTransm/Prio/Infopage>
All characters are writeable by hand using an ordinary terminal program such as hyper
terminal etc. Not all records needs to be given, for instance <> is a valid message that
delivers default message to default paging address.
The following limitations apply:
Mailbox number
(Record A, Ericsson dialect):
This record is accepted but ignored since it
is not
supported by
UNITE.
Infopage
(Record C, Ascom dialect):
This record is accepted but ignored since it
is not
supported by
UNITE.
Bleep each transmission:
This parameter was available in 942SI. The parameter is not
available in UPAC, instead the parameter can be set in
advanced GUI under “system 900”->”Beep at each Tx”.
Flow control XON/XOFF:
Not supported since there are some issues with the control
characters. If the block check character becomes any of the
two control characters XON or XOFF, the flow control fails,
therefore
flow control is no longer supported
.
PagFunc:
The Line protocol only supports call type 3 (plain paging) and
4 (alarm). All others are handled as plain paging.
NoOfTransm:
The Line protocol does not propagate no of transmissions but
it must be valid if submitted.
InfoPage:
The Line protocol does not propagate Infopage but it must be
valid if submitted.