Transferring the Mobiiliviesti service to a new service platform

In migration, the actual technical change is carried out by the customer himself, i.e. the customer is required to take measures to change the platform. The aim has been to make the change so that the impact on customers is quite minor, i.e. everything possible is done by Telia, and the customer is left with the task of changing the end point to their own API.

MT direction customers (messages sent to the terminal) only need to change  the  endpoint URL in accordance with the instructions.

MO direction customers (messages arriving at the customer's system from terminal devices) that use short numbers or operator-independent numbers beginning with 040 need to overthrow the numbers in sync with Telia on the new platform and change the endpoint in accordance with the instructions. 

Please note that the Telia Message Interface and Telia Mobile Payment services will continue on the Opaali platform and will not be affected by the changes mentioned in this letter.
Technical interface description: "Telia Finland Mobiiliviesti API Emulation" Technical documents and descriptions can be found in the support section of the web portal.

Before making the change, the customer must ensure that traffic is allowed (firewall openings) from the following addresses:

To enable messaging to the new platform, a connection to the API address (endpoint) must be ensured: ws.mkv.telia.fi (IP address is 80.74.206.12)

Incoming traffic (MO messages or delivery receipts) comes from two IP addresses. Traffic from these must be allowed: proxy-fi.cdc.telia.net (IP addresses are 80.74.204.131 and 80.74.204.130).

To send SMS messages, there is a technical application that sends invitations to the current api.opaali.telia.fi endpoint. Endpoints are set in the app's code set or configuration for message forwarding.

Action required from the customer
The endpoints set in the application should be changed to the new Lekab endpoint.
Note that the endpoint setting can potentially be managed and implemented in very different ways in different implementations and applications. Telia has no information about the customer's own implementation.

Example
The endpoint can also be configured to be searched from another source, i.e. the point you want to search for must be changed there. It can also be, for example, hardcoded directly into the app, or the endpoint can be assigned to one of the UIs where the endpoint is changed.

The endpoints are:

• Communication API. Message sending, includes basic authentication.

•    Authentication API. Customers who use non-basic authentication and want to use a limited-time token will be sent an invitation via the authentication API. The token is valid for 10 minutes, during which time messages can be sent securely.

When sending a message, the Communications API uses the received token for authentication.

When SMS short message numbers and/or operator-independent numbers beginning with 040 are in use, to which mobile users can send SMS messages that are transmitted to the customer's service via an API interface, the numbers shall be transferred to a new platform at a separately agreed time in cooperation with Telia.

Telia will contact the customer by phone in order to agree on a time for transferring these numbers to the new platform.

The overthrow is done for the first digit transfer on a short-digit basis, and all traffic for that short number is transferred at once. A new porting time will be agreed for possible transfers of several/subsequent numbers.

Before the transfer time, please note that communication is allowed.

During the overthrow contact, the transfer of numbers in the MO direction is carried out

After agreeing on an appointment, a Teams meeting reservation has been made with the customer's technical information. the company and other necessary parties from the customer and Telia's experts. In this meeting, the following will be done:

• Telia directs numbers to the new platform
• If the customer retrieves the messages from the service, the customer changes the endpoint from which the messages are retrieved at the same time

•   At the time of overthrowing, it is ensured together with the customer that the traffic works

• Test traffic with test messages
•  Both parties check the situation on their respective platforms/reports

Endpoint for retrieving MO messages (Poll) from the system:

• Communication API

The Push and Poll-type functions used in Opaali are also available on the new Lekab platform.

If incoming messages are delivered to the customer's system (Push), the URLs remain as they were defined in Opaali and can be managed by the customer in the new web interface.

Customer data will be transferred by Telia to the new platform, and users and applications will be transferred under each company. For users who have been users of Opaali, user profiles are created in Lekab with the web portal role, which can be used to manage the service from the web interface. The customers' SMS applications that were in Opaali will be transferred to Lekab as user profiles with an API role. The user IDs will remain the same, but users of the web portal will need to retrieve a new password according to the instructions.

• In Lekab, both web portal users and applications are users
• Opaali had separate web portal users and separate applications

The username and password of the applications will remain the same as on the Opaali platform.

Logging in to the web portal 

The username is the same as when logging in to the Opaali portal, but the password must be retrieved from the "Forgot your password" link.

Information corresponding to the current reporting is also available from the reporting of the new server platform.

In the future, reports from the Lekab platform will be available with the default setting 90 days back, whereas previously Opaali was available 6 months back.

It is advisable to save the report data every three months, after which it will not be available.

If the same customer uses both Kontakti SMS Web and Mobiiliviesti, the address and user interface will be the same, but the views and functions will be different depending on the service.

If, for example, an http adapter or some other special implementation has been used in connection with a service previously available in Opaali, please contact customer service on 0200 27007

Opaali will be available (broadcasts, reporting) for a limited time and will be closed completely for Mobiiliviesti at a later datec, which will be announced in more detail. For the time being, there is always the possibility to return to Opaali if the transition to Lekab is not immediately successful.

Only production services will be transferred. If you have "sandbox" modes, request the migration separately. In the new service, all applications are in production mode. If you want to transfer an application that was in test use to a new platform (e.g. Under the name test), it should be noted that the traffic still works in production, and therefore goes online and is invoiced.

If you need help or have any questions, you can contact us by phone on 0200 27007. Select from option 3 - Changes to subscriptions and services for enterprise customers. The service hours of the number are 9:00–15:00 (local network charge).

Do I have to make a change?
Yes, we are Telia Kontakti SMS Interface The Mobiiliviesti service will be centralised on the new platform.

Can I test the new platform somehow?
If your company uses a test application, testing can be done there. Alternatively, you can create a new test application from the management interface itself and test with it.

We recommend starting migrations with a test app or a low-use app.

If you have a test short number, contact Telia to transfer it to the new platform.