MOD-14-1758 DIUG Issue 1

Sepura TETRA Terminal
Data Interface User Guide

Software Release: Version 10.14
MOD-14-1758
Issue 1
This document is issued under NDA only
COMMERCIAL IN CONFIDENCE
© SEPURA PLC 2014

MOD-14-1758
NOTICE
All rights reserved. This document may not be reproduced in any form either in part or in whole without the
prior written consent of Sepura plc, nor may it be edited, duplicated or distributed using electronic
systems.
This document and the product it describes are considered protected by copyright according to the
applicable laws.
The information in this document is subject to change without notice. This document is intended for
Sepura plc’s customers and/or other parties only for the purposes of the agreement or arrangement under
which this document is submitted, and no part of it may be reproduced or transmitted in any form or
means without the prior written permission of Sepura plc.
The document has been prepared to be used by professional and properly trained personnel, and the
customer and/or other party assumes full responsibility when using it. Sepura plc welcomes customer
and/or other party comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this document concerning the suitability, capacity, or performance
of the mentioned hardware or software products cannot be considered binding but shall be defined in the
agreement or arrangement made between Sepura plc and the customer and/or other party.
However, Sepura plc has made all reasonable efforts to ensure that the instructions contained in the
document are adequate and free of material errors and omissions. Sepura plc will, if necessary, explain
issues which may not be covered by this document.
Sepura plc’s liability for any errors in this document is limited to the documentary correction of errors.
Sepura plc WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR
ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL, (INCLUDING MONETARY LOSSES), that might
arise from the use of this document or the information in it.
Other product names mentioned in this document may be trademarks of their respective companies, and
they are mentioned for identification purposes only.
Copyright © Sepura plc 2014. All rights reserved.
Contact Details
Sepura plc
Radio House
St Andrew’s Road
Cambridge CB4 1GR
United Kingdom
Web : www.sepura.com
Tel: +44 (0)1223 876000
Fax: +44 (0)1223 879000
Issued by Issue 1 Page 2 of 200
Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

MOD-14-1758
ISSUE HISTORY
Version Date Change
Issue 1 21 July 2014 Initial Version
REFERENCES
Reference Title
[1] ETSI specification ETS 300 392-2 Edn 1 - http://www.etsi.org/
[2] ETSI specification ETS 300 392-2 Edn 2 (v2.3.2) - http://www.etsi.org/
[3] NMEA-0183 version 2.01 - http://www.nmea.org/
[4] ITU V.24 - http://www.itu.int/
[5] ITU V.250 - http://www.itu.int/
[6] ETSI specification EN 100 392-5 version 1.3.5- http://www.etsi.org/
[7] GPS Functionality and Air Interface User Guide (Sepura document MOD-10-1147)
[8] TIP: TTR 001-17 Radio User Assignment - http://www.tetramou.com/

MOD-14-1758
CONVENTIONS
Convention Description
Note icon, emphasizes related, reinforcing, or important information.
Caution icon. Indicates actions or processes that require caution from the user

MOD-14-1758
Table of Contents
1 INTRODUCTION ........................................................................................................9
2 PHYSICAL INTERFACE DETAILS ..........................................................................10

2.1 Hand-Held ........................................................................................................................................ 10
2.1.1 Signal Lists ...................................................................................................................................................................... 12
2.1.2 Connectivity Options ........................................................................................................................................................ 13
2.2 Mobile and Gateway ....................................................................................................................... 15
2.3 Serial Protocol ................................................................................................................................ 17
2.4 Dual Serial port ............................................................................................................................... 18

®
2.5 Bluetooth functionality ................................................................................................................. 18
2.6 USB functionality ............................................................................................................................ 19
2.7 Connector Protector ....................................................................................................................... 19
3 PEI AT COMMAND INTERFACE COMMAND SYNTAX .........................................20

3.1 Command Mode Responses ......................................................................................................... 20
3.2 Transparent Data Mode .................................................................................................................. 21
4 PEI TEXT MESSAGING ...........................................................................................22

4.1 Sending Status Messages ............................................................................................................. 23
4.2 Supported SDS Messages ............................................................................................................. 24
4.3 SDS-TL Message Encoding ........................................................................................................... 25

4.3.1 The Importance of the SDS-TL Header............................................................................................................................ 25
4.3.2 Message numbering ........................................................................................................................................................ 25
4.3.3 End-to-end acknowledgement ......................................................................................................................................... 26
4.4 SDS-TL Short-form Delivery Report ............................................................................................. 27
4.5 SDS-TL Report ................................................................................................................................ 28
4.6 SDS-TL Compliance ....................................................................................................................... 29
4.7 Restrictions ..................................................................................................................................... 30

4.7.1 SDS Message Size .......................................................................................................................................................... 30
4.7.2 Group Calls ..................................................................................................................................................................... 30
4.7.3 Multiple Messages ........................................................................................................................................................... 30
4.8 Short Data and Status Message Examples ................................................................................. 31

4.8.1 Status message transmission example ............................................................................................................................ 31
4.8.2 Status message reception example ................................................................................................................................. 31
4.8.3 Simple SDS-TL protocol transmission example ............................................................................................................... 31
4.8.4 Full SDS TL protocol transmission example..................................................................................................................... 32
4.8.5 Incoming full SDS-TL protocol example ........................................................................................................................... 33
4.8.6 Sending a Delivery Report Example ................................................................................................................................ 33
4.8.7 Sending a Delivery Short Report Example ....................................................................................................................... 34

MOD-14-1758
4.8.8 SDS Message Routing .................................................................................................................................................... 34
5 PEI CIRCUIT MODE CALLS ....................................................................................37

5.1 Circuit-mode Voice Calls ............................................................................................................... 37
5.1.1 Preparation ...................................................................................................................................................................... 37
5.1.2 Setup ............................................................................................................................................................................... 37
5.1.3 Reception and Connection............................................................................................................................................... 37
5.1.4 Transmission control in a half-duplex call......................................................................................................................... 38
5.1.5 Call Termination .............................................................................................................................................................. 38
5.1.6 Control of Audio Routing for Mobile and Gateway ............................................................................................................ 39
5.1.7 Example of Message Flow for a Half-Duplex Voice Call ................................................................................................... 40
5.2 Circuit-mode Data Calls ................................................................................................................. 40

5.2.1 Preparation ...................................................................................................................................................................... 41
5.2.2 Setup ............................................................................................................................................................................... 41
5.2.3 Reception and Connection............................................................................................................................................... 41
5.2.4 Switching Between a Call and Command Mode............................................................................................................... 41
5.2.5 Call Termination .............................................................................................................................................................. 41
6 PEI PACKET DATA .................................................................................................42

6.1 Hayes AT command for Packet Data ............................................................................................ 42
6.1.1 ATD - Dial ........................................................................................................................................................................ 42
6.1.2 Terminating the Session .................................................................................................................................................. 42
6.1.3 Return Codes .................................................................................................................................................................. 43
6.2 IP Addresses (Static/Dynamic) ...................................................................................................... 43
6.3 Dialling from Windows and Linux ................................................................................................. 43

6.3.1 Windows .......................................................................................................................................................................... 43
6.3.2 Pocket PC ....................................................................................................................................................................... 43
6.3.3 Linux................................................................................................................................................................................ 43
7 PEI AT COMMAND SET OVERVIEW ......................................................................45

7.1 Commands ...................................................................................................................................... 45
7.1.1 A/ – Repeat Last Command............................................................................................................................................. 45
7.1.2 ATA - Answer .................................................................................................................................................................. 46
7.1.3 ATD - Dial ........................................................................................................................................................................ 47
7.1.4 ATE - Echo ...................................................................................................................................................................... 50
7.1.5 ATH - Hook State ............................................................................................................................................................ 51
7.1.6 ATI - Identify Host Product ............................................................................................................................................... 52
7.1.7 ATO - Return to Online .................................................................................................................................................... 54
7.1.8 ATQ - Results Code ........................................................................................................................................................ 55
7.1.9 ATR - MT Reboot ............................................................................................................................................................ 56
7.1.10 ATS0 - Automatic Answer ........................................................................................................................................... 57
7.1.11 ATS2 - Escape character ............................................................................................................................................ 58
7.1.12 ATS3 - Line Termination Character ............................................................................................................................. 59
7.1.13 ATS4 - Line Feed Character........................................................................................................................................ 60
7.1.14 ATS5 - Backspace Character ...................................................................................................................................... 61
7.1.15 ATV - Results Code .................................................................................................................................................... 62
7.1.16 ATZ - Reboot .............................................................................................................................................................. 63
7.1.17 AT+CBC - Battery Charge ........................................................................................................................................... 64
7.1.18 AT+CCI - Cell Information ........................................................................................................................................... 66
7.1.19 AT+CGPS - GPS Functions ........................................................................................................................................ 68
7.1.20 AT+CLVL - Volume Control ......................................................................................................................................... 69
7.1.21 AT+CMGS - Send Message ........................................................................................................................................ 70
7.1.22 AT+CMEE - Extended Error Reporting ........................................................................................................................ 73
7.1.23 AT+CNCI - Neighbour Cell Information ....................................................................................................................... 74
7.1.24 AT+CNUM - Identities ................................................................................................................................................. 76
7.1.25 AT+CNUMD - Get MT Dynamic Group Identities ......................................................................................................... 77
7.1.26 AT+CPIN - Enter PIN .................................................................................................................................................. 79
7.1.27 AT+CREG - Registration Status .................................................................................................................................. 81
7.1.28 AT+CSPBOPTA - BOS Read Smart Card OPTA ........................................................................................................ 83
7.1.29 AT+CSPSCTR Smart Card Text Reports .................................................................................................................... 84
7.1.30 AT+CSPDCS - DMO Connectivity Status .................................................................................................................... 85

MOD-14-1758
7.1.31 AT+CSPICPN - Incoming Call Proprietary Extensions Notification Command ............................................................. 87

7.1.32 AT+CSPKA Key agreeement ...................................................................................................................................... 88
7.1.33 AT+CSPLOGIO - Log In / Log Out Command ............................................................................................................. 89
7.1.34 AT+CSPRTC - Time Server Synchronisation .............................................................................................................. 90
7.1.35 AT+CSPSCS Smart Card Status ................................................................................................................................. 91
7.1.36 AT+CSPTAA1 - Application Action 1 - Radio Switch Off .............................................................................................. 92
7.1.37 AT+CSPTAA2 - Softkey Action ................................................................................................................................... 93
7.1.38 AT+CSPTAA3 - Licensed Soft Key Functions ............................................................................................................. 95
7.1.39 AT+CSPTAP1 - Application Parameter 1 - Scanning On / Off ................................................................................... 100
7.1.40 AT+CSPTAP16 - Application Parameter 16 (BOS DMO Cryptomode) ...................................................................... 101
7.1.41 AT+CSPTAP17 - Application Parameter 17 (BOS E2EE Enable) .............................................................................. 102
7.1.42 AT+CSPTAP18 Application Parameter 18 (BOS SDS Encryption Key) .................................................................... 103
7.1.43 AT+CSPTGF - Talk Group Folders............................................................................................................................ 104
7.1.44 AT+CSPTGFC - Talk Group Folder Configuration ..................................................................................................... 106
7.1.45 AT+CSPTGFS - Group Folder Select ........................................................................................................................ 110
7.1.46 AT+CSPTGG - Set or Read groups when operating in Gateway Mode ..................................................................... 112
7.1.47 AT+CSPTGI - Talk Group Information ....................................................................................................................... 114
7.1.48 AT+CSPTNI - Get TETRA Network Identities ............................................................................................................ 116
7.1.49 AT+CSPTNS - Set TETRA Network .......................................................................................................................... 117
7.1.50 AT+CSPTSS - TETRA Stack Select .......................................................................................................................... 118
7.1.51 AT+CSPTR – Reboot radio ....................................................................................................................................... 120
7.1.52 AT+CSPTSSN - TETRA Stack Active Select Notification Command ......................................................................... 121
7.1.53 AT+CSQ - Signal Quality........................................................................................................................................... 122
7.1.54 AT+CTBCT - TETRA Broadcast ................................................................................................................................ 123
7.1.55 AT+CTGS - Group Attachment.................................................................................................................................. 125
7.1.56 AT+CTSDC - Service Definition for Circuit Mode services ......................................................................................... 128
7.1.57 AT+CTSDS - Service Definition for SDS ................................................................................................................... 132
7.1.58 AT+CTSP - Service Profiles ...................................................................................................................................... 134
7.1.59 AT+CTSTR - TETRA Status Text Read..................................................................................................................... 137
7.1.60 AT+CTXD - Transmission Demand ........................................................................................................................... 139
7.1.61 AT+CUTXC - Uplink Transmission Ceased ............................................................................................................... 141
7.1.62 AT+GMI - Manufacturer Identity ................................................................................................................................ 143
7.1.63 AT+GMM - Model Identity ......................................................................................................................................... 144
7.1.64 AT+GMR - Revision Numbers ................................................................................................................................... 146
7.1.65 AT+GSN - Serial Numbers ........................................................................................................................................ 147
7.1.66 AT+IPR - EDC Data Rate .......................................................................................................................................... 148
7.1.67 AT&F - Factory Defaults ............................................................................................................................................ 149
7.1.68 AT@N - Read ITSI .................................................................................................................................................... 151
7.1.69 AT@T ....................................................................................................................................................................... 152
7.1.70 AT@Z ....................................................................................................................................................................... 152
7.1.71 +++ – Escape Sequence ........................................................................................................................................... 153
7.2 Unsolicited Responses ................................................................................................................ 154

7.2.1 +CDTXC - Downlink Transmission Ceased.................................................................................................................... 154
7.2.2 +CMGS - Send Message ............................................................................................................................................... 155
7.2.3 +CNUMD - Report MT Dynamic Group Identities ........................................................................................................... 156
7.2.4 +CREG – Report Registration Status ............................................................................................................................. 157
7.2.5 +CSPSCS - Smart card status ....................................................................................................................................... 159
7.2.6 +CSPSCTR - Smart Card Text Report ........................................................................................................................... 160
7.2.7 +CSPTAP16 - Application Parameter 16 (BOS DMO Cryptomode) ............................................................................... 161
7.2.8 +CSPTAP17 - Application Parameter 17 (BOS E2EE Enable) ....................................................................................... 161
7.2.9 +CSPTAP18 - Application Parameter 18 (BOS SDS Encryption Key) ............................................................................ 162
7.2.10 +CSPBOPTA - BOS Report Smart Card OPTA ......................................................................................................... 163
7.2.11 +CSPBTOPTA - BOS Transmitting Party OPTA ........................................................................................................ 164
7.2.12 +CSPDCS - Report DMO Connectivity Status ........................................................................................................... 165
7.2.13 +CSPICP – Incoming Call Proprietary Extensions ..................................................................................................... 166
7.2.14 +CSPLOGIO – Log In / Log Out Status ..................................................................................................................... 167
7.2.15 +CSPTD – Terminal Disable Status .......................................................................................................................... 169
7.2.16 +CSPTSSA - TETRA Stack Select Active Stack Notification ..................................................................................... 170
7.2.17 +CTBCT - TETRA Broadcast .................................................................................................................................... 171
7.2.18 +CTCC - Call completion........................................................................................................................................... 173
7.2.19 +CTCR - Call Release ............................................................................................................................................... 174
7.2.20 +CTGS ...................................................................................................................................................................... 175
7.2.21 +CTICN - Incoming Call Notification .......................................................................................................................... 176
7.2.22 +CTOCP - Outgoing Call Progress ............................................................................................................................ 178
7.2.23 +CTSDSR - SDS Received ....................................................................................................................................... 180
7.2.24 +CTXG - Transmission Grant Status ......................................................................................................................... 182
7.2.25 +CTXI - Transmission Interrupt ................................................................................................................................. 183
7.2.26 +CTXN - Transmission Continue ............................................................................................................................... 184
7.2.27 +CTXW - Transmission Wait ..................................................................................................................................... 185
7.3 CME errors within the Tetra PEI .................................................................................................. 186

7.3.1 Responses to commands .............................................................................................................................................. 186

MOD-14-1758
7.3.2 CME errors and Sepura radios ...................................................................................................................................... 187
8 TETRA SIMULTANEOUS TRAFFIC AND SDS LIMITATIONS .............................189
9 EXTERNAL DIGITAL INPUTS AND OUTPUTS ....................................................192

9.1 Inputs ............................................................................................................................................. 192
9.2 Outputs .......................................................................................................................................... 192
10 GLOSSARY ........................................................................................................194
11 APPENDIX 1: COMMANDS AND SOFTWARE VERSIONS ..............................196

11.1 Table to show which commands are in which software versions ....................................... 196
11.2 Table to show which responses are in which software versions ........................................ 199
12 APPENDIX 2: DUMMY OPTA.............................................................................200

MOD-14-1758
1 INTRODUCTION
This document is intended for use by developers of applications utilising the Peripheral Equipment
Interface (PEI) of Sepura TETRA Terminals.
Sepura TETRA Terminals (Hand-held, Mobile and Gateway) share a common PEI AT command
interface.
Sepura TETRA hand-held, mobile and gateway products additionally support an optional internal GPS
module that provides over-the-air position reporting and interrogation allowing remote control from
another TETRA terminal or dispatcher.
The commands for controlling the GPS Products via SDS messaging are described in reference [7].

MOD-14-1758
2 PHYSICAL INTERFACE DETAILS
2.1 Hand-Held
The Facility Connector provides an RS232 interface for external data connection and product testing.
SRH Series Front of radio
PIN 14
PIN 26
PIN 13 PIN 1
View looking at base of radio
STP Series
Front of product on this side
S1…..
…..S16
P1
P2
Facility Socket Pin-Out – view looking at socket
The Facility plug internal metal screening parts should be connected to a drain wire at the
crimp point which contacts a foil wrapped screen over all the cable wires
When the Sepura data cable supplied is connected to the hand-held terminal the user has the use of one
serial port to connect an external application or device to the terminal.
.
The port is mapped onto by Logical Port 1 and can be used in the following configurations:
 One Hayes AT Packet Data session can be active.

 One Hayes AT Circuit Mode application can be active.
This will allow, for example, an external GPS device to be connected to the serial port which may also be
used to download software or customisation to the terminal.

MOD-14-1758
Where there are limitations on the port usage for a particular command, this will be referenced in the
section detailing that command.

MOD-14-1758
2.1.1 Signal Lists
SRH Series
Pin
Signal Name I/O Description Performance
Number
(1)
1 USC_0 I/O Universal Serial I/O 3V Logic
(1)
(1)
(1)
(1)
(1)
(1)
General purpose I/O

11 GPIO_0 I/O 3V Logic
line
18 POWER_OUT I/O Supply out Battery voltage output.
Max guaranteed current supply is 350mA. Internal

polyfuse will open circuit at a current above this.
Actual fusing current is dependent on ambient
temperature.
20 PWR_OFF I External On-Off control 3V Logic, active low, pulled up internally with 47k
for the radio resistor.
22 GND - Main Ground return Max 0.5A per contact
23 GPIO_3 I/O General purpose I/O 3V Logic

line and secondary
serial data
25 GPIO_1 I/O General purpose I/O 3V Logic

line and secondary
serial data

MOD-14-1758
STP Series
Pin
Signal Name I/O Description Performance
Number
S1 FAC_LINE_IN I Audio line Input Reserved for car kit
S2 FAC_LINE_OUT O Audio line output Reserved for car kit
S3 LINE_GND Audio ground
(1)
S4 USC_0 I/O Universal Serial I/O 3V Logic
(1)
(1)
(1)
(1)
(1)
(1)
S11 Reserved I/O Do not connect
S13 Reserved I Do not connect
S14 GND
Power out when radio

S16 FAC_POWER_OUT O
on
P1 CHARGER_IN I Charge voltage
P2 CHARGER_GND Charge ground
(1)
Pins named USC_n are designated the ‘Universal Serial Connections’, which supports
various serial buses shown in the following sections. Details of the various USC formats
are given in [2]
2.1.2 Connectivity Options
2.1.2.1 Supported Connectivity Options
These connectivity options show signal function allocation for different supported accessory types. Table
entries marked ‘X’ are used as specified in section 0 otherwise signal function is as described in the table
below.

MOD-14-1758
SRH Series
Signal Name Data Lead - Primary RS232 (Hayes mode)
POWER_OUT X
USC_0 DSR (Output) Set Low Not used
(1)
USC_1 TXD (Input)
(1)
USC_2 RXD (Output)
USC_3 RI (Output) Set High Not used
(1)
USC_4 CTS (Output)
(1)
USC_5 RTS (Input)
(1)
USC_6 DTR (Input)
(1)
GPIO_0 DCD (Output)
GPIO_1 RXD2 (Input) Not Used
GPIO_3 TXD2 (Output) Not Used
GND X
(2)
Screening X
STP Series
Signal Name Data Lead - Primary RS232 (Hayes mode)
FAC_POWER_OUT FAC_POWER_OUT
(1)
USC_0 DCD (Output)
(1)
USC_1 TXD (Input)
(1)
USC_2 RXD (Output)
(1)
USC_3 DTR (Input)
(1)
USC_4 RTS (Input)
(1)
USC_5 CTS (Output)
USC_6 X
GND X
(2)
Screening X
(1)
RS232 control signals are inverted at the radio facility connector and should be inverted
with an external buffer to achieve the correct sense required for the RS232 specification

MOD-14-1758
(2)
The screening reference point on the Radio end of the cable is the metal shrouding
within the facility plug
2.1.2.2 Universal Serial Connection (USC) Pins - Function Selection
This section describes how the different communication formats for the USC are selected.
Default USC functionality is Primary RS232 – Hayes mode.
The details of this message are covered in an associated Security document.
All USC functions are selected by a Hayes message over Primary RS232.
2.1.2.3 Accessory Identifier (ACC_ID)
The following resistors identify type of accessory connected to the facility socket of the radio. The resistor
should be connected between ACC_ID and GND and have a tolerance of 2%.
Accessory Function Value of ACC_ID Available functions

Resistor
Data Lead Anything but short USC is Primary RS232 in Hayes mode
circuit
2.2 Mobile and Gateway
The interface connector is a 15-way high-density female D-type socket located on the lower edge of the
Console or Applications Interface Unit (AIU) case. Mobile and Gateway products may be connected to
none, one or two Consoles, AIUs or to one of each. A data connection can be made to one, or both of
these interfaces (if this facility is provided on the model used). Interconnection directly to one of the
Console Interface Connectors on the transceiver body is also possible. The Data connections are the
same. A 15-way high-density D-type male to 9 way D-type female serial cable is available from Sepura,
Part Number 300-00065.
55 4 3 2 1
10 9 8 7 6
15 14 13 12 11
9
View looking at connector on the outside of the Transceiver, Console or AIU

MOD-14-1758
The electrical interface is as follows:
Transceiver
Pin No. Signal Name Signal Direction Signal Function Signal
(15 way HD Characteristics
D type)
Output from
9 RS232_DCD RS232 levels
control subsystem
Output from
10 RS232_RXD RS232 levels
control subsystem
Input to control
11 RS232_TXD RS232 levels
subsystem
Input to control Hardware flow
12 RS232_RTS RS232 levels
subsystem control
Output from Hardware flow
13 RS232_CTS RS232 levels
control subsystem control
Input to control Data terminal
14 RS232_DTR RS232 levels
subsystem ready
Power Ground
15 GND - and return for -
digital paths.
Over-all cable Connect to digital
metal shell Screen -
screen GND

MOD-14-1758
2.3 Serial Protocol
Serial data transmission between the radio and Terminal Equipment devices operate with the following
parameters.
Parameter Setting
Mode Asynchronous
Rate (bps) 38400, 19200, 9600, 4800
Start Bits 1
Data Bits 8
Stop Bits 1
Parity None
HW Flow Control Not used in command mode.
The radio only uses hardware flow control when in transparent mode i.e. whilst on-line in
a circuit mode data call. It does not use hardware flow control when in command mode -
i.e. whilst off-line
Some older software versions required Hardware Flow Control for command mode
operation, hence it is recommended to always use a 9 way serial cable.
Command mode communications should not be attempted prior to

either:

Sending 'AT' and receiving an 'OK' in response or

CTS being asserted.
Doing so can render the terminal inoperable and require it to be re-
programmed (Radio Manager).
Transmit Sequence Least Significant Bit first
The baud rate at switch-on is controlled by a customization parameter.

MOD-14-1758
2.4 Dual Serial port
Dual serial port capabilities are provided on the mobile terminals (SRM models), this provides the user
with the opportunity to connect more than one external application or device to the terminal, or alternately
have one application utilising both ports.
The mobile terminal has two independent serial ports. This enables the connection of two devices, both
running different applications, a Hayes AT, Packet Data or Circuit Mode (Voice, SDS and Status)
application. In general, the port which supports Hayes AT is the first serial port and Logical Port 1 is
mapped onto it. The port which supports Packet Data is the second serial port and Logical Port 2 is
mapped onto it. It is possible to configure the mobile terminal so that the usage of the ports is reversed so
that Logical Port 1 is mapped onto Serial Port 2 and Logical Port 2 is mapped onto Serial Port 1.
The ports can be used in the following configurations:
 One Hayes AT Packet Data session can be active.

 One Hayes AT Circuit Mode application can be active.
 One Hayes AT Packet Data application and one Hayes Circuit Mode application can be active.
This will allow, for example, an external GPS device to be connected to one serial port and the user to
connect their mobile data Terminal to the other port.
Either serial port can be used to download software or customisation to the terminal but while this is
occurring, the other port is automatically disabled.
Where there are limitations on the port usage for a particular command, this will be referenced in the
section detailing that command.
2.5 Bluetooth® functionality

®
The STP8000 or STP8100 with optional Bluetooth module allows a data device, typically a PC or PDA, to
®
send and receive data to and from the STP8000/8100 with optional Bluetooth module wirelessly instead
of via a wired connection to the physical serial port on the Facility Connector.
® ®
The STP8000 or STP8100 with optional Bluetooth module supports the Bluetooth Serial Port Profile
(SPP) which allows applications to remotely control the terminal wirelessly using the same AT command
set as is available on the physical serial port in the AT command state.
® ®
The STP8000 or STP8100 with optional Bluetooth module supports the Bluetooth Dial Up Networking
profile (DUN), which allows applications to send and receive packet data via a wireless connection to the
®
STP8000/8100 with optional Bluetooth module as is available on the physical serial port in the online
data state.
®
The STP8000 or STP8100 with optional Bluetooth module also allows applications to send and receive
packet data using the Serial Port Profile (SPP), switching between AT command state and online data
state as is currently available on the physical serial port.
®
Only one Bluetooth data device may connect to the terminal at one time. The connected data device will
®
have access to either the SPP or the DUN (if customised as available) and only one Bluetooth data
service may be used at a time. If two services are customised the one which is not being used will
automatically be disabled until the service being used is released, at which time the disabled service will
again be active (if customised) and available for use by the external device.
The number and profile of the services are dependent on the configuration applying to the logical port
mapping:

MOD-14-1758
 If set to Normal (AT on first physical port) both SPP and DUN services are available and are both
mapped to Logical Port 2
 If set to Swapped (PD on first physical port) only SPP is available and is mapped to Logical Port
1.
2.6 USB functionality
Serial port functionality, as described above, is supported through the VAC Port on a connected SCC.
Using USB functionality disconnects and replaces the Serial port on that console. Support of USB
functionality requires that specific Sepura drivers are installed.
2.7 Connector Protector
The Connector Protector feature allows a radio to be used in a saltwater environment or an area with high
humidity (e.g.mist / fog) without fear of corrosion to the connectors. To achieve this level of protection the
Facility Connector disables some pins, in particular those used for communications.
When Connector Protector is working the radio cannot be programmed or controlled by AT

commands.
For products that support Connector Protector, and when Connector Protector is enabled, the following
applies:
 Protection is turned on a customisable time delay after the product is switched on if during that
time delay:
o No activity is detected on the serial port;
o Charging is not detected.
 Protection is turned on a customisable time delay after the product is removed from charging if
during that time delay:
o No activity is detected on the serial port.
Connector Protector may be enabled and disabled by User Profiles, by Settings Card and by Soft Keys.
Connector Protector is indicated by the following icons:
Connector Protector working.
Connector Protector not working due to detected serial port activity or charging

MOD-14-1758
3 PEI AT COMMAND INTERFACE COMMAND SYNTAX

The terminal defaults to AT Command Mode at switch-on. If a PIN is required to access the radio, this
must have been successfully entered before AT Command Mode is fully active. In this mode, commands
sent from the application to the PEI of the terminal should always start with a two character AT prefix, in
upper or lower case, however the ‘A’ and the ‘T’ must always be of the same case.
*
Every command should be terminated with a <CR> (Carriage Return – ASCII code 13) character .
*
The terminal will also accept and ignore the <LF> (Line Feed – ASCII code 10) character
following a <CR> but this is not required
Concatenated commands are not supported
The general format of commands and responses are as defined in [5].In Execute and Set commands, any
parameter may be omitted. When a parameter is omitted, it will take the default value as specified for each
command. Power-on defaults for some persistent parameters are listed under AT&F in section 7.1.67.
3.1 Command Mode Responses
In AT Command Mode, the terminal may generate one or more responses as a result of an AT command
received on the PEI or may generate an event driven indication to the application (e.g. incoming SDS
message or data call). The intermediate information responses generally follow the syntax
<COMMANDNAME>:<SPACE><TEXT><CR><LF>, optionally followed by additional <TEXT><CR><LF>.
Details are listed with each command in section 6. These responses, whether information text is present
or not, will be terminated by either <CR><LF>OK<CR><LF> or by an extended error response of the form
<CR><LF>+CME ERROR: nnn<CR><LF>, see section 7.3. Verbal responses are surrounded by a
<CR><LF> sequence*.
The general format of responses is as follows:
Response to an Execute or Set command

