Answers to frequently asked questions about YateBTS and our RAN and Core Network products.
MO calls already start with MSISDN as Calling Party Number (A-number) and generally do not require any changes.
Only in the case of multi-MSISDN can home routing be required using CAMEL to rewrite the A-number to the desired one.
A MVNO never has MSRNs because it does not have MSCs to which MT calls should be routed.
It may instead have various other types of numbers for landing or services.
If it is MNO then it will have its own MSRNs which if it receives inbound roamers it will communicate to others under the conditions below.
If it does not have inbound roamers then the calls to MSRN will come only from their own GMSC and the rules are internal.
A MNO can tell you its own MSRN range, if those numbers are inaccessible from normal telephony and / or may require special routing.
It is common for an MNO to allocate special calling routes for:
MSRNs, possibly each MSC with its range and route (so that the MNO does not have to route between them, to get there from the first place)
MO calls that are home routed by local rules set by the MNO
Separate Billing - Many billing platforms require separate physical trunks or addresses to separate MVNO / local roaming from interconnect billing
Definitions:
Local / national roaming = the MVNO subscriber is in the MNO network with which he has a contract
Roaming (generic / international) = the MVNO subscriber is in a different network than the MNO with which he has a national contract
Interconnect = call between different networks (A and B are not subscriptions of the same operator) regardless of roaming
YateBTS products can be installed on the following Linux distributions: Mageia, CentOS and Fedora.
For our clients we recommend: Mageia 7 as it has a newer kernel than CentOS 7.
These three distributions use the same file format .rpm for the packages.
RPMs are often collected centrally in one or more repositories on the internet. Most sites have their own RPM repositories which may either act as local mirrors of such internet repositories or be locally maintained collections of useful RPMs.
urpmi (Mageia), yum (CentOS) and dnf (Fedora and other RPM-based distros) are package management tools used for installing, removing, updating and querying software packages of local or remote (networked) media.
Package management tools attempt to solve issues which might be cause by dependencies, software compilation from source code, wrongful placement of common installation and configuration files, distribution of software with bugs. And, thus, developers attempt to increase the overall quality and coherence of a Linux-based operating system
For example, when you want to install yate-smsc. The package management tool queries the Yate repository in search for the full name of the package which might be something like: yate-smsc-1.3-1_r5240_r5342_prot.mga7.rpm
The package management tool will carry out any dependencies and it will set every file contained by the rpm package in the appropriate location without the intervention of the user.
To see the contents which have been installed by yate-smsc package use the following command:
rpm -q yate-smsc
We have worldwide MVNOs as clients. The process might be long and needs plenty documentation, so we build up a page to give you a big picture: https://yatebts.com/solutions_and_technology/how-to-become-a-full-mvno/
We have a reseller program and are always looking for new partnerships. You can send us an email on this subject at: sales@ss7ware.com or contact@ss7ware.com and we will provide you the contracts.
Few benefits our resellers have are:
Free shipping to any destination worlwide
Fixed prices, but we do provide discounts & rebates to our reseller
Dropshipping – no need to buy stock
Yes, we have operational MVNOs in many countries are using our solutions. Few of them are in: Spain, Germany, France, Czech Republic, Denmark, Netherlands etc.
These are 3 successful stories and you can also find testimonials from the clients that are using YateBTS software: https://yatebts.com/solutions_and_technology/best-mvno-list-successful-stories/
The errors are handled in three ways:
Errors authoritatively unrecoverable - no retries are attempted, the SMS fails immediately
Examples: unknownSubscriber, callBarred, teleserviceNotProvisioned, equipmentProtocolError, equipmentNotSM-Equipped
Errors caused by temporary subscriber or memory unavailability - they have their own large retry interval and immediate retry on notification
Examples: absentSubscriber, unidentifiedSubscriber, memoryCapacityExceeded, sc-Congestion, sm-DeliveryFailure
Any other errors - it is unlikely the message will pass through but we retry anyway
Example:
If the firewall responds with an incorrect error (for example, “Invoke-IncorrectParameter”), it will fall in the 3rd case, causing a few retries followed by message drop.
In this scenario, the problem would be in the SMS User Data.
A SMS firewall in the visited MSC detects an incorrect User Data Header and returns this unexpected error (the standard has no support for firewalls).
If there wasn’t any firewall, the phone would have rejected the message with equipmentProtocolError telling us that it will never accept it because it is malformed.
We support all FDD/TDD bands except for LTE-U bands.
We do support the following bands for LabKit : 1,2,3,4,5,7,8,11,12,13,14,17,18,19,20,21,24,25,26,28,30,31,34,37,38,39,40,41,42,44,46,47,48,49,50,51,52,53,65,66,68,70,71,72,73,74,85,87,88
We support the following bands for SatSite
1,2,3,4,5,7,8,11,12,13,14,17,18,19,20,21,24,25,26,28,30,34,37,38,39,40,41,42,44,46,47,48,49,50,51,52,53,65,66,68,70,71,74,85
We do NOT support the following bands: 29, 32, 67,69, 75,76.
You can learn more about LTE frequency bands at: https://en.wikipedia.org/wiki/LTE_frequency_bands
- In any GSM mode, you don't need allowance from the CORE Network to use a PLMN-id (MCC/MNC)
- Only in LTE enb mode, when LabKit is working as an eNodeB you need that MME entity allows PLMN-ID broadcasted by the eNodeB equipment.
So, if you want to test different MCC/MNC in 4G LTE mode, please :
- Give the list of the MCC-MCN you want to use for the next 2 weeks (in order to add it in the Hosted Core as permitted PLMN-IDs)
Ex: 00101, 22201-22210, etc. (source: https://en.wikipedia.org/wiki/Mobile_Network_Codes_in_ITU_region_2xx_(Europe) )
- This way you won't need to buy a MiniCore, yet*
* I say yet because in time you might want to do tests with VoLTE, Voice over WiFi, or USSD
Straight answer:
- Hosted Core does not allow access to the customer to change the allowed MCC/MNC used in MME, but we can add a list of PLMNs you need there.
- Then you can change the PLMN-IDs from the eNodeB, and broadcast whatever you want. (and if the HostedCore supports it, eNodeB will connect, then UEs will connect)
We support Cell Broadcast in LabKits only in GSM modes. ( https://en.wikipedia.org/wiki/Cell_Broadcast )
We support Cell Broadcast in YateBTS (working modes: 2G NiPC, 2G roaming, 2G dataroam).
To activate the service you have to log in into LMI (Local Management Interface).
These types of messages imply more than just the RAN component (BTS/ENB)
Usually there is another application that pushes messages to the RAN component and RAN component pushes messages to the phones.
Phone must be set up to receive cell broadcast (emergency) messages. Some phones have this directly build in in the firmware.
Phones have 1000 channels (from 0 to 999) - named CMBR (Cell Broadcast Message Range)
SIMs also have a memory zone that can old up to 5 broadcast channels.
These codes differ for each country/continent.
For example Romania is using only 5 codes for Cell Broadcast (service named: RoAlert).
Test Cell Broadcast with LTE LabKit now!
Core network uptime is usually reflected by the Linux server holding the Core network software.
As our Yate products are software products, we have servers/VMs online for years now.
Yate software running on these servers was upgraded during time. (is a normal behavior)
Downtime for an upgrade procedure usually it is approx 60 seconds, but may vary to less on certain equipment.
Please boot the server in Legacy/BIOS mode with a Mageia/CentOS or a recovery stick. Then use the "Memory Test" option and find out if a hardware problem appeared on that server. Usually physical memory (RAM) might crash or hard disk drive (HDD) or solid-state drive (SSD). Replace the broken components or remove it if the system allows it and turn on the server.
Yes, we support unattended-upgrades / scheduled upgrades for our Yate Products and it can be done very easily from YateMMI.
To schedule unattended upgrades:
- Access YateMMI (Mobile Management Interface)
- Click on Equipment
- Select Schedule Update (bottom left corner), this opens a new browser window, here enter Start Time (the time when updates start on the selected nodes) and Gap Time (the time between server updates).
The purpose of unattended upgrades is to install the latest Yate Products updates automatically and unattended.
Answer:
To enable the Personal Hotspot on your iOS device you need to configure the Hotspot APN (Access Point Name) by following the next steps:
- Please go to Settings > Cellular/Mobile Data > Mobile Data Network.
- Please tap on APN in the Personal Hotspot section and type your APN - leave username and password fields empty.
Your device is now configured for Personal Hotspot (also known as tethering).
Whenever you want to use it you can go to Settings > Mobile Data > Personal Hotspot, turn Personal Hotspot ON and follow on screen instructions.
Personal Hotspot on your iOS device will provide internet access to other devices on Wi-Fi, Bluetooth or USB.