OutSystems.com
My Platform
Community
Support
Training
Training
Guided Paths
Build an App
Training Planner
Courses
Developer Schools
Boot Camps
Certifications
Tech Talks
Documentation
Documentation
Overview
ODC
O11
Forums
Forge
Get Involved
Get Involved
Jobs
Ideas
Members
Mentorship
User Groups
Downloads
Search in OutSystems
Log in
Sign Up
Community
/
Forums
/
Questions
Miguel Palmeirinha
Rank: #34571
OutSystems and SMS
292
Views
0
Comments
Question
OutSystems Agile Platform has a built-in SMS gateway and provides the following functionalities regarding SMS:
·
Handle and process an SMS-MO (Mobile Oriented) , possibly replying with a new SMS-MT (Mobile Terminated);
·
Generate new SMS-MT;
·
Keep track of dialogs user/application dialogs, maintaining session status;
·
Host multiple applications (eSpaces) and route the SMS-MO to the appropriate eSpace and the exact session (if any);
·
Manage information about delivery reports;
·
Execute custom business logic on specific events, possibly handling SMS specific properties, captured from the operator network environment;
·
Integrate “out-of-box” with multiple SMS-Centers via multiple Large Accounts via several protocols, such as UCP or SMPP;
·
Integrate with custom SMS gateway via a custom interface;
·
Handle complex incoming SMS routing algorithms, possibly sharing Large Accounts among several VAS (Values Added Services);
Each SMS-MO follows the flow:
1.
Is delivered from the operator network to the SMS Center;
2.
The SMS Center delivers the message to the SMS Gateway via UCP, SMPP or similar protocol. The OutSystems Agile Platform includes a built-in SMS Gateway, although it can be replaced by a 3
rd
party SMS Gateway;
3.
The SMS Gateway posts the incoming message to the Outsystems Agile Platform Server Dispatcher. The Dispatcher is responsible for the delivery of the message to the exact eSpace, according to SMS Inbound Routing rules. At this level an incoming message can be associated with an existing dialog status. In that case, dialog status is retrieved and can be used at the eSpace business logic level. Dialog status matching is based on the pair (MSISDN; SMS-C Large Account). Messages are posted in a HTTP/XML format.
4.
At the eSpace level, an incoming message is processed, handling its content and properties, sending a new message back to the end user.
If the needed features are simpler than creating complex outbound and inbound SMS flows, you can always consume a WebService from a Mobile Operator that provide a service to deliver SMS to a specific number.
Please visit the
What do I need to get sms working
topic on the OutSystems Network forums for more information.
Log in to Answer
Log in to Answer
Log in to Follow
Loading...
頑張って翻訳しています
AI 翻訳中です。長くかからないはずですので、お待ちください!