= <Final Response>
or <Information Response>
followed by <Final Response>
Response to a Read command

= <Information Response>
Response to a Test command

followed by <Final Response>
Unsolicited Response
<Information Response>
= <CommandName>:<space>Free text<cr><lf>
<Final response>
= <cr><lf>OK<cr><lf>
or <cr><lf>+CME ERROR:<space>nnn<cr><lf>
*Both the <CR> and <LF> line terminating characters may be substituted by any other ASCII characters in the range 0-127 by
modifying S-registers S3 and S4 respectively (See Sections 7.1.12 and 7.1.13 for further details).

MOD-14-1758
3.2 Transparent Data Mode
When a Circuit Mode Data call is successfully established via the ATD or ATA commands, the PEI will
switch from AT Command Mode to Transparent Data Mode. In Transparent Data Mode, the terminal
receives and sends free form binary data. Flow control is applied to the PEI as per ITU V.250 [5]. When
hardware flow control is used to control the flow from the radio to the external data application, the data
buffer in the radio is capable of storing a maximum of 2048 bytes. This corresponds to approximately 2
seconds for a 7.2kbit circuit mode channel. Data will be discarded when the buffer becomes full. Sepura
recommends that the external application should implement an end-to-end software flow control
mechanism if flow control beyond the capabilities of that buffer is required. When the Data call is cleared
down, the interface will return to AT Command Mode.

MOD-14-1758
4 PEI TEXT MESSAGING
There are several types of Data Messages and Data Call Types available to the application developer.
These include:
1. Status Messaging. This type of message transfer sends a number over the air, which
corresponds to a particular pre-programmed message in the TETRA Terminal’s
customisation.
2. Short Data Service Messaging. This type of Data Message transfers a short message of
typically up to 120 characters.
In order to ensure the correct transfer of data messages, the SDS standard includes a Transport Layer to
stipulate the exact formatting of messages. Termed SDS-TL, the Transport Layer sets the rules for
header information that must be prefixed to data messages so that duplicated messages are avoided, and
acknowledgement facilities are available when required.
Part of the SDS-TL scheme involves the use of message sequence numbers, which are allocated by the
sending radio and reported back to the sending application when the messages is transmitted over the air
interface. Using these sequence numbers, the receiving application is responsible for discarding duplicate
†
messages . Similarly, the sending application can request a delivery report (acknowledgement) when the
message is either received (e.g. by the data application) or consumed (e.g. read by the user) or both. It is
the responsibility of the receiving application (not the TETRA radio) to generate the delivery report, using
the sequence number from the original message.
There are 4 main ways you can use the Short Data Service:
1. SDS Application (for example a program running on a computer that is connected to the PEI of a
Terminal)  Terminal User Interface
2. SDS Application  SDS Application (both Applications are connected via the PEI of a Terminal)
3. Terminal User Interface  SDS Application
4. Terminal User Interface  Terminal User Interface
In the case of the SDS Application  SDS Application it is up to the application to

generate all the required acknowledgements and delivery reports where required. In this
instance, the Terminal does not control the required SDS-TL acknowledgements
All Sepura TETRA Terminals are capable of receiving simple and full SDS-TL messages.
It is dependent on the version of Terminal software and Infrastructure used. Please
contact your Sepura Representative if you are unsure
† Sepura radios will discard identical simple status or simple SDS messages received within a 10 second window received from
the same originating address. This does not apply to Full SDS-TL messages or to timestamped status messages due to the
message reference included with these SDS-TL types.

MOD-14-1758
4.1 Sending Status Messages
The AT+CMGS command, see 7.1.21, allows either a Status message or a Short Data message to be
sent from the PEI. The parameters for the sending of the message over the TETRA air interface are set up
using the command AT+CTSDS, see 7.1.57.
Called
end-to-
Set Data Message Parameters AI Party Access
Area end
Command Service Identity Priority
encryption
Type
AT+CTSDS= 13, 0 , 0 , 0 , 0
Send Message Data

Destination Identity
Command Length
AT+CMGS= dddddddd ,16 <cr><lf>

Status Number
hhhh <cntlZ>
Where:
 the Identity can be 1 to 8 digits in length (valid Individual or Group Identity)
 the Data Length is the number of bits of user data and is always 16 for a Status message
 the Status Number is exactly 4 ASCII Hexadecimal digits, valid range 0000 to FFFF.
 Status 0000 is Emergency and sent with Emergency Priority over the air, irrespective of the value of
Access Priority specified in the AT+CTSDS command.
The status values 1 to 32743 (7BFF Hex) are reserved by the TETRA standard, 31744 to
32767 (7C00 to 7FFF Hex) are for use by SDS-TL and 32768 to 65535 (8000 to FFFF
Hex) are available for TETRA network and user specific definitions
After sending a Status Message, some TETRA Infrastructures will send a Status Message
Acknowledgement. The most common Infrastructure status messages you might see are
in the table below
Status Meaning
FE00 Hex (65024) Status Message Delivered
FE01 Hex (65025) Status Negative Acknowledgement (Most likely the message has failed)
Please refer to your TETRA Infrastructure supplier for exact operation details of these status message
acknowledgements.

MOD-14-1758
4.2 Supported SDS Messages
Sepura TETRA Terminals support several different types of SDS-TL Message headers that are used for
different applications.
The following table provides a summary of the Protocol Identifiers (PIDs) supported internally by Sepura
terminals:
Protocol Application Comment

Identifier
2 Simple Text The simplest form of SDS text messaging. Full SDS-TL
functionality is disabled. There is no confirmation that any
message is delivered successfully. The OK back from the
radio indicates the message has been transmitted to the
Network.
3 Simple GPS As per Simple Text but specific to GPS messages only.
9 Immediate Text Display As per Simple Text but text displayed immediately
130 Complex SDS-TL Text Full SDS-TL Header that allows most flexibility in SDS
Transfer messages.
131 Complex SDS-TL GPS Full SDS-TL Header that allows most flexibility in SDS
Message Transfer messages used with GPS applications.
137 SDS TL Immediate Display Full SDS-TL Header
138 UDH Concatenated Text Full SDS-TL Header
Message
193 RUA (Radio User Full SDS-TL Header
Assignment)
200 Sepura Encapsulated Full SDS-TL Header
Messages
201 Performance Monitoring Full SDS-TL Header
The initial routing of SDS Messages is set at switch-on by a single customization parameter which directs
all PIDs to the same destination. Subsequently, the routing of SDS Messages is controlled on a PID by
PID basis, for each mode (Trunked, Direct, Repeater or Gateway), by the use of the +CTSP command,
see 7.1.58.
The exceptions to this rule are:
 when the PID is 3 or 131 and the SDS message has been sent from one of the customized “GPS
Identities” in which case the message will be routed to the internal GPS module within the radio
irrespective of the settings in the service profile;
 when the PID is 193 in which case the message is routed to the internal RUA application;
 when the PID is 201 in which case the message is routed to the internal Performance Monitoring
entity.
If an SDS message with a PID, which is not one of those in the table above, is routed to the Terminal (i.e.
radio) it will be rejected. If it has a PID which identifies a full SDS-TL header, then a “Protocol not
supported” report is returned.

MOD-14-1758
4.3 SDS-TL Message Encoding
SDS Messages may be sent and received using a ‘simple’ SDS-TL header which is one that uses a much-
abbreviated SDS-TL Header. There is no Protocol Header (compare this to a full SDS-TL message),
which leaves just the Protocol Identifier and the encoding scheme. As a result, full transport layer features
such as duplicate message elimination and message acknowledgements are not possible. When using
the ‘Standard PEI’ protocol on the PEI interface, these ‘simple’ messages are sent and received in exactly
the same way as the messages with full SDS-TL headers. The SDS-TL header and data is presented at
the PEI as a single string of hexadecimal characters. It is the responsibility of the data application to
encode/decode the PID and all other parameters and to identify whether a full SDS-TL header is present.
The parameters for the sending of the message over the TETRA air interface are set up using the
command AT+CTSDS, see 7.1.57. The send format for an SDS message is as follows:
Called end-to-
Set Data Message Parameters AI Party Access end
Area
Command Service Identity Priority encrypt-
Type ion
AT+CTSDS= 12 , 0 , 0 , 0 , 0
Send Message Data
Command Length
AT+CMGS= dddddddd ,nnn<cr><lf>

User Data
hhhh...hhhh <cntlZ>
Where:
 the Identity can be 1 to 8 digits in length (for an Individual or Group Short Identity)
 the Data Length is the number of bits of user data expressed as a decimal number including the SDS-
TL header
 the User Data may be up to 2047 bits, expressed as ASCII Hexadecimal digits. This includes the
SDS-TL Header information.
There are restrictions on the length under some circumstances, see 8, and that some
SwMIs impose a maximum length that can be supported
4.3.1 The Importance of the SDS-TL Header
The SDS-TL header controls several aspects of messaging. This includes:

 The type of SDS message you are sending
 Delivery Report support
 Service Selection (Individual or Group Message)
 If the network supports it, allow this message to be stored
 The message reference number
 The Text Character Set (for Text Messages) or the GPS Coding Scheme (for GPS
messages).
4.3.2 Message numbering
Message numbering allows an application to discard repeated message deliveries, which can arise due to
the nature of the transmission process. Such duplications can occur due to link errors, but it may also

MOD-14-1758
happen due to normal operation for a group-addressed message. Without message reference numbers, it
is not possible (either in the radio terminal or in the application) to distinguish between two identical
messages and the same message being sent twice. Message numbers range from 0 to 255, and these
are calculated by the radio terminal for outgoing SDS messages. An external data application which is
sending an SDS message with a full SDS-TL header, should set the Message Reference field of the
header to 255 (FF Hex) and will be advised, in the PEI response, of the actual message number used
over the air interface.
4.3.3 End-to-end acknowledgement
In certain cases it may be important to check that a particular message has been received and understood
by a TETRA Terminal. This is especially so for commands that do not elicit an immediate response. By
setting a certain field in the SDS-TL header, the receiving station(s) can be made to automatically respond
to the sent message. This response may be triggered on receipt of the message or when it is “consumed”
(e.g. read by the user). Any incoming end-to-end acknowledgment messages are routed to the application
that requested the acknowledgement, as identified using the Message Number. (i.e. a delivery report or a
consumption report is routed to the application that generated the original SDS; a report
acknowledgement is routed to the application that had received the original SDS and generated the
delivery or consumption report.)
It is advised that the Delivery Report Requested flag is NOT set when sending a message
to a group. You may need to seek permission from your Network Operator if you wish to
use this feature as it is possible you will get Delivery Reports from every user attached to
the Group.
Similarly the requesting of Delivery Reports is not advised for an SDS Message
addressed to a Gateway when that Gateway may be relaying SDS Messages to a DMO
group address.
When sending a message on the uplink, this field represents the Service Selection
(Individual or Group Identity). For received downlink messages, this field indicates
whether a Short Form Report (in the form of a status message) is an acceptable
response.

MOD-14-1758
4.4 SDS-TL Short-form Delivery Report
An SDS-TL report message is one which contains no user-defined data, but merely exists to support
message delivery reporting. It is sent in response to an SDS-TL transfer message.
A subset of 16-bit Status messages has been reserved for SDS-TL Report messages. These have the
advantage of brevity – the message is 16 bits long instead of the long-form report’s 32 bit SDS-TL header.
However, short-form delivery reports cannot be requested by the originating application – this is a function
of the TETRA Infrastructure.
The four base values for Short Delivery Report Status Messages are:
Status Meaning
7C00 Not Delivered (Protocol or encoding not supported)
7D00 Memory Full
7E00 Message Delivered OK
Message Consumed (e.g. the user has read the message on the User Interface of
7F00
the Terminal)
To generate a Short Delivery Report Status value, take a base Status value from the list above and ADD
the SDS-TL Message Reference Number.
For example:
If an application has received the SDS message number 123 as per the previous example, add the
Message Number to the Message Delivered OK Status to generate the Short Delivery Report Status to
send back.
7B + 7E00 = 7E7B
This is sent as a Status Message to the originator of the SDS-TL message, see 4.1 above.
For the complete list of SDS-TL Delivery Report codes, refer to [2] Clause 29, SDS-TL service and
protocol.
If a message is sent to a Group requesting a Delivery Report, a Short Delivery Report Status may be
received from every radio attached to that talkgroup.

MOD-14-1758
4.5 SDS-TL Report
An SDS-TL report message contains no user-defined data, but merely exists to support message delivery
reporting. It is sent in response to an SDS-TL transfer when the Delivery Report field is set to ’1’, ‘2’ or ‘3’.
The send format for an SDS-TL report message is as follows:
Called end-to-
Set Data Message Parameters AI Party Access end
Area
Command Service Identity Priority encrypt-
Type ion
AT+CTSDS= 12 , 0 , 0 , 0 , 0
Send Message Data
Command Length
AT+CMGS= dddddddd ,nnn<cr><lf>

SDS-TL Header
hhhhhh <cntlZ>
Where:
 dddddddd, the Identity can be 1 to 8 digits in length and is the originator of the message that is being
acknowledged.
 nnn, the Data Length is the number of bits of user data expressed as a decimal number including the
SDS-TL header. For a full SDS-TL report message without a storage request it will always be 32 bits.
 hhhhhh, the SDS-TL header is expressed as ASCII Hexadecimal digits. The content of this part of the
message are assembled according to [2] Clause 29.
Usually, Short Delivery Report Status Messages are used by an Application to generate a Delivery Report.
It is more common, however, for the TETRA Infrastructure to generate an SDS-TL Delivery Report if there
is a network problem or, for example, the subscriber has their radio turned off.
For the complete list of SDS-TL Delivery Status codes, refer to [2] Clause 29, SDS-TL service and
protocol.

MOD-14-1758
4.6 SDS-TL Compliance
 Storage in SDS-TL terms is not supported by the terminal. The software application to which Sepura
Products report should therefore not permit storage of its messages. The terminal does not store
messages for later transmission.
 Other SDS-TL fields (not documented here) such as forward address type, forward address short
number address, forward address SSI, forward address extension are not currently supported.
 The Sepura Products will not permit storage of position reports.
 The Sepura Products will honour received messages with requests for SDS-TL report where
appropriate.

MOD-14-1758
4.7 Restrictions
4.7.1 SDS Message Size
There are restrictions regarding the maximum message size that can be transmitted based upon the
current state of the Terminal. Please refer to the table in Section 8 for greater explanation.
Please check with your local TETRA Network supplier to confirm the maximum message capacity
available.
4.7.2 Group Calls
While a radio is receiving speech during a group call, it must route all signalling information (such as
transmit requests) via Frame 18. Transmission of SDS messages during this time will be restricted by the
capabilities of the infrastructure (see Section 8). The Sepura terminal will always attempt to send the
message.
4.7.3 Multiple Messages
It is important to avoid overloading the network and radio by issuing multiple requests for data
transmission. For example, a request for an immediate position report should not be sent with a request
for delivery confirmation. Delivery reports should NOT be requested when sending group addressed
messages or when sending SDS Messages addressed to a gateway when that gateway may be relaying
the message to a DMO group address.

MOD-14-1758
4.8 Short Data and Status Message Examples
4.8.1 Status message transmission example
The following example demonstrates how to send a Status Message of number 33000 to SSI address
12345678:
AT+CTSDS=13,0,0,0,0<CR><LF>
<CR><LF>
OK<CR><LF>
AT+CMGS=12345678,16<CR><LF>
80E8<cntlZ>
<CR><LF>
OK<CR><LF>
4.8.2 Status message reception example
The following example shows the behaviour when the Status Message of example 4.8.1 is delivered.
When a Status Message of number 33000 is received by terminal (SSI=12345678) from another terminal
(SSI=11111111), it is presented at the PEI as follows:
<CR><LF>
+CTSDSR: 13,11111111,0,12345678,0,16<CR><LF>
80E8<CR><LF>
4.8.3 Simple SDS-TL protocol transmission example
The following example demonstrates how to send a SDS Message of “Hello” using the simple text PID to
SSI address 12345678:
<CR><LF>
OK<CR><LF>
AT+CMGS=12345678,56<CR><LF>
020148656C6C6F<cntlZ>
<CR><LF>
OK<CR><LF>

MOD-14-1758
The user data in this message is constructed as follows:

02 = PID (2 decimal)
01 = Latin-1 alphabet
48 = ‘H’
65 = ‘e’
6C = ‘l’
6C = ‘l’
6F = ‘o’
<cntlZ> terminates the user data
4.8.4 Full SDS TL protocol transmission example
The following example demonstrates how to send a SDS Message of “Hello” using the Full SDS-TL text
PID to SSI address 12345678 including a request for both delivery and consumption reports:
<CR><LF>
OK<CR><LF>
AT+CMGS=12345678,72<CR><LF>
8204FF0148656C6C6F<cntlZ>
<CR><LF>
OK<CR><LF>

0 = Message Type (SDS-TRANSFER)
4 = 0100 binary. The first bit does not request a consumption report; the second bit requests a
delivery report, the third bit indicates an individual destination address; the fourth bit does
not request storage in the SwMI
FF = The message reference number, the value here is not used and is changed by the sending
Radio Terminal
01 = No timestamp (only ever added by a SwMI) and text is coded with Latin-1 alphabet
48 = ‘H’
65 = ‘e’
6C = ‘l’
6C = ‘l’
6F = ‘o’
In the case that storage is requested in the SwMI (Store and Forward) the appropriate bit is set and the
extra addressing information is included. As an example the following message is sent to the Store and
Forward Service Centre (SSI address 11223344), to be forwarded to an SSI of 12345678 and deleted if
not delivered within an hour:
AT+CMGS=11223344,104<CR><LF>
8205FF81BC614E0148656C6C6F<cntlZ>
<CR><LF>
OK<CR><LF>


