Opensips SMPP Setup to Send/Receive SMS and connect it to Asterisk SIP Instant Messaging

We need and expert with Opensips in order to configure and connect it to Asterisk PBX to configure Opensips for handling SIP messaging to SMS provider and vice versa. a complete Opensips solution to send/receive sms from peer-to-peer SMS provider. Encoding and splitting the messages by Opensips with following guideline: All software must auto start on server boot We already installed Opensips 3.0 on Centos 7.6 (FreePBX 14 and asterisk 16.3.0) Provide full list of commands to install the above and files edited to be able to install on another server at a later date Give us solution for backup and restore all config files to our backup server. The project is to connect our Opensips server to a peer-to-peer SMS provider by smpp The following guidelines must be carefully observed when originating a message out (MO): • The src TN value should be a valid and active number under the customer account. • All values submitted must be properly URL encoded (aka percent-encoded). ([login to view URL]) • A SMS message must be contained in 140 bytes as this is the total payload available to send a single message. i.e.: GSM 7-bit alphabet can pack 160 characters out of this (7-bits x 160 = 1,120 bits /8 = 140 bytes). UTF-8 allows a maximum of 140 characters while it is only 70 for an UTF-16/UCS-2 encoded message. • Message payload must be UTF-8 encoded (not Latin-1 nor ISO-8859-1) in order to support any characters outside GSM 7-bit alphabet (GSM 03.38). • Any message containing at least one character not contained in the GSM 7-bit alphabet will be automatically converted to UC2 encoding in order to be transmitted properly to the destination. This means that the total message length is automatically set to 70 characters at maximum. • Any message submitted with a payload greater than 140 bytes (i.e: >160 7-bit characters) will be rejected. In order to send messages of greater length, your application must split the original message into separate messages. We recommend adding a small delay before each part to help in ensuring they arrive in the correct order. • To fully support 160-character messages, the list of allowed characters in messages is the GSM 03.38 7-bit basic default alphabet. Note however that GSM 03.38 supports a basic character set extension comprised of the following special characters: |, ^, {, }, [,], ~ and \ • For line break in a message, use \r\n; e.g: Your next appointment is on \r\n July 7th at 1:00PM. We setup SIP IM with online/offline messaging and also I create a dial-plan for outside SMS by API and it's works, but the problem is encoding and splitting the messages. The provider suggest us to use SMPP instead of API. And we find Opensips and Installed it but we have no idea how it's work or how to config it, we want to help us to configure Opensips for handling SIP messaging to SMS provider and vice versa. ***Please Only Experts*** Opensips SMSC setup to offer a sms service and connect to asterisk SIP IM. 1. Expected Install and configure: -Opensips 3.0 -SMPP server for connection the provider -Connect the Opensips to FreePBX asterisk 2.- We need system test, trainning to troubleshooting issues, documentation etc. support per 3 months to fix any issue (we can deal support per month cost after finish the job) I'm looking for a very expertise, on Opensips, smpp and Asterisk. An honest guy to work into a long time. We take in account: Experience with Opensips and Asterisk $$ Best Offer $$