Posted by JPLa on August 23, 2019

According to API_Telia_OMA_Messaging_REST the Telia-OMA Messaging API supports Latin 9 alphabet by default, which includes Finnish characters and the Euro symbol (€). You can use Cyrillic characters if you add an sms-charset HTTP header with value as UCS-2 in the API Request. But often you need to use an escape sequence to get certain characters work in the JSON or XML data that is used in an API request.

Posted by JPLa on August 19, 2019

Sometimes an error message tries to be helpful, but ends up obfuscating the real problem. When the http_adapter encounters an unrecoverable error while trying to authenticate towards the Opaali API, it will stop trying (after all, the situation seems to be unrecoverable) and returns an error message for all future requests:

Posted by JPLa on June 14, 2019

Now that the http_adapter has been in production use for a while, I have finally updated some of the documentation. The README.md was updated and a new document http_adapter_reference.md has been added. These documents are in markdown format, you can view them formatted on GitHub but you may need a markdown compatible tool to print them out correctly.

Posted by JPLa on May 23, 2019

This is a summary of the enhanced binary message features which were introduced in the release R4SP2 of Opaali. These are proprietary enhancements to the OMA Messaging specification whose binary message support offers much less than what was possible with Content Gateway (CGW).

Posted by JPLa on May 8, 2019

Here is an actual case of configuring the http_adapter based on experiences of migrating two internal services from Content Gateway to Opaali with minimal changes to the services. (The names and other details have been changed.)