![tell Pager4 3GA.IN4.R2 Installation And User Manual Download Page 29](http://html1.mh-extra.com/html/tell/pager4-3ga-in4-r2/pager4-3ga-in4-r2_installation-and-user-manual_1083867029.webp)
29
CID reporting to CMS over IP:
You can configure up to 4 IP availabilities of CMS servers or receivers as follows.
Name
: CMS server or receiver name. The name entered in this section is used for identification
of the server/receiver within the program, and the program will also use this name when
configuring notification templates.
IP address/domain name
: CMS server or receiver IP address or domain name. When a SIM
card with a private APN is used, and the given server or receiver is not in the same APN, it is
necessary to enable access of the server/receiver IP address in the given APN.
Port
: CMS server or receiver communication port number.
Protocol
:
select the appropriate communication protocol for the given server or receiver from
the drop-down menu. Available protocols:
TELLMon
,
TEX
,
SIA IP
(ANSI/SIA DC-09-2007).
Supervision message
: enable/disable supervision message sending. Supervision message
sending cannot be disabled in case of using the TEX or the TELLMon communication protocol.
Supervision message interval / Unit of measure
: if supervision message sending is enabled,
you can configure the sending interval and unit of measure. The supervision message sending
interval can be configured from 10 seconds to 30 minutes.
Network protocol
:
according to the chosen communication protocol you can use
TCP
or
UDP
network protocol. The UDP protocol allows for less data traffic. For TEX communication protocol
only TCP network protocol is available.
AES key
: the custom AES encryption key can be used for SIA IP protocol only. If an encryption
key is configured, the SIA IP packages will be encrypted with the given key and they have to be
decrypted on the receiver side using the same key. The maximum length of the AES key is up to
16 characters, or up to 32 characters in case of using hexadecimal format.
Send each message in a new session:
if required for the given receiver, in case of the
SIA DC-09
protocol it can be enabled to send each message in a new TCP session. In case of
using UDP, if this option is enabled, the device will open a new port for each message.
CID reporting to CMS over DTMF-based voice call:
Please note that in certain cases you may experience issues with reporting to CMS over DTMF-
based voice call. Success of communication highly depends on the properties of the given GSM
network, such as line quality, line noise and DTMF handling. Due to network digitalization, DTMF
signal tones might get distorted while being processed by the network in such extent that the
receiver will not be able to interpret the transmitted Contact ID event codes. The risk of this is
even higher if the signal is transmitted through multiple GSM operators (e.g. if using SIM cards
from different operators on the transmission and reception site). The device offers an option to
adjust the signals in order to correct such problems, therefore if necessary, special DTMF
communication parameters can be configured in the “
Advanced settings
” menu.
You can configure up to 2 DTMF receiver phone numbers (
TEL1 DTMF
and
TEL2 DTMF
) as
follows.
Name
: CMS DTMF receiver name. The name entered in this section is used for identification of
the receiver within the program, and the program will also use this name when configuring
notification templates.
Phone number
: the phone number of the DTMF receiver.