TCR100 SPECIFICATION
| MOBILE | |
| Mobile module | 4G+ (LTE-A) – Cat 6 up to 300 Mbps, 3G – Up to 42 Mbps |
| Status | Signal strength, SINR, RSRP, RSRQ, Bytes sent/received, connected band, carrier aggregation, IMSI, ICCID |
| SMS | SMS status, SMS configuration, send/read SMS via HTTP POST/GET, Email to SMS, SMS to Email, SMS to HTTP, SMS to SMS, SMS auto reply |
| USSD | Supports sending and reading Unstructured Supplementary Service Data messages |
| Black/White list | Operator black/white list |
| Multiple PDN | Possibility to use different PDNs for multiple network access and services |
| Band management | Band lock, Used band status display |
| APN | Auto APN |
| Bridge mode | Direct connection (bridge) between mobile ISP and device on LAN |
| WIRELESS | |
| Wireless mode | 2.4 GHz (802.11 b/g/n, 2×2 MIMO), 5 GHz (802.11 ac, 1×1 MIMO), Access Point (AP), Station (STA) |
| WiFi security | WPA3-EAP, WPA3-SAE, WPA2-Enterprise-PEAP, WPA2-PSK, WEP; AES-CCMP, TKIP, Auto Cipher modes, client separation |
| ESSID | ESSID stealth mode |
| Wireless Hotspot | Captive portal (Hotspot), internal/external Radius server, SMS OTP, MAC auth, built in customizable landing page, walled garden |
| Wireless mesh/roaming | Wireless mesh (802.11s), fast roaming (802.11r) |
| ETHERNET | |
| WAN | 1 x WAN port (can be configured as LAN) 10/100 Mbps, compliance with IEEE 802.3, IEEE 802.3u standards, supports auto MDI/MDIX crossover |
| LAN | 1 x LAN port, 10/100 Mbps, compliance with IEEE 802.3, IEEE 802.3u standards, supports auto MDI/MDIX crossover |
| NETWORK | |
| Routing | Static routes, Dynamic routes |
| Network protocols | TCP, UDP, IPv4, IPv6, ICMP, NTP, DNS, HTTP, HTTPS, SMTP, SSL v3, TLS, ARP, VRRP, PPP, PPPoE, UPNP, SSH, DHCP, Telnet client, SNMP, MQTT, Wake on LAN (WOL) |
| Connection monitoring | Ping Reboot, Wget reboot, Periodic Reboot, LCP and ICMP for link inspection |
| Firewall | Port forwards, traffic rules, NAT rules, custom rules |
| DHCP | Static and dynamic IP allocation, DHCP Relay, Relayd |
| QoS / Smart Queue Management (SQM) | Traffic priority queuing by source/destination, service, protocol or port, WMM, 802.11e |
| DDNS | Supported >25 service providers, others can be configured manually |
| Network backup | Mobile, Wired and WiFi WAN options, each of which can be used as an automatic Failover |
| Load balancing | Balance Internet traffic over multiple WAN connections |
| SSHFS | Possibility to mount remote file system via SSH protocol |
| SECURITY | |
| Authetication | Pre-shared key, digital certificates, X.509 certificates |
| Firewall | Pre-configured firewall rules can be enabled via WebUI, unlimited firewall configuration via CLI; DMZ; NAT; NAT-T |
| Attack prevention | DDOS prevention (SYN flood protection, SSH attack prevention, HTTP/HTTPS attack prevention), port scan prevention (SYN-FIN, SYN-RST, X-mas, NULL flags, FIN scan attacks) |
| VLAN | Tag based VLAN separation |
| Mobile quota control | Custom data limits for SIM card |
| WEB filter | Blacklist for blocking out unwanted websites, Whitelist for specifying allowed sites only |
| Access control | Flexible access control of TCP, UDP, ICMP packets, MAC address filter |
| VPN | |
| OpenVPN | Multiple clients and a server can run simultaneously, 12 encryption methods |
| OpenVPN Encryption | DES-CBC, RC2-CBC, DES-EDE-CBC, DES-EDE3-CBC, DESX-CBC, BF-CBC, RC2-40-CBC, CAST5-CBC, RC2-64-CBC, AES-128-CBC, AES-192-CBC, AES-256-CBC |
| IPSec | IKEv1, IKEv2, with 5 encryption methods for IPsec (DES, 3DES, AES128, AES192, AES256) |
| GRE | GRE tunnel |
| PPTP, L2TP | Client/Server instances can run simultaneously, L2TPv3 support |
| Stunnel | Proxy designed to add TLS encryption functionality to existing clients and servers without any changes in the program’s code |
| DMVPN | Method of building scalable IPsec VPNs |
| SSTP | SSTP client instance support |
| ZeroTier | ZeroTier VPN client support |
| WireGuard | WireGuard VPN client and server support |
| MODBUS | |
| MODBUS TCP SLAVE | |
| ID filtering | Respond to one ID in range [1;255] or any |
| Allow remote access | Allow access through WAN |
| Custom registers | MODBUS TCP custom register block, which allows to read/write to a file inside the router, and can be used to extend MODBUS TCP slave functionality |
| MODBUS TCP MASTER | |
| Supported functions | 01, 02, 03, 04, 05, 06, 15, 16 |
| Supported data formats | 8 bit: INT, UINT; 16 bit: INT, UINT (MSB or LSB first); 32 bit: float, INT, UINT (ABCD (big-endian), DCBA (little-endian), CDAB, BADC), HEX, ASCII |
| MQTT GATEWAY | |
| Gateway | Allows sending commands and receiving data from MODBUS Master trough MQTT broker |
| DNP3 | |
| Supported modes | TCP Master, DNP3 Outstation |
| DATA TO SERVER | |
| Protocols | HTTP(S), MQTT, Azure MQTT, Kinesis |
| MONITORING & MANAGEMENT | |
| WEB UI | HTTP/HTTPS, status, configuration, FW update, CLI, troubleshoot, event log, system log, kernel log |
| FOTA | Firmware update from server, automatic notification |
| SSH | SSH (v1, v2) |
| SMS | SMS status, SMS configuration, send/read SMS via HTTP POST/GET |
| Call | Reboot, Status, Mobile data on/off, Output on/off |
| TR-069 | OpenACS, EasyCwmp, ACSLite, tGem, LibreACS, GenieACS, FreeACS, LibCWMP, Friendly tech, AVSystem |
| MQTT | MQTT Broker, MQTT publisher |
| SNMP | SNMP (v1, v2, v3), SNMP trap |
| JSON-RPC | Management API over HTTP/HTTPS |
| MODBUS | MODBUS TCP status/control |
| RMS | Teltonika Remote Management System (RMS) |
| IoT PLATFORMS | |
| Clouds of things | Allows monitoring of: Device data, Mobile data, Network info, Availability |
| ThingWorx | Allows monitoring of: WAN Type, WAN IP, Mobile Operator Name, Mobile Signal Strength, Mobile Network Type |
| Cumulocity | Allows monitoring of: Device Model, Revision and Serial Number, Mobile Cell ID, ICCID, IMEI, Connection Type, Operator, Signal Strength, WAN Type and IP |
| Azure IoT Hub | Can send device IP, Number of bytes send/received, Mobile connection state, Network link state, IMEI, ICCID, Model, Manufacturer, Serial, Revision, IMSI, SIM State, PIN state, GSM signal, WCDMA RSCP, WCDMA EC/IO, LTE RSRP, LTE SINR, LTE RSRQ, CELL ID, Operator, Operator number, Connection type, Temperature, PIN count to Azure IoT Hub server |
| SYSTEM CHARACTERISTICS | |
| CPU | QCA9531, MIPS 24kc, 650 MHz |
| RAM | 128 MB, DDR2 |
| FLASH storage | 16 MB, SPI Flash |
| FIRMWARE / CONFIGURATION | |
| WEB UI | Update FW from file, check FW on server, configuration profiles, configuration backup |
| FOTA | Update FW/configuration from server |
| RMS | Update FW/configuration for multiple devices at once |
| Keep settings | Update FW without losing current configuration |
| POWER | |
| Connector | 4 pin industrial DC power socket |
| Input voltage range | 9 – 30 VDC, reverse polarity protection, voltage surge/transient protection |
| Power consumption | 3.7 W average, 9.3 W max |
| PHYSICAL INTERFACES (PORTS, LEDS, ANTENNAS, BUTTONS, SIM) | |
| Ethernet | 2 x RJ45 ports, 10/100 Mbps |
| Status LEDs | 1 x Internet, 1 x WiFi, 3 x Mobile connection strength, 2 x Ethernet status |
| SIM | 1 x SIM slots (Mini SIM – 2FF), 1.8 V/3 V, external SIM holder (Embedded SIM variant available) |
| Antenna | 2 x SMA for LTE, 2 x Internal for 2.4 GHz WiFi, 1 x Internal for 5 GHz WiFi |
| Power | 1 x 4 pin DC connector |
| WPS | WPS activation button |
| WiFi On/Off | WiFi enable/disable button |
| Reset | Reboot/User default reset/Factory reset button |
| PHYSICAL SPECIFICATION | |
| Casing material | Plastic housing with aluminum screws and heatsink |
| Dimensions (W x H x D) | 150 x 37 x 105 mm |
| Weight | 376 g |
| Mounting options | Flat surface placement |
| OPERATING ENVIRONMENT | |
| Operating temperature | -40 C to 75 C |
| Operating humidity | 10 % to 90 % non-condensing |
Does the TCR100 router support DIN rail mounting?
Yes - The Teltonika TCR100 4G Router can be installed using a DIN rail mounting kit. These DIN rail kits are sold separately.
Does the TCR100 router support DIN rail mounting?
Yes - The Teltonika TCR100 4G Router can be installed using a DIN rail mounting kit. These DIN rail kits are sold separately.
How long does it take the TCR100 to connect to 4G after powering on?
Once the TCR100 router has been configured then after power cycling the router it usually takes around 1 minute and 30 seconds for the router to connect to the 4G network.
Can the TCR100 be used for remote access to CCTV?
Yes - the Teltonika TCR100 can be used for remote access to CCTV but you will need to use a Fixed IP SIM Card which is a service that provides the router with a fixed, public IP address. Remote access to CCTV can not be achieved using a standard mobile data SIM card.