MOD-14-1758
5 = 0101 binary. The first bit does not request a consumption report; the second bit requests a
delivery report, the third bit indicates an individual destination address; the fourth bit
requests storage in the SwMI
FF = The message reference number, the value here is not used and is changed by the sending
Radio Terminal
81 = 10000 binary. This set of bits indicates a validity period for the message, in this case 1 hour.
Followed by
001 binary. This set of bits indicates the forward address type, in this case an SSI.
BC614E = The address to which the message is to be forwarded, in this case the hex equivalent
of '12345678'. Note that this segment of the message must be of the required length (three
bytes for an SSI) even if zeros need to be added.
01 = No timestamp (only ever added by a SwMI) and text is coded with Latin-1 alphabet
48 = ‘H’
65 = ‘e’
6C = ‘l’
6C = ‘l’
6F = ‘o’
Note that similar rules will apply to received forwarded messages that have their 'storage' bit set.
4.8.5 Incoming full SDS-TL protocol example
Using the second example above (full SDS-TL text message), when an SDS-TL transfer message is
received by the terminal, it will be presented at the PEI as follows:
<CR><LF>
+CTSDSR: 12,11111111,0,12345678,0,72<CR><LF>
82047B0148656C6C6F<CR><LF>
In this example:
the sending terminal has an SSI of 11111111 (with type indicator set to '0';
the sending terminal has allocated a message reference number of 123 (7B Hex);
the SwMI has not added a timestamp;
the SwMI recommends a short-form report.
Following the reception of this message, which has requested a delivery report, the external data
application should send either a short-form report or a full SDS-TL Report, using the message reference
number from the incoming message.
Note that the addresses may be reported as TSI and TSI indicator e.g. '123123412345678,1', see 7.2.23
4.8.6 Sending a Delivery Report Example
This example shows the message sent back to the originator by the receiving data application when it has
received the message in the second example above. This message is sent if the data application wishes
to send a full report. For an example of the corresponding short report, see 4.8.7 below.
<CR><LF>
OK<CR><LF>
AT+CMGS=11111111,32<CR><LF>
8210007B<cntlZ>

MOD-14-1758
<CR><LF>
OK<CR><LF>

0 = 0000 binary. The first bit does not request an acknowledgement; the second and third bits
are required to be fixed at 0; the fourth bit does not request storage in the SwMI
00 = Receipt Acknowledgement
7B = The message reference number
4.8.7 Sending a Delivery Short Report Example
This example shows the message sent back to the originator by the receiving data application when it has
received the message in the second example above. This message is sent if the data application wishes
to send a short report. For an example of the corresponding full report, see 4.8.6 above.
<CR><LF>
OK<CR><LF>
AT+CMGS=12345678,16<CR><LF>
7E7B<cntlZ>
<CR><LF>
OK<CR><LF>

7E = Receipt Acknowledgement
7B = The message reference number
4.8.8 SDS Message Routing
AT+CTSP controls the routing of incoming SDS message. It can also control the routing of signalling for
voice and circuit mode data calls. The routing from switch-on is controlled by customization parameters.
The default settings for these parameters is to route all (with some specific exceptions such as delivery
reports and GPS control messages) incoming SDS, Status and voice calls to the terminal's user interface,
and all data calls to the PEI. The command AT+CTSP can be used to change the routing for any one of
these message types. When the routing for SDS is changed by AT+CTSP, the specified routing only
applies to the PID specified in the command and to the current operating mode (Trunked, Direct, Repeater
or Gateway).
Assuming that we start with the default initial settings and are working in Trunked Mode...
All voice calls are indicated on the display and alerting device of the radio
All Status messages (except some special values) are indicated on the display of the terminal
All SDS messages with a text PID are indicated on the display of the terminal
All SDS messages with a GPS PID and a GPS Source address are processed by the GPS module (if
present)

MOD-14-1758
All other SDS PIDs are discarded.
All data calls are reported to the PEI for the external data application to process. If the data application
needs to receive the signalling for voice calls so that it can control these, it will need to issue a command
to change the routing:
AT+CTSP=1,0,0
These parameter values mean: "TE Only", "Call Control", "Voice". If the data application needs to receive
SDS-TL messages with a PID of 130 it will need to issue a command to change the routing:
AT+CTSP=1,3,130
These parameter values mean: "TE Only", "SDS-TL", "not used", "PID=130". SDS messages with other
PIDs will continue to be routed to the radio, where they will be processed or discarded. Similarly, if the
data application needs to receive SDS-TL messages with a PID of 207, it will need to issue a command to
change the routing:
AT+CTSP=1,3,207
If the data application needs to give the display of all future SDS-TL messages with a PID of 130 back to
the terminal's display it will need to issue a command to change the routing:
AT+CTSP=0,3,130
These parameter values mean: "MT Only", "SDS-TL", "not used", "PID=130". To check the current routing,
the data application may issue a read command:
AT+CTSP?
A typical response would be:

+CTSP: 1,0,0, 0,3,46, 0,3,97, 0,3,148, 0,3,199, 0,3,250,
1,0,1, 0,3,47, 0,3,98, 0,3,149, 0,3,200, 0,3,251,
0,1,10, 0,3,48, 0,3,99, 0,3,150, 0,3,201, 0,3,252,
0,1,11, 0,3,49, 0,3,100, 0,3,151, 0,3,202, 0,3,253,
0,2,20, 0,3,50, 0,3,101, 0,3,152, 0,3,203, 0,3,254,
0,3,0, 0,3,51, 0,3,102, 0,3,153, 0,3,204, 0,3,255
0,3,1, 0,3,52, 0,3,103, 0,3,154, 0,3,205,
0,3,2, 0,3,53, 0,3,104, 0,3,155, 0,3,206,
0,3,3, 0,3,54, 0,3,105, 0,3,156, 1,3,207,
0,3,4, 0,3,55, 0,3,106, 0,3,157, 0,3,208,
0,3,5, 0,3,56, 0,3,107, 0,3,158, 0,3,209,
0,3,6, 0,3,57, 0,3,108, 0,3,159, 0,3,210,
0,3,7, 0,3,58, 0,3,109, 0,3,160, 0,3,211,
0,3,8, 0,3,59, 0,3,110, 0,3,161, 0,3,212,
0,3,9, 0,3,60, 0,3,111, 0,3,162, 0,3,213,
0,3,10, 0,3,61, 0,3,112, 0,3,163, 0,3,214,
0,3,11, 0,3,62, 0,3,113, 0,3,164, 0,3,215,
0,3,12, 0,3,63, 0,3,114, 0,3,165, 0,3,216,
0,3,13, 0,3,64, 0,3,115, 0,3,166, 0,3,217,
0,3,14, 0,3,65, 0,3,116, 0,3,167, 0,3,218,
0,3,15, 0,3,66, 0,3,117, 0,3,168, 0,3,219,
0,3,16, 0,3,67, 0,3,118, 0,3,169, 0,3,220,
0,3,17, 0,3,68, 0,3,119, 0,3,170, 0,3,221,
0,3,18, 0,3,69, 0,3,120, 0,3,171, 0,3,222,
0,3,19, 0,3,70, 0,3,121, 0,3,172, 0,3,223,
0,3,20, 0,3,71, 0,3,122, 0,3,173, 0,3,224,

MOD-14-1758
0,3,21, 0,3,72, 0,3,123, 0,3,174, 0,3,225,

0,3,22, 0,3,73, 0,3,124, 0,3,175, 0,3,226,
0,3,23, 0,3,74, 0,3,125, 0,3,176, 0,3,227,
0,3,24, 0,3,75, 0,3,126, 0,3,177, 0,3,228,
0,3,25, 0,3,76, 0,3,127, 0,3,178, 0,3,229,
0,3,26, 0,3,77, 0,3,128, 0,3,179, 0,3,230,
0,3,27, 0,3,78, 0,3,129, 0,3,180, 0,3,231,
0,3,28, 0,3,79, 0,3,130, 0,3,181, 0,3,232,
0,3,29, 0,3,80, 0,3,131, 0,3,182, 0,3,233,
0,3,30, 0,3,81, 0,3,132, 0,3,183, 0,3,234,
0,3,31, 0,3,82, 0,3,133, 0,3,184, 0,3,235,
0,3,32, 0,3,83, 0,3,134, 0,3,185, 0,3,236,
0,3,33, 0,3,84, 0,3,135, 0,3,186, 0,3,237,
0,3,34, 0,3,85, 0,3,136, 0,3,187, 0,3,238,
0,3,35, 0,3,86, 0,3,137, 0,3,188, 0,3,239,
0,3,36, 0,3,87, 0,3,138, 0,3,189, 0,3,240,
0,3,37, 0,3,88, 0,3,139, 0,3,190, 0,3,241,
0,3,38, 0,3,89, 0,3,140, 0,3,191, 0,3,242,
0,3,39, 0,3,90, 0,3,141, 0,3,192, 0,3,243,
0,3,40, 0,3,91, 0,3,142, 0,3,193, 0,3,244,
0,3,41, 0,3,92, 0,3,143, 0,3,194, 0,3,245,
0,3,42, 0,3,93, 0,3,144, 0,3,195, 0,3,246,
0,3,43, 0,3,94, 0,3,145, 0,3,196, 0,3,247,
0,3,44, 0,3,95, 0,3,146, 0,3,197, 0,3,248,
0,3,45, 0,3,96, 0,3,147, 0,3,198, 0,3,249,
Routing is not remembered when the radio is switched off, and will revert to the
customized initial routing at switch-on.
There are two different routing values for voice calls; one for Trunked Mode and another
one for Direct mode.
MT means "Mobile Termination" and is the Tetra Radio
TE means "Terminal Equipment" and is the equipment connected to the PEI (sometimes
known as a Mobile Data Terminal or MDT)

MOD-14-1758
5 PEI CIRCUIT MODE CALLS
5.1 Circuit-mode Voice Calls
The Sepura products support the following call types.

 full-duplex individual voice calls with hook signalling (not available in DMO)
 half-duplex individual voice calls with hook signalling (not available in DMO)
 half-duplex group voice calls with direct setup
5.1.1 Preparation
Before making or receiving any voice call under the control of a data application, the signalling needs to
be routed to the data application. The initial setting of this routing is customized in the radio. Subsequently
it may be changed using the AT+CTSP command, see 7.1.58.
Before making or receiving a group call, the data application additionally needs to:
 Determine the groups configured in the terminal using the AT+CNUM command, see 7.1.24
 Attach to one or more of those groups using the AT+CTGS, see 7.1.55.
 In order to make an outgoing group call, one group should be attached with a <group type> of
‘Select’; additional groups attached with other group types are optional.
5.1.2 Setup
In order to set up a voice call, the data application needs to set the parameters for the call using
AT+CTSDC, see 7.1.56. Parameters appropriate for TMO voice calls are:
AT+CTSDC=0,0,0,1,1,0,1,1 (group call)

AT+CTSDC=0,0,0,0,0,0,0,1 (duplex call to another Tetra identity)
AT+CTSDC=0,0,0,0,1,0,0,1 (half-duplex call to another individual Tetra identity)
AT+CTSDC=0,3,0,0,0,0,0,1 (duplex call to a PABX identity)
AT+CTSDC=0,4,0,0,0,0,0,1 (duplex call to a PSTN identity)
Note that these settings are for TMO. For DMO some parameters may not be valid, e.g. the fourth
parameter must be a '1' as the hook type in DMO is 'direct'. See 7.1.56 for restrictions.
The gateway addresses for PABX and PSTN calls are customized in the terminal and cannot be changed
from a Data Application via the PEI.
After setting the parameters for the call, the call is set up using the ATD command, see 7.1.3.
The unsolicited response +CTOCP indicates the progress of an outgoing call set-up see 7.2.22.
5.1.3 Reception and Connection
When an incoming speech call is received by the radio, it is routed to the radio’s user interface, or to the
PEI as determined by the Service Profile routing. There is no notification to the PEI for any call which is
routed to the radio’s user interface. For calls which are routed to the Data Application via the PEI, an
unsolicited report +CTICN, see 7.2.21, is sent to the PEI to indicate an incoming call and all its
parameters. If it is a hooking call, it should be answered using an ATA command, see 7.1.2. The issuing of
the ATA is also treated as a request to transmit for a half-duplex call. If the external data application does
not require transmit permission the ATA should be followed by a AT+CUTXC command, see 7.1.61. A
direct setup call does not require any PEI signalling for it to be answered.

MOD-14-1758
5.1.4 Transmission control in a half-duplex call
During a half-duplex voice call which has been initiated from, or routed to, the external data application,
transmissions are controlled using the following commands:
AT+CTXD Transmission Demand, see 7.1.59
AT+CUTXC Transmission Ceased (uplink, i.e. this radio), see 7.1.61
and the following responses:
+CTXG Transmission Grant Status, see 7.2.24
+CDTXC Transmission Ceased (downlink, i.e. another radio), see 0
+CTXI Transmission Interrupt, see 7.2.25
+CTXW Transmission Wait, see 7.2.27
+CTXN Transmission Continue, see 7.2.26
5.1.5 Call Termination
A voice call which has been initiated from, or routed to, the external data application, may be terminated
by the SwMI or by the remote terminal, in which case this will be reported to the external application using
a +CTCR response, see 7.2.19.
A voice call which has been initiated from, or routed to, the external data application, may also be
terminated by the local Data Application sending an ATH command, see 7.1.5.

MOD-14-1758
5.1.6 Control of Audio Routing for Mobile and Gateway
For voice calls, Mobiles and Gateways may be fitted with one console, two consoles, one Accessory
Interface Unit (AIU), two AIUs or one AIU and one console. One console or one AIU will allow up to two
audio accessories to be attached. Two consoles, two AIUs or one of each will allow up to four audio
accessories to be attached. In addition to audio accessories attached via consoles and AIUs, there is an
optional loudspeaker attached directly to the transceiver. Use of SCC allows additional accessories
connected to the VAC Port.
When a voice call is initiated by the user interface on a console or is an incoming call routed to the user
interface, the audio accessory to be used (known as the “controlling accessory”) is the accessory which
has been taken off hook, or had its PTT pressed. If no accessory has been determined by this, a default
accessory is used initially.
When a voice call is initiated by commands from the PEI, or is an incoming call routed to the PEI, the
audio accessory to be used is determined according to the following rules which take into account the
customization parameter “Accessory Type on PEI”:
‡
 The audio accessory ports are checked in order for an accessory of the same type as “Accessory
Type on PEI”. The first matching accessory is the controlling accessory.
‡
 If no matching accessory has been found, the audio accessory ports are checked in the same order
for any audio accessory. The first audio accessory found is the controlling accessory.
 If the audio accessory found is a half-duplex accessory and the incoming call is not Direct Setup, its
PTT is initially treated as being pressed. The external application may terminate this transmission by
sending AT+CUTXC.
Once a call is in progress, any audio accessory with a PTT, or the external data application, may request
transmission in a half-duplex call, provided another accessory or the external data application has not
requested transmission, and has not yet terminated that request. When that transmission request is
accepted by the MS, the accessory associated with the request becomes the controlling accessory.
When a voice call is an incoming hooking setup call routed to the PEI and the audio accessory to be used
has been determined and it is a half-duplex accessory, it is treated as if its PTT has been pressed.
‡ The order of checking is Port 1 on console/AIU x; Port 2 on console/AIU x; VAC Port on console x; Port 1 on console/AIU y; Port
2 on console/AIU y; VAC Port on console y - where x is the console number (1 or 2) of the console that answered the call and y is
the console number (1 or 2) of the other console, i.e. accessory ports are checked on the console that answers the call first.

MOD-14-1758
5.1.7 Example of Message Flow for a Half-Duplex Voice Call
TE MT SwMI MT TE
Setup AT+CTSDC
OK
ATD
U-SETUP
D-CALL PROCEEDING
D-ALERT D-SETUP
+CTICN
[D-INFO] [D-INFO]
ATA
U-CONNECT
D-CONNECT D-CONNECT ACK D-CALL
+CTOCP +CTCC
+CTXG (another) +CTXG (grant)
OK OK
end Tx
AT+CUTXC
U-TX CEASED
OK
D-TX CEASED D-TX CEASED
+CDTXC
+CDTXC
2nd Tx
AT+CTXD
U-TX DEMAND
OK
D-TX GRANTED D-TX GRANTED
+CTXG (grant) +CTXG (another)
AT+CUTXC
U-TX CEASED
OK
D-TX CEASED D-TX CEASED
+CDTXC
+CDTXC
Clear ATH
U-DISCONNECT
D-RELEASE D-RELEASE
+CTCR +CTCR
OK
5.2 Circuit-mode Data Calls

The Sepura products support full-duplex individual circuit-mode data calls

MOD-14-1758
5.2.1 Preparation
Before making or receiving any data call, the signalling needs to be routed to the data application. The
initial setting of this routing following each power-on is customized in the radio. Subsequently it may be
changed using the AT+CTSP command, see 7.1.58.
5.2.2 Setup
In order to set up a data call, the data application needs to set the parameters for the call using
AT+CTSDC, see 7.1.56. Parameters appropriate for data calls are:
AT+CTSDC=1,0,0,0,0,0,0,0 (7.2kb/s unprotected duplex hooking individual call)

AT+CTSDC=2,0,0,0,0,0,0,0 (4.8kb/s low protection duplex hooking individual call)
AT+CTSDC=5,0,0,0,0,0,0,0 (2.4kb/s high protection duplex hooking individual call)
After setting the parameters for the call, the call is set up using the ATD command, see 7.1.3
5.2.3 Reception and Connection
When an incoming data call is received by the radio, it is routed to the radio’s user interface, or to the PEI
as determined by the Service Profile routing. A data call routed to the terminal’s user interface will be
rejected. For the normal configuration, calls which are routed to the Data Application via the PEI, an
unsolicited report +CTICN, see 7.2.21, is sent to the PEI to indicate an incoming call and all its
parameters. If it is a hooking call, it is should be answered using an ATA command, see 7.1.5.
5.2.4 Switching Between a Call and Command Mode
A circuit mode data call can be interrupted by the following sequence from the Data Application via the
PEI.
<1 second during which no data is sent>+++<1 second during which no data is sent>
The “+++” is sent on the circuit mode channel to the remote application. The call may also be interrupted
on products which support hardware flow control by removing the DTR signal. The local terminal is then
switched into command mode which allows any AT commands to be requested. Commands which are not
supported during a data call (such as setting up a new call) will be rejected with an error. Error messages
for each command are listed with the commands in section 7. Any data received from the circuit mode
channel while the local terminal is in command mode will be discarded.
5.2.5 Call Termination
A data call may be terminated by the SwMI or by the remote terminal, in which case this will be reported to
the external application using a +CTCR response, see 7.2.19.
A Data call may also be terminated by the local Data Application by switching into command mode, see
5.2.4, and then sending a ATH command, see 7.1.5.

MOD-14-1758
6 PEI PACKET DATA
6.1 Hayes AT command for Packet Data
The following summarises the AT command for Packet Data.
6.1.1 ATD - Dial
Description
Packet data is available on all hand-held and mobile products, it is not available on gateway products
when operating as a gateway.
While Hayes AT is the active serial protocol and it is in Command state, the reception of ATD*99# will
cause the radio to initiate the setup of the PPP link and contextually the activation of the PDP context.
Execution Syntax
ATD*<GPRS Service Code IP>#
The only allowed value for <GPRS Service Code IP> will be 99. Any other value will cause an error to be
returned.
Upon the reception of the command the radio will return CONNECT and will switch to PPP and the DCD
line will be asserted for the duration of the PD context activation (i.e. whilst the PEI is in online data state
with PPP protocol active). If the establishment of the PPP link fails, the radio will return No Carrier / No
Dial tone and will switch back to Hayes.
Example
ATD*99#
CONNECT
<PPP protocol>
6.1.2 Terminating the Session
The session can be terminated for several reasons:
By TE PPP Inactivity Timeout expires

The TE shuts down the PPP link by dropping DTR or Sending the Hayes escape sequence
By Radio The PDP context is deactivated

The radio is about to switch off or de-register
PDP context activation fails
PPP link setup fails
When the session is terminated, the radio will:

 drop the DCD (&C1)
 clear any ongoing Packet Data transfer
 deactivate the context
 return NO CARRIER
 revert to Hayes.

MOD-14-1758
6.1.3 Return Codes
Return Value Description

CONNECT Command accepted
ERROR Syntax error etc.
NO CARRIER / NO DIAL TONE Connection terminated or attempt failed
BUSY Service is already in use
6.2 IP Addresses (Static/Dynamic)
Static or dynamic operation is configured in the MS. If set to non-zero in the MS, this selects a static IP
address when connecting. If static IP addressing is selected then the remote end should be also
configured to be static with the same address for the connection to proceed.
6.3 Dialling from Windows and Linux
Below are some guidelines for setting up the connection from a windows and Linux environment, which
may be helpful.
6.3.1 Windows
1. Install a 9600 standard modem on the com: port you want to use.
2. Configure the modem to the baud rate for the PEI port of the terminal set in the programmer,
hardware handshaking, n81.
3. Open the accessories/Dial-Up Networking and set up a new connection.
4. Select the 9600 modem from above and click on ‘configure’.
5. Configure the modem to the baud rate set in step 2, hardware handshaking, n81.
6. Set Area Code blank, Set telephone number to *99#, ignore the Country.
7. When the connection is started, use a user name and password compatible with the SwMI.
6.3.2 Pocket PC
When using a device running Pocket PC, ensure that the action of the ATZ command is set to reset,
rather than reboot in the Sepura hand-held. This parameter is set using the Sepura programming tool.
6.3.3 Linux
1. PPP should be started with the following chat script:
pppd connect ‘chat –v “” ATDT*99# CONNECT’ /dev/cua0 38400 crtscts modem noipdefault defaultroute
mtu 576 :10.0.0.4
The trailing “:10.0.0.4” gives an address to the otherwise address-less link.
The ppp options file should contain the following (shown for the login “fred”):
ipcp-accept-local
ipcp-accept-remote
lock

MOD-14-1758
name fred
2. If authentication is enabled entries will need to be added to pap-secrets
Example:
fred * password
user * pass
(The second line may be necessary if the SwMI challenges the linux box). If chap is available then add
entries to chap-secrets.

MOD-14-1758
7 PEI AT COMMAND SET OVERVIEW
7.1 Commands
Unless stated otherwise STP9000 Series product share command differences with STP8000
7.1.1 A/ – Repeat Last Command
Description
This command repeats the last command.
Execution Syntax
A/
Note: a trailing <cr> is not required.

MOD-14-1758
7.1.2 ATA - Answer
Source
[5] 6.3.5
Description
Answer an incoming call.
This command is only supported on Logical Port 1
The product will behave as if a hooking accessory has been taken ‘off hook’ and, for a half-duplex call, a
PTT has been pressed. If transmission is not required this should be followed by a AT+CUTXC.
ATA on a port which has not been sent the +CTICN at this time will be equivalent to sending an ATA when
there is no incoming call, and will produce +CME ERROR: 4
The +CTICN indication is not repeated.
Execution Syntax
ATA
Set Syntax
N/A
Test Syntax
ATA=?
Read Syntax
N/A
Any characters after this command are ignored.
Responses
State Response
Call Completion +CTCC: <params>
No new incoming call for any reason (including +CME ERROR: 3
No Service and Already in a Call) (Command out of context)
Test Response
<cr><lf>OK<cr><lf>
Example
<cr><lf>+CTICN: 123,0,0,0,20550,0,0,0,0,1,90021,10<cr><lf>
ATA<cr>
<cr><lf>+CTCC: 123,0,0,0,0,0,1<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.3 ATD - Dial
Source
[5] 6.3.1
Description
Make an outgoing voice or circuit mode data call (not Packet Data).
This command is fully supported on Logical Port 1. Logical port 2 only supports the Dial String parameter
that is necessary to activate a Packet Data Context.
Characters after the ‘D’ until the line end are addressing information for the call (dial string). Valid
characters are 0,1,2,3,4,5,6,7,8,9,*,#,+
Invalid characters within the dial string are not ignored and will result in the return of an error report.
It is not possible to set up a duplex, direct mode voice call.
The product will behave as if a hooking accessory has been taken ‘off hook’ and, for a direct setup call, a
PTT has been pressed. If transmission is not required this should be followed by a AT+CUTXC.
For a BOS-digital terminal it will not be possible to setup an encrypted emergency priority call.
Group calls should be setup to the currently selected group. If necessary use AT+CTGS to select the
required group first.
Execution Syntax
ATD[<Dial String>]
Set Syntax
N/A
Test Syntax
ATD=?
Read Syntax
N/A
Where the format of the <dial string> is defined by the dial string type.
The dial string type is set either to the default settings, or to the last + CTSDC command.
The options are :

 Individual
 Group
 PSTN gateway
 PABX gateway
 Service Centre (ITSI)
 Service Centre (E 164 number)
The <dial string> received must be parsed against the above format.
When the <dial string> represents a TSI it must be 15 digits (including leading zeros).
When the Data Application invokes this function the radio checks for error conditions and reports as
follows. To maintain backward compatibility, the error numbers used are dependant upon the setting of the
parameter PEI Compliance Level, [8154].

MOD-14-1758
State Response when PEI Response when PEI

Compliance Level [8154] is 0 Compliance Level [8154] is 1
Calling (this) radio not in service +CME ERROR: 512 +CME ERROR: 30
(Service not available) (no network service)
In service whilst in equal or +CME ERROR: 2 +CME ERROR: 3
higher priority call or new call (MT adaptor link reserved) (Operation not allowed - in current
does not have a pre-emptive state)
priority (try and set up a second
call) Call priority is set using
AT+CTSDC
In service – called radio busy +CTCR: (with disconnect cause +CTCR: (with disconnect cause
indicating called party busy) indicating called party busy)
In service TMO – called radio +CTCR: (with disconnect cause +CTCR: (with disconnect cause
not found, or command aborted indicating no acknowledgement) indicating no acknowledgement)
In DMO - called radio not found, +CTCR: (with disconnect cause +CTCR: with disconnect cause
or command aborted indicating 'Called party not indicating 'Called party not
reachable') reachable).
In service – in call successful +CTCC: (with parameters) +CTCC: (with parameters)
In service whilst in lower priority +CTCR: (with parameters for +CTCR: (with parameters for
call and new call has a pre- original call, with disconnect original call, with disconnect
emptive priority (terminate cause indicating user request) cause indicating user request)
current call and set up a second +CTCC: (with parameters for new +CTCC: (with parameters for new
call). Call priority is set using call) call)
AT+CTSDC
Dial String too long +CME ERROR: 26 +CME ERROR: 26
(Dial string too long) (Dial string too long)
Invalid characters in dial string +CME ERROR: 27 +CME ERROR: 27
(Invalid chars in dial string) (Invalid chars in dial string)
In service – Duplex or individual +CME ERROR: 513 +CME ERROR: 40
call attempted during DMO (Service not supported during (Service not supported during
mode while DMO individual calls DMO) DMO)
are disabled
Duplex or individual call +CME ERROR: 518 +CME ERROR: 518
attempted during Repeater (Service not supported during (Service not supported during
mode while DMO individual calls repeater mode) repeater mode)
are disabled
Duplex call attempted during +CME ERROR: 513 +CME ERROR: 40
DMO mode (Service not supported during (Service not supported during
DMO) DMO)
No talkgroup selected during +CME ERROR: 3 +CME ERROR: 3
DMO mode (Operation not allowed in current (Operation not allowed - in current
state) state)
Duplex call, CMD call or no key +CME ERROR: 4 +CME ERROR: 3
for call attempted to encrypted (Operation not supported) (Operation not allowed - in current
destination state)
In service – but TX inhibited +CME ERROR: 515 +CME ERROR: 41
Transmissions are inhibited (Transmissions are inhibited)
Packet Data Connection CONNECT CONNECT
established
Wrong <GPRS Service Code NO CARRIER NO CARRIER
IP> or Packet Data connection
cannot be established
Packet data Service is not NO DIALTONE NO DIALTONE
available

MOD-14-1758
Packet Data Service is already BUSY BUSY

in use
Calling (this) radio is operating +CME ERROR: 519 +CME ERROR: 519
as a DMO Gateway (Service not supported by DMO (Service not supported by DMO
Gateway) Gateway)
CC Voice is set to 'Both' +CME ERROR: 3 +CME ERROR: 43
(Operation not allowed) (Service not supported in V+D)
In DMO mode and +CME ERROR: 3 +CME ERROR: 40
corresponding service profile for (Operation not allowed) (Service not supported in DMO)
CC Voice is set to 'Both'
In Repeater mode and +CME ERROR: 3 +CME ERROR: 518
corresponding service profile for (Operation not allowed) (Service not supported in
CC Voice is set to 'Both' Repeater Mode)
Individual call without presence +CME ERROR: 3 +CME ERROR: 43
check attempted in Trunked (Operation not allowed) (Service not supported in V+D)
Mode
Encrypted emergency priority +CME ERROR: 3 +CME ERROR: 3
call attempted for a BOS-digital (Operation not allowed) (Operation not allowed - in current
terminal state)
Individual call attempted during +CTCR: (with disconnect cause +CTCR (with disconnect cause
DMO mode while DMO channel indicating 'Network Congestion') indicating 'Network Congestion')
is busy
Dial string TSI not 15 digits +CME ERROR: 34 +CME ERROR: 34
(Parameter out of range) (Parameter out of range)
Note: as stated above, when a dial string contains one or more invalid characters it is rejected with
+CME ERROR: 27. The following are valid characters, dependant upon the value of <Called Party Identity
Type> in the most recent +CTSDC command. All other characters are invalid.
Called Party Permitted Characters
Identity Type
0 SSI 0123456789
1 TSI 0123456789
3 PABX 0123456789*#+
4 PSTN 0123456789*#+
Test Response
<cr><lf>OK<cr><lf>
Example
ATD20550<cr>
<cr><lf>+CTOCP: 123,0,0,0,0,0,0,1<cr><lf>
<cr><lf>+CTOCP: 123,0,0,0,0,0,0,1<cr><lf>
<cr><lf>+CTCC: 123,0,0,0,0,0,1<cr><lf>

MOD-14-1758
7.1.4 ATE - Echo
Source
[5] 6.2.4
Description
Turn command echo on or off
Where two ports are supported by the product, this setting will only affect the PEI port that receives this
command.
Execution Syntax
N/A
Set Syntax
ATE[<value>]
Read Syntax
ATE?
Test Syntax
ATE=?
Defined Values
0 Switch echo off
1 Switch echo on
Any other value returns :
+CME ERROR: 34
(parameter out of range)
Default
1 Echo is on ([5] default)
Test Response
<cr><lf>OK<cr><lf>
Example
ATE1<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.5 ATH - Hook State
Source
[5] 6.3.6
Description
Changes hook state to on-hook. Effectively disconnects the call. Where two ports are supported by the
product, it is not possible to disconnect a call on the other PEI.
Execution Syntax
ATH[<value>]
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
ATH=?
Defined Values
0 – go back on hook (disconnect call or terminate any indication of a failed call)
Any other value returns
+CME ERROR: 34 (parameter out of range)
State Response
In call on PEI +CTCR: <Params>
Not in a call controlled by PEI and +CME ERROR: 3
not alerting for a failed call setup (Operation out of context)
initiated by the current PEI
Slave of an individual call in +CME ERROR: 3
occupation in DMO (Operation out of context)
Test Response
<cr><lf>OK<cr><lf>
Example
ATH0<cr>
<cr><lf>+CTCR: 123,1<cr><lf>
ATH1<cr>
<cr><lf>+CME ERROR: 34<cr><lf>

MOD-14-1758
7.1.6 ATI - Identify Host Product
Source
[5] 6.1.3
Description
Causes the radio to return lines of informational text. The values and the text they return are proprietary to
the manufacturer. The text is specified in neither [5] nor [6].
Where two ports are supported by the product, this command works on either or both PEIs.
Execution Syntax
ATI[<value>]
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
ATI=?
Defined Values
1 Returns Manufacturer Identity
2 Returns Product Identity
3 Returns Software revision numbers
Where Manufacturer Identity is:

SEPURA<cr><lf>
Where product identity is one of:

SRH3000<cr><lf>
SRM3500<cr><lf>
SRG3500<cr><lf>
SRC3300<cr><lf>
SRC3100<cr><lf>
SRH3500W<cr><lf>
SRH3800W<cr><lf>
SRM3500W<cr><lf>
SRG3500W<cr><lf>
SRC3300W<cr><lf>
STP8000<cr><lf>
SRH3900<cr><lf>
STP8100<cr><lf>
SRG3900<cr><lf>
STP8200<cr><lf>
STP8X100<cr><lf>
STP9000<cr><lf>
STP9100<cr><lf>
STP9200<cr><lf>

MOD-14-1758
Where software revision numbers are a set of up to six 12 digit numbers:

<Boot Software>,<Control Software>,<Console1 software>,<Console2 software>,<MMI/Authentication software
>[,<Secure processor software>]<cr><lf>
Not all products have all software items and will return empty strings between the commas.
Product Revision Numbers returned

Hand-Held <Boot>,<Control>,,,<Authentication>,<Secure micro>
3000 series and
Portable 8000 series
Mobile or Gateway <Boot>,<Control>,<Console 1 if fitted>,<Console 2 if fitted>,<Authentication>,
3000 series <Secure micro>
Any other value returns
+CME ERROR: 34
(Parameter out of range)
Test Response
<cr><lf>OK<cr><lf>
Example
ATI1<cr><cr>
<cr><lf>SEPURA<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.7 ATO - Return to Online
Source
[5] 6.3.7
Description
Return to online data state from online command state. To get to this state, a data call must have been
either initiated, or answered, then the escape sequence sent to switch from online mode to command
mode. This command is only appropriate to the command during a data call. Voice calls do not have
online data mode.
Execution Syntax
ATO[<value>]
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
ATO=?
Defined Values
0 Return to online data state from online command state
Any other value gives a response:

+CME ERROR: 34 (Parameter out of range)
State Response
Data Call active, but interface in command mode. Call +CTCC <params>
successfully resumed
Not in a data call on this PEI which has been escaped, +CME ERROR: 3 (Operation not allowed)
see 5.2.4
Test Response
<cr><lf>OK<cr><lf>
Example
ATO<cr>
<cr><lf>+CTCC=123,0,0<cr><lf>

MOD-14-1758
7.1.8 ATQ - Results Code
Source
[5] 6.2.5
Description
Result code suppression. All responses from the terminal can be stopped. Quiet mode.
command.
Execution Syntax
ATQ[<value>]
Set Syntax
N/A
Read Syntax
ATQ?
Test Syntax
ATQ=?
Defined Values
0 Terminal transmits result codes
1 Terminal does not transmit result codes. (there is no response to this command)

+CME ERROR: 34
Default
0 Terminal transmits result codes
Test Response
<cr><lf>OK<cr><lf>
Examples
ATQ0<cr>
<cr><lf>OK<cr><lf>
ATQ1<cr>

MOD-14-1758
7.1.9 ATR - MT Reboot
Source
[5] 6.14.12
Description
This command resets the configuration of the serial interface to their factory defaults (see AT&F), aborts
any calls and performs a normal switch off and switch on. This is the same as an ATZ command
customised to perform reboot.
Execution Syntax
ATR
Set Syntax
N/A
Test Syntax
N/A
Read Syntax
N/A
Example
ATR
OK
<Radio reboots>

MOD-14-1758
7.1.10 ATS0 - Automatic Answer
Source
[5] 6.3.8
Description
This parameter controls the automatic answer feature of the terminal. The value would normally indicate
the number of RING responses before the call is automatically answered. However, in this
implementation, the repeated RING response has been replaced by a single +CTICN response. [5]
indicates that the RING frequency depends on the infrastructure. There is no indication of the frequency of
the RING indication in [5].
Therefore the value will now have to reflect the number of seconds before the call is answered after the
+CTICN response.
Execution Syntax
N/A
Set Syntax
ATS0 =[<value>]
Read Syntax
ATS0?
The response always contains three decimal digits, with leading zeros where necessary.
Test Syntax
ATS0=?
Defined Values
0 Automatic answering is disabled
1 – 255 Answer the call after <value> number of seconds

+CME ERROR: 34
Default
0
Test Response
<cr><lf>OK<cr><lf>
Example
ATS0=1<cr>
<cr><lf>OK<cr><lf>
ATS0?<cr>
<cr><lf>001<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.11 ATS2 - Escape character
Source
Unknown
Description
Defines the escape character to be used
command.
Execution Syntax
N/A
Set Syntax
ATS2=[<value>]
Read Syntax
ATS2?
Test Syntax
ATS2=?
Defined Values
The value is the decimal value of a character to be used for the escape sequence. The escape sequence
requires a string of 3 of these characters within 1 second.
Values 0 – 127 are valid
Default
43 (+ character)
Return Values
Value = 0 – 127
OK

+CME ERROR: 34
Test Response
<cr><lf>OK<cr><lf>
Example
ATS2=37<cr>
<cr><lf>OK<cr><lf>
<cr><lf>+CTICN: 123,0,0,0,20551,0,0,0,0,1,0,90021,10<cr><lf>
<cr><lf>OK<cr><lf>
ATA<cr>
<cr><lf>+CTCC: 123,0,0,0,0,0,1<cr><lf>
<cr><lf>+Hello World<cr><lf>
%%%
<cr><lf>OK<cr><lf>+

MOD-14-1758
7.1.12 ATS3 - Line Termination Character
Source
[5] 6.2.1
Description
Defines the command line termination character to be used. An execution command which changes this
value is terminated by the old line termination character. All responses and all subsequent commands use
the new line termination character.
command.
Execution Syntax
N/A
Set Syntax
ATS3=[<value>]
Read Syntax
ATS3?
Test Syntax
ATS3=?
Defined Values
The value is the decimal value of a character to be used for the command termination character.
Default
13 (Carriage Return character)
Return Value
If value = 0 – 127
OK
+CME ERROR: 34
Test Response
<cr><lf>OK<cr><lf>
Example
ATS3=10<cr>
<cr><lf>OK<cr><lf>
AT<LF>
<cr><lf>OK<cr><lf>
AT<CR>

MOD-14-1758
7.1.13 ATS4 - Line Feed Character
Source
[5] 6.2.2
Description
Defines the character that is sent, along with the character defined with S3, as a line terminator when the
terminal sends a response.
For instance, the defaults for S3 and S4 would give a response of

<cr><lf>OK<cr><lf>
Changing the value of S4 will affect the <LF> character.
command.
Execution Syntax
N/A
Set Syntax
ATS4=[<value>]
Read Syntax
ATS4?
Test Syntax
ATS4=?
Defined Values
The value is the decimal value of a character to be used for the line termination character.
Valid values are 0 – 127
Default
10 (Line Feed character)
Return Value
If value = 0 – 127
OK
+CME ERROR: 34
Test Response
<cr><lf>OK<cr><lf>
Example
ATS4=36<cr>
<cr><lf>OK<cr><lf>
AT%
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.14 ATS5 - Backspace Character
Source
[5] 6.2.3
Description
Defines the character that takes the function of the backspace command.
command.
Execution Syntax
N/A
Set Syntax
ATS5=[<value>]
Read Syntax
ATS5?
Test Syntax
ATS5=?
Defined Values
The value is the decimal value of a character to be used for the delete character.
Return Value
If value = 0 – 127
OK
+CME ERROR: 34
Default
8 (Backspace character)
Test Response
<cr><lf>OK<cr><lf>
Example
ATS5=38<cr>
<cr><lf>OK<cr><lf>
Typed: helll&o
Echo: helll& &o
<cr><lf>CME ERROR: 36<cr><lf>

MOD-14-1758
7.1.15 ATV - Results Code
Source
[5] 6.2.6
Description
Determines the format of the result code and information responses. Verbose mode. This command
seems to have two functions, it sets both the number of CR/LFs before and after the result code, and
changes the numeric result code (0) to a verbose (OK) textual result code.
command.
Execution Syntax
ATV[<value>]
Set Syntax
N/A
Read Syntax
ATV?
Test Syntax
ATV=?
Defined Values
1 Terminal sends full headers and trailers
Return Value
If value = 1
OK
Else
+CME ERROR: 34
Default
Terminal sends full headers and trailers, together with verbose result codes.
As the commands BUSY, CONNECT, NO CARRIER have been replaced in [6] with informational fields to
+CTCC, and +CTCR, the only verbose response is now ‘OK’.
Test Response
<cr><lf>OK<cr><lf>
Example
ATV1
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.16 ATZ - Reboot
Source
[5], [6]
Description
Resets the configuration to their factory defaults. Abort any calls and reset the radio.
This setting will reset the radio with a ‘clean’ shut-down and re-start, using the ‘switch off’ and ‘switch on’
functions, see {3}.This will affect both the PEI port where the command originated, and the other PEI port
(where two ports are supported by the product). This will happen without the knowledge of the application
currently running on the other PEI port. See also +CSPRT command.
If the user of the radio has activated the Transmit Inhibit function before the execution
of the ATZ command; when the radio re-starts, the Transmit Inhibit function will no
longer be active. This is the same behaviour as the user switching the radio off and
on again.
The action of the ATZ command will depend on the setting in the customisation of the
handheld (not applicable to mobile or Gateway) radio from software version V5.0-005
onwards. This can be set to either:
Radio reboots
Radio does not reboot
Execution Syntax
ATZ
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
ATZ=?
Defined Values
[5] optionally includes a value, but does not give any definitions. Other modem manufacturers indicate that
the value can be used to load default setting <value> where there is more than one default setting. Any
value will be discarded.
Test Response
<cr><lf>OK<cr><lf>
Example
ATZ<CR>
(radio resets)

MOD-14-1758
7.1.17 AT+CBC - Battery Charge
Source
ETSI Standard TS 100 916, section 8.4
TTR 001-18, Part 18: Peripheral Equipment Interface (PEI), section 17.3.1
Description
Reads battery connection status and battery charge level of the terminal.
Execution Syntax
AT+CBC
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+CBC=?
Execution Response
+CBC: <bcs>,<bcl><cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
<bcs> - battery connection status
0 Terminal is powered by the battery
2 Terminal does not have a battery connected
<bcl> - battery charge level

0 battery is exhausted, or terminal does not have a battery connected
1...100 battery has 1-100 percent of capacity remaining
Portable terminals support a subset of the <bcl> range (see tables below), that correspond to the battery
level indications on the UI / screen.
AT+CBC 3000 Series Terminals: Battery level indication on UI

response
+CBC: 2,0 No battery connected (dummy battery)
+CBC: 0,11 Four empty segments
+CBC: 0,22 Bottom segment half filled
+CBC: 0,33 Bottom segment filled
+CBC: 0,44 Bottom segment filled and second segment half filled
+CBC: 0,55 Bottom two segments filled
+CBC: 0,66 Bottom two segments filled and third segment half filled
+CBC: 0,77 Bottom three segments filled
+CBC: 0,88 Bottom three segments filled and fourth segment half filled
+CBC: 0,100 All four segments filled

MOD-14-1758
AT+CBC 8000 Series Terminals: Battery level indication on UI

response
+CBC: 2,0 No battery connected (dummy battery)
+CBC: 0,12 Bottom segment filled (empty)
+CBC: 0,25 Bottom two segment filled
+CBC: 0,37 Bottom three segment filled and second segment half filled
+CBC: 0,50 Bottom four segments filled
+CBC: 0,62 Bottom five segments filled and third segment half filled
+CBC: 0,75 Bottom six segments filled
+CBC: 0,88 Bottom seven segments filled
+CBC: 0,100 All eight segments filled
Mobile products always return <bcs> = 2 and <bcl> = 100.
An 8000 Series terminal with an unauthenticated or unchargeable battery will return <bcs> = 0 and <bcl>
=0
Note: This command is also supported when the battery is charging, indicating <bcs> = 0 and the current
charge level.
Test Response Syntax

+CBC: (battery connection status),(supported battery charge levels)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
3000 Series:
+CBC: (0,2),(0,11,22,33,44,55,66,77,88,100)<cr><lf>
<cr><lf>OK<cr><lf>
8000 Series:
+CBC: (0,2),(0,12,25,37,50,62,75,88,100)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CBC<cr>
+CBC: 0,55<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.18 AT+CCI - Cell Information
Source
Proprietary to Sepura
Description
Return the Cell information
Execution Syntax
N/A
Set Syntax
N/A
Read Syntax
AT+CCI?
Test Syntax
AT+CCI=?
Response
<cr><lf>+CCI: <MNI>,<RSSI>,<BER>,<LA>,<F>,<C1>,<BNC_LA>,<BNC_C2>,<BNC_RSSI><cr><lf>
where
<MNI> Mobile Network Identity
<RSSI> Serving cell RSSI in dBm (-90dBm will be reported as -90)
<BER> Serving cell BER estimate in % (This value parameter is not supported and is always set to 99.9)
<LA> Serving cell Local Area
<F> Current (CCH or TCH) frequency expressed as nnn.nnnn in MHz e.g. 394.2375
<C1> Serving cell C1
<BNC_LA> Best neighbouring cell LA (best is currently highest C2 value, later highest score)
<BNC_C2> Best neighbouring cell C2 value
<BNC_RSSI> Best Neighbouring cell RSSI
When there is no information to send for a particular parameter, that parameter is null.
When the product is operating as a DMO Gateway, all parameters apply to the TMO service
Responses
State Response when PEI Compliane Response when PEI Compliane
Level [8154] is 0 Level [8154] is 0
No service +CME ERROR: 30 +CME ERROR: 30
(No network service) (No network service)
In service See Response above See Response above
Direct Mode +CME ERROR: 513 +CME ERROR 40
(Not possible when in DMO mode) (Not possible when in DMO mode)
Repeater Mode +CME ERROR: 518 +CME ERROR: 518
(Service not supported when in (Service not supported when in
Repeater Mode) Repeater Mode)

MOD-14-1758
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CCI?<cr>
<cr><lf>+CCI: 2347100,-89,99.9,2,394.0125,20,0,30,100<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.19 AT+CGPS - GPS Functions
Source
Proprietary to Sepura.
Description
Requests one-off position report to PEI using NMEA sentences.
This command is only supported on Logical Port 1.
Execution Syntax
N/A
Set Syntax
AT+CGPS=<value>
Defined Values
<value> = 20 report position to PEI now
Read Syntax
N/A
Set Response
+CME ERROR: 4 (Operation not supported) if GPS not fitted or not licensed
for <value> = 20
<cr><lf>OK<cr><lf>
Test Syntax
AT+CGPS=?

+CGPS: (list of supported values) <cr><lf>
OK<cr><lf>
Test Response
+CGPS: (20) <cr><lf>
OK<cr><lf>
Example
AT+CGPS=20<cr>
<cr><lf>OK<cr><lf>
$GPGLL,5212.883625,N,00008.430892,E,155647.395,A,A*58<cr><lf>
$GPRMC,155647.395,A,5212.883625,N,00008.430892,E,1.628,311.26,280504,,,A*5E<cr><lf>
$GPGGA,155647.395,5212.883625,N,00008.430892,E,1,6,1.40,-62.557,M,47.000,M,,*43<cr><lf>
$GPGSA,M,3,24,04,13,10,17,08,,,,,,,4.37,1.40,4.15*04<cr><lf>
$GPGSV,3,1,09,24,46,232,24,04,22,193,22,13,46,072,38,10,46,299,23*72<cr><lf>
$GPGSV,3,2,09,27,66,124,,17,45,286,22,08,46,178,34,16,10,026,*79<cr><lf>
$GPGSV,3,3,09,06,05,315,*44<cr><lf>

MOD-14-1758
7.1.20 AT+CLVL - Volume Control
Source
Description
Set or read the volume control
The most recent volume level set by the PEI or the UI will have precedence.
Execution Syntax
N/A
Set Syntax
AT+CLVL=<value>
Read Syntax
AT+CLVL?
Test Syntax
AT+CLVL=?
Defined Values
0–9 increments between minimum and maximum volume
9 < value < 256 same volume level as 9 (maximum volume)
value > 256 +CME ERROR: 34
Return Values
0–9 increments between minimum and maximum volume

+CLVL: (list of volume values) <cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CLVL: (0-255) <cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CLVL?<cr>
<cr><lf>+CLVL: 3<cr><lf>
<cr><lf>OK<cr><lf>
AT+CLVL=12<cr>
<cr><lf>OK<cr><lf>
For products that support Local Volume Control the set command set ALL volumes for that console to the
<value> and the read command returns the volume level of the transceiver loudspeaker.

MOD-14-1758
7.1.21 AT+CMGS - Send Message
Source
[6] section 6.13.2
Description
Send SDS or STATUS message.
The command is originally derived from the GSM specification TS 100 585 3.5.1. GSM specifies Block
mode, Text mode and PDU mode. [6] specifies only one mode for sending SDS messages, although it
does not actually specify which of the above. PDU mode is the most likely.
The parameters for the SDS message will either be set up using the power-on defaults, can be set up
before using this command using +CTSDS or can be reset (with others) using &F
The terminating character (CtrlZ) will attempt to send the message, <ESC> will abort sending the
message.
For terminals that require OPTA inclusion in outgoing SDS test messages, a Dummy
OPTA value must be included at the start of the SDS payload (see Appendix 2:
Dummy OPTA)
It is the responsibility of the external application to break down long SDS messages
into the individually packaged parts before being transmitted using this command.
Execution Syntax
N/A
Set Syntax
AT+CMGS=<called party identity>,<length><cr>user data<CtrlZ>/<ESC>
[6] calls for <cr><lf> between the length and the user data. GSM, and other Tetra suppliers specify just
<cr>. We will accept either just <cr> or <cr><lf>.
Read Syntax
N/A
Test Syntax
AT+CMGS=?
Defined Values
<called party identity> depends on the number type set up from default, or modified by the +CTSDS
command.
<length> Number of bits of user data.
Note: The maximum length of the SDS message cannot exceed the number of bytes defined in the ‘PEI
SDS Message Size Limit’ parameter. If the message exceeds this permissible length the ‘+CME ERROR:
24’ will be generated (see below).
The possibility exists for E2EE terminals that after the SDS message is sent from the PEI, but before the
message is sent over the air that an E2EE wrapper is applied to the outgoing SDS message. This will
increase the size of the message payload that will be sent accordingly. The size of the header is a
function of the destination address and the specific E2EE solution supported by the terminal. To
guarantee that the maximum size of SDS messages sent via the PEI do not exceed the TIP compliant
max size (140 bytes) it is recommended that the ‘PEI SDS Message Size Limit’ parameter should not
exceed 118 bytes.
<user data> Message and SDS-TL header. This is encoded in ASCII Hex. The message reference within
the SDS-TL should be set to FF

MOD-14-1758
Responses
+CMGS: <SDS Instance>[,<SDS Status> [, <message reference>]]
Where the (i) SDS Instance is a number from 0 – 255 used for local (to this terminal) reference.
Message reference (r) is the SDS-TL over-the-air reference, 0 – 65535.
Response when PEI Response when PEI

State
Send successful CMGS: i,s,r CMGS: i,s,r
Text string is longer than maximum +CME ERROR : 24 +CME ERROR : 24
length allowed. (Text string too long) (Text string too long)
Invalid characters in text string (i.e.
+CME ERROR : 25
not Hexadecimal characters or +CME ERROR : 25
(Invalid characters in text
Dummy OPTA not present but (Invalid characters in text string)
string)
required)
+CME ERROR : 26 +CME ERROR : 26
Dial String too long
(Dial string too long) (Dial string too long)
Invalid characters in dial string
(Invalid chars in dial string) (Invalid chars in dial string)
Calling (this) radio not in service
(no network service) (no network service)
Out of range error
The required TSI address is less than
15 digits or the SSI portion of the TSI +CME ERROR: 34 +CME ERROR: 34
(lower 8 digits) or the SSI is greater
24
than 16777215 (2 -1)
Text String does not match length +CME ERROR : 35 +CME ERROR : 35
field within command (Syntax error) (Syntax error)
Unable to process the sending of the
message, (e.g. because another +CME ERROR : 512 +CME ERROR: 42
SDS messages is already being (Service not available) (Service not available)
processed)
Not supported in TMO
When sending in TMO the MNI
portion of the required TSI (top 7 +CME ERROR: 514 +CME ERROR: 43
digits) does not correspond to the
TMO SwMI MNI.
+CME ERROR : 515 +CME ERROR: 41
In service – but TX inhibited
(Transmissions are inhibited) (Transmissions are inhibited)
Defined values in response

SDS Instance (i) is a number from 0 – 255 used for local (to this terminal) reference.
SDS Status (s) has the following meaning when PEI Compliance Level [8154] is 0:
SDS Status Meaning
2 Outgoing message stored and unsent
3 Outgoing message stored and sent
8 Outgoing message deleted and unsent
9 Outgoing message deleted and sent
Values 8 and 9 are proprietary to Sepura

MOD-14-1758
SDS Status Meaning
4 Outgoing message successfully sent
5 Outgoing message transmission failed (no more attempts will be made)
For Simple SDS-TL Protocol Ids (values 0-127), the Message reference (r) is always 0. For Full SDS-TL
protocol Ids (values 128-255) Message reference (r) is the SDS-TL over-the-air reference, 1 - 254.
Test Response
<cr><lf>+CMGS: <Address Range>, (0-<Max Length>) <CR><LF> <User Data> (<Ctrl Z>, <ESC>)
<cr><lf>OK<cr><lf>
Where: <Address Range > is dependant upon the <Called party address type> set using the AT+CTSDS
command. That is:
If <Called party address type> = ‘SSI’ then <Address range> = (0-16777215) or
If <Called party address type> = ‘TSI’ then <Address range> = (000-999)(0000-9999)(00000000-
16777215)
If <Called party address type> = ‘PABX’ or ‘PSTN’ then <Address range> = (24)
Note: ‘(24)’ denotes the maximum length of the permitted dial string.
<Max Length> is the length in bits defined by PEI SDS Message Byte Length Limit parameter.
Example Test Responses

Where the max length of SDS that can be sent from the PEI is defined as 110 bytes and the <Called party
address type> = ‘SSI’ (the bold italics denote the control characters not displayed text):
<CR><LF>+CMGS: (0-16777215),(0-880)<CR><LF><User Data>(<Ctrl Z>,
<ESC>)<CR><LF>OK<CR><LF>
As above when the <Called party address type> = ‘PABX’ (the bold italics denote the control characters
not displayed text):
<CR><LF>+CMGS: (24),(0-880)<CR><LF><User Data>(<Ctrl Z>,
<ESC>)<CR><LF>OK<CR><LF>
Example 1 when PEI Compliance Level [8154] is 0

AT+CMGS=20550,48<CR>C00000616263<CtrlZ>
<CR><LF>+CMGS: 1,2<CR><LF> Stored and unsent, no message reference
<CR><LF>OK<CR><LF>
<CR><LF>+CMGS: 1,2,2<CR><LF> Stored and unsent, message reference added
<CR><LF>+CMGS: 1,9,2<CR><LF> Deleted and sent, no message reference

AT+CMGS=901223877600,48<CR>C00000616263<Ctrl Z>
<CR><LF>+CMGS: 1,2<CR><LF>
<CR><LF>OK<CR><LF>
<CR><LF>+CMGS: 1,2,2<CR><LF>

AT+CMGS=901223877600,48<CR>C00000616263<Ctrl Z>
<CR><LF>OK<CR><LF>
See section 4.8.1 for Status Message examples.

MOD-14-1758
7.1.22 AT+CMEE - Extended Error Reporting
Source
[6]
Description
Enables or disables the CME final extended result code response.
Where two ports are supported by the product, this command has no effect on the other PEI port.
Execution Syntax
N/A
Set Syntax
AT+CMEE=<value>
Read Syntax
AT+CMEE?
Test Syntax
AT+CMEE=?
Defined Values
1 Terminal returns extended code CME error and numeric result code.
Any value other than 1 returns

+CME ERROR: 34

+CMEE: (list of extended error report types)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CMEE: (1)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CMEE=1<cr>
<cr><lf>OK<cr><lf>
AT+CMEE?<cr>
<cr><lf>+CMEE: 1<cr><lf>

MOD-14-1758
7.1.23 AT+CNCI - Neighbour Cell Information
Source
Description
Return the Neighbour Cell information
Execution Syntax
N/A
Set Syntax
N/A
Read Syntax
AT+CNCI?
Test Syntax
AT+CNCI=?
Responses
<cr><lf>+CNCI: <cr><lf>
1,<NC1_F>,<NC1_RSSI>,<NC1_C2>,<cr><lf>
.
. repeated…
.
31,<NC16_F>,<NC16_RSSI>,<NC16_C2><cr><lf>
where:
NCn_F is the frequency of the neighbouring cell expressed as nnn.nnnn in MHz of the Base TX main
carrier. Leading and trailing zeros are included
NCn_RSSI is the received signal of this signal in dBm (-90dBm is printed as -90)
NCn_C2 is the C2 value of the received signal
The list is in the order of largest C2 first.
31 fields can be reported. When less that 31 neighbouring cells are available, the empty fields are marked
with commas (see example)
State Response when PEI Compliance Response when PEI Compliance

Direct Mode +CME ERROR: 513 +CME ERROR: 40
(Service not supported when in (Service not supported when in
Repeater Mode) Repeater Mode)

MOD-14-1758
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CNCI?<CR>
<cr><lf>+CNCI<cr><lf>
1,394.1375,-90,30,><cr><lf>
2,393.2125,-92,28,<cr><lf>
3,393.9875,-101,22,<cr><lf>
4,394.0125,-110,20,<cr><lf>
5,,,,<cr><lf>
6,,,,<cr><lf>
7,,,,<cr><lf>
8,,,,<cr><lf>
9,,,,<cr><lf>
10,,,,<cr><lf>
11,,,,<cr><lf>
12,,,,<cr><lf>
13,,,,<cr><lf>
14,,,,<cr><lf>
15,,,,<cr><lf>
16,,,,<cr><lf>
17,,,,<cr><lf>
18,,,,<cr><lf>
19,,,,<cr><lf>
20,,,,<cr><lf>
21,,,,<cr><lf>
22,,,,<cr><lf>
23,,,,<cr><lf>
24,,,,<cr><lf>
25,,,,<cr><lf>
26,,,,<cr><lf>
27,,,,<cr><lf>
28,,,,<cr><lf>
29,,,,<cr><lf>
30,,,,<cr><lf>
31,,,<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.24 AT+CNUM - Identities
Source
[6] 6.11.4
Description
Returns the ITSI of the terminal, the list of groups that can be attached, the PABX and PSTN gateway.
The phonebook is not listed.
The ITSI is one number.
The list of groups can be 3000 numbers for 3000 / 8000 Series terminals, and does not include DGNA
Groups.
When the product is operating as a DMO gateway, the reported groups are the DMO GTSIs.
The PABX and PSTN gateways are individual numbers.
By following specification ETS 300392-5, this command could respond with as many lines as the
maximum number of talk groups supported, and as such could make this command unusable. The
proprietary command @N has been offered as an alternative, see 7.1.68.
Execution Syntax
N/A
Set Syntax
N/A
Read Syntax
AT+CNUM?
Test Syntax
AT+CNUM=?
Response
+CNUM: <num type>,<Called Party Identity>[,alpha][,<cr><lf>
<num type>[,<Called Party Identity>[,alpha]],<cr><lf>]
... [<num type>[,<Called Party Identity>[,alpha]]]<cr><lf>
Defined Values
Number Type
0 Individual
1 Group
2 PSTN Gateway
3 PABX Gateway
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CNUM?<cr>
<cr><lf>+CNUM: 0,234710000020550,<cr><lf>
1,234710000080001,<cr><lf>
1,234710000080002,<cr><lf>
2,234710000010001<cr><lf>
3,234710000010000<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.25 AT+CNUMD - Get MT Dynamic Group Identities
Source
[6] section 6.11.5.3
Description
This command is for reporting of dynamic group identities. The execution command requests the MT
enable / disable unsolicited reporting of dynamic group changes and requests the MT report either the
number of dynamic groups or details of a range of DGNA groups. When enabled the corresponding
unsolicited result code reports the number of dynamic groups whenever there is a change to the number
of identities or any of the dynamic groups or to the current stack, see 7.2.3. It is then up to the TE to
request further information and for it to work out what has changed.
Execution Syntax
AT+CNUMD=<Ident Unsolic>[,<lower range limit>,<upper range limit>]
Defined Values
Field Values Remark
<Ident Unsolic> 0 or 1 0 = 'Disable dynamic identity unsolicited result code'
(default value)
1 = 'Enable dynamic identity unsolicited result code'
<lower range limit> 1 to 4096 Both absent: report number of DGNA groups
1,4096: report details of all DGNA groups
<upper range limit> 1 to 4096 n,m: report details of requested subset of DGNA
groups
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+CNUMD=?
Execution Response
In response to report number of DGNA groups:
+CNUMD: <number of groups><cr><lf>
<cr><lf>OK<cr><lf>
In response to report details of DGNA groups:

+CNUMD:<cr><lf>
[<num type>,<called party identity>[,<alpha>]<cr><lf>
...
<num type>,<called party identity>[,<alpha>]<cr><lf>]
<cr><lf>OK<cr><lf>

MOD-14-1758
Defined Values
Field Values Remark
<number of groups> 0 to 50 Number of dynamic groups stored in context data
<num type> 1 Type of identity; must be 1 = Group
<called party identity> cccnnnniiiiiiii GTSI of dynamic group where c = MCC, n = MNC, i =
SSI
<alpha> Up to 16 characters Alias text of dynamic group, if any, encoded
according to parameter Hayes Text Format, [8152]
Test Response
+CNUMD: (0-1),(1-4096),(1-4096)<cr><lf>
<cr><lf>OK<cr><lf>
Examples
AT+CNUMD=1<cr> (request number of DGNA groups)
<cr><lf>
+CNUMD: 2<cr><lf>
<cr><lf>OK<cr><lf>
AT+CNUMD=1,1,4096<cr> (request details of all DGNA groups)

<cr><lf>
+CNUMD:<cr><lf>
1,234710000080001,DG1<cr><lf>
1,234710000080002,DG2<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.26 AT+CPIN - Enter PIN
Source
TS 100 916 section 8.3.
Description
This command is used by the TE to enter either a radio password (Master PIN or Master Reset PIN) or a
smart card password (PIN or PUK). The read command returns an alphanumeric string indicating whether
some password is required or not. The execute command sends a password to the ME for validation and
reports the result. If no password request is pending, the ME returns a +CME ERROR. If the password
required is Master Reset PIN or PUK, a new PIN may be supplied and if so this replaces the old Master
PIN or smart card PIN except in the case of a BOS terminal in which case the new PIN is ignored and the
ME resets the PIN retry counter using the PUK.
This command is supported on Logical Port 1 and Logical Port 2.
Execution Syntax
AT+CPIN=<pin>[,<newpin>]
Defined Values
Field Values Remark
<pin> up to 8 decimal digits Radio 'Master PIN' can be up to 4 digits
Radio 'Master Reset PIN' can be up to 8 digits
Smart card 'PIN' can be up to 8 digits
Smart card 'PUK' can be up to 8 digits
<newpin> up to 8 decimal digits Radio 'Master PIN' can be up to 4 digits
Set Syntax
N/A
Read Syntax
AT+CPIN?
Test Syntax
AT+CPIN=?
Execute Response
OK
Or the following error codes:

Description Error Code
Command not valid in current state +CME ERROR: 3 (Operation not allowed)
Smart card required and not inserted +CME ERROR: 10 (SIM not inserted)
Failure accessing smart card +CME ERROR: 13 (SIM failure)
Smart card present but not recognised or blocked +CME ERROR: 15 (SIM wrong)
Password invalid +CME ERROR: 16 (Incorrect password)

MOD-14-1758
Read Response
+CPIN: <code>
OK

Smart card required and not inserted +CME ERROR: 10 (SIM not inserted)
Failure accessing smart card +CME ERROR: 13 (SIM failure)
Smart card present but not recognised or blocked +CME ERROR: 15 (SIM wrong)
Defined Values
Field Values Remark
<code> READY MT is not waiting for any password
RADIO PIN MT is waiting for Radio 'Master PIN'
RADIO PUK MT is waiting for Radio 'Master Reset PIN'
SIM PIN MT is waiting for Smart card 'PIN'
SIM PUK MT is waiting for Smart card 'PUK'
Test Response
<cr><lf>+CPIN: (0-99999999),(0-99999999)
<cr><lf>OK<cr><lf>
Example
AT+CPIN?<cr>
<cr><lf>
+CPIN: RADIO PIN<cr><lf>
<cr><lf>OK<cr><lf>
AT+CPIN=9876<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.27 AT+CREG - Registration Status
Source
TS 100 916 section 7.2
[6] 6.11.3
Description
Using the Read Syntax causes the terminal to return the registration state. The Set Syntax can enable the
terminal to send unsolicited responses indicating a change of registration state, e.g. if the terminal
becomes unregistered, the terminal will send an unsolicited +CREG message indicating this. The
unsolicited responses will be disabled during data mode.
It will return the registration state in any call state during command mode.
Execution Syntax
N/A
Set Syntax
AT+CREG=<Value>
Read Syntax
AT+CREG?
Test Syntax
AT+CREG=?
Where <value> is defined as :

0 Disable network registration unsolicited result codes
1 Enable network registration unsolicited result codes on status change
2 Enable network registration unsolicited result codes on every location area change
Default
0
Read Response when PEI Compliance Level [8154] is 0

+CREG <registered status>[, <LA>[, <MNI>]]<cr><lf>
unless the terminal is in DMO mode, then
+CME ERROR: 513
When the product is operating as a DMO Gateway, all parameters apply to the TMO service
where <registered status> is defined as :

0 Not registered and not searching
1 Registered home network
2 Not registered, but currently searching
3 System Reject
<LA> is the decimal number of the Location Area
<MNI> is the Mobile Network Identity (expressed as exactly three decimal digits of Country Code followed
by exactly four decimal digits of Network Code)

MOD-14-1758
Read Response when PEI Compliance Level [8154] is 1

When the terminal is in DMO mode, then +CME ERROR 40
When the product is operating as a DMO Gateway, all parameters apply to the TMO service.
where <registered status> is defined as :

0 Registering or searching a network, one or more
networks are available;
1 Registered home network
2 Not registered, no network currently available
3 System Reject
Note that the definitions of values 0 and 2 are each different to those defined when PEI
Compliance Level [8154] is 0
<LA> is the decimal number of the Location Area
<MNI> is the Mobile Network Identity (expressed as exactly three decimal digits of Country Code followed
by exactly four decimal digits of Network Code)

+CREG: (list of Reg Unsolic values)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CREG: (0-2)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CREG?<CR>
<cr><lf>+CREG: 1, 1000, 2342400<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.28 AT+CSPBOPTA - BOS Read Smart Card OPTA
Source
Description
This command reads the OPTA from a BOS terminal with a smart card. It is not supported on non-BOS-
Digital terminals.
Execution Syntax
N/A
Set Syntax
N/A
Read Syntax
AT+CSPBOPTA?
Test Syntax
AT+CSPBOPTA=?
Read Response
State Response
OPTA from BOS smart card available in terminal <cr><lf>+CSPBOPTA: <OPTA text>
<cr><lf>OK<cr><lf>
SIM not inserted +CME ERROR: 10
(SIM not inserted)
PIN required +CME ERROR: 11
(SIM CHV1 required)
PUK required +CME ERROR: 12
(SIM Unblocking CHV1 required)
Unable to read OPTA from smart card +CME ERROR: 13
(SIM failure)
SIM unrecognised, disabled or failed to authenticate +CME ERROR: 15
(SIM wrong)
Defined Values
Field Values Remark
<OPTA text> Up to 24 characters OPTA from BOS smart card, encoded according
to parameter Hayes Text Format, [8152]
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CSPBOPTA?<cr>
<cr><lf>
+CSPBOPTA: aaaaaaaaaaaaaaaaaaaaaaaa<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.29 AT+CSPSCTR Smart Card Text Reports
Source
This command is proprietary to Sepura.
Description
This is a non-standard form of the set command that will allow a terminal enable or disable the reporting of
information generated by a smart card.
This command is supported on Logical Port 1.
Execution Syntax
None
Set Syntax
AT+CSPSCTR=<TextRep Unsolic>
Read Syntax
AT+CSPSCTR?
Test Syntax
AT+CSPSCTR=?
Set Response
<cr><lf>OK<cr><lf>
Read Response
+CSPSCTR=<TextRep Unsolic><cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CSPSCTR: (0-1)<cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
Field Values Remark
<TextRep Unsolic> 0 or 1 0 – ‘Disable smart card text reports’ (default)
1 – ‘Enable smart card text reports’
Example Enable smart card text reports

AT+CSPSCTR=1<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.30 AT+CSPDCS - DMO Connectivity Status
Source
Description
Controls the unsolicited reporting of, and the solicited reading of, the availability of connectivity via a DMO
Gateway or DMO Repeater.
Execution Syntax
N/A
Set Syntax
AT+CSPDCS=<value>
Defined Values
<value>
0 Disable unsolicited DMO connectivity status reports
1 Enable unsolicited DMO connectivity status reports
Default
<value>
0 Disable unsolicited DMO connectivity status reports
Read Syntax
AT+CSPDCS?
Test Syntax
AT+CSPDCS=?
Read Response
+CSPDCS: <DMO Gateway>,<DMO Gateway restrictions>,<DMO Repeater>
Defined Values
where
<DMO Gateway> is the availability of a DMO Gateway with sufficient signal strength and a valid Usage
Restriction Type and Validity Time
<DMO Gateway restrictions> indicates the restrictions that may apply to services available via a detected
DMO Gateway
<DMO Repeater> is the availability of a DMO Repeater with sufficient signal strength and a valid Usage
Restriction Type and Validity Time
<DMO Gateway>
0 Not detected
1 Detected and usable
2 Detected but filtered
<DMO Gateway restrictions>

0 No restriction
1 SwMI not present

MOD-14-1758
<DMO Repeater>
0 Not detected
Test Response
+CSPDCS: (0-1)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CSPDCS?<cr>
+CSPDCS: 0,1,0<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.31 AT+CSPICPN - Incoming Call Proprietary Extensions Notification Command
Source
Description
This command enables and disables the generation of the +CSPICP unsolicited report, see 7.2.13
Execution Syntax
N/A
Set Syntax
AT+CSPICPN=<value>
Read Syntax
AT+CSPICPN?
Read Response Syntax

+CSPICPN: <value>
OK
Test Syntax
AT+CSPICPN=?
Defined Values
<value> is:
0 Disabled
1 Enabled
Test Response
+CSPICPN: (0-1)
OK

MOD-14-1758
7.1.32 AT+CSPKA Key agreeement
Source
Description
This command will cause a BOS-digital terminal to initiate a key agreement to update the E2EE keys
stored on the smart card.
Execution Syntax
None
Set Syntax
AT+CSPKA=<key request command>
Read Syntax
None
Test Syntax
AT+CSPTAA7=?
Set Response
State Response
Key agreement successfully initiated <cr><lf>OK<cr><lf>
Key agreement could not be initiated +CME ERROR: 3
Test Response
+CSPKA: (0-1)<cr><lf>
<cr><lf>OK<cr><lf>
Unsolicited Response
None
Defined Values
Field Values Remark
<key request command> 0 or 1 0 – Cancel key agreement
1 – ‘Start key agreement’
Example
AT+CSPKA=1<cr>
<cr><lf>OK<cr><lf> (key agreement then proceeds)

MOD-14-1758
7.1.33 AT+CSPLOGIO - Log In / Log Out Command
Source
Description
Send log in or log off commands to authentication server or request current authentication status to
support procedures specified in [8].
This command is supported on logical port 1 and logical port 2
Execution Syntax
AT+CSPLOGIO=<mode>[,<rui>[,<ru-pin>]]
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+CSPLOGIO=?
Execute Responses
If Logon or Logoff requested and command not valid in current terminal state (in DMO for example)
<cr><lf>+CME ERROR: 3 (Operation not allowed)
If Logon alpha-numeric information is supplied but numeric information required by logon command
<cr><lf>+CME ERROR: 33 (Parameter wrong type)
If Logon or Logoff requested and command accepted, action initiated and request sent
<cr><lf>OK<cr><lf>
If Query Status requested, see +CSPLOGIO unsolicited responses for returned format.
Test Response
<cr><lf>OK<cr><lf>
Defined Values
Element Values Remark
<mode> 0-2 0 = Logon
1 = Logoff
2 = Query Status
<rui> Up to 24 characters Radio User Identity, encoded according to parameter
Hayes Text Format, [8152]
Required if <mode> is 'Logon'
<ru-pin> Up to 7 characters Radio User PIN, encoded according to parameter
Example
AT+CSPLOGIO=0,USER 01,11223<cr> request logon
<cr><lf>OK<cr><lf> logon request sent

MOD-14-1758
7.1.34 AT+CSPRTC - Time Server Synchronisation
Source
Description
Set or read the date, UTC time, and local time offset to UTC held by the time server.
Execution Syntax
N/A
Set Syntax
AT+CSPRTC=<UTC seconds since 00:00:00 Jan 1st>,<year>,<local time offset sign>,<local time offset>
Read Syntax
AT+CSPRTC?
Test Syntax
AT+CSPRTC=?
Defined Values
<UTC seconds> 0-31535999 (for normal years)
0-31622399 (for leap years)
<year> 2000-2255
<local time offset sign> -,+
<local time offset> 0-840 in minutes
Set Response
<cr><lf>OK<cr><lf> Command was accepted
+CME ERROR: 34 value(s) out of range
Read Response
+CSPRTC: [<UTC seconds since 00:00:00 Jan 1st>],[<year>],<local time offset sign>,<local time offset>
<cr><lf>OK<cr><lf>
The UTC time and year fields are empty if the timer server has never been synchronised.

+CSPRTC: (UTC seconds since 00:00:00 January 1st),(year),(local time offset sign),(local time offset)
<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CSPRTC: (0-31622399),(2000-2255),(-,+),(0-840) <cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CSPRTC=7776001,2005,+,0<cr>
<cr><lf>OK<cr><lf>
AT+CSPRTC? <cr>
+CSPRTC: 7776001,2005,+,0 <cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.35 AT+CSPSCS Smart Card Status
Source
Description
This is a non-standard form of the set command that will allow a BOS-digital or Sectra E2EE smart card
terminal to have the reporting of status information generated by a smart card enabled or disabled.
Execution Syntax
None
Set Syntax
AT+CSPBSCS=<StatusRep Unsolic>
Read Syntax
AT+CSPBSCS?
Test Syntax
AT+CSPBSCS=?
Set Response
<cr><lf>OK<cr><lf>
Read Response
+CSPBSCS=<StatusRep Unsolic><cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CSPBSCS: (0-1)<cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
Field Values Remark
<StatusRep Unsolic> 0 or 1 0 – Disable smart card status reports (default)
1 – Enable smart card status reports
Example Enable smart card status reports

AT+CSPBSCS=1<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.36 AT+CSPTAA1 - Application Action 1 - Radio Switch Off
Source
Description
This command aborts any calls that are in progress and performs a normal switch off. There is no
converse AT command for switching the radio on again as this involves a hardware signal.
Execution Syntax
AT+CSPTAA1
Set Syntax
None
Read Syntax
None
Test Syntax
AT+CSPTAA1=?
Execution Response
<cr><lf>OK<cr><lf>
Test Response
<cr><lf>OK<cr><lf>
Example Switch Radio Off

AT+CSPTAA1<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.37 AT+CSPTAA2 - Softkey Action
Source:
Description:
Execute the appropriate action as if that soft key had been pressed. Can be used even when the soft key
function has not been allocated to a physical soft key.
This command is supported on logical port 1.
Execution Syntax
AT+CSPTAA2=<soft_key_function>
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+CSPTAA2=?
Execute Responses
If valid soft_key_function: <cr><lf>OK<cr><lf> (Note that this positive confirmation is only that the softkey
function has been requested)
or the following error condition:
Requested soft key function is not +CME ERROR: 34
allowed (Value out of range)
Cannot initiate Quick Call if already in +CME ERROR: 3
Alarm Call (AT command not recognised or out of context)
Speech Service Profile is set to 'Both'
Quick Call requested but terminal in TxI +CME ERROR 512
Alarm Call requested, terminal in TxI (Service not available)
and Alarm Call in TxI not allowed
Alarm or Quick Call requested but not +CME ERROR 513
allowed (disabled) in DMO (Service not supported in DMO)
Alarm or Quick Call requested but not +CME ERROR 514
allowed (disabled) in TMO (Service not supported in TMO)
Quick Call requested but terminal in +CME ERROR 519
DMO Gateway mode (Service not supported by DMO Gateway)
Test Response
+CSPTAA2: (10,143) <cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
Defined Values
Field Value
<soft_key_function> 10 = Emergency soft key function
143 = Quick Call soft key function
Note that for Emergency and Quick Calls, this command is not used to end the call (use ATH).
Example
AT+CSPTAA2=143<cr> request Quick Call
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.38 AT+CSPTAA3 - Licensed Soft Key Functions
Source
Description
This command executes the appropriate action as if that soft key had been pressed. This command may
be used even when the soft key function has not been allocated to a physical soft key.
This command is only supported on logical port 1.
This command is licensed by Part Number 600-00037, Soft key function via PEI
Execution Syntax
AT+CSPTAA3=<soft_key_function>
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+CSPTAA3=?
Execute Response
If the 'AT Softkeys' feature is not licensed then this command is rejected with CME ERROR: 4 (Operation
not supported).
Otherwise: <cr><lf>OK<cr><lf>
Note that this positive confirmation is only that the soft key function has been requested; even when
the requested function performs no action or subsequently fails to complete an action.
Test Response
+CSPTAA3: (0-255) <cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
<soft_key_function> 0 None
1 Last Call re-dial
4 Keypad lock select/de-select
5 Clear All (Return to Top Level Screen)
7 Volume Up
8 Volume Down
10 Alarm
11 Increment talk group
12 Decrement talk group
13 Trunked Mode/Direct Mode Toggle
Dialling Mode Selection – Cycle Through Programmed Dialling
14
Modes
15 Toggle Fast Access Mode
16 Pulse External Alert DO1
17 External Alert On / Off
18 Alert Enable
20 Navigate to card #1

MOD-14-1758

24 Home Group Select
25 Invert Display Toggle
26 Reject or Exit From Call
27 Quick Status Message 1
30 Toggle Scanning Mode
31 Toggle Display Mode (Large/Normal)
32 Hands Free
52 Accessory Public State Toggle
61 Report Position to PEI1
Enable/Disable Continuous Position Reports to PEI1 - only if in
62
Car Kit
63 Set default Service definition for PEI1
65 Quick Group 1 Select
70 Last Requested Group Toggle
71 Switch stack to DMO
72 Switch Stack to TMO
73 Switch stack to Repeater
76 Tone Signalling
77 Zeroise
78 Transmit Inhibit Toggle
82 Loudspeaker On/Off
84 Preemptive PTT
88 Sequence 1
89 Sequence 2
90 Sequence 3
91 Sequence 4
92 Activate Transmit Inhibit
93 Deactivate Transmit Inhibit
96 Save All Data
97 Generate Paging Alert
98 Discreet quick status 1 (status value for AL call request)
99 Discreet quick status 2 (status value for AL emergency call

MOD-14-1758

request)
100 Normal Operation User Profile
101 User Profile 2
102 User Profile 3
103 User Profile 4
104 User Profile 5
105 User Profile 6
106 User Profile 7
107 User Profile 8
108 User Profile 9
109 User Profile 10
110 Do Not Disturb
111 Goto WAP Homepage
112 Goto WAP Bookmarks
113 Goto WAP Browser Menu
114 Goto WAP Help
115 Goto WAP Browse
117 Bluetooth On / Off
118 Bluetooth Headset Connect / Disconnect
119 Display Missed Event Information box
120 Start Key Agreement
121 Toggle E2EE State
133 Man Down Alert and Man Down Alarm Clear
134 Man Down Toggle soft key
136 ‘Send’ (green) key TLS Quick Status
137 ‘Clear’ (red) key TLS Quick Status
140 Toggle Accessory Audio State
141 Menu option
142 Talkgroup folder option
144 Stop Key Agreement
145 TMO Cryptomode Normal
146 TMO Cryptomode 3 Master/Auto
147 TMO Cryptomode 3 Master/Man
148 TMO Cryptomode 3 Slave
149 DMO Cryptomode 1
150 DMO Cryptomode 2
151 DMO Cryptomode 3 Master/Auto
152 DMO Cryptomode 3 Master/Man
153 DMO Cryptomode 3 Slave
194 Press PTT - see Note 1
195 Release PTT - see Note 1
196 Mute Internal Loudspeaker and Internal Earpiece - see Note 1
197 Unmute Internal Loudspeaker and Internal Earpiece - see Note 1
198 Enable portable line output - see Note 1
199 Disable portable line output - see Note 1
200 Key Press Vibration Alert Toggle
201 Select Next Language
202 Select First Language
203 Select Second Language

MOD-14-1758

223 Smart Menu 1
224 Smart Menu 2
225 Smart Menu 3
226 Smart Menu 4
227 Smart Menu 5
228 Smart Menu 6
229 Smart Menu 7
230 Smart Menu 8
231 Smart Menu 9
232 Smart Menu 10
233 Smart Menu 11
234 Smart Menu 12
235 Smart Menu 13
236 Smart Menu 14
237 Smart Menu 15
238 Smart Menu 16
239 Smart Menu 17
240 Smart Menu 18
241 Smart Menu 19
242 Smart Menu 20
Only the listed values are supported via the AT commands and users are advised not to use unlisted
values.
Note 1: These commands are not toggle functions.

For example command Press PTT '194' will press and hold the PTT. A subsequent '194' is ignored
as the PTT is already pressed. To release the PTT use the '195' command. When an application
is using these commands it is recommended that a '195' command is sent whenever the external
controller connects to ensure the PTT is in a known state.
If this PTT Press soft key function has been activated without a subsequent PTT Released soft
key function being activated, any further activation of the PTT Pressed soft key function performs
no action.
key function being activated, any pressing of any other PTT, whether on the product or one of its
accessories, performs no action.
key function being activated, any release of any other PTT, whether on the product or one of its
accessories, performs no action.
A similar situation exists for mute loudspeaker and line output functionality.
The ‘Mute Internal Loudspeaker and Internal Earpiece’ soft key function ‘196’ stops all audio
(including alert tones) emanating from the portable product’s internal loudspeaker and internal

MOD-14-1758
earpiece. This soft key function acts independently of the ‘Loudspeaker on/off’ soft key function
‘82’ and the Loudspeaker On/Off Card in the radio settings subject file. This soft key function does
not change any other audio output (e.g. to a car kit’s loudspeaker or an accessory’s earpiece).
For example, following a ‘Mute Internal Loudspeaker and Internal Earpiece’ soft key function any
operation of the ‘Loudspeaker on/off’ soft key function or the Loudspeaker On/Off Card in the
radio settings subject file changes the selection in the Loudspeaker On/Off Card and changes the
icon on the display but has no effect on the audio at the loudspeaker or earpiece until the ‘Unmute
Internal Loudspeaker and Internal Earpiece’ soft key function has been activated.
This ‘Enable Line Output’ soft key function ‘198’ has no function on a mobile product.
Otherwise, this ‘Enable Line Output’ soft key function enables received audio (including alert
tones) to emanate from the portable product’s Line Output connection on the Facility connector,
irrespective of the operational state of the radio or any audio routing.
The signal level on this Line Output connection is independent of the setting of the product’s
volume control and of any other controls which affect audio volume (such as covert mode).
Example
AT+CSPTAA3=194<cr> Press (and hold down) PTT
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.39 AT+CSPTAP1 - Application Parameter 1 - Scanning On / Off
Source
Description
This command allows the scanning state context data parameter to be read and set by the TE. The effect
of changing the scanning state via this command is the same as if the change had been made from either
the user interface or by the soft key toggle function.
Execution Syntax
None
Set Syntax
AT+CSPTAP1=<Scanning State>
Defined Values
<Scanning State> 0 or 1 0 = Scanning Off
1 = Scanning On
Read Syntax
AT+CSPTAP1?
Test Syntax
AT+CSPTAP1=?
Set Response
<cr><lf>OK<cr><lf>
Read Response
+CSPTAP1: <Scanning State><cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CSPTAP1: (0-1)<cr><lf>
<cr><lf>OK<cr><lf>
Example Scanning turned on

AT+CSPTAP1=1<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.40 AT+CSPTAP16 - Application Parameter 16 (BOS DMO Cryptomode)
Source
Description
This command allows the BOS DMO E2EE Cryptomode context data parameter to be read and set by the
TE. The effect of changing the DMO cryptomode via the AT+CSPTAP16 command is the same as if the
change had been made from the user interface.
The command name includes an application parameter number so that it is extensible to support other
arbitrarily numbered radio application parameters in the future. This approach is taken rather than having
a parameter identifier field so that the normal read and test syntaxes can be used.
Execution Syntax
None
Set Syntax
AT+CSPTAP16=<DMO Cryptomode>
Defined Values
<DMO Cryptomode> 1-2 1 = Mode 1
2 = Mode 2
Read Syntax
AT+CSPTAP16?
Test Syntax
AT+CSPTAP16=?
Set Response
State Response
DMO cryptomode successfully changed <cr><lf>OK<cr><lf>
DMO cryptomode could not be changed +CME ERROR: 3
Read Response
<cr><lf>+CSPTAP16: <DMO Cryptomode><cr><lf>
<cr><lf>OK<cr><lf>
Test Response
<cr><lf>+CSPTAP16: (1-2)<cr><lf>
<cr><lf>OK<cr><lf>
Example Change to DMO Cryptomode 2

AT+CSPTAP16=2<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.41 AT+CSPTAP17 - Application Parameter 17 (BOS E2EE Enable)
Source
Description
This command allows the BOS Selected E2EE State context data parameter to be read and set by the TE.
The effect of changing the Selected E2EE State via the AT+CSPTAP17 command is the same as if the
Execution Syntax
None
Set Syntax
AT+CSPTAP17=<E2EE State>
Defined Values
<E2EE State> 0-1 0 = E2EE disabled (Selected E2EE State = Off)
1 = E2EE enabled (Selected E2EE State = On)
Read Syntax
AT+CSPTAP17?
Test Syntax
AT+CSPTAP17=?
Set Response
State Response
E2EE state successfully changed <cr><lf>OK<cr><lf>
E2EE state could not be changed +CME ERROR: 3
Read Response
<cr><lf>+CSPTAP17: <E2EE State><cr><lf>
<cr><lf>OK<cr><lf>
Test Response
<cr><lf>OK<cr><lf>
Example Disable E2EE

AT+CSPTAP17=0<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.42 AT+CSPTAP18 Application Parameter 18 (BOS SDS Encryption Key)
Source
Description
This command allows the BOS SDS Encryption Key context data parameter to be read and set by the TE.
The effect of changing the SDS Encryption Key via the AT+CSPTAP18 command is the same as if the
Execution Syntax
None
Set Syntax
AT+CSPTAP18=<SDS Encryption Key>
Defined Values
<SDS Encryption Key> 0-2 0 = Clear
1 = TK-TMO
2 = TK-SM
Read Syntax
AT+CSPTAP18?
Test Syntax
AT+CSPTAP18=?
Set Response
<cr><lf>OK<cr><lf>
Read Response
<cr><lf>+CSPTAP18: <SDS Encryption Key><cr><lf>
<cr><lf>OK<cr><lf>
Test Response
<cr><lf>OK<cr><lf>
Example Use TK-TMO

AT+CSPTAP18=1<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.43 AT+CSPTGF - Talk Group Folders
Source
Description
Lists all enabled talk group folders in the terminal.
Only folders at the top level in the structure are listed.

Folder numbers 1 to 200, F201 to F250 equate to folder numbers in the range 1 to 250 (as defined in
Radio Manager).
No folders outside this range are listed.
Execution Syntax
N/A
Set Syntax
N/A
Read Syntax
AT+CSPTGF?
Test Syntax
AT+CSPTGF=?
Read Response
+CSPTGF: <always attached folder>,<cr><lf>
<folder number>,<folder name>[,<cr><lf>
<folder number>,<folder name>,<cr><lf>]
…
[<folder number>,<folder name>]<cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
<always attached 0 0 always attached folder not configured
folder> 1-200 #, F# the folder number of the always attached
3000 / 8000 Series folder
terminals add:
F201-F250
<folder number> 0-203 0 Favourites
3000 / 8000 Series 1 Folders 1
terminals add: 2 Folders 2
F201-F250 . . (#) Folder #
200 Folders 200
F201 Folder 201
F202 Folder 202
. . (F#) Folder #
F250 Folder 250
201 All
202 DGNA
203 UDSL
<folder name> Up to 16 characters talk group folder name

MOD-14-1758
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CSPTGF? <cr>
+CSPTGF: 0,<cr><lf>
0,Favourites,<cr><lf>
1,OPS1,<cr><lf>
2,SURV1,<cr><lf>
3,DMO1,<cr><lf>
4,DMO2,<cr><lf>
201,ALL<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.44 AT+CSPTGFC - Talk Group Folder Configuration
Source
Description
This command lists all enabled and disabled talk group folders in the terminal including talk group
membership of folders, and allows you to read and set the required attributes.
Only folders at the top level in the structure are listed

Radio Manager).
No folders outside this range are listed.
If the set operation on a Folder Number results in the creation of a new generic talk group folder, that talk
group folder will be positioned as the last top level generic folder.
If the set operation changes the Enable Attribute or the Visible Attribute of a folder, this only changes
these attributes for the Folder Number in the request, not for any child folders of the Folder Number.
Execution Syntax
N/A
Set Syntax
AT+CSPTGFC=<Folder Number>, [<Folder Name>], [<Enable Attributes>], [<Edit Attributes>], [<Visible
Attributes>], [, <Talkgroup 1 Index> [, <Talkgroup 2 Index>, [… [, <Talkgroup max index>]…]]]
Where:
Folder Number 0-200 0 Favourites
3000 / 8000 Series 1 Folder 1
terminals add: 2 Folder 2
F201-F250 . . (#) Folder #
200 Folder 200
F201 Folder 201
F202 Folder 202
. . (F#) Folder #
F250 Folder 250
If the Folder Number has not previously been
configured in the terminal the successful ‘Set’
operation will result in the creation of the folder with
the relevant names and attributes.
Folder Name 16*(8 bit Characters) Talk Group Folder Name
The absence of this value in the Set Syntax will cause
the corresponding Folder Name to remain
unchanged.
If New folder being created and no name provided
then the default name of the folder will be the Textual
value of the folder number preceded by the letters
‘TGF’, e.g. Folder no 151 will have a name “TGF151”
Enable Attributes 'True', 'False' This element sets or un-sets the Enable folder
attribute, as per bit zero in the Talk group Folder
Attribute parameter [3805.n]
The absence of this attribute in the Set Syntax will
cause the corresponding folder attribute to remain
unchanged.
If the ‘Set’ command results in a Folder being created

MOD-14-1758

then the absence of this attribute will result in the
attribute being set to the default value associated with
the corresponding bits in the Talk group Folder
Attribute parameter [3805.n].
The ‘Background’ Folder (index = 204) cannot have
its Enable Attribute set to ‘True’.
Edit Attributes 'True', 'False' This element sets or un-sets the Enable folder
attribute, as per bit two in the Talk group Folder
unchanged.
The combination of the ‘Edit’ & ‘Visible’ attributes is
such that if ‘Edit’ Attribute is set to ‘True’ then the
‘Visible’ attribute must be set to ‘True’
Only folders with the index value in the range 0-200
can have this value set to ‘True’.
Visible Attributes 'True', 'False' This element sets or un-sets the Enable folder
attribute, as per bit two in the Talk group Folder
unchanged.
The combination of the ‘Edit’ & ‘Visible’ attributes is
such that if ‘Edit’ Attribute is set to ‘True’ then the
‘Visible’ attribute must be set to ‘True’
Talk Group i Index 1-2000 Talk Group Index (See AT+CSPTGI) where i ranges
2001-2050 (DGNA) from 1 to 75 i.e. there can be up to 75 Talk Groups in
T2001-T3000/T9900* a Talk Group Folder.
Note: The list of Talk Group Indexes will be the
content of the resulting Talk Group Folder, providing
the command succeeds.
If no groups are provided in the Set Command, this
will result in the removal of groups from that folder.
*Talk Group i Index: T2001-T3000 for SRH3500 series, SRH3800 series, SRC3000 series, SRM3500
and SRG3500
T2001-T9900 for SRH3900 series, STP8000 series and SRG3900 series.
Read Syntax
AT+CSPTGFC?
Test Syntax
AT+CSPTGFC=?
Read Response
+CSPTGFC: <always attached folder>,<cr><lf>
<folder number>,<folder name>[,<talkgroup 1 index>]…[,<talkgroup max index>][,<cr><lf>
<folder number>,<folder name>[,<talkgroup 1 index>]…[,<talkgroup max index>],<cr><lf>]

MOD-14-1758
… [<folder number>,<folder name>[,<talkgroup 1 index>]…[,<talkgroup max index>]]<cr><lf>

<cr><lf>OK<cr><lf>

<always attached 0, 1-200 0 always attached folder not configured
folder> 3000 / 8000 Series #, F# the folder number of the always attached
terminals add: folder
F201-F250
F201-F250 . . (#) Folder #
200 Folder 200
F201 Folder 201
F202 Folder 202
. . (F#) Folder #
F250 Folder 250
201 All
202 DGNA
203 UDSL
<folder name> Up to 16 characters talk group folder name
<talkgroup i index> 1-2000, talk group index (see AT +CSPTGI)
2001-2100 where i ranges from 1 to max, and max is:
T2001-T3000/T9900* 75 for Folder = Favourites or Folder #
2050 for Folder = All
50 for Folder = DGNA
10 for Folder = UDSL
*<talkgroup I index>: T2001-T3000 for SRH3500 series, SRH3800 series, SRC3000 series, SRM3500
and SRG3500
Test Response
<cr><lf>OK<cr><lf>
Set Response
<cr><lf>OK<cr><lf>
One or more of the ‘Folder Number’, ‘Enable Attribute’, ‘Edit
Attribute’, ‘Visible Attribute’ & ‘Talk Group i Index’ elements is out +CME ERROR: 34
of range.
The ‘Editable’ value is set to ‘True’ whilst the ‘Visible’ attribute is
not set to ‘True’.
The Set command has attempted to enter groups into the ‘All’,
‘DGNA’, ‘UDSL’ or ‘Background’ folders.
The Set command attempted to insert more than the maximum
number of groups permissible for the corresponding Talk group +CME ERROR: 4
folder number.
The Set command attempted to set the enable attribute on the
background folder
The Set command attempted to set make the ‘All’, ‘DGNA’,
‘UDSL’ or ‘Background’ folders editable.
Example
AT+CSPTGFC? <cr>
+CSPTGFC: 0,<cr><lf>
0,Favourites,1,2,<cr><lf>

MOD-14-1758
1,OPS1,2,3,<cr><lf>
2,SURV1,3,2,<cr><lf>
3,DMO2,4,1,<cr><lf>
4,DMO1,3,4,2,<cr><lf>
201,ALL,1,2,3,4<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.45 AT+CSPTGFS - Group Folder Select
Source
Description
This command is used to set/read the folder on the RCU/MCU. It selects an enabled talk group folder and
reads the currently selected folder. The Set command changes the RCU talk group folder and also the
shown in the FAB on the UI as confirmation that the Set command has succeeded. The Read command
returns only the RCU talk group folder, regardless of whether there is an RCU currently attached. Note
that changing the talk group folder via the terminal UI with no RCU/MCU attached does not change the
selected RCU folder.
Radio Manager).
The 'Current' folder is not reported if it is outside of this range.
Folders may be anywhere in the folder structure.
If the terminal UI is not locked by an attached RCU or MCU, a talk group folder selection is followed by an
attachment request/selection of the first talk group in the folder. The terminal will automatically change to
Trunked mode or Direct mode depending on the type of talk group to be requested.
If the terminal UI is locked by an attached RCU or MCU, the talk group to be requested is indicated by the
rotary knob position (RCU) or displayed value (MCU).
If no valid talk group can be requested, the currently selected folder and talk group (before the folder
change) is not lost.
If the terminal is operating in gateway mode, talk group folder selection takes place as described above
only after the user exits gateway mode.
Execution Syntax
N/A
Set Syntax
AT+CSPTGFS=<folder number>
where <folder number>, see defined values below.
Set Response
+CSPTGFS: <folder number><cr><lf><cr><lf>OK<cr><lf>
if folder was selected
or one of the following error conditions:

Requested folder does not exist or is
+CME ERROR: 34
disabled
PEI Compliance Level [8154] is 0 +CME ERROR: 515
In service – but TX inhibited (Transmissions are inhibited)
PEI Compliance Level [8154] is 1 +CME ERROR: 41
In service – but TX inhibited (Transmissions are inhibited)

MOD-14-1758
Read Syntax
AT+CSPTGFS?
Read Response
The folder on the Fast Access Box is always returned, if any.
+CSPTGFS: [<folder number>]<cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
F201-F250 . . (#) Folder #
200 Folder 200
F201 Folder 201
F202 Folder 202
. . (F#) Folder #
F250 Folder 250
201 All
202 DGNA
203 UDSL
Test Syntax
AT+CSPTGFS=?

+CSPTGFS: (range of valid <folder number>s)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CSPTGFS: (0-203,F201-F250)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CSPTGFS=1 <cr>
+CSPTGFS: 1,<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.46 AT+CSPTGG - Set or Read groups when operating in Gateway Mode
Source
This command is only valid when the radio is operating in Gateway Mode where it is used to set or read
the DMO and TMO group that is in use by the Gateway. In all other operating modes the radio returns an
error code. In all situations, the solicited response identifies the groups that are attached after negotiation
with the infrastructure.
Execution Syntax
N/A
Set Syntax
AT+CSPTGG=<DMO count>, <TMO count>[, <DMO GTSI 1> [... , <DMO GTSI n>]]
[, <group type 1>, <GSSI 1> [...,<group type m>, <GSSI m>]]
The DMO GTSI must be one that is defined as a DMO group. Only one DMO GTSI is supported by the
software specified here. The frequency used for the DMO transmissions and reception and Talk Group
Alias Text are the ones associated with the first DMO talkgroup with a matching value of GTSI. The TMO
GSSI and Group Type have the same meaning as used in the AT+CTGS command in TMO. At least one
group (either DMO or TMO) must be specified. If either count is zero, the corresponding (TMO or DMO)
groups are not changed from their previous values.
Read Syntax
AT+CSPTGG?
Test Syntax
AT+CSPTGG=?
Response
+CSPTGG: <DMO count>, <TMO count>[, <DMO GTSI 1> [,<cr><lf>
<DMO GTSI n>...]] [,<cr><lf>
<group type 1>, <GSSI 1> [,<cr><lf>
<group type m>, <GSSI m>...]]<cr><lf>
Error Responses
Compliance Level is 0 Compliance Level is 0
+CME ERROR: 513 +CME ERROR: 40
In Direct Mode
(Service not supported in DMO) (Service not supported in DMO)
In Trunked Mode
(Service not supported in TMO) (Service not supported in TMO)
In Gateway Mode, but DMO GSSI +CME ERROR: 4 +CME ERROR: 4
specified is not known to the MT (Operation not supported) (Operation not supported)
In Gateway Mode, but more than +CME ERROR: 4 +CME ERROR: 4
one DMO GSSI specified (Operation not supported) (Operation not supported)
In Gateway Mode, but both counts
(DMO GTSIs and TMO GSSIs) are
(Operation not supported) (Operation not supported)
zero
radio not in TMO service
In service - but the request
contains more than one TMO
(Operation not supported) (Operation not supported)
group which is of type 1 (selected)

MOD-14-1758
In gateway mode, but at least one

TMO GSSI specified is not known
(Parameter value out of range) (Parameter value out of range)
to the MT
In service, but unable to process
Group Attachment (e.g. because a +CME ERROR: 512 +CME ERROR: 42
group attachment is already being (Service not available) (Service not available)
processed)
The parameters <DMO count> and
<TMO count> do not match the +CME ERROR 32 +CME ERROR 32
quantity of the following (Error decoding data) (Error decoding data)
parameters
Defined Values
<DMO count> is a number indicating how many instances of <DMO GTSI> follow. It has a range
of 0 to 1.
<TMO count> is a number indicating how many instances of the <Group Type> and <GSSI>
parameter pairs follow for TMO attachments. It has a range of 0 to 10.
<DMO GTSI> This is a 15-digit number where the most significant 3 digits are the MCC, the next
4 digits are the MNC and the final 8 digits are the GSSI
<GSSI> is as defined for +CTGS
<Group Type> is as defined for +CTGS
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CSPTGG?<cr>
<cr><lf>+CSPTGG: 1,2,234710000080000,<cr><lf>
1,40411,<cr><lf>
2,40432<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.47 AT+CSPTGI - Talk Group Information
Source
Description
Retrieve information on all talk groups available to the terminal, which are members of a specified folder.
Radio Manager).
Folders may be anywhere in the folder structure.
Execution Syntax
AT+CSPTGI=<folder number>
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+CSPTGI=?
Execution response
+CSPTGI: <folder number>[,<cr><lf>
<talkgroup index>,<type>,,,,<number>,,<alias>[,<cr><lf>
<talkgroup index>,<type>,,,,<number>,,<alias>,<cr><lf>]
... [<talkgroup index>,<type>,,,,<number>,,<alias>]]<cr><lf>
<cr><lf>OK<cr><lf>
or the following error condition:

Requested folder does not exist or is
+CME ERROR: 34
disabled
Note the presence of blank comma separated fields for elements not currently supported.

MOD-14-1758
Defined Values
F201-F250 . . (#) Folder #
200 Folder 200
F201 Folder 201
F202 Folder 202
. . (F#) Folder #
F250 Folder 250
201 All
202 DGNA
203 UDSL
<talkgroup index> 1-2000, The unique index of the talk group
2001-2100 (if DGNA) 1-2000 Static talk groups
T2001-T3000/T9900* T2001-T3000/T9900* Static talk groups
2001-2100 Dynamic talk groups (DGNA)
<type> 0 Trunked mode single group
1 Trunked mode user defined scan list
2 Direct mode group
<number> 1-9900, Talk group number
9901-9999 (DGNA) 1-9900 Static talk groups
9901-9999 Dynamic talk groups (DGNA)
<alias> up to 16 characters The talk group alias text
*<talkgroup index>: T2001-T3000 for SRH3500 series, SRH3800 series, SRC3000 series, SRM3500
and SRG3500
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CSPTGI=1 <cr>
+CSPTGI: 1,<cr><lf>
1,0,,,,10,,City Centre,<cr><lf>
12,0,,,,1,,OPS 1,<cr><lf>
34,1,,,,100,,All Groups,<cr><lf>
49,2,,,,5,,DMO 1<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.48 AT+CSPTNI - Get TETRA Network Identities
Source
Description
This command reads details of the networks configured in the terminal.
Execution Syntax
N/A
Set Syntax
N/A
Read Syntax
AT+CSPTNI?
Test Syntax
AT+CSPTNI=?
Read Response
+CSPTNI: <network index>,<network identity text>,<network alias text><cr><lf>
<network index>,<network identity text>,<network alias text><cr><lf>
...
<network index>,<network identity text>,<network alias text><cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
Field Values Remark
<network index> 1 to 30 Index of network within the customisation parameter
lists
<network identity> cccnnnn Mobile Network Identity (MNI) from [1101], where c =
MCC, n = MNC
<network alias text> Up to 16 characters Corresponding Mobile Network Code Alias Wide Text
from [1122], encoded according to parameter Hayes
Text Format, [8152]
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CSPTNI?<cr>
<cr><lf>
+CSPTNI: 1,2347100,City Airport<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.49 AT+CSPTNS - Set TETRA Network
Source
Description
This command selects either the network to be used or automatic network selection.
Execution Syntax
N/A
Set Syntax
AT+CSPTNS=<network index>
Defined Values
Field Values Remark
<network index> 0 to 30 0 = automatic network selection
1-30 = index of network within the customisation
parameter lists to be selected
Read Syntax
AT+CSPTNS?
Test Syntax
AT+CSPTNS=?
Set Response
<cr><lf>OK<cr><lf>
Read Response
<cr><lf>+CSPTNS: <network index>
<cr><lf>OK<cr><lf>
Test Response
<cr><lf>+CSPTNS: (0-30)
<cr><lf>OK<cr><lf>
Example
AT+CSPTNS=0<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.50 AT+CSPTSS - TETRA Stack Select
Source
Description
This is a command that will change the currently active TETRA stack (Trunked Mode, Direct Mode,
Gateway Mode or Repeater Mode) used by the radio.
Set Syntax
AT+CSPTSS=<stack>
Where: <stack> is the stack to be switched to, which can be one of the following numerical values:
1 ‘TMO’
2 ‘DMO’
3 'DMO Gateway'
4 ‘Repeater' (Set, Read, Test)
The following list addresses the situations where the command should not be used:
During a call
If the terminal is in a call, the Set Command is deferred until the call finishes. It is only when the call
finishes that the response is generated.
As with all commands, while waiting for a response no further AT commands are
accepted; including any commands to control the ongoing call.
TXI Mode
If the terminal is in TXI mode the Set Command is used to attempt to change the stack to a TMO stack,
then the Set Command will fail, citing the reason as “Stack change not permitted”. This is because the
terminal is not allowed to generate any AI signalling and the transition between DMO & TMO forces the
terminal to (de)register with the SwMI, which is not permitted. No other action will be performed.
Setting Stack to Current
If the new stack requested is the same as the currently active stack then the terminal will reject the TETRA
Stack Select Set Request with a “Requested stack already active” failure reason. No other action will be
performed.
Stack in the process of being made active
If the terminal’s Change Stack process has been invoked and the new stack is not yet active, the terminal
will respond with an error indicating “Stack change in progress”. No other action will be performed as a
result of this command.
Set Response
If Successful:
<cr><lf>OK<cr><lf>
If unsuccessful:
+CME ERROR: <error code>
Where <error code> is one of the values defined in the following table.
“Requested stack already active” +CME ERROR: 516
“Stack change in progress” +CME ERROR: 517
“<Stack> values out of range” +CME ERROR: 34
“Stack change not permitted” +CME ERROR: 3

MOD-14-1758
The response message is generated as an acknowledgement that the TETRA Stack Select Set command
has been received and that the Stack Change process has been invoked. Any number used, other than
the supported values reported in the TETRA Stack Select Test Response (see below) will result in a
response failure with the “<Stack> values out of range” being cited as the reason.
The response to the TETRA Stack Select Set command will not indicate the starting of the
new stack, but the successful invocation of the product’s stack change process. The
TETRA Stack Select Active Stack Notification message performs the function of informing
the external computer that the new stack is active (see section 0)
Read Syntax
AT+CSPTSS?
Under certain circumstances the terminal will not be able to state what the current active stack is. These
are defined in the following list:
Stack in the process of being made active
If the terminal’s Change Stack process has been invoked and the new stack is not yet active, the terminal
will responds indicating “No Active Stack” otherwise it will return the corresponding <stack> value.
Read Response
+CSPTSS: <stack>
OK
Where <stack> is the stack that is currently active in the terminal
0= ‘No Active Stack’
1= ‘TMO’
2= ‘DMO’
3= ‘DMO Gateway”
Test Syntax
AT+CSPTSS=?

+CSPTSS: (list of supported TETRA stacks) <cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CSPTSS: (1-2) <cr><lf> or, when DMO Gateway functionality is customized, +CSPTSS: (1-3) <cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.51 AT+CSPTR – Reboot radio
Source
Description
This command resets the configuration of the serial interface to their factory defaults (see AT&F 7.1.67),
aborts any calls and performs a normal switch off and switch on. This is the same as an ATZ command
customised to perform reboot.
Execution Syntax
AT+CSPTR
Set Syntax
N/A
Test Syntax
N/A
Read Syntax
N/A
Example
AT+CSPTR
OK
<Radio reboots>

MOD-14-1758
7.1.52 AT+CSPTSSN - TETRA Stack Active Select Notification Command
Source
Description
This command is used to enable or disable the sending of the unsolicited +CSPTSSA message (see
7.2.16) when a new stack becomes active. The default behaviour will be to disable the messages and it
will be the responsibility of the external application to request the terminal to enable them, using this
message.
Set Syntax
AT+CSPTSSN=<value>
Where <value> is:
0 ‘Disable'
1 ‘Enable’
Set Response
If Successful:
<cr><lf>OK<cr><lf>
If unsuccessful:
+CME ERROR: <error code>
Where <error code> is one of the values defined the following table.
If the <value> submitted with the command is neither ‘0’ nor ‘1’, then the
+CME ERROR: 34
request will fail with the failure response “Values out of range”
If the terminal is processing another AT command the request will fail with
+CME ERROR: 3
the failure response “Operation not permitted”
Read Syntax
AT+CSPTSSN?
Read Response
+CSPTSSN: <value>
OK
Where <value> is:
‘Disabled’
‘Enabled’
Test Syntax
AT+CSPTSSN=?

+CSPTSSN: (list of supported enable-disable values)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CSPTSSN: (0-1) <cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.53 AT+CSQ - Signal Quality
Source
Based on TS 100 916 section 8.5
Description
Returns the RSSI of the channel when in Trunked mode. Returns an error in DMO mode.
It will return the RSSI/BER in any state.
Execution Syntax
N/A
Set Syntax
N/A
Read Syntax
AT+CSQ?
Test Syntax
AT+CSQ=?
Response
+CSQ: <rssi>,<ber><cr><lf>
<cr><lf>OK<cr><lf>
When the product is operating as a DMO Gateway, all parameters apply to the TMO service.
State Response when PEI Compliance Response when PEI Compliance

Direct Mode +CME ERROR: 513 +CME ERROR: 40
(Service not supported when in Repeater (Service not supported when in
Mode) Repeater Mode)
Defined Values
<rssi>
Channel RSSI in dBm (-90dBm will be reported as -90)
<ber>
This parameter is not supported and is always set to 7
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CSQ?<CR>
<cr><lf>+CSQ: -89,7<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.54 AT+CTBCT - TETRA Broadcast
Source
[6] section 6.14.3
Description
This command is a non-standard set form of the command and is used to enable / disable the reporting of
TETRA Broadcast unsolicited result codes. When enabled the corresponding unsolicited result code
reports the current SwMI features every time there is a relevant change in the SYSINFO broadcast by the
SwMI, see 7.2.17. The current SwMI features data is derived from the air interface SYSINFO with
extended services element.
Execution Syntax
None
Set Syntax
AT+CTBCT=<Bcast Unsolic>
Defined Values
Field Values Remark
<Bcast Unsolic> 0 or 1 0 = 'Disable Broadcast unsolicited result code'
(default value)
1 = 'Enable Broadcast unsolicited result code'
Read Syntax
AT+CTBCT?
Test Syntax
AT+CTBCT=?
Set Response
<cr><lf>OK<cr><lf>
Read Response
+CTBCT: [<LA>,<BS service>,<Security information>,<SDS-TL addressing>]<cr><lf>
<cr><lf>OK<cr><lf>
Note that the parameters are omitted if the terminal is in TMO or GMO but not registered.

MOD-14-1758
Defined Values
Field Values Remark
<LA> 0 to 16,383 Location Area code of the service cell, see
clause 16.10.30 of EN 300 392-2 [2] and clause
6.17.30 of EN 300 392-5 [6]
<BS service> 000 to FFF Services supported by the BS of the serving cell,
taken from the BS service details information element
broadcast in SYSINFO, see clause 18.5.2 of
EN 300 392-2 [2] and clause 6.17.7 of
EN 300 392-5 [6]. It is a 12 bit value encoded as the
hex equivalent containing the values of the following
from MSB to LSB:
Bit 11 - Registration
Bit 10 - De-registration
Bit 9 - Priority cell
Bit 8 - Minimum mode service
Bit 7 - Migration
Bit 6 - System wide services
Bit 5 - TETRA voice service
Bit 4 - Circuit mode data service
Bit 3 - Reserved
Bit 2 - SNDCP service
Bit 1 - Air interface encryption service
Bit 0 - Advance link support
<Security information> 0 to 2 An indication of whether the SwMI supports Air
Interface encryption and if so what level, see clause
6.17.50 of EN 300 392-5 [6]. Values are:
0 = Class 1
1 = Class 2
2 = Class 3
<SDS-TL addressing> 0 to 3 Indicates the SwMI support for its preferred SDS-TL
addressing method as described in the extended
services broadcast information element, see clause
21.4.4.1 of EN 300 392-2 [2] and clause 6.17.48 of
EN 300 392-5 [6]. Values are:
0 = Reserved
1 = Service centre addressing preferred
2 = Never use service centre addressing
3 = MS choice to use service centre addressing
Test Response
+CTBCT: (0-1)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CTBCT=1<cr> (enable unsolicited reporting)
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.55 AT+CTGS - Group Attachment
Source
[6] section 6.15.6
Description
Configures groups in the terminal to be selected or scanned. When the set command is accepted with no
errors, all existing group attachments in the terminal are removed. When the terminal is operating in Direct
Mode, the frequency used for the DMO transmissions and reception and Talk Group Alias Text are the
ones associated with the first DMO talkgroup with a matching value of GTSI.
This command is not supported when the product is operating as a DMO Gateway
Where two ports are supported by the product, adding or removing a group affects both PEI ports.
Therefore, if an application removes a group, then that group will be lost to both PEI ports.
In all situations, the unsolicited response identifies the groups that are attached after negotiation with the
infrastructure.
.
Execution Syntax
N/A
Set Syntax
AT+CTGS=<group type>,<GSSI>[,<group type>,<GSSI>]
The entries are one group per line, with a maximum of 10 in TMO and 1 in DMO. These groups may be
statically configured or DGNA assigned.
Warning! If a customer defined Always Attached Folder has been created do not include any group that
exists in that folder.
When the product is operating in DMO:

The <group type> value is ignored, and is treated as value 1 (Select).
A delay of at least 1.1s is required before call setups are attempted.
Read Syntax
AT+CTGS?
Test Syntax
AT+CTGS=?
Set / Read Response

<cr><lf>OK<cr><lf> see note
+CTGS: [<group type>,<GSSI>[,<cr><lf>
<group type>,<GSSI>[,<cr><lf>
...
<group type>,<GSSI>]]...]<cr><lf>
<cr><lf>OK<cr><lf> see note
If the SwMI rejects all the groups (or the only group) specified in the +CTGS set command, the response
is:
<cr><lf>OK<cr><lf>
<cr><lf>+CTGS: 0<cr><lf>
Up to 26 groups can be returned, including DGNA groups.

MOD-14-1758
For a Set Response the ‘<cr><lf>OK<cr><lf>’ (confirmation that command has been received) may occur
before or after the reported groups because the reported groups are an unsolicited report initiated when all
group attachment negotiation has occurred. Normally, the ‘<cr><lf>OK<cr><lf>’ will occur first in TMO; and
the reported group will occur first in DMO (because group selection in DMO does not involve any
negotiation using over-the-air signalling). For a Read Response the ‘<cr><lf>OK<cr><lf>’ occurs after the
reported groups.

Radio not in service +CME ERROR: 30 +CME ERROR: 30
In service - but the request +CME ERROR: 4 +CME ERROR: 4
contains more than one group (Operation not supported) (Operation not supported)
which is of type 1 (selected)
In Direct Mode, but the GSSI is not
known for this terminals MNI
In trunked mode, but at least one +CME ERROR: 34 +CME ERROR: 34
GSSIs specified is not known to the (Parameter value out of range) (Parameter value out of range)
MT (i.e. it is neither in the list of
programmed groups nor in the list
of dynamic groups)
GTSI addressing format not +CME ERROR: 32 +CME ERROR: 32
supported (Error decoding data) (Error decoding data)
In service, but unable to process +CME ERROR: 512 +CME ERROR: 42
Group Attachment (e.g. because a (Service not available) (Service temporarily not
group attachment is already being available)
processed)
In service, but unable to process +CME ERROR: 512 +CME ERROR: 41
Group Attachment because (Service not available) (Transmissions are inhibited)
terminal has TX inhibited)
In Direct Mode, but GSSI specified +CME ERROR: 4 +CME ERROR: 4
is a DGNA (Operation not supported) (Operation not supported)
In Direct Mode, but GSSI specified +CME ERROR: 100 +CME ERROR: 34
is not known to the MT (Unknown error) (Parameter value out of range)
In Direct Mode, but more than one +CME ERROR: 100 +CME ERROR: 34
group specified (Unknown error) (Parameter value out of range)
In DMO Gateway Mode +CME ERROR: 519 +CME ERROR: 519
(Service not supported by DMO (Service not supported by DMO
Gateway) Gateway)
CTGS command contains at least +CME ERROR: 34 +CME ERROR: 34
one ,Group Type> of 0 (Parameter value out of range) (Parameter value out of range)
Defined Values
<group type>
Value Meaning in [6] Class of Usage
0 (only in Set None
or Read Reserved
response)
1 Select Selected
2 scan priority 1 Normal: Not Scanned
3 scan priority 2 Normal: PGS Low
4 scan priority 3 Normal: PGS Normal
5 scan priority 4 Normal: PGS High
6 scan priority 5 Locked
7 scan priority 6 Always Scanned

MOD-14-1758
Test Response
<cr><lf>OK<cr><lf>
Example
AT+CTGS?<cr>
<cr><lf>+CTGS: 2,40411<cr><lf>
2,40432<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.56 AT+CTSDC - Service Definition for Circuit Mode services
Source
[6] section 6.14.5
Description
Sets the service definition for Circuit Mode services such as data or voice.
This command is not supported when the product is operating as a DMO Gateway.
Execution Syntax
N/A
Set Syntax
AT+CTSDC=<AI service>,<called party identity type>[,<area>,<hook>,<simplex>[,<end-to-end
encryption> [,<comms_type>[,<slots/codec>[,<RqTx>[,<priority>[,<CLIR control>]]]]]]]
Read Syntax
AT+CTSDC?
Test Syntax
AT+CTSDC=?
Response
+CME ERROR: 3 when the product has Service Profile configured as ‘Both’ in a preceding AT+CTSP
command
+CME ERROR: 4 when the product is operating as a BOS terminal and <end-to-end encryption> is set to
‘end-to-end-encryption’
+CME ERROR: 519 when the product is operating as a DMO Gateway, otherwise
+CTSDC:=<AI service>,<called party identity type>[,<area>,<hook>,<simplex>[,<end-to-end encryption>

[,<comms_type>[,<slots/codec>[,<RqTx>[,<priority>]]]]]]
Defined Values
<AI service> Trunked Mode
0 Tetra Speech
1 7.2 Kbit/s unprotected data
2 Low protection 4.8kbit/s data interleaving depth = 1
5 High protection 2.4kbit/s data interleaving depth = 1
<AI service> Direct Mode

0 Tetra Speech
<called party identity type> Trunked Mode

0 SSI
3 PABX
4 PSTN
<called party identity type> Direct Mode

0 SSI
1 TSI

MOD-14-1758
<area>
Area selection is not implemented and the only valid value is :
0 Area not defined
<hook> Trunked Mode

0 hook signalling
1 direct signalling
<hook> Direct Mode

1 direct signalling
<simplex> Trunked Mode

0 Duplex
1 Simplex
<simplex> Direct Mode

1 Simplex
<end to end encryption>

0 Clear
1 End-to-end encryption
<comms type> Trunked Mode

0 Point to point
1 Point to multipoint
<comms type> Direct Mode

0 Point to point with presence checking
4 Point to point without presence checking
<slots/codec> Trunked Mode

For a data call
0 1 slot
For a speech call
1 Tetra encoded speech
<slots/codec> Direct Mode

For a speech call
<RqTx> Trunked Mode

0 Request to Transmit
1 No Request to Transmit
<RqTx> Direct Mode

0 Request to Transmit
<priority> Trunked Mode

0 Priority Not Defined
1 - 15 Call Priority
<priority> Direct Mode

0 Priority Not Defined
1-3 Call Priority
<CLIR control>
This parameter is not supported by the radio.

MOD-14-1758
The following combinations of parameters are supported (if the values are supported in the mode):
Voice Voice Voice

Data
Duplex Simplex Group
Hook Supported Supported Supported Not supported
Direct Not supported Not supported Not supported Supported
Simplex Not supported Not supported Supported Supported
Duplex Supported Supported Not supported Not supported
Comms Type 1 slot Supported Not supported Not supported Not supported
Comms Type Tetra Speech Not supported Supported Supported Supported
Point to point Supported Supported Supported Not supported
Pont to multipoint Not supported Not supported Not supported Supported
Point to point without Not supported Not supported Supported Not supported
presence check
Default
<AI service>
0 Tetra Speech
<called party identity type>

0 SSI
<area>
0 Area not defined
<hook>
0 hook signalling
<simplex>
0 Duplex

0 Clear
<comms type>
0 Point to point
<slots/codec>
<RqTx>
0 Request to Transmit with simplex call setup
<priority>
0 Priority not defined

+CTSDC: (list of AI services),(list of called party identity types),(list of areas),(list of hook values),(list of
simplex values),(list of e-e encryption values),(list of comms type values),(list of slots/codec values),(List
of RqTx values),(list of priority values),(list of CLIR control values)<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
Test Response
+CTSDC: (0-2,5),(0-1,3-4),(0),(0-1),(0-1),(0-1),(0-1,4),(0-1),(0-1),(0-15),()<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CTSDC=1,0,0,0,0,0,0,0<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.57 AT+CTSDS - Service Definition for SDS
Source
[6] section 6.14.6
Description
Sets the service definition for the SDS service
Execution Syntax
N/A
Set Syntax
AT+CTSDS=<AI service>,<called party identity type>,<area>,<access priority>[,<end-to-end encryption>]
Read Syntax
AT+CTSDS?
Test Syntax
AT+CTSDS=?
Response
+CTSDS: <AI service>,<called party identity type>[,<area>[,<access priority>[,<end-to-end encryption>]]]
Defined Values
<AI service> Trunked and Direct Modes
12 SDS type 4
13 Status
<AI service> Gateway Mode

12 SDS type 4 (message from this device to TMO)
13 Status (message from this device to TMO)
28 SDS type 4 (message from this device to DMO)
29 Status (message from this device to DMO)

0 SSI
1 TSI
3 PABX The PABX will use the first PABX algorithm’s Outgoing identity, whether or not this
algorithm is enabled.
4 PSTN The PSTN will use the first PSTN algorithm’s Outgoing identity, whether or not this
algorithm is enabled.
<area>
Area selection is not implemented and the only valid value is :
0 Area not defined

MOD-14-1758
<access priority>
0 Low priority
1 High priority
2 Emergency priority
Prior to v6.0 operation was as follows: Any value in the command was overridden by the
radio. The radio would use an ‘Emergency’ access priority for a status message with a
status value of 0; in all other cases the access priority used was the customized default
access priority.

0 Clear (value is ignored)
Defaults
<AI service>
12 SDS type 4

0 SSI
<area>
0 Area not defined
<access priority>
0 Low priority

0 Clear

+CTSDS: (list of AI services),(list of called party identity types),(list of areas),(list of access priorities), (list
of e-e encryption values)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CTSDS: (12-13),(0-1,3-4),(0),(0-2),(0)<cr><lf>
<cr><lf>OK<cr><lf>
Example 1
AT+CTSDS=12,0,0,0,0<cr>
<cr><lf>OK<cr><lf>
Example 2
AT+CTSDS=12,3,0,0,0<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.58 AT+CTSP - Service Profiles
Source
[6] section 6.14.4.1
Description
This command is used to disable incoming call signalling (from the air interface) to the MT to be sent to
the PEI. The default is that all signalling is forwarded to the PEI so a TE should disable each service for
which it does not want to accept signalling. The read command will return all non-default services with a
profile set by the TE. See also 4.8.8 SDS Message Routing.
Combinations of parameters which are not supported are rejected with +CME ERROR: 4
Warning: Changing the service profile for a call type while there is an ongoing call of
that same type may affect the behaviour of the ongoing call.
Note: Routing tables are held independently for each operating mode and can only be
set and reported when in that mode.
Execution Syntax
N/A
Set Syntax
AT+CTSP=<service profile>,<service layer 1>[,<service layer 2>] [,<PID>]
Note that it is valid for ',<service layer 2>' to be omitted and ',<PID>' to be present in the case of SDS-TL.
Read Syntax
AT+CTSP?
Test Syntax
AT+CTSP=?
Response
+CTSP: =<service profile>,<service layer 1>[,<service layer 2>] [,<PID>][,<cr><lf>
<service profile>,<service layer 1>[,<service layer 2>] [,<PID>][,<cr><lf>
...
<service profile>,<service layer 1>[,<service layer 2>] [,<PID>]]...]<cr><lf>
Note that ', <service layer 2>' is omitted when ',<PID>' is present in the case of SDS-TL.
When operating in Trunked Mode, Direct Mode or Repeater Mode, profiles are reported for <Service Layer
1> values 0, 2 and 3. When operating in Gateway Mode, profiles are reported for <Service Layer 1>
values 2 and 3 only.

MOD-14-1758
Error Condition Response when PEI Response when PEI

Compliance Level is 0 Compliance Level is 0
A parameter has an unsupported +CME ERROR: 34 +CME ERROR: 34
value (Parameter value out of range) (Parameter value out of range)
The combination of service layer 1 +CME ERROR: 34 +CME ERROR: 34
with service layer 2 is not permitted (Parameter value out of range) (Parameter value out of range)
(e.g. SDS-TL with Voice)
Service Profile value is invalid for +CME ERROR: 4 +CME ERROR: 4
the specified Service Layer 1 and (Operation not supported) (Operation not supported)
Service layer 2 combination which
would otherwise be permitted (e.g.
CC Data routed to MT)
Direct Mode and requested profile +CME ERROR: 513 +CME ERROR: 40
is not available in direct mode (Not supported in direct mode) (Not supported in direct mode)
In DMO Gateway Mode and +CME ERROR: 519 +CME ERROR: 519
requested profile is not available in (Service not supported by DMO (Service not supported by DMO
direct mode Gateway) Gateway)
In Repeater Mode and requested +CME ERROR: 518 +CME ERROR: 518
profile is not available in direct (Service not supported by (Service not supported by DMO
mode Repeater Mode) Repeater)
Start-up of radio not yet complete +CME ERROR: 3 +CME ERROR: 3
(Operation out of context) (Operation out of context)
Defined Values
<service profile> (for Trunked / Direct Mode / Repeater Mode)
0 MT only
1 TE only
2 Both (only for Voice, Status and SDS-TL)
<service profile> (for Gateway Mode)

1 TE only
3 Neither
17 Route to DMO interface and copy to PEI
19 Route to DMO interface
<service layer 1> (for Trunked / Direct Mode / Repeater Mode)

0 CC
1 MM (reported only)
2 SDS
3 SDS_TL
<service layer 1> (for Gateway Mode)

2 SDS
3 SDS_TL
<service layer 2> (for Trunked / Direct Mode / Repeater Mode)

0 Voice
1 Data
10 Registration (reported only)
11 Group Management (reported only)
20 Status
<service layer 2> (for Gateway Mode)

20 Status
<PID>
0 .. 255 Protocol Identifier, as defined in section 29 of {1}

MOD-14-1758

+CTSP: (list of service profile values),(list of service layer 1 values),(list of service layer 2 values),(list of
PIDs)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CTSP: (0-3,17,19),(0,2-3),(0-1,20),(0-255)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CTSP=1,2,1<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.59 AT+CTSTR - TETRA Status Text Read
Source
[6] section 6.14.3
Description
This command reads the configured text strings associated with SDS numeric values.
Execution Syntax
AT+CTSTR=<AI service>
Defined values
Field Values Remark
<AI service> 13 Status
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+CTSTR=?
Execution Response
+CTSTR: 13,<Status value>,<Status text><cr><lf>
<Status value>,<Status text><cr><lf>
...
<Status value>,<Status text><cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
Field Values Remark
<Status value> 0 and 32768 to 65535 Status values (numbers) including 0 for emergency
status and the rest coming from Status File Number
[3125] (low memory product) or from Extended
Status File Number [3981] (high memory product)
<Status text> Up to 16 characters Corresponding Status File Wide Text [3121] (low
(low memory product) memory product) or from Extended Status File Wide
Up to 140 characters Text [5260] (high memory product), encoded
(high memory product) according to parameter Hayes Text Format, [8152]
Test Response
<cr><lf>+CTSTR: (13)<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
Example
AT+CTSTR=13<cr>
<cr><lf>
+CTSTR: 13,0,EMERGENCY<cr><lf>
33001,ON DUTY<cr><lf>
...
34919,WARRANTS<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.60 AT+CTXD - Transmission Demand
Source
[6] section 6.15.8
Description
Sends a TX demand once a voice simplex call is active on this PEI port.
If this command is sent on a PEI port that is not in a call then a +CME ERROR: 3 will be returned.
If Tx demand is granted, operation of any other PTT is ignored until transmission ceases.
Execution Syntax
N/A
Set Syntax
AT+CTXD=<CC Instance>,<TxDemandPriority>[,<end-to-end encryption>]
Read Syntax
N/A
Defined Values
<CC Instance> is ignored and can be any valid value (0 - 999).
<TxDemandPriority>
0 Low (TMO), Normal (DMO)
1 High
2 Pre-emptive
3 Emergency pre-emptive

0 Clear
Test Syntax
AT+CTXD=?

MOD-14-1758
Response
If call active on this port and TX-
<cr><lf>OK<cr><lf> <cr><lf>OK<cr><lf>
demand is allowed
In DMO Gateway Mode
(Operation out of context) (Operation out of context)
In service – but TX inhibited
(Transmissions are inhibited) (Transmissions are inhibited)
Tx demand not allowed (e.g. not in a +CME ERROR: 3 +CME ERROR: 3
call, or already has Tx permission) (Operation out of context) (Operation out of context)

+CTXD: (list of CC instance values),(list of Tx demand priority values),(list of e-e encryption
values)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CTXD: (0-999),(0-3),(0-1)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+CTXD=112,1<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.61 AT+CUTXC - Uplink Transmission Ceased
Source
[6] section 6.15.9
Description
Sent from the application once it wants to stop transmitting.
If a call is active on this port, and a command AT+CTXD has already been sent to put the terminal into
simplex transmit, or the call was set up with simplex transmit enabled, then the AT+CUTXC command can
be sent.
If this command is sent on a PEI port that is either:

 not in a call
 does not have transmission permission granted to itself
then a +CME ERROR: 3 will be returned.
Execution Syntax
N/A
Set Syntax
AT+CUTXC=<CC Instance>
Note: <CC Instance> is ignored and can be any valid value (0 - 999).
Read Syntax
N/A
Test Syntax
AT+CUTXC=?
Response
State Response
If call active on this port and transmission permission is
<cr><lf>OK<cr><lf>
granted to itself
+CME ERROR: 3
In DMO Gateway Mode
(Operation out of context)
Tx ceased not allowed (e.g. not in a call, or does not +CME ERROR: 3
currently have control of Tx permission) (Operation out of context)

+CUTXC: (list of CC instance values)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+CUTXC: (0-999)<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
Example
AT+CTXD=112,1<cr> // terminal tx on
<cr><lf>OK<cr><lf>
AT+CUTXC=112 // terminal tx off
<cr><lf>OK<cr><lf>
AT+CUTXC=112 // ooops
<cr><lf>+CME ERROR: 3<cr><lf>

MOD-14-1758
7.1.62 AT+GMI - Manufacturer Identity
Source
[5] 6.1.4
Description
Returns the Manufacturer Identification. The returned text will not contain ‘OK<cr>’ or ‘0<cr>’, and will be
less than 2048 characters long.
Execution Syntax
AT+GMI
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+GMI=?
Response
+GMI: SEPURA
Test Response
<cr><lf>OK<cr><lf>
Example
AT+GMI<cr>
<cr><lf>+GMI: SEPURA<cr><lf>
<cr><lf>OK<cr><lf>
Note that the '+GMI: ' is not included in responses when using logical port 2.

MOD-14-1758
7.1.63 AT+GMM - Model Identity
Source
[5] 6.1.5
Description
Returns the Model Identification. The returned text depends on the model in use. The returned text will
not contain ‘OK<cr>’ or ‘0<cr>’, and will be less than 2048 characters long.
Execution Syntax
AT+GMM
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+GMM=?
Response
The response from the terminal depends on the terminal type.
The options are:
+GMM: SRH3000
+GMM: SRM3500
+GMM: SRG3500
+GMM: SRC3300
+GMM: SRC3100
+GMM: SRH3500W
+GMM: SRH3800W
+GMM: SRM3500W
+GMM: SRG3500W
+GMM: SRC3300W
+GMM: STP8000
+GMM: SRH3900
+GMM: STP8100
+GMM: SRG3900
+GMM: STP8200
+GMM: STP8X000
+GMM: STP8X100
+GMM: STP9000
+GMM: STP9100
+GMM: STP9200
Test Response
<cr><lf>OK<cr><lf>

MOD-14-1758
Example
AT+GMM<cr>
<cr><lf>+GMM: STP8000<cr><lf>
<cr><lf>OK<cr><lf>
Note that the '+GMM: ' is not included in responses when using logical port 2.

MOD-14-1758
7.1.64 AT+GMR - Revision Numbers
Source
[5] 6.1.6
Description
Returns revision identification, in the form of up to 6 x 12 digit numbers as a comma separated string. The
returned text will not contain ‘OK<cr>’ or ‘0<cr>’, and will be less than 2048 characters long.
Execution Syntax
AT+GMR
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT+GMR=?
Response
+GMR: <Boot Software>,<Control Software>,<Console1 software>,<Console2 software>,<MMI/Authentication
software>[,<Secure processor software>]<cr><lf>
Where software revision numbers are a set of up to six 12 digit numbers.
Not all products have all software items and they will return empty strings between the commas.
Product Revision Numbers returned

Hand-Held <Boot>,<Control>,,,<Authentication>,<Secure micro>
3000 series and
Portable 8000 series
Mobile or Gateway <Boot>,<Control>,<Console 1 if fitted>,<Console 2 if fitted>,<Authentication>,
3000 series <Secure micro>
Test Response
<cr><lf>OK<cr><lf>
Example
AT+GMR<cr>
<cr><lf>123456789012,123456789012,123456789012,123456789012,123456789012<cr><lf>
<cr><lf>OK<cr><lf>
Note that the '+GMR: ' is not included in responses when using logical port 2.

MOD-14-1758
7.1.65 AT+GSN - Serial Numbers
Source
[5] 6.1.7
Description
Returns hardware serial number identification, in the form of a 15-digit TEI and up to 3 x 15 alpha-numeric
serial number characters as a comma separated string. The returned text will not contain ‘OK<cr>’ or
‘0<cr>’, and will be less than 2048 characters long.
Execution Syntax
AT+GSN
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT +GSN=?
Response
+GSN: <TEI>,<Transceiver serial number>[,<Console 1 serial number>[,<Console 2 serial number>]]
Where TEI is 15 digits and serial numbers are a set of up to 3 x 15 alpha-numeric characters.
Test Response
<cr><lf>OK<cr><lf>
Example
AT+GSN<cr>
<cr><lf>+GSN:
123456001234560,2PN123456ABC1A2,2PN456789DEF3B4,2PN012345XYZ5C6<cr><lf>
<cr><lf>OK<cr><lf>
Note that the '+GSN: ' is not included in responses when using logical port 2

MOD-14-1758
7.1.66 AT+IPR - EDC Data Rate
Source
[5] 6.2.10
Description
Sets the serial port data rate at which the terminal accepts commands and data.
Where two ports are supported by the product, this command has no effect on the other PEI port
Execution Syntax
N/A
Set Syntax
AT+IPR =<rate>
Read Syntax
AT+IPR?
Test Syntax
AT+IPR=?
Defined Values
<rate> is defined as the baud rate of the serial interface. It can be set to the following values:
4800, 9600, 19200, 38400
Responses
If <value> is valid
OK
else
+CME ERROR: 34 (Value out of range)
Note that the data rate is not changed until after the 'OK' has been transmitted.

+IPR: (list of autobaud rates),(list of fixed baud rates)<cr><lf>
<cr><lf>OK<cr><lf>
Test Response
+IPR: (),(4800,9600,19200,38400)<cr><lf>
<cr><lf>OK<cr><lf>
Example
AT+IPR=38400<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.67 AT&F - Factory Defaults
Source
[5] 6.1.2
Description
Sets all the communication parameters to the factory default. The parameters affected are
Parameter Value Response

Echo E 1 = Echo on
Quiet mode Q 0 = Quiet mode off
Auto answer S0 0 = Disabled
Escape Character S2 +
Command line terminator S3 13 = CR
Response formatting S4 10 = LF
Command line editing S5 8 = BS
Verbose errors V 1 = Full headers and trailers
Final error reporting CMEE 1 = Extended numeric errors
Parameters for SDS services CTSDS AI service = 12 (SDS type 4)
Called Party Identity type = 0 (SSI)
Area = 0
Access Priority = 0
End-to-end Encryption = 0
Parameters for Circuit mode CTSDC AI service = 0 (Tetra Speech)
services (data or voice) Called Party Identity type = 0 (SSI)
Area = 0
Hook = 0
Simplex = 0
End-to-end Encryption = 0
Service Profile CTSP Programmable parameters
Baud Rate IPR Programmable parameter
Execution Syntax
AT&F =<value>
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
AT&F=?
Defined Values
The optional <value> field can select a number of factory default configurations. Not implemented in the
Sepura terminal.
The only valid <value> is 0. Any other value returns ERROR

MOD-14-1758
Default
0
Responses
None
States
This command works normally in any command state.
Test Response
<cr><lf>OK<cr><lf>
Example
AT&F<cr>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.68 AT@N - Read ITSI
Source
Section 4.3.2.20
Description
This command complements the AT+CNUM command in that it returns just the ITSI of the terminal. The
+CNUM command returns all the numbers that the terminal knows, i.e. its ITSI, and all the groups the
terminal can attach to. This could be quite an extensive list. The @N command had therefore been kept to
return just the ITSI.
This command is only supported on logical port 1
Execution Syntax
AT@N
Set Syntax
N/A
Read Syntax
N/A
Test Syntax
N/A
Defined Values
None
Responses
The terminal’s ITSI expressed as a 15 digit decimal number comprising a three digits for the country code
followed by four digits for the network code followed by eight digits for the SSI. All leading zeros are
included.
States
This command works normally in any command state.
Test Response
<cr><lf>OK<cr><lf>
Example
AT@N<cr>
<cr><lf>044070010020550<cr><lf>
<cr><lf>OK<cr><lf>

MOD-14-1758
7.1.69 AT@T
Source
Sepura proprietary
Description
This command is for use only by Sepura tools.
7.1.70 AT@Z
Source
Sepura proprietary
Description
This command is for use only by Sepura tools.

MOD-14-1758
7.1.71 +++ – Escape Sequence
This command is used to escape from transparent mode.

Syntax: <at least 1 second pause>+++<at least 1 second pause>
Register S2 can be used to change the escape character
The characters specified by S2 (normally +) are sent over the air to the destination.
The radio will not clear out of a circuit mode data call by the lowering of DTR by itself. A
Hang-up command is required once escaped from transparent mode

MOD-14-1758
7.2 Unsolicited Responses
Unless stated otherwise STP9000 Series product share command differences with STP8000
7.2.1 +CDTXC - Downlink Transmission Ceased
Source
[6] 6.15.11
Description
The talking party has ceased transmission when in a simplex call.
Response
+CDTXC <CC instance>,<TxRqPrmsn>
Defined Values
Where
<CC instance>
CC instance is a three-digit number allocated by the calling terminal unique to that call.
<TxRqPrmsn>
0 Allowed to Request
1 Not allowed to Request

MOD-14-1758
7.2.2 +CMGS - Send Message
Source
[6] section 6.13.2
Description
Unsolicited response following an AT+CMGS Send SDS or STATUS message. See 7.1.21
Response
+CMGS: <SDS Instance>[,<SDS Status> [, <message reference>]]
Note that multiple responses may be received as the message enters and is removed from the queue
Defined Values
SDS Instance is a number from 0 – 255 used for local (to this terminal) reference.
SDS Status Meaning
SDS Status Meaning
4 Outgoing message successfully sent
5 Outgoing message transmission failed (no more attempts will be made)
For Simple SDS-TL Protocol IDs (values 0-127), the Message reference (r) is always 0. For Full SDS-TL
protocol IDs (values 128-255) Message reference (r) is the SDS-TL over-the-air reference, 1 - 254.
Example
<cr><lf>+CMGS: 1,9,1<cr><lf>

MOD-14-1758
7.2.3 +CNUMD - Report MT Dynamic Group Identities
Source
[6] section 6.11.5.3
Description
When enabled, see 7.1.25, this unsolicited result code reports the number of dynamic groups whenever
there is a change to the number of identities or any of the dynamic groups or to the current stack. It is
then up to the TE to request further information and for it to work out what has changed.
This response is only supported on Logical Port 1.
Response
+CNUMD: <number of groups><cr><lf>
Defined Values
Field Values Remark
<number of groups> 0 to 50 Number of dynamic groups
Example
<cr><lf>
+CNUMD: 3<cr><lf> (There are now three groups)

MOD-14-1758
7.2.4 +CREG – Report Registration Status
Source
TS 100 916 section 7.2
[6] 6.11.3
Description
When enabled, using the AT+CREG command, this unsolicited response reports the current registration
status in the TMO network. These unsolicited reports may occur at any time except while in the Online
Data State.
This response is not generated whilst operating solely in DMO and when operating as a DMO Gateway all
parameters apply to the TMO service.
This response is supported on Logical Port 1.
Response when PEI Compliance Level [8154] is 0

where the fields are defined as :
Field Values Remark
<Registration Status> 0-3 0 = Not registered and not searching
1 = Registered home network
2 = Not registered, but currently searching
3 = System Reject
6.17.30 of EN 300 392-5 [6]
<MNI> <000-999><0000- Mobile Network Identity is 7 digits long, comprising of
9999> two components:
Mobile Country Code (MCC) &
Mobile Network Code(MNC)>
<MNI> = <MCC><MNI>
The <MCC> is three digits long and <MNC> is four
digits long.
e.g. “0780050” where MCC=78 & MNC = 50

MOD-14-1758
Response when PEI Compliance Level [8154] is 1

The response message is dependant upon the value of <Reg unsolic> used in the Set command:
Field Values Response Message
<Reg unsolic> 1 +CREG <registered status><cr><lf>
2 +CREG <registered status>[, <LA>[, <MNI>]]<cr><lf>
where the fields are defined as :
Field Values Remark
<Registration Status> 0-3 0 = Registering or searching a network, one or more
networks are available
1 = Registered home network
2 = Not registered, no network currently available
3 = System Reject
6.17.30 of EN 300 392-5 [6]
<MNI> <000-999><0000- Mobile Network Identity is 7 digits long, comprising of
9999> two components:
Mobile Country Code (MCC) &
Mobile Network Code(MNC)>
<MNI> = <MCC><MNI>
The <MCC> is three digits long and <MNC> is four
digits long.
e.g. “0780050” where MCC=78 & MNC = 50
Example 1 (PEI Compliance Level = 0)

Registered on Home network, LA=1000, MCC=234, MNC=2400
<cr><lf>+CREG: 1,1000,2342400<cr><lf>
Example 2 (PEI Compliance Level = 0)

Not registered but currently searching for a network.
<cr><lf>+CREG: 2<cr><lf>

MOD-14-1758
7.2.5 +CSPSCS - Smart card status
Source
This report is a proprietary to Sepura.
Description
This report is used by BOS-Digital and Sectra smart card terminals to report status information that has
been provided by the smart card to the terminal. The terminal may have performed some processing of
the smart card information prior to sending this report.
The report operates in unsolicited report mode only.
This report is only supported on Logical Port 1
Unsolicited Response Syntax

<cr><lf>+CSPSCS: <SC instance>,<SC status>
Defined Values
<SC instance> 0, 1 0 – originated from internal smart card
1 – originated from external smart card
<SC status> 0 - 13 0 – No smart card present
1 – Wrong smart card present
2 – Smart card activation failure
3 – Smart card authentication failure
4 – No valid key available
5 – Wrong key
6 – Key agreement failure
7 – OPTA not available
8 – PIN required
9 – PIN not required
10 – PUK required
11– SIM-ME authentication successful
12 – SIM-SwMI authentication successful
13 – Key available
Example
<cr><lf>+CSPSCS: 1,5<cr><lf>

MOD-14-1758
7.2.6 +CSPSCTR - Smart Card Text Report
Source
Description
This unsolicited response reports text information originating from a smart card. Text information could be
reported in the DISPLAY TEXT proactive UICC command.
For information provided in the DISPLAY TEXT proactive command the <duration units> and <duration
interval> elements may be specified.

+CSPSCTR: <sc instance>,<user input required>,<duration units>,<duration interval>,<inkey
type>,<length>,<text string><cr><lf>
Defined Values
Field Values Remark
<sc instance> 0, 1 0 – Originated from internal smart card
1 – Originated from external smart card
<user input required> 0 0 – No (Display Text)
<duration units> 0, 1, 2 0 – minutes
1 – seconds
2 – tenths of seconds
<duration interval> 0 – 255 0 – Not used
1-255 – Number of <duration units> to display <text
string>
<inkey type> 0 0 – Reserved
<length> Number of bits in <text string>
<text string> Text string provided from BOS smart card, encoded
according to parameter Hayes Text Format, [8152]
Note that Hayes Text Format should be configured to be ‘Mixed’ to allow support for ISO8859-15 encoded
text via Default SDS Encoding Scheme [8135] and Text Coding Scheme 1 [8241].
Example Display Text: ‘abc’

<cr><lf>
+CSPSCTR: 1,0,0,0,0,24,abc<cr><lf>

MOD-14-1758
7.2.7 +CSPTAP16 - Application Parameter 16 (BOS DMO Cryptomode)
Source
Description
A BOS-Digital terminal reports the change in the value of the BOS DMO E2EE Cryptomode context data
parameter using this unsolicited report.
This unsolicited report is only supported on Logical Port 1.

+CSPTAP16: <DMO Cryptomode><cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
Field Values Remark
<DMO Cryptomode > 1-2 1 = Mode 1
2 = Mode 2
Example DMO Cryptomode 2 selected

<cr><lf>+CSPTAP16: 2<cr><lf>
7.2.8 +CSPTAP17 - Application Parameter 17 (BOS E2EE Enable)
Source
Description
A BOS-digital terminal reports a change in the value of the terminal’s Selected E2EE State context data

+CSPTAP17: <E2EE State><cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
Field Values Remark
<E2EE State> 0-1 0 = Clear (Selected E2EE State = Off)
1 = Encrypted (Selected E2EE State = On)
Example Terminal in clear mode operation, Selected E2EE State = ‘off’


MOD-14-1758
7.2.9 +CSPTAP18 - Application Parameter 18 (BOS SDS Encryption Key)
Source
Description
A BOS-Digital terminal reports the change in the value of the BOS SDS Encryption Key context data

+CSPTAP18: <SDS Encryption Key><cr><lf>
<cr><lf>OK<cr><lf>
Defined Values
Field Values Remark
<SDS Encryption Key> 0-2 0 = Clear
1 = TK-TMO
2 = TK-SM
Example TK-SM selected


MOD-14-1758
7.2.10 +CSPBOPTA - BOS Report Smart Card OPTA
Source
Description
This unsolicited response reports the OPTA from a BOS-digital smart card when it has changed as a
result of over-the-air update using the OTAK mechanism.

State Response
Updated OPTA from BOS smart card <cr><lf>+CSPBOPTA: <OPTA text>
SIM failure (unable to read OPTA from +CME ERROR: 13
smart card)
Defined Values
<OPTA text> Up to 24 characters OPTA from BOS smart card, encoded according
to parameter Hayes Text Format, [8152]
Note that Hayes Text Format should be configured to be ‘Mixed’ to allow support for ISO8859-15 encoded
text via Default SDS Encoding Scheme [8135].
Example
<cr><lf>
+CSPBOPTA: aaaaaaaaaaaaaaaaaaaaaaaa<cr><lf>

MOD-14-1758
7.2.11 +CSPBTOPTA - BOS Transmitting Party OPTA
Source
Description
This unsolicited response is used by BOS-Digital terminals to report the transmitting party's OPTA shortly
after the start of incoming transmissions in half duplex voice calls. It is not supported by non-BOS-Digital
terminals.
Response
+CSPBTOPTA: <CC instance>,<Tx Grant>,<OPTA text>
Defined Values
Field Values Remark
<CC instance> nnn Three digit number allocated by the calling terminal
unique to that call.
<Tx Grant> 3 Transmission granted to another
<OPTA text> Up to 24 characters OPTA from BOS smart card, encoded according to
parameter Hayes Text Format, [8152]
Example
<cr><lf>
+CSPBTOPTA: 123,3,aaaaaaaaaaaaaaaaaaaaaaaa<cr><lf>

MOD-14-1758
7.2.12 +CSPDCS - Report DMO Connectivity Status
Source
Description
This unsolicited report states the availability of connectivity via a DMO Gateway or DMO Repeater.
Response
+CSPDCS: <DMO Gateway>,<DMO Gateway restrictions>,<DMO Repeater>
Defined Values
where
<DMO Gateway> This is the availability of a DMO Gateway with sufficient signal strength and a valid
Usage Restriction Type and Validity Time
<DMO Gateway restrictions> This indicates the restrictions that may apply to services available via a
detected DMO Gateway
<DMO Repeater> This is the availability of a DMO Repeater with sufficient signal strength and a
valid Usage Restriction Type and Validity Time
<DMO Gateway>
0 Not detected
<DMO Gateway restrictions>

0 No restriction
1 SwMI not present
<DMO Repeater>
0 Not detected

MOD-14-1758
7.2.13 +CSPICP – Incoming Call Proprietary Extensions
Source
Description
This unsolicited response indicates additional information for incoming call set-up, that is not available in
the +CTICN report, see 7.2.21
Response
+CSPICP: <CC instance>, <priority>
Defined Values
Where
<CC instance> is a three-digit number allocated by the calling terminal unique to that call.
<priority> is a value between 0 and 15 corresponding to the call priority received from the TETRA air
interface.

MOD-14-1758
7.2.14 +CSPLOGIO – Log In / Log Out Status
Source
Description
This unsolicited response, supporting procedures specified in [8], indicates that the terminal has received
information from the SwMI that may indicate a state change or an error in the authentication process.
This command is supported on logical port 1 and logical port 2
Response
+CSPLOGIO: <code>,<reason>,<type>,<rui>,<profile ID>,<assignment period>
Not all information may be supplied by the SwMI (or may be relevant in the context of other fields) and
unavailable information will return empty strings between the commas.
Defined Values
Field Values Remark
<code> 0-2 0 = READY: Dis-assigned, Terminal dis-assigned
1 = ASSIGNED, Assigned after successful logon
2 = INVALID, Terminal in mode that does not allow
authentication
<reason> 0-18 Reject Reasons:
0 = Cause not defined or unknown
1 = Incorrect combination of RUI and PIN
2 = Too many assignment attempts, user assignment no
longer possible
3 = Too many assignment attempts, user assignment is
not possible for a period
4 = Assignment rejected due to proprietary rules
5 = The SwMI is currently unable to perform the
assignment authentication
6 = The assignment is rejected as an explicit dis-
assignment is required from the MS first
7 = Reserved
Cancel Reasons:
8 = Cause not defined or unknown
9 = Dis-assignment due to timeout
10 = Dis-assignment by dispatcher
11 = Dis-assignment due to assignment of user at another
terminal
12 = Dis-assignment due to proprietary rules
13 = Dis-assignment due to internal SwMI problem
14 = Dis-assignment due to a mismatch in the message
exchange
15 = Resereved
Other Reasons:
16 = Timeout pending
17 = Permanent disabled
18 = The radio is currently not able to send the
assignment (e.g. radio problem or non-trunked mode)

MOD-14-1758
Field Values Remark

<type> 0-5 0 = Assignment not required, current assignment still valid
or No RUI present
1 = RUN type
2 = SSI type
3 = MS-ISDN type
4 = Alpha-tag type
5 = Permanent dis-assignment
<rui> Up to 24 characters Radio User Identity, encoded according to parameter
<profile ID> 0 - 255 Profile definition
<assignment 0 - 65534 Original assignment period or remaining timeout pending
period> assignment time, in minutes.
65535 A value of 65535 indicates that the assignment period is
infinite (and will not timeout) or is undefined /
unknown.
Examples
+CSPLOGIO: 0,,4,,
Terminal not logged on but an alpha-tag type logon has been requested
+CSPLOGIO: 1,,4,USER 02,,480

User 'USER 02' logged onto the system. The RUI string is an alpha-tag. The user is logged on for 8 hours.

MOD-14-1758
7.2.15 +CSPTD – Terminal Disable Status
Source
Description
This unsolicited response indicates that the terminal has been temporarily disabled or enabled by
authorised over-the-air signalling. This message is only sent once.
Response
+CSPTD: <TEIStatus>,<ITSIStatus>
Defined Values
Where
<TEIStatus> is the status of the Terminal Equipment upon acceptance of a Disable command
<ITSIStatus> is the status of the Subscriber Identity upon acceptance of a Disable command
<TEIStatus>
0 Enabled
1 Terminal Equipment Temporary Disabled
<ITSIStatus>
0 Enabled
1 Subscription Temporary Disabled

MOD-14-1758
7.2.16 +CSPTSSA - TETRA Stack Select Active Stack Notification
Source
Sepura proprietary
Description
This message is designed to allow the external computer to keep track of either when a request to make a
stack active has completed or, if changed through other means, exactly what stack is currently active.
The terminal will generate this message and send it to the external computer, via the PEI, whenever a
new stack is made active, providing the message has been enabled by using the AT+CSPTSSN
command (see section 7.1.52)
Response
+CSPTSSA: <stack>
Defined Values
Where <stack> is the stack that is currently active in the terminal
1 ‘TMO’
2 ‘DMO’
3 ‘DMO Gateway’
4 ‘Repeater’

MOD-14-1758
7.2.17 +CTBCT - TETRA Broadcast
Source
[6] section 6.14.3
Description
When enabled, see 7.1.54, this unsolicited result code reports the current SwMI features every time there
is a relevant change in the SYSINFO broadcast by the SwMI. The current SwMI features data is derived
from the air interface SYSINFO with extended services element.
This response is only supported on Logical Port 1.
Response
+CTBCT: <LA>,<BS service>,<Security information>,<SDS-TL addressing><cr><lf>
Defined Values
Field Values Remark
6.17.30 of EN 300 392-5 [6]
<BS service> 000 to FFF Services supported by the BS of the serving cell,
taken from the BS service details information element
broadcast in SYSINFO, see clause 18.5.2 of
EN 300 392-2 [2] and clause 6.17.7 of
EN 300 392-5 [6]. It is a 12 bit value encoded as the
hex equivalent containing the values of the following
from MSB to LSB:
Bit 11 - Registration
Bit 10 - De-registration
Bit 9 - Priority cell
Bit 8 - Minimum mode service
Bit 7 - Migration
Bit 6 - System wide services
Bit 5 - TETRA voice service
Bit 4 - Circuit mode data service
Bit 3 - Reserved
Bit 2 - SNDCP service
Bit 1 - Air interface encryption service
Bit 0 - Advance link support
<Security information> 0 to 2 An indication of whether the SwMI supports Air
Interface encryption and if so what level, see clause
6.17.50 of EN 300 392-5 [6]. Values are:
0 = Class 1
1 = Class 2
2 = Class 3
<SDS-TL addressing> 0 to 3 Indicates the SwMI support for its preferred SDS-TL
addressing method as described in the extended
services broadcast information element, see clause
21.4.4.1 of EN 300 392-2 [2] and clause 6.17.48 of
EN 300 392-5 [6]. Values are:
0 = Reserved
1 = Service centre addressing preferred
2 = Never use service centre addressing
3 = MS choice to use service centre addressing

MOD-14-1758
Example
+CTBCT: 1645,B22,1,2<cr><lf>
(LA = 1645,
BS Service = 1101001000102 –
1 Registration mandatory
1 De-registration mandatory
0 Cell is not a priority cell
1 Cell never uses minimum mode
0 Migration is not supported
0 System wide services temporarily not supported
1 TETRA voice supported
0 Circuit mode data not supported
0 Service not available
0 SNDCP service not available
1 AI encryption available
0 Advanced link not supported,
Security info = Class 2,
SDS-TL Addressing = Never use service centre)

MOD-14-1758
7.2.18 +CTCC - Call completion
Source
[6] 6.15.2 (which is incorrect, stating that this is a command rather than a response)
Description
This unsolicited response indicates that the call set-up phase has completed. The call maintenance phase
should now be entered. This message is not used when setting up SDS messaging.
Response
+CTCC: <CC instance >,<hook>,<simplex>[,<AI service>[,<end to end encryption>[,<comms
type>[,<slots/codec>[<proprietary>]]]]]]]
Defined Values
Where
<hook>
0 hook signalling
1 direct signalling
<simplex
0 Duplex
1 Simplex
<AI service>
0 Tetra Speech

0 Clear
<comms type>
0 Point to point
3 Broadcast
<slots/codec>
For a data call
0 1 slot
For a speech call
<proprietary>
Never used
Example
<cr><lf>+CTCC: 0,0,0,0,1<cr><lf>

MOD-14-1758
7.2.19 +CTCR - Call Release
Source
[6] 6.15.3
Description
This unsolicited response indicates that the call has been cleared.
Response
+CTCR <CC instance >,<disconnect cause>
Defined Values
Where
<disconnect cause>
0 Not defined
1 User request
2 Called party busy
3 Called party not reachable
4 Called party does not support encryption
5 Network congestion
6 Not allowed traffic
7 Incompatible traffic
8 Service not available
9 Pre-emption
10 Invalid call identifier
11 Called party rejection
12 No CC entity
13 Timer expiry
14 SwMI disconnect
15 No Acknowledgement
16 Unknown Tetra Identity
17 Supplementary Service dependant
18 Unknown External subscriber number
19 Call restoration failed
20 Called part requires encryption
Example
<cr><lf>+CTCR: 123,13<cr><lf>

MOD-14-1758
7.2.20 +CTGS
Source
[6] section 6.15.6
Description
Whenever the groups attached at the MT change as a result of SwMI or MS user action and PEI
Compliance Level [8154] parameter is 1, an unsolicited +CTGS response is sent to the TE listing all
attached groups.
Response
<cr><lf>+CTGS: [<group type>,<GSSI>[,<cr><lf>
<group type>,<GSSI>[,<cr><lf>
...
<group type>,<GSSI>]]...]<cr><lf>
Defined Values
Where
<group type>
Value Meaning in [6] Class of Usage
0 None Reserved
1 Select Selected
2 scan priority 1 Normal: Not Scanned
3 scan priority 2 Normal: PGS Low
4 scan priority 3 Normal: PGS Normal
5 scan priority 4 Normal: PGS High
6 scan priority 5 Locked
7 scan priority 6 Always Scanned
Example
<cr><lf>+CTGS: 1,40411,<cr><lf>
7,40432,<cr><lf>

MOD-14-1758
7.2.21 +CTICN - Incoming Call Notification
Source
[6] 6.15.4
Description
This unsolicited response indicates incoming call set-up progress.
There is no notification for an incoming Ambience Listening call.
Response
+CTICN: <CC instance>,<call status>,<AI service>[,<calling party identity type>[,<calling party
identity>[,<hook>[,<simplex>[,<end-to-end encryption>[,<comms type>[,<slots/codec>[,<called party
identity type>[,<called party identity>[,<priority>]]]]]]]]]]
Defined Values
Where
<CC instance>
<Call status>
0 Call Progressing
<AI service>
0 Tetra Speech
<calling party identity type>

0 SSI
1 TSI
3 PABX external subscriber number
4 E164 external subscriber number
<calling party identity>

Calling party identity, format dependent on <calling party identity type >
Note that a <calling party identity> of All 1s (Open MNI) is reported as '999999916777215'.
<hook>
0 Hook signalling
1 direct signalling
<simplex>
0 Duplex
1 Simplex

0 Clear
<comms type>
0 Point to point
3 Broadcast
4 Point to point without presence check

MOD-14-1758
<slots/codec>
For a data call
0 1 slot
For a speech call

0 SSI
1 TSI
<called party identity>

Calling party identity, format dependent on <calling party identity type>
<priority>
Priority is a value between 0 and 15 corresponding to the call priority received from the TETRA air
interface.

MOD-14-1758
7.2.22 +CTOCP - Outgoing Call Progress
Source
[6] 6.15.5
Description
This unsolicited response indicates the progress of an outgoing call set-up.
The called party identity type, called party identity and priority elements are only included when the service
profile for CC voice is routing to both. Note that these fields are added to facilitate logging of UI initiated
calls via the PEI and are not currently part of the standard ETSI definition of this report.
See sections 5.1.2 on Set Up of Circuit-mode Voice Calls and 7.1.3 ATD Dial command for information on
how calls are set up.
Response
+CTOCP <CC instance>,<call status>,<AI service, [<hook>[,<simplex>[,<end-to-end
encryption>[,<comms type>[,<slots/codec>[,<called party identity type>[,<called party
identity>[,<priority>]]]]]]]]]
Defined Values
Where
<CC instance>
<call status>
0 Call Progressing
1 Call queued
2 Called party paged
3 Call continue
4 Hang time expired
<AI service>
0 Tetra Speech
<hook>
0 hook signalling
1 direct signalling
<simplex>
0 Duplex
1 Simplex

0 Clear
<comms type>
0 Point to point
3 Broadcast

MOD-14-1758
<slots/codec>
For a data call
0 1 slot
For a speech call

0 SSI
1 TSI
4 PSTN external subscriber number

Called party identity, format dependent on <called party identity type>
<priority>
Priority is a value between 0 and 15 corresponding to the call priority received from the TETRA air
interface.

MOD-14-1758
7.2.23 +CTSDSR - SDS Received
Source
[6] 6.15.7
Description
This unsolicited message carries the contents of a received SDS message.
Response
+CTSDSR: <AI service>,[<calling party identity>],[<calling party identity type>],<called party identity>,
<called party identity type>,<length>[,<encrypted>]<cr><lf><user data>
Defined Values
Where
<AI service> (for Trunked / Direct Mode)

12 SDS type 4
13 Status
108 SDS type 4 (incoming message to MT copied to TE)
109 Status (incoming message to MT copied to TE)
140 SDS Type 4 (outgoing message from MT copied to TE)
141 Status (outgoing message from MT copied to TE)
<AI service> (for Gateway Mode)

12 SDS type 4 (terminating message)
13 Status (terminating message)
44 SDS type 4 (passing message from DMO to TMO)
45 Status (passing message from DMO to TMO)
76 SDS type 4 (passing message from TMO to DMO)
77 Status (passing message from TMO to DMO)
<calling party identity>

Calling party identity, format dependant on <calling party identity type >
Note that a <calling party identity> of All 1s (Open MNI) is reported as '999999916777215'.
<calling party identity type>

0 SSI
1 TSI
4 E164 external subscriber number

Called party identity, format dependant on <called party identity type >

0 SSI
1 TSI
<length>
number of bits in the user data.

MOD-14-1758
<encrypted>
Optional element indicating an encrypted message, set to the value '1'.
<user data>
Message and SDS-TL header. This is encoded in ASCII Hex
Example 1
<cr><lf>+CTSDSR: 12,,,234240000020550,1,48<cr><lf>C00000616263<cr><lf>
Example 2
<cr><lf>+CTSDSR: 12,,,901223877600,3,48<cr><lf>C00000616263<cr><lf>

MOD-14-1758
7.2.24 +CTXG - Transmission Grant Status
Source
[6] 6.15.10
Description
This unsolicited response indicates a change of transmit status. This could either be to grant Tx or to
remove Tx.
Response
+CTXG <CC instance>,<Tx Grant>,<TxRqPrmsn>,<end-to-end encryption>[,<TPI type>[,<TPI>]]
Defined Values
Where
<CC instance>
<TxGrant>
0 Transmission Granted
1 Transmission not Granted
2 Transmission Queued
3 Transmission Granted to another
<TxRqPrmsn>

0 Clear
<TPI Type>
0 SSI
1 TSI
<TPI>
A numeric value of 8 digits representing an SSI or 15 digits representing a TSI.

MOD-14-1758
7.2.25 +CTXI - Transmission Interrupt
Source
[6] 6.15.13
Description
The transmission has been interrupted. Permission to transmit has been withdrawn.
Response
+CTXI <CC instance>,<TxGrant>,<TxRqPrmsn>,<end to end encryption>[,<TPI type>[,<TPI>]]
Defined Values
Where
<CC instance>
<TxGrant>
0 Transmission Granted
1 Transmission not Granted
2 Transmission Queued
3 Transmission Granted to another
<TxRqPrmsn>

0 Clear
<TPI Type>
0 SSI
1 TSI
<TPI>
A numeric value of 8 digits representing an SSI or 15 digits representing a TSI.

MOD-14-1758
7.2.26 +CTXN - Transmission Continue
Source
[6] 6.15.12
Description
The transmission can continue after an interruption.
Response
+CTXN <CC instance>,<TxCont>,<TxRqPrmsn>
Defined Values
Where
<CC instance>
<TxCont>
0 Do Not continue
1 Continue
<TxRqPrmsn>
State Response
Repeater +CME ERROR: 518
Mode (Service not supported when in Repeater Mode)

MOD-14-1758
7.2.27 +CTXW - Transmission Wait
Source
[6] 6.15.14
Description
This unsolicited message indicates that the transmission has been interrupted.
Response
+CTXW <CC instance>,<TxRqPrmsn>
Defined Values
Where
<CC instance>
<TxRqPrmsn>
State Response
Repeater +CME ERROR: 518
Mode (Service not supported when in Repeater Mode)

MOD-14-1758
7.3 CME errors within the Tetra PEI
7.3.1 Responses to commands
There are two types of response, informational text (such as baud rate) and result codes.
Result codes can be either final (e.g. OK) or unsolicited (e.g. +CTICN).
AT+CMD=?<cr> // a fictitious AT command requesting a response

<cr><lf>+CMD: data<cr><lf> // information response
<cr><lf>OK<cr><lf> // final result code
The format of these can generally be set with the following commands, although many of these have
restricted values within the Sepura products:
ATS3
ATS4
ATV
ATX
AT+CMEE
The effects of these individual commands have already been detailed. However, the interaction is studied
here.
The +CMEE command sets the level of CME error reporting.
1 Numeric
The Sepura terminal will only support Numeric reporting of errors. The responses CONNECT, BUSY etc
will be replaced with the appropriate informational responses as if +CMEE = 1.
The Sepura terminal will only support Verbose reporting of final result codes (ATV1)
The Sepura terminal will not support ATX

MOD-14-1758
7.3.2 CME errors and Sepura radios
The list of CME errors specified in [6] seems to have been cut and pasted from TS 100 916 (GSM). The
error codes are listed together with a 5-word description, but no explanation as to where they may be
used.
This leaves the manufacturer to map each command onto signals available within their product.
The Sepura radio needs to give errors not covered by ETS 300 392-2.
Direct mode / Trunked mode errors (CM data, status or SDS within DMO)
PTT contention
The CME errors supported by the Sepura PEI are shown below.
Values over 500 are proprietary to Sepura.
The Sepura function for some values depends on the customisation of PEI Compliance Level [8154] (0 or
1) as indicated.
CME Error ETS392-5 Description Sepura function

0: Another call active
2 MT adapter link reserved
1: Not used
0: AT command not recognised or out of context
3 Operation not allowed
1: At command out of context
0: AT command valid, but parameters incorrect
4 Operation not supported
1: AT command not supported
10 SIM not inserted SIM not inserted
11 SIM CHV1 (PIN) required SIM CHV1 (PIN) required
12 SIM Unblocking CHV1 (PUK) required SIM Unblocking CHV1 (PUK) required
13 SIM failure SIM failure (unable to read OPTA from smart card)
SIM wrong (unrecognised, disabled or failed to
15 SIM wrong
authenticate)
20 Memory full Out of memory, queue(s) full
24 Text string too long SDS message too long
25 Invalid characters in text string Invalid characters in SDS message
26 Dial string too long Dial string too long
27 Invalid characters in dial string Invalid characters in dial string
30 No network service Not registered
Network timeout (possibly due to call going out of
31 Network timeout
coverage)
32 Error decoding data SDS message length different from length field
Alpha character rather than numeric character in
33 Parameter wrong type
field
34 Parameter value out of range Value out of range
35 Syntax error Syntax error
36 Data received without command No AT at beginning of line
37 Timeout waiting for data Command half entered, then long pause
0: Not used
40 Service not supported in DMO 1: The MT supports the requested service but not
while it is in DMO
0: Not used
41 Transmissions are inhibited 1: The MT is in Transmit inhibit mode and is not able
to process the command in this state
0: Not used
1: The MT is involved in a signalling activity and is
42 Service temporarily not available
not able to process the command until the
current transaction ends
0: Not used
43 Service not supported in V+D 1: The MT supports the requested service but not
while it is in V+D
100 Unknown error
0: Service not available. This indicates that a
512 Manufacturer specific service is temporarily unavailable.
1: Not used

MOD-14-1758
CME Error ETS392-5 Description Sepura function

0: Service not supported in DMO. This indicates that
the application has asked for a combination of
513 Manufacturer specific services that can never be possible when in
DMO
1: Not used
0: Service not supported in TMO. This indicates that
the application has asked for a combination of
514 Manufacturer specific services that can never be possible when in
TMO
1: Not used
0: Transmissions are inhibited
To be used whenever a command cannot be
515 Manufacturer specific
completed because of TxI
1: Not used
Requested stack already active (Used in response to
516 Manufacturer specific
AT+CSPTSS)
0: Stack change in progress. (Used in response to
517 Manufacturer specific AT+CSPTSS)
1: Not used
518 Manufacturer specific Service not supported by DMO Repeater
519 Manufacturer specific Service not Supported by DMO Gateway
520 Manufacturer specific Service not supported in Temporary Disabled Mode

MOD-14-1758
8 TETRA SIMULTANEOUS TRAFFIC AND SDS LIMITATIONS
While voice, or circuit mode data, traffic is being transmitted or received in a call, the channel capacity for
signalling is different from that available when idle: in most circumstances the capacity is reduced. The
different channel characteristics are described below according to the data channel that is available to be
used for signalling. Channel abbreviations are those defined in [1].
SDS cannot be sent through the PEI (but can be sent from the user interface of the radio
or from an integral GPS module) while the PEI is in Transparent Data Mode during a
circuit-mode data call, see 3.2.
Call State UPLINK Channel Types DOWNLINK Channel Types

MCCH, Common SCCH or MCCH, Common SCCH or
No Call
Assigned SCCH Assigned SCCH
Full Duplex Call
SACCH or STCH SACCH or STCH
(voice or data)
RX in Half Duplex
SACCH SACCH or STCH
Same Base Site Call
RX in Half Duplex FACCH
SACCH or STCH
Inter-Site Call
TX in Half Duplex
SACCH or STCH SACCH or STCH
Same Base Site Call
TX in Half Duplex FACCH
SACCH or STCH
Inter-Site Call
Idle in Half Duplex Call
FACCH FACCH
(Call is open, but no-one is talking on
the channel)

MOD-14-1758
where:
Channel Type SDS message restrictions Speed and Contention
MCCH, Limited by [1] to 255 characters The SwMI controls when random
Common SCCH including SDS-TL header, but a access opportunities are available and
SwMI may only support a smaller when capacity is allocated for
or Assigned SCCH message (typically 140 characters completion of the transmission of the
plus header) SDS according to requirements for
Main Control Channel usage of the MCCH. Typically less
or Common
than 1s for a 140 character message.
(or Assigned) Secondary
Control Channel
FACCH Limited by [1] to 255 characters, but The SwMI controls when random
recommended to be no more than access opportunities are available and
127 including SDS-TL header, but a when capacity is allocated for
Fast Associated Control
Channel SwMI may only support a smaller completion of the transmission of the
message (typically 140 characters SDS according to requirements for
plus header) usage of the FACCH. Typically faster
than MCCH as contention for use of
the channel is much smaller.
SACCH Limited by [1] to 255 characters, but Speed of transfer will be slow. There is
recommended in [1] to be no more only sufficient capacity on the SACCH
than 127 including SDS-TL header. for approximately 33 characters per
Slow Associated Control
Channel Because SAACH channel capacity is second (in bursts of 33 characters)
very small, a SwMI may only support without any contention for the use of
SDS messages which are much the channel. A 120 character message
smaller (typically 30 characters or will typically take about 5 seconds to
less). be transmitted.
STCH Limited by [1] to 18 characters Speed of transfer will be fast as the
including SDS-TL header. Messages whole message is transmitted in two
which are longer than this will be adjacent sub-slots (i.e. approximately
Stealing Channel
transmitted using the SACCH 14ms)
Size limitations refer to the Logical Link Control (LLC) - Basic Link Air Interface Signalling
and do not apply when using LLC Advanced Link. Advanced Link is not currently
supported by Sepura terminals.
All Half Duplex Calls apply equally to Group or Individual Call Types
All ‘characters’ are 8-bit
When messages are fragmented, except where the whole messages can be sent using
the STCH, the first part of the message is sent by random access, and subsequent
fragments are sent in granted slots which are controlled by the SwMI
Status messages are short enough not to require fragmentation. They will be transmitted
and received using whichever channel is available (STCH, FACCH, SACCH, MCCH)

MOD-14-1758
The Stealing Channel (where transmission capacity is stolen from the speech or data
traffic and used for signalling, including SDS) is governed by rules in [1] concerning the
maximum size of a message, and how often a part of the traffic channel may be stolen.
Any message which needs to be sent when the only channels available are STCH and
SACCH and which cannot meet the restrictions for use of STCH is sent using the SACCH
When a SDS message has been queued in a Sepura radio, ready for transmission, other
messages (e.g. PTT on/off messages) from the same radio will be delayed until the first
SDS message has been completely transmitted. This queuing of SDS messages will be
particularly noticeable on a SACCH. Signalling messages being transmitted by other
radios in the call may also be delayed depending on the SwMI’s allocation of random
access opportunities on the available channel
Although the PEI is able to support SDS messages up to the maximum size permitted on
the TETRA air interface (255 characters including SDS-TL header where used), and the
user interface of the radio is able to display messages of that length, there are smaller
size limits for messages saved in the Data Store and for those created from the user
interface of the radio

MOD-14-1758
9 EXTERNAL DIGITAL INPUTS AND OUTPUTS

Sepura mobile product supports one digital output and three digital inputs on the transceiver unit and a
further digital output and three digital inputs on each attached AIU. Consoles do not support the additional
digital input and outputs.
A Sepura hand-held product (SRH3000 series and STP8000 series) in a car kit supports a single digital
output and does not support any digital inputs.
9.1 Inputs
Digital inputs are available on the Mobile Transceiver power connector pins 7, 8, 15 and on pins 6, 7, 8 of
the data connector of the AIU. Each digital input requires a minimum input voltage of 2.0V to detect a
‘high’ state and a maximum input voltage of 0.8V to detect a ‘low’ state. They are protected against
accidental application of vehicle supply voltage.
Each input will detect a change of state which is held for at least 232ms. Each of the positive-going
change and the negative-going change on each physical input may be customised to trigger a soft-key
function by setting the customization parameter ‘Soft Key for External Digital Input’.
By their nature, some of these soft-key functions may not complete successfully even
when the state change on the digital input has been held for sufficient time and has
been detected. For example, the sending of a status message may be prevented by
the terminal being out-of-service. It is recommended that these inputs should only be
used for soft-key functions which do not require any feedback or in situations where
that feedback can be determined by other means (such as alert tones and console
display messages).
Where feedback is required to be provided to an automated process, the PEI AT Command Interface, as
described elsewhere in this document, provides an alternative interface for several functions whose
successful execution can be fully acknowledged, including the sending of status and SDS-TL messages;
the changing of selected talk group and the changing of operational mode (DMO, TMO, etc.).
Where it is necessary in order to perform the requested function, many soft key
functions will terminate conflicting activity such as a call that is in progress. Such a
terminated call may be an emergency call.
Soft key functions that do this include, for example, those which change operating
mode (DMO, TMO, etc.) and those which change talk group.
9.2 Outputs
Digital outputs are available on the Mobile Transceiver power connector pin 14, on the AIU data connector
pin 1 and on the car kit vehicle harness pin 6. Both the SRH3000 car kit and the STP8000 car kit use the
same vehicle harness interface. Each digital output is an open drain, active low device with a maximum
sink current of 500mA. A relay, or other interface device, should be used when controlling high current
devices such as a vehicle horn or lights. The voltage drop at 500mA does not exceed 800mV. The open
voltage should not exceed the battery supply to the Mobile or Car Kit. These outputs are protected against
accidental short circuit to the vehicle supply voltage.
Each output can be customized to perform one of a set of five predefined functions; or can be controlled
(on, off, pulse) by soft-key functions, which themselves may be triggered by pressing a key, changing the
state on a digital input or by the reception of a status message.
When pulsed by a soft key function, the output remains active for a period between 150ms and 170ms.

MOD-14-1758
The five predefined functions are:

 Activated on incoming call setup completion or on outgoing group call setup completion
Deactivated on end of call
 Activated on outgoing alarm call initiation
Deactivated depends upon customization of the parameter ‘Alarm External Alert Time’:
Never deactivated (until switch-off)
After time 1..99 seconds
On completion of call setup
 Activated on incoming hooking call indication
Deactivated on end of incoming call indication
 Activated on any incoming call indication
Deactivated on the first to occur of:
Any key press
After time 1..60 seconds
End of call
(additionally, the availability of this function can be enabled / disabled by a soft key function)
 Activated while the audio signal ‘line output’ is enabled
Deactivated while the audio signal ‘line output’ is disabled

MOD-14-1758
10 GLOSSARY
Term Description
AI Air Interface
AIU Applications Interface Unit
BER Bit Error Ratio
C1 Path loss parameter for the serving cell
C2 Path loss parameter for neighbour cells
CC Call Control
CCH Control Channels
CM Circuit Mode
DGNA Dynamic Group Number Assignment
DMO Direct Mode Operation
DMO gateway A device which allows users working in direct mode to communicate with users in
trunked mode. (This is often used to extend the working range of a radio)
DTR Data Terminal Ready
Duplex Duplex calls are telephone type calls in which both parties can talk simultaneously
ETSI European Telecommunications Standards Institute
FACCH Fast Associated Control Channel
GPRS General Packet Radio Service
GPS Global Positioning System
GSM Global System for Mobile Communications
GTSI Group TETRA Subscriber Identity
Half-duplex Half-duplex calls are when only one party can talk (transmit) at any time.
ISSI Individual Short Subscriber Identity
ITSI Individual TETRA Subscriber Identity
ITU International Telecommunication Union
LA Location Area
LCC Logical Link Control
MCCH Main Control Channel
MDT Mobile Data Terminal
MT Mobile Termination
NMEA National Marine Electronics Association
PABX Public Automatic Branch Exchange
PD Packet Data
PDP Packet Data Protocol
PDU Protocol Data Unit
PEI Peripheral Equipment Interface

MOD-14-1758
PGS Priority Group Scanning

PID Protocol Identifier
PPP Point-to-Point Protocol
PSTN Public Switched Telephone Network
PTT Press To Talk
RSSI Received Signal Strength Indicator
SACCH Slow Associated Control Channel
SCCH Secondary Control Channel
SDS Short Data Services
Simplex See Half-duplex
SSI Short Subscriber Identity
STCH Stealing Channel
SwMI Switching and Management Infrastructure
Talk-group A pre-defined group of users
TCH Traffic Channel
TE Terminal Equipment
TETRA Terrestrial Trunked Radio
TMO Trunked Mode Operation
TSI TETRA Subscriber Identity
TXI Transmissions Inhibited
UDSL User Defined Scan List
UI User Interface

MOD-14-1758
11 APPENDIX 1: COMMANDS AND SOFTWARE VERSIONS
11.1 Table to show which commands are in which software versions
V10.12
V10.13
V10.14
V10.5
V10.8
V10.9
v10.0
V6.0
V6.3
V7.0
V7.2
V8.0
V8.6
V9.0
V9.5
AT Command
A/               
ATA              * 
ATD  *     *     *   
ATE               
ATH               
ATI  * *   *   * * *    
ATO               
ATQ               
ATR    
ATS0               
ATS2               
ATS3               
ATS4               
ATS5               
ATV               
ATZ               
AT+CBC     *        
AT+CCI    *        *   
AT+CGPS *          *    
AT+CLVL               
AT+CMEE               
AT+CMGS *        *   *   
AT+CNCI    *        *   
AT+CNUM       *        
AT+CNUMD         
AT+CPIN         
AT+CREG            * *  
AT+CSPBOPTA         
AT+CSPSCTR       
AT+CSPDCS            *   
AT+CSPICPN *              

MOD-14-1758
V10.12
V10.13
V10.14
V10.5
V10.8
V10.9
v10.0
V6.0
V6.3
V7.0
V7.2
V8.0
V8.6
V9.0
V9.5
AT Command
AT+CSPKA       
AT+CSPLOGIO        
AT+CSPRTC               
AT+ CSPSCS       
AT+CSPTAA1         
AT+CSPTAA2    
AT+CSPTAA3      *
AT+CSPTAP1         
AT+CSPTAP16       
AT+CSPTAP17       
AT+CSPTAP18       
AT+CSPTGF       *  *      
AT+CSPTGFC   *  *  *      
AT+CSPTGFS    *   *  *   *   
AT+CSPTGG *  *         *   
AT+CSPTGI     *  *      
AT+CSPTNI         
AT+CSPTNS         
AT+CSPTSS    *           
AT+CSPTR               
AT+CSPTSSN               
AT+CSQ    *        *   
AT+CTBCT         
AT+CTGS   *         * *  
AT+CTSDC       *     *   
AT+CTSDS *              
AT+CTSP *  * *   *     *   
AT+CTSTR      *   
AT+CTXD  *          *   
AT+CUTXC               
AT+GMI               
AT+GMM  * * *  *   * * *    
AT+GMR      *         
AT+GSN   
AT+IPR               

MOD-14-1758
V10.12
V10.13
V10.14
V10.5
V10.8
V10.9
v10.0
V6.0
V6.3
V7.0
V7.2
V8.0
V8.6
V9.0
V9.5
AT Command
AT&F               
AT@N               
AT@T               
AT@Z               
+++               

MOD-14-1758
11.2 Table to show which responses are in which software versions
V10.12
V10.13
V10.14
V10.0
V10.5
V10.8
V10.9
V6.0
V6.3
V7.0
V7.2
V8.0
V8.6
V9.0
V9.5
AT Response
+CDTXC               
+CMGS            *   
+CNUMD         
+CREG            * *  
+CSPSCTR    *   
+CSPBOPTA    
+CSPBTOPTA         
+CSPDCS            *   
+CSPICP               
+CSPLOGIO        
+CSPSCS    *   
+CSPTD               
+CSPTSSA    *           
+CTBCT         
+CTCC  *             
+CTCR  *             
+CTGS    
+CTICN  * *    *        
+CTOCP  *     *        
+CTSDSR *      *        
+CTXG  *             
+CTXI * *             
+CTXN    *           
+CTXW    *           
 = In this version
* = changed from previous description

MOD-14-1758
12 APPENDIX 2: DUMMY OPTA
For terminals that support OPTA Inclusion, the first 24 characters of an outgoing text message, sent from
the PEI using AT+CMGS will need to be a dummy OPTA.
A Dummy OPTA comprises of 24 space characters encoded according to the character set defined for the
outgoing SDS message.
Whether a Dummy OPTA needs to be included is a function of both the terminal and the SwMI that the
terminal is operating in. An application can determine whether a terminal requires OPTA using the
AT+CSPBOPTA command (see section 7.1.28). When a terminal requires OPTA, all text messages will
be required to include the dummy OPTA. The terminal will, in turn, insert the true value of the OPTA, prior
to sending the SDS message over the air interface.
OPTA Inclusion, when applied, is required for SDS message with the following PID values:
PID Description
2 Simple Text
9 Immediate Display text
130 SDS TL Text message
137 SDS TL Immediate Display
§
138 UDH – Concatenated Text message
Note: The terminal will only process a single outgoing UDH message at a time. If a UDH
st
fragment is used (other than the 1 fragment) with a different UDH message reference
st
than contained in the most recent 1 fragment sent, then the latter UDH message will be
rejected with '+CME ERROR : 25'
st
Sending a new 1 fragment of a UDH will succeed but will invalidate the sending of any
UDH message fragment that contains a UDH message reference other than the last sent
st
1 fragment.
Note that OPTA Inclusion is not required for delivery reports.
§ In the case of UDH messages the OPTA is only required in the first fragment of a given concatenated SDS message.

MOD-14-1758 DIUG Issue 1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MOD-14-1758 DIUG Issue 1

Uploaded by

Copyright:

Available Formats

Sepura TETRA Terminal

Data Interface User Guide

This document is issued under NDA only

© SEPURA PLC 2014

Issued by Issue 1 Page 2 of 200

Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

Issue 1 21 July 2014 Initial Version

[1] ETSI specification ETS 300 392-2 Edn 1 - http://www.etsi.org/

[2] ETSI specification ETS 300 392-2 Edn 2 (v2.3.2) - http://www.etsi.org/

[3] NMEA-0183 version 2.01 - http://www.nmea.org/

[4] ITU V.24 - http://www.itu.int/

[5] ITU V.250 - http://www.itu.int/

[6] ETSI specification EN 100 392-5 version 1.3.5- http://www.etsi.org/

[8] TIP: TTR 001-17 Radio User Assignment - http://www.tetramou.com/

Issued by Issue 1 Page 3 of 200

Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

Note icon, emphasizes related, reinforcing, or important information.

Issued by Issue 1 Page 4 of 200

Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

2 PHYSICAL INTERFACE DETAILS ..........................................................................10

2.2 Mobile and Gateway ....................................................................................................................... 15

2.3 Serial Protocol ................................................................................................................................ 17

2.4 Dual Serial port ............................................................................................................................... 18

2.6 USB functionality ............................................................................................................................ 19

2.7 Connector Protector ....................................................................................................................... 19

3 PEI AT COMMAND INTERFACE COMMAND SYNTAX .........................................20

3.2 Transparent Data Mode .................................................................................................................. 21

4 PEI TEXT MESSAGING ...........................................................................................22

4.2 Supported SDS Messages ............................................................................................................. 24

4.3 SDS-TL Message Encoding ........................................................................................................... 25

4.4 SDS-TL Short-form Delivery Report ............................................................................................. 27

4.5 SDS-TL Report ................................................................................................................................ 28

4.6 SDS-TL Compliance ....................................................................................................................... 29

4.7 Restrictions ..................................................................................................................................... 30

4.8 Short Data and Status Message Examples ................................................................................. 31

Issued by Issue 1 Page 5 of 200

Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

4.8.8 SDS Message Routing .................................................................................................................................................... 34

5 PEI CIRCUIT MODE CALLS ....................................................................................37

5.2 Circuit-mode Data Calls ................................................................................................................. 40

6 PEI PACKET DATA .................................................................................................42

6.2 IP Addresses (Static/Dynamic) ...................................................................................................... 43

6.3 Dialling from Windows and Linux ................................................................................................. 43

7 PEI AT COMMAND SET OVERVIEW ......................................................................45

Issued by Issue 1 Page 6 of 200

Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

7.1.31 AT+CSPICPN - Incoming Call Proprietary Extensions Notification Command ............................................................. 87

7.2 Unsolicited Responses ................................................................................................................ 154

7.3 CME errors within the Tetra PEI .................................................................................................. 186

Issued by Issue 1 Page 7 of 200

Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

7.3.2 CME errors and Sepura radios ...................................................................................................................................... 187

8 TETRA SIMULTANEOUS TRAFFIC AND SDS LIMITATIONS .............................189

9 EXTERNAL DIGITAL INPUTS AND OUTPUTS ....................................................192

9.2 Outputs .......................................................................................................................................... 192

11 APPENDIX 1: COMMANDS AND SOFTWARE VERSIONS ..............................196

12 APPENDIX 2: DUMMY OPTA.............................................................................200

Issued by Issue 1 Page 8 of 200

Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

Issued by Issue 1 Page 9 of 200

Sepura Product Management Commercial-in-Confidence ©Sepura plc 2014

2 PHYSICAL INTERFACE DETAILS