YateOTA compatible keystore
April 18, 2024
This page describes how a Keystore API should look like to be compatible with YateOTA, in case you opt to build your own Keystore/middleware instead
This page describes how a Keystore API should look like to be compatible with YateOTA, in case you opt to build your own Keystore/middleware instead
From release tag 6005 Starting with release tag 6005, there’s a new feature that lets me set configurations on all YateUCN devices at once using
From release tag 6005 Combined attach can now be configured directly from YateMMI interface Combined attach options For multiple YateUCN that have the IMS configured, Combined
From release tag 6005 Starting with release tag 6005, IMS configuration is possible directly from the YateMMI interface. For multiple YateUCNs that have the IMS
Introduction to Roaming Numbers Roaming numbers can be set using YateMMI interface(starting with release 6005) together with the option to automatically Generate routing for roaming
New features YateMMI has a few new features that will help with easier set-up configuration. Automatic generation of Routing Rules in YateMMI for: Roaming numbers
Testing OTA commands in OTA SMSC mode Initial set-up for OTA SMSC Mode Yate OTA Server has three available Delivery Mode Configurations, OTA Scheduler, OTA
Testing OTA commands in Local mode Card Reader and Card Auth Card Reader While operating in OTA Local mode we recommend using ACR-39 card reader.
RAM campaigns introduction The purpose of the Remote Applet Management (RAM) Campaigns are to manage the Applets that resides on the SIM and communicate with
Remote File Management (RFM) Operations. The purpose of the RFM (Remote File Management) campaign is to manage values on the SIM’s files. Although Update and Custom RFM
SC NULL TEAM IMPEX SRL, CUI: RO16352909
Address: Str. Occidentului 3, et 3, ap. 5, Sector 1, Bucuresti, Romania, 010981