000013159 - What is the correct format of message sent to SMS aggregator?

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000013159
Applies ToAuthentication Manager 7.1 SP4
SMS Aggregator
On Demand Tokencode
IssueWhat is the correct format of message sent to SMS aggregator?
Customer is using MIR3 web services and their software package called inEnterprise to send emergency notifications. He would like to use web services to send the on demand message with tokencode. The inEnterprise sends a call to Cybase 365 as SMS aggregator.
Resolution
1. MIR3 is not approved vendor. On MIR3 web services, the admin should be given access permissions to access SMS aggregator web services.
2. XML file provided by MIR3 should be modified.

The below modification to xml file is very generic and may vary for other vendors. Please contact SMS aggregator vendor to understand the XML file.
 
Example: XML Code for MIR3:
SMS Plug-In: HTTP
Base URL: https://ws.mir3.com/services/v1.2/mir3
I imported a security certificate from MIR3 for https connection.
HTTP Method: XML
XML Request Body:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://www.mir3.com/ws">
<soapenv:Header />
<soapenv:Body>
<oneStepNotification xmlns="http://www.mir3.com/ws">
<apiVersion>2.18</apiVersion>
<authorization>
<username>$cfg.user</username>
<password>$cfg.password</password>
</authorization>
<notificationDetail>
<contactCycleDelay>360</contactCycleDelay>
<contactAttemptCycles>1</contactAttemptCycles>
<textDeviceDelay>360</textDeviceDelay>
<leaveMessage>
<message>false</message>
<callbackInfo>false</callbackInfo>
</leaveMessage>
<broadcastInfo>
<broadcastDuration>600</broadcastDuration>
<recipients>
<dynamicRecipient>
<firstName>anonymous</firstName>
<lastName>anonymous</lastName>
<devices>
<device>
<deviceType>SMS-Text</deviceType>
<address>$msg.address</address>
<description>Mobile Phone Number</description>
</device>
</devices>
</dynamicRecipient>
</recipients>
</broadcastInfo>
<priority>STANDARD</priority>
<title>Sample Title</title>
<verbiage>
<text>On-Demand Tokencode: +$msg.message</text>
</verbiage>
</notificationDetail>
</oneStepNotification>
</soapenv:Body>
</soapenv:Envelope>
 
Changes to XML above:
In the above XML code change <deviceType>SMS</deviceType> to <deviceType>SMS-Text</deviceType>
Account User Name and Password were created through MIR3's inEnterprise COTS product used by another Lockheed Martin group, LMNotify.
Success Response Code: true
Response Format: .+?<success>(.)</success>.
Edited the xml code on SMS configuration setup page .
Added the word SMS.Text in the code under device type.
After that it worked.
Edited the field SUCCESS response = He has removed "00" and added the word true
Edited the field Response format" Removed the word "error code" and replaced with "<Success>" (.*) <Success> "
Legacy Article IDa54966

Attachments

    Outcomes