Issues getting MO-SMS notifications via AerFrame

  • 1
  • Problem
  • Updated 2 years ago
  • Solved
Hi, I've tried following the instructions for setting up AerFrame notifications here: http://neo.aeris.com/support/accessing-the-aeris-network/send-receive-sms-api/

Below is the process that I followed.

When sending an SMS message, the device receives it. I've verified this via the TCP connection that it makes to my server that the settings sent via SMS were received.
The device responds to SMS messages with another SMS confirmation.
I get the confirmation from AerFrame that sending the message was successful, but don't get any response SMS.

Is the device able to send an SMS and I'll receive it by AerFrame? If yes, do I have to set up anything special on the device end?

Another note, there seem to be many calls in the API docs that don't exist: http://neo.aeris.com/support/apis/aerframe-2/#notificationChannelManagementOperations

* GET notificationchannel/v2/{accountId}/channels
* GET/networkservices/v2/{accountId}/devices/{deviceIdType}/{deviceId}/localDialableNumber

And probably a few others.





ID: {MYACCTNUM}
Key: {MYACCTAPIKEY}
App key: {MYAPPKEY}
Callback URL: https://api.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/channels/000f7fdc-974e-277a-3582-673186e06ce8/callback





IMSI: {MYDEVICEIMSI}
Text: +XT:1001?


https://api.aerframe.aeris.com/registration/v2/{MYACCTNUM}/applications?apiKey={MYACCTAPIKEY}
{
"applicationName":"AT2",
"applicationShortName":"AT2",
"applicationTag":"AT2",
"description":"AT2"
}

response:
{
"applicationName": "AT2"
"applicationShortName": "AT2"
"applicationTag": "AT2"
"description": "AT2"
"apiKey": "{MYAPPKEY}"
"resourceURL": "https://api.aerframe.aeris.com/registration/v2/{MYACCTNUM}/applications/000f7a41-63ac-9f4c-6b96-36229b252946"
"useSmppInterface": false
}


https://api.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/channels?apiKey={MYAPPKEY}
{
"applicationTag":"aerframe",
"channelData":{
"maxNotifications":"15",
"type":"nc:LongPollingData"
},
"channelLifetime":"7200",
"channelType":"LongPolling",
"clientCorrelator":"AT2"
}

response:
{
"clientCorrelator": "AT2"
"applicationTag": "aerframe"
"channelType": "LongPolling"
"channelData": {
"channelURL": "https://longpoll.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/longpoll/000f7fdc-974e-277a-3582-673186e06ce8"
"maxNotifications": 15
}-
"channelLifetime": 7200
"callbackURL": "https://api.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/channels/000f7fdc-974e-277a-3582-673186e06ce8/callback"
"resourceURL": "https://api.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/channels/000f7fdc-974e-277a-3582-673186e06ce8"
}


https://api.aerframe.aeris.com/smsmessaging/v2/{MYACCTNUM}/inbound/subscriptions?apiKey={MYAPPKEY}
{
"callbackReference":{
"callbackData":"AT2-mosub1",
"notifyURL":"https://api.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/channels/000f7fdc-974e-277a-3582-673186e06ce8/callback"
},
"criteria":"SP:*",
"destinationAddress":[
"AT2"
]
}

response:
{
"callbackReference": {
"notifyURL": "https://api.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/channels/000f7fdc-974e-277a-3582-673186e06ce8/callback"
"callbackData": "AT2-mosub1"
"notificationFormat": "JSON"
}-
"destinationAddress": [1]
0: "AT2"
-
"criteria": "SP:*"
"resourceURL": "https://api.aerframe.aeris.com/smsmessaging/v2/{MYACCTNUM}/inbound/subscriptions/000f7a64-65ad-7f39-131b-23646b860e4d"
"link": [0]
}


https://api.aerframe.aeris.com/smsmessaging/v2/{MYACCTNUM}/outbound/AT2/subscriptions?apiKey={MYAPPKEY}
{
"callbackReference":{
"callbackData":"AT2-mtsub1",
"notifyURL":"https://api.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/channels/000f7fdc-974e-277a-3582-673186e06ce8/callback"
},
"filterCriteria":"SP:*"
}

response:
{
"callbackReference": {
"notifyURL": "https://api.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/channels/000f7fdc-974e-277a-3582-673186e06ce8/callback"
"callbackData": "AT2-mtsub1"
"notificationFormat": "JSON"
}-
"filterCriteria": "SP:*"
"resourceURL": "https://api.aerframe.aeris.com/smsmessaging/v2/{MYACCTNUM}/outbound/AT2/subscriptions/000f7ffc-09c5-e99f-273f-8a88150a5f49"
"link": [0]
}


https://api.aerframe.aeris.com/smsmessaging/v2/{MYACCTNUM}/outbound/AT2/requests?apiKey={MYAPPKEY}
{
"address":[
"{MYDEVICEIMSI}"
],
"senderAddress":"AT2",
"outboundSMSTextMessage":{
"message":"+XT:1001?"
},
"clientCorrelator":"AT2",
"senderName":"AFTestClient"
}


response:
{
"address": [1]
0: "{MYDEVICEIMSI}"
-
"senderAddress": "AT2"
"senderName": "AFTestClient"
"outboundSMSTextMessage": {
"message": "+XT:1001?"
}-
"clientCorrelator": "AT2"
"resourceURL": "https://api.aerframe.aeris.com/smsmessaging/v2/{MYACCTNUM}/outbound/AT2/requests/000f801f-04e2-078f-4eaf-e7e803eaca2d"
}



https://longpoll.aerframe.aeris.com/notificationchannel/v2/{MYACCTNUM}/longpoll/000f7fdc-974e-277a-3582-673186e06ce8?apiKey={MYAPPKEY}


response:
{
"deliveryInfoNotification": [1]
0: {
"callbackData": "AT2-mtsub1"
"deliveryInfo": [1]
0: {
"address": "{MYDEVICEIMSI}"
"deliveryStatus": "DeliveredToTerminal"
"link": [2]
0: {
"rel": "MTMessageRequest ResourceUrl"
"href": "https://api.aerframe.aeris.com/smsmessaging/v2/{MYACCTNUM}/outbound/AT2/requests/2085265129"
}-
1: {
"rel": "MTDeliverySubscription ResourceUrl"
"href": "https://api.aerframe.aeris.com/smsmessaging/v2/{MYACCTNUM}/outbound/AT2/subscriptions/000f7ffc-09c5-e99f-273f-8a88150a5f49"
}-
-
}-
-
}-
-
"inboundSMSMessageNotification": [0]
}


Photo of Ryan Ahlfors

Ryan Ahlfors

  • 2 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Abraham Fuentes

Abraham Fuentes, Official Rep

  • 61 Posts
  • 0 Reply Likes
Official Response
Ryan,

After talking this over with several team members the general consensus is that this short code will most likely never be changed.

Please let us know if this answers your concerns so that we may close this issue out.

Regards,
Abraham Fuentes