M2M One Newsletter – February 2019
Welcome to our first newsletter of 2019!
It’s hard to believe that the holiday period has already come and gone and that we are quickly heading into March.
We hope that you all managed to have a bit of a break over the holiday period and that you (like us) are ready and raring to go.
2019 looks like it will shape up to be a big year for M2M and IoT communications here in Australia.
- The Telstra NB-IoT network is getting closer to becoming a commercial network and it is ready for the next stage of testing (see more below).
- Cat-M1 has proved to be a very reliable technology for M2M/IoT applications with great benefits (specifically in cost and power savings). We are seeing more and more devices being launched in this space.
As always M2M One will be participating in a number of trade-shows later in the year and we’ll keep you updated as shows come up with registration and ticketing details. We love the opportunity to meet face to face and hear about your IoT applications so make sure you come to our booth and say hi if we’re in your region.
Finally I would like to take this opportunity to again thank all of our loyal customers for your continued business with us and we look forward to helping you grow your business in 2019 – If there is anything we at M2M One can do to help, please reach out and let us know.
- NB-IoT Services
There has been a lot of discussion about NB-IoT and many questions about when it will be ready to go.
While Telstra announced it’s NB-IoT network last year it is still not quite commercially ready just yet – However, there has been some recent movement and we are close to a full commercial launch.
So where exactly are we with NB-IoT today?
Telstra has now approved the Telit ME910C1-AU module and there are a number of modules from other brands currently in the approval process for certification.
As demand grows we have seen a number of modules and finished devices being tested in the market (many coming out of Europe who are leading the way in NB-IoT networks).
What will the finished product look like from Telstra/M2M One?
Up to now we have been advised by Telstra that the final version of NB-IoT will feature:
- A dedicated NB-IoT APN
- Dedicated NB-IoT SIM Cards
- A special account for managing NB-IoT Services
At M2M One we now have new testing capabilities for our customers for NB-IoT. We can confirm the following for customers:
- APN Settings – The APN for NB-IoT will be ‘telstra.iot‘
- This APN can be used for both NB-IoT and Cat-M1
- Cat-M1 will also support ‘telstra.m2m‘ but NB-IoT will not.
- SIM Cards – we were given 300 trial SIMs to offer to our customers last year. Up until this week they were not able to used, however we now have the ability to activate these SIMs for customers to test.
- M2M One Testing – We have tested the NB-IoT SIMs and network this week and can confirm that both are working (subject to network availability).
So whats next… Commercial Roll Out Caution
As you can start to test on what is planned to be the official launch APN you can start to make some headway to a production device.
However – M2M One do advise caution, there is still a lot that is not 100% known about how the final version of commercial costing and interoperability between NB-IoT and Cat M1 will look.
Telstra have currently advised that for a device to be Telstra Approved devices will need to use both technologies.
While some of these things are now working, it is difficult to predict exactly how they will operate in a final commercial model – hence while testing can give you some great insight as to how the NB-IoT network will work, and how it will interact with your own systems, we caution against putting any of it into production until the above is clarified.
As always we will continue to update customers on how NB-IoT is progressing – if you would like to have a more details conversation please get in touch with your Business Development Manager.
- Telstra 2100Mhz 3g Shutdown reminder
As an ongoing reminder, the Telstra 2100MHz 3G shut down is continuing and is still set to be complete by end of March 2019. Again we remind customers that if you have 3G devices out there and have noticed some reception issues out of the blue – this could quite possibly be the cause.
If you have any concerns please get in touch with your account manager and we will see if there is anything we can suggest to help you through the shutdown period.
If you do not have a migration path to 4G yet, we would strongly recommend investigating one ASAP – again please get in touch if you would like to discuss this further.
M2M One currently have the following exhibitions confirmed for 2019 with more on the way! Make sure you keep an eye on our monthly newsletters and events page on the M2M One website (Click here)
Security Exhibition + Conference
July 24-26 2019
National Roads & Traffic Expo 2019
September 17-18 2019
Melbourne Convention & Exhibition Centre,
October 23-24 2019
Melbourne Convention & Exhibition Centre,
CeBIT Australia 2019
October 29-31 2019
Each month we bring you tips and tricks for getting the most value out of the M2M Control Centre.
CISCO Jasper API Access for M2M One
M2M One provide full API access into the CISCO Jasper M2M Control Centre through both SOAP & REST – The SOAP API library is long established and offers the greatest variety of available API calls but CISCO Jasper are updating the REST API regularly in an effort to make REST the default API method of choice for customers.
Full documentation for the API is available from the Knowledge Base within CISCO Jasper (Note: You must be logged to the control centre to use the Knowledge Base and access any of the links used in the email below) – The Knowledge Base can be accessed via Help > Knowledge Base in the top right corner of Control Centre or for direct access to the API section you can use this link: https://m2mone.jasperwireless.com/assets/documentation/lang_en/enterprise/iot_lte/Content/api/rest/uber_api_intro.htm
Using the SOAP API
The M2M One instance of CISCO Jasper utilizes a single standard API key & shared push secret for SOAP access and authentication is required using your Control Centre username & password – Details below:
- SOAP API web-server end-point domain name – The domain name for the SOAP API web service end-point is https://api-telstra.jasper.com
- SOAP Address element – The soap:address location element/property in the WSDL files specifies the end-point for where to send the SOAP messages for each web service. The domain name in this URI is https://api-telstra.jasper.com – Example: <soap:address location=”https://api-telstra.jasper.com/ws/service/terminal”/>
- WSDL Files – For customers using code that automatically reads the end-point location from the WSDL file (instead of hard-coding the value). The full list of existing WSDL files can be found at: https://m2mone.jasperwireless.com/provision/secure/apidoc/technicalReferences.html#GetWsdlFiles
Using the REST API
The REST API uses a unique REST API Key for each user on your Control Centre account. This key needs to be generated from your user profile page and then appended to an authorization header that includes your username.
To generate a REST API key for your username log into Control Centre and navigate to your User Profile this can be accessed by clicking your username in the top right-hand corner. Once in the user profile screen you will see a button labelled Generate REST API Key, click this to create your unique code (wait a moment for this to generate and don’t click Refresh) and then click Show REST API Key to view it.
Once you have an API Key, follow these instructions to create an authorization header:
- Combine the user name and API Key into a single string with a colon separating the values. For example, if the user name is starterkit and the APIKey is d703f52b-1200-4318-ae0d-0f6092b2e6ab, the concatenated string would be: starterkit:d703f52b-1200-4318-ae0d-0f6092b2e6ab
- Encode the concatenated string using Base64 (i.e. RFC2045-MIME): c3RhcnRlcmtpdDpkNzAzZjUyYi0xMjAwLTQzMTgtYWUwZC0wZjYw
- Set the Authorization header value to Basic followed the encoded string from step 2. Make sure there is a space between Basic and the encoded string:
- REST API Base URL – The Control Center REST API is securely available over HTTPS.