Roaming services on Tsa non-M2M Vodafone and O2 SIMs are for users who travel periodically, not for those who roam on foreign networks on a semi-permanent or permanent basis.
More detail on the FUP is available in the ‘International Zones Guide on the Tsa extranet here: https://extranet.Tsa.co.uk/#Page:Rate_Cards_New
Tsa also offers M2M, multi-network, roaming SIM / eSIM options:
- eSIM (Global coverage with over 450 networks available)
- KPN (European Coverage – over 100 networks)
- EE (coverage in UK/EU/USA)
- Three (Global coverage with over 330 networks)
With some exceptions (*) there are no formal restrictions on these M2M SIMs roaming permanently. However, roaming agreements are reviewed on an annual basis and countries can unilaterally impose regulations on operators (as happened recently in Turkey). Roaming agreements also have caveats to account for unexpected or untypical usage etc. Because of this it is not possible for anyone to guarantee that a SIM will be able to roam permanently in any given country / on any specific network.
What we can say is that this has not happened on any Tsa SIMs thus far.
It is also true that if an individual roaming agreement was discontinued and our SIM had multiple network options in the country in question, the SIM would roam on one of the alternative networks.
On eSIM it’s possible to provide ‘local profiles’ but they are more likely to be more expensive than a local SIM. You gain certainty that you’re not going to get cut off, but the SIM is not roaming; a local SIM will often be a better option.
* - The exceptions are Brazil, China, India, Turkey and UAE. For those countries then national regulations prohibit permanent roaming and so long-term deployments will need local operator signoff in advance.
NB – The content of this article has been checked but Tsa assumes no liability for its accuracy, completeness, or timeliness
More detail on the FUP is available in the ‘International Zones Guide on the Tsa extranet here: https://extranet.Tsa.co.uk/#Page:Rate_Cards_New
Tsa also offers M2M, multi-network, roaming SIM / eSIM options:
- eSIM (Global coverage with over 450 networks available)
- KPN (European Coverage – over 100 networks)
- EE (coverage in UK/EU/USA)
- Three (Global coverage with over 330 networks)
With some exceptions (*) there are no formal restrictions on these M2M SIMs roaming permanently. However, roaming agreements are reviewed on an annual basis and countries can unilaterally impose regulations on operators (as happened recently in Turkey). Roaming agreements also have caveats to account for unexpected or untypical usage etc. Because of this it is not possible for anyone to guarantee that a SIM will be able to roam permanently in any given country / on any specific network.
What we can say is that this has not happened on any Tsa SIMs thus far.
It is also true that if an individual roaming agreement was discontinued and our SIM had multiple network options in the country in question, the SIM would roam on one of the alternative networks.
On eSIM it’s possible to provide ‘local profiles’ but they are more likely to be more expensive than a local SIM. You gain certainty that you’re not going to get cut off, but the SIM is not roaming; a local SIM will often be a better option.
* - The exceptions are Brazil, China, India, Turkey and UAE. For those countries then national regulations prohibit permanent roaming and so long-term deployments will need local operator signoff in advance.
NB – The content of this article has been checked but Tsa assumes no liability for its accuracy, completeness, or timeliness
Please see below the APN settings for the various different JolaMobile SIM cards:
For all SIMs the Authentication Type must be set to PAP and Roaming needs to be Enabled
Some customers have also seen the need to manually force their device to connect to 4G
O2
APN: mobile.o2.co.uk
Username: o2web
Password: password
Vodafone
APN: internet
Username: web
Password: web
eSIM (all eSIM options including eSIM Private APN & eSIM L2TP)
APN: globaldata.iot
Username: blank
Password: blank
However, some devices cannot have empty fields for these sections. If there are issues registering please try entering;
APN: globaldata.iot
Username: esim
Password: esim
EE Fixed IP
APN: wlapn4.com
Username: fixedip
Password: fixedip
EE M2M
APN: EEM2M
Username:
Password:
EE – Private APN
APN: mm.m2m
Username - test
Password - test
Vodafone Fixed IP
APN: wlapn4.com
Username: fixedip
Password: fixedip
KPN MultiNetwork
APN: fast.m2m
Username:
Password:
KPN Multinetwork + SMS
APN: CMLink
Username:
Password:
KPN Multinetwork ‘PPG’ (Pay-Per-GB)
APN: fast.vpn
Username:
Password:
Three IoT / M2M
APN: 3iot.com
Username:
Password:
For all SIMs the Authentication Type must be set to PAP and Roaming needs to be Enabled
Some customers have also seen the need to manually force their device to connect to 4G
O2
APN: mobile.o2.co.uk
Username: o2web
Password: password
Vodafone
APN: internet
Username: web
Password: web
eSIM (all eSIM options including eSIM Private APN & eSIM L2TP)
APN: globaldata.iot
Username: blank
Password: blank
However, some devices cannot have empty fields for these sections. If there are issues registering please try entering;
APN: globaldata.iot
Username: esim
Password: esim
EE Fixed IP
APN: wlapn4.com
Username: fixedip
Password: fixedip
EE M2M
APN: EEM2M
Username:
Password:
EE – Private APN
APN: mm.m2m
Username - test
Password - test
Vodafone Fixed IP
APN: wlapn4.com
Username: fixedip
Password: fixedip
KPN MultiNetwork
APN: fast.m2m
Username:
Password:
KPN Multinetwork + SMS
APN: CMLink
Username:
Password:
KPN Multinetwork ‘PPG’ (Pay-Per-GB)
APN: fast.vpn
Username:
Password:
Three IoT / M2M
APN: 3iot.com
Username:
Password:
On this page
MobileManager API Documentation Introduction This page provides information about the different methods in Jola MobileManager's REST API. More coming soon. Authentication The API uses Basic Authentication. SKU API Description GET api/v1/cpe/categories GET api/v1/cpe/categories/{category}/items No documentation available. GET api/v1/cpe/{cpeId}/skus No documentation available. Tariffs API Description GET api/v1/tariffs Get Tariffs. Returns a list of tariffs GET api/v1/tariffs/{id}/boltons Get Tariff Boltons. Returns a list of boltons available for a specific tariff Customers API Description GET api/v1/customers Get Customers. Returns a list of customers for the current reseller GET api/v1/customers/{id} Get Customer. Returns a specific customer POST api/v1/customers Add Customer. Adds a new customer to the reseller GET api/v1/customers/{id}/sims/ Get a list of SIMs DELETE api/v1/customers/{id} Delete Customer. Hides a customer from the default view GET api/v1/customers/{id}/sims/ Get Customer Sims. Returns a list of Sims for the given customer POST api/v1/customers/{id}/sims/{simid} Assign Sim. Assigns a SIM to the given customer DELETE api/v1/customers/{id}/sims/{simid} Unassign Sim. Removes a SIM from the given customer Sims API Description GET api/v1/sims Get Sims. Returns a list of Sims for the current reseller GET api/v1/sims/{id} Get Sim. Returns a single sim specified by Id GET api/v1/sims/{id}/checkpac Check PAC Code. Checks the given PAC code and Mobile Number against the network the specified SIM exist on PUT api/v1/sims{id}/update Update SIM Details Orders API Description GET api/v1/orders List Orders. Returns a list of orders for the given parameters. GET api/v1/orders/{id} Get Order. Returns a single order POST api/v1/orders/activation Activate a SIM POST api/v1/orders/bolton Create a new Bolton order for the given SIM. POST api/v1/orders/cease Create new Cease Order. Requests a cease on a SIM POST api/v1/orders/bar Create BAR Order. Adds a BAR to the SIM which stops GPRS traffic on the SIM POST api/v1/orders/unbar Create Unbar Order. Removes an Activate Bar from a SIM POST api/v1/orders/tarrifchange Creates a Tariff Change Order. Moves the tariff for a given SIM to a new tariff. POST api/v1/orders/cpe No documentation available.
MobileManager API Documentation
Introduction
This page provides information about the different methods in Jola MobileManager's REST API. More coming soon.
Authentication
The API uses Basic Authentication.
SKU
API
Description
GET api/v1/cpe/categories
GET api/v1/cpe/categories/{category}/items
No documentation available.
GET api/v1/cpe/{cpeId}/skus
No documentation available.
Tariffs
API
Description
GET api/v1/tariffs
Get Tariffs. Returns a list of tariffs
GET api/v1/tariffs/{id}/boltons
Get Tariff Boltons. Returns a list of boltons available for a specific tariff
Customers
API
Description
GET api/v1/customers
Get Customers. Returns a list of customers for the current reseller
GET api/v1/customers/{id}
Get Customer. Returns a specific customer
POST api/v1/customers
Add Customer. Adds a new customer to the reseller
GET api/v1/customers/{id}/sims/
Get a list of SIMs
DELETE api/v1/customers/{id}
Delete Customer. Hides a customer from the default view
GET api/v1/customers/{id}/sims/
Get Customer Sims. Returns a list of Sims for the given customer
POST api/v1/customers/{id}/sims/{simid}
Assign Sim. Assigns a SIM to the given customer
DELETE api/v1/customers/{id}/sims/{simid}
Unassign Sim. Removes a SIM from the given customer
Sims
API
Description
GET api/v1/sims
Get Sims. Returns a list of Sims for the current reseller
GET api/v1/sims/{id}
Get Sim. Returns a single sim specified by Id
GET api/v1/sims/{id}/checkpac
Check PAC Code. Checks the given PAC code and Mobile Number against the network the specified SIM exist on
PUT api/v1/sims{id}/update
Update SIM Details
Orders
API
Description
GET api/v1/orders
List Orders. Returns a list of orders for the given parameters.
GET api/v1/orders/{id}
Get Order. Returns a single order
POST api/v1/orders/activation
Activate a SIM
POST api/v1/orders/bolton
Create a new Bolton order for the given SIM.
POST api/v1/orders/cease
Create new Cease Order. Requests a cease on a SIM
POST api/v1/orders/bar
Create BAR Order. Adds a BAR to the SIM which stops GPRS traffic on the SIM
POST api/v1/orders/unbar
Create Unbar Order. Removes an Activate Bar from a SIM
POST api/v1/orders/tarrifchange
Creates a Tariff Change Order. Moves the tariff for a given SIM to a new tariff.
POST api/v1/orders/cpe
No documentation available.
MobileManager API Documentation Introduction This page provides information about the different methods in Jola MobileManager's REST API. More coming soon. Authentication The API uses Basic Authentication. SKU API Description GET api/v1/cpe/categories GET api/v1/cpe/categories/{category}/items No documentation available. GET api/v1/cpe/{cpeId}/skus No documentation available. Tariffs API Description GET api/v1/tariffs Get Tariffs. Returns a list of tariffs GET api/v1/tariffs/{id}/boltons Get Tariff Boltons. Returns a list of boltons available for a specific tariff Customers API Description GET api/v1/customers Get Customers. Returns a list of customers for the current reseller GET api/v1/customers/{id} Get Customer. Returns a specific customer POST api/v1/customers Add Customer. Adds a new customer to the reseller GET api/v1/customers/{id}/sims/ Get a list of SIMs DELETE api/v1/customers/{id} Delete Customer. Hides a customer from the default view GET api/v1/customers/{id}/sims/ Get Customer Sims. Returns a list of Sims for the given customer POST api/v1/customers/{id}/sims/{simid} Assign Sim. Assigns a SIM to the given customer DELETE api/v1/customers/{id}/sims/{simid} Unassign Sim. Removes a SIM from the given customer Sims API Description GET api/v1/sims Get Sims. Returns a list of Sims for the current reseller GET api/v1/sims/{id} Get Sim. Returns a single sim specified by Id GET api/v1/sims/{id}/checkpac Check PAC Code. Checks the given PAC code and Mobile Number against the network the specified SIM exist on PUT api/v1/sims{id}/update Update SIM Details Orders API Description GET api/v1/orders List Orders. Returns a list of orders for the given parameters. GET api/v1/orders/{id} Get Order. Returns a single order POST api/v1/orders/activation Activate a SIM POST api/v1/orders/bolton Create a new Bolton order for the given SIM. POST api/v1/orders/cease Create new Cease Order. Requests a cease on a SIM POST api/v1/orders/bar Create BAR Order. Adds a BAR to the SIM which stops GPRS traffic on the SIM POST api/v1/orders/unbar Create Unbar Order. Removes an Activate Bar from a SIM POST api/v1/orders/tarrifchange Creates a Tariff Change Order. Moves the tariff for a given SIM to a new tariff. POST api/v1/orders/cpe No documentation available.
MobileManager API Documentation
Introduction
This page provides information about the different methods in Jola MobileManager's REST API. More coming soon.
Authentication
The API uses Basic Authentication.
SKU
API
Description
GET api/v1/cpe/categories
GET api/v1/cpe/categories/{category}/items
No documentation available.
GET api/v1/cpe/{cpeId}/skus
No documentation available.
Tariffs
API
Description
GET api/v1/tariffs
Get Tariffs. Returns a list of tariffs
GET api/v1/tariffs/{id}/boltons
Get Tariff Boltons. Returns a list of boltons available for a specific tariff
Customers
API
Description
GET api/v1/customers
Get Customers. Returns a list of customers for the current reseller
GET api/v1/customers/{id}
Get Customer. Returns a specific customer
POST api/v1/customers
Add Customer. Adds a new customer to the reseller
GET api/v1/customers/{id}/sims/
Get a list of SIMs
DELETE api/v1/customers/{id}
Delete Customer. Hides a customer from the default view
GET api/v1/customers/{id}/sims/
Get Customer Sims. Returns a list of Sims for the given customer
POST api/v1/customers/{id}/sims/{simid}
Assign Sim. Assigns a SIM to the given customer
DELETE api/v1/customers/{id}/sims/{simid}
Unassign Sim. Removes a SIM from the given customer
Sims
API
Description
GET api/v1/sims
Get Sims. Returns a list of Sims for the current reseller
GET api/v1/sims/{id}
Get Sim. Returns a single sim specified by Id
GET api/v1/sims/{id}/checkpac
Check PAC Code. Checks the given PAC code and Mobile Number against the network the specified SIM exist on
PUT api/v1/sims{id}/update
Update SIM Details
Orders
API
Description
GET api/v1/orders
List Orders. Returns a list of orders for the given parameters.
GET api/v1/orders/{id}
Get Order. Returns a single order
POST api/v1/orders/activation
Activate a SIM
POST api/v1/orders/bolton
Create a new Bolton order for the given SIM.
POST api/v1/orders/cease
Create new Cease Order. Requests a cease on a SIM
POST api/v1/orders/bar
Create BAR Order. Adds a BAR to the SIM which stops GPRS traffic on the SIM
POST api/v1/orders/unbar
Create Unbar Order. Removes an Activate Bar from a SIM
POST api/v1/orders/tarrifchange
Creates a Tariff Change Order. Moves the tariff for a given SIM to a new tariff.
POST api/v1/orders/cpe
No documentation available.
The data reporting in Mobile manager is dependent on the data from the networks. Depending on the carrier and service, update times can vary.
Below is a table of services and data update timeframes, we will accept a fault outside of these times unless there is a known issue.
When a fault is raised we may also ask customers to wait an additional amount of time (eg. 24 hours) depending on the time of the month eg. at the start and end of the month. In addition, some carriers rely on a data session ending in order to calculate the usage – this can also add to the delay in data to Mobile Manager but no longer than 24 hours.
If no data is showing after this time period has elapsed, we will commence investigations with the relevant parties.
Network
Data Delay
O2
Up to 7 days
Vodafone
Up to 24 hours
eSIM
Up to 4 hours
EE Fixed IP
Up to 4 hours
EE M2M
Up to 4 hours
EE - Private APN
Up to 4 hours
Vodafone Fixed IP
Up to 4 hours
KPN Multi-Network
Up to 4 hours
KPN Multi-Network + SMS
Up to 4 hours
KPN Multi-Network 'PPG (Pay-Per-GB)
Up to 4 hours
Three IoT/M2M
Up to 4 hours
Below is a table of services and data update timeframes, we will accept a fault outside of these times unless there is a known issue.
When a fault is raised we may also ask customers to wait an additional amount of time (eg. 24 hours) depending on the time of the month eg. at the start and end of the month. In addition, some carriers rely on a data session ending in order to calculate the usage – this can also add to the delay in data to Mobile Manager but no longer than 24 hours.
If no data is showing after this time period has elapsed, we will commence investigations with the relevant parties.
Network
Data Delay
O2
Up to 7 days
Vodafone
Up to 24 hours
eSIM
Up to 4 hours
EE Fixed IP
Up to 4 hours
EE M2M
Up to 4 hours
EE - Private APN
Up to 4 hours
Vodafone Fixed IP
Up to 4 hours
KPN Multi-Network
Up to 4 hours
KPN Multi-Network + SMS
Up to 4 hours
KPN Multi-Network 'PPG (Pay-Per-GB)
Up to 4 hours
Three IoT/M2M
Up to 4 hours
There are a few sims that are unable to be sim swapped.
There are some sims that are unable to be SIM Swapped, please find a list of SIMs below that can and cannot be sim swapped.
Can SIM Swap:
Vodafone Dynamic SIMs
O2 Dynamic Sims.
Can NOT SIM Swap:
eSIMs
eSIM L2TP Sims
EE Standard M2M Sims
EE Fixed IP Sims
Three Dynamic Sims.
KPN Sims.
KPN IoT Sims
KPN SMS Sims
Vodafone Fixed IP Sims.
There are some sims that are unable to be SIM Swapped, please find a list of SIMs below that can and cannot be sim swapped.
Can SIM Swap:
Vodafone Dynamic SIMs
O2 Dynamic Sims.
Can NOT SIM Swap:
eSIMs
eSIM L2TP Sims
EE Standard M2M Sims
EE Fixed IP Sims
Three Dynamic Sims.
KPN Sims.
KPN IoT Sims
KPN SMS Sims
Vodafone Fixed IP Sims.
O2 Dynamic Sims
Activate
Timescale = upto 24hrs (typically - 15mins)
Bar or Unbar
Timescale = upto 24hrs (typically - 15mins)
Tariff change
Timescale = 1st day of the following month
Vodafone Dynamic Sims
Activate
Timescale = upto 24hrs (typically - 15mins)
Bar or Unbar
Timescale = upto 24hrs (typically - 15mins)
Tariff change
Timescale = 1st day of the following month
Vodafone Fixed IP Sims
Activate
Timescale = upto 3 working days (typically - 3 working days)
Bar or Unbar
Timescale = upto 1 working day (typically - 1 working day)
Tariff change
Timescale = 1st day of the following month
EE Fixed IP Sims
Activate
Timescale = upto 2 hours (typically - instant)
Bar or Unbar
Timescale = upto 15mins (typically - instant)
Tariff change
Timescale = 1st day of the following month
EE Sims
Activation
Timescale = upto 24hrs (typically - 15mins)
Bar or Unbar
Timescale = upto 24hrs (typically - 15mins)
Tariff change
Timescale = 1st day of the following month
MultiNetwork Sims
Activation
Timescale = upto 15mins (typically - instant)
Bar or Unbar
Timescale = upto 15mins (typically - instant)
Tariff change
Timescale = 1st day of the following month
Three IOT/Big Data Sims
Activation
Timescale = upto 2 hours
Bar or Unbar
Timescale = upto 2 hours
Tariff change
Timescale = 1st day of the following month
eSIM Sims
Activation
Timescale = upto 2 hours
Bar or Unbar
Timescale = upto 2 hours
Tariff change
Timescale = 1st day of the following month
Activate
Timescale = upto 24hrs (typically - 15mins)
Bar or Unbar
Timescale = upto 24hrs (typically - 15mins)
Tariff change
Timescale = 1st day of the following month
Vodafone Dynamic Sims
Activate
Timescale = upto 24hrs (typically - 15mins)
Bar or Unbar
Timescale = upto 24hrs (typically - 15mins)
Tariff change
Timescale = 1st day of the following month
Vodafone Fixed IP Sims
Activate
Timescale = upto 3 working days (typically - 3 working days)
Bar or Unbar
Timescale = upto 1 working day (typically - 1 working day)
Tariff change
Timescale = 1st day of the following month
EE Fixed IP Sims
Activate
Timescale = upto 2 hours (typically - instant)
Bar or Unbar
Timescale = upto 15mins (typically - instant)
Tariff change
Timescale = 1st day of the following month
EE Sims
Activation
Timescale = upto 24hrs (typically - 15mins)
Bar or Unbar
Timescale = upto 24hrs (typically - 15mins)
Tariff change
Timescale = 1st day of the following month
MultiNetwork Sims
Activation
Timescale = upto 15mins (typically - instant)
Bar or Unbar
Timescale = upto 15mins (typically - instant)
Tariff change
Timescale = 1st day of the following month
Three IOT/Big Data Sims
Activation
Timescale = upto 2 hours
Bar or Unbar
Timescale = upto 2 hours
Tariff change
Timescale = 1st day of the following month
eSIM Sims
Activation
Timescale = upto 2 hours
Bar or Unbar
Timescale = upto 2 hours
Tariff change
Timescale = 1st day of the following month
If you use a standard 4G mobile broadband SIM card in your 4G router then you will be unable to use Dynamic DNS. This is because 4G mobile network providers in the UK use Carrier-Grade NAT (CGNAT) which means that your 4G SIM connection is allocated a PRIVATE IP address on the mobile networks private network.
So if you have a PC connected to your 4G Router and visit www.showmyip.co.uk then the IP address you will see will be a public IP address belonging to the mobile network and your SIM card connection will be sitting behind this public IP address along with 250 other devices all with private IP addresses.
therefore in order to get connected to YOUR device, you would need to contact your mobile provider and ask them to remove the other 249 customers sharing that public IP address and port forward the public IP to your private IP.
The way around this is to just use a Jola Fixed IP SIM card.
So if you have a PC connected to your 4G Router and visit www.showmyip.co.uk then the IP address you will see will be a public IP address belonging to the mobile network and your SIM card connection will be sitting behind this public IP address along with 250 other devices all with private IP addresses.
therefore in order to get connected to YOUR device, you would need to contact your mobile provider and ask them to remove the other 249 customers sharing that public IP address and port forward the public IP to your private IP.
The way around this is to just use a Jola Fixed IP SIM card.
There are two reasons your SIM could be locked by FPLMN
If the operation is performed while the module is scanning/attaching to a network it can interrupt and restart that process on some modules (resulting in unnecessary over-signalling).
If the firmware clears this list frequently and is spinning in a loop then that can result in excessive signalling (through excessive retries to the same operator).
The FPLMN (Forbidden Public Land Mobile Network) list is a collection of data stored on your SIM that consists of forbidden networks. Traditionally, modems append networks to this list after failed attempts at registering onto them in order to speed up connections in the future. In order to determine if you have anything written on your FPLMN we recommend you run the following AT command:
at+crsm=176,28539,0,0,12
Here we are telling the SIM to give us datafile 28539 in binary. Notice from the picture below that we get 24 "F"s this lets us know that the FPLMN is empty which is what we want. If you have anything other than 24 "F"s then something has been written onto your FPLMN.
To clear the FPLMN you'll first want to consult your modem's documentation to make sure you are aware of any special instructions as usually, you'll need to set it to minimal operation mode or airplane mode, depending upon the module. In this example, we are setting the device to minimum functionality which disables transmit and receive RF circuits for both circuit-switched and packet-switched services with at+cops=0.
Clear the FPLMN:
at+crsm=214,28539,0,0,12,"FFFFFFFFFFFFFFFFFFFFFFFF"
be sure to include exactly 24 "F"s.
Last, don't forget to switch your device back to full functionality if that was modified.
If the operation is performed while the module is scanning/attaching to a network it can interrupt and restart that process on some modules (resulting in unnecessary over-signalling).
If the firmware clears this list frequently and is spinning in a loop then that can result in excessive signalling (through excessive retries to the same operator).
The FPLMN (Forbidden Public Land Mobile Network) list is a collection of data stored on your SIM that consists of forbidden networks. Traditionally, modems append networks to this list after failed attempts at registering onto them in order to speed up connections in the future. In order to determine if you have anything written on your FPLMN we recommend you run the following AT command:
at+crsm=176,28539,0,0,12
Here we are telling the SIM to give us datafile 28539 in binary. Notice from the picture below that we get 24 "F"s this lets us know that the FPLMN is empty which is what we want. If you have anything other than 24 "F"s then something has been written onto your FPLMN.
To clear the FPLMN you'll first want to consult your modem's documentation to make sure you are aware of any special instructions as usually, you'll need to set it to minimal operation mode or airplane mode, depending upon the module. In this example, we are setting the device to minimum functionality which disables transmit and receive RF circuits for both circuit-switched and packet-switched services with at+cops=0.
Clear the FPLMN:
at+crsm=214,28539,0,0,12,"FFFFFFFFFFFFFFFFFFFFFFFF"
be sure to include exactly 24 "F"s.
Last, don't forget to switch your device back to full functionality if that was modified.
In order for us to effectively support you with your mobile query, please can you carry out the following checks;
1) Has the device been powered down for 5 minutes? - This is essentially forces to the SIM to reconnect.
2) Has the SIM been tested in a known working device – eg. mobile phone, unlocked to any network? - This helps eliminate a potential issues with devices.
3) Has the APN details been manually configured in the device? TsaMobile APN Settings - Occasionally we see issues where the Automatic APN changes and picks up the wrong details.
4) Has the SIM been moved to a different location? - This helps us determine whether there are issues with the mast/network in that area.
5) ) If your issues are related to a Tsa provided mobile router not reporting data usage on Mobile Manager, please hold the reset button for 10 seconds. – This will factory default the router reverting any TR69 server settings. Please note this will also change any settings you may have configured in the router. The APN will also need manually configuring again. TsaMobile APN Settings
Once these checks have been carried out please can you confirm the following details;
1) Affected SIM ICCID
2) Network of the SIM
3) Location of the SIM (postcode)
4) If using a Tsa supplied router, please attach an image showing the Status Lights on the router and device serial number
5) A testing window of 1 hour where Tsa can SIM Swap the SIM to a blank one in our office for testing. (Date/Time)
We may require a fault form to be filled out for the network to investigate issues, if you could provide us with a completed form with as much detail as possible this would help reduce the length of time for the network to resolve issues.
1) Has the device been powered down for 5 minutes? - This is essentially forces to the SIM to reconnect.
2) Has the SIM been tested in a known working device – eg. mobile phone, unlocked to any network? - This helps eliminate a potential issues with devices.
3) Has the APN details been manually configured in the device? TsaMobile APN Settings - Occasionally we see issues where the Automatic APN changes and picks up the wrong details.
4) Has the SIM been moved to a different location? - This helps us determine whether there are issues with the mast/network in that area.
5) ) If your issues are related to a Tsa provided mobile router not reporting data usage on Mobile Manager, please hold the reset button for 10 seconds. – This will factory default the router reverting any TR69 server settings. Please note this will also change any settings you may have configured in the router. The APN will also need manually configuring again. TsaMobile APN Settings
Once these checks have been carried out please can you confirm the following details;
1) Affected SIM ICCID
2) Network of the SIM
3) Location of the SIM (postcode)
4) If using a Tsa supplied router, please attach an image showing the Status Lights on the router and device serial number
5) A testing window of 1 hour where Tsa can SIM Swap the SIM to a blank one in our office for testing. (Date/Time)
We may require a fault form to be filled out for the network to investigate issues, if you could provide us with a completed form with as much detail as possible this would help reduce the length of time for the network to resolve issues.