| 2-Way / MMSC Route |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Bradley Shackleford New member Username: Bshackleford Post Number: 10 Registered: 02-2020 |
Hi Team, I feel this is an odd request but makes sense in my head. We are acting as a "customer" on our network and we set-up automated PINGs for SMS which in turn returns the below. My question is, if I send a PINGMMS keyword, I know it can respond with a MMS/Picture/Gif etc, but is there SMS commands to return something like "@@MMSCROUTE@@"? I reviewed the 2-way command page but have not found anything that shows the route for MM4 connections. "Message received from @@SENDER@@ over @@SMSCROUTE@@ on day @@MSGDATE@@ at @@MSGTIME@@ EST." Thank You, Bradley | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8341 Registered: 10-2002 |
Hi Bradley, That would make sense, but no, there is no 2-way SMS command option that returns this. In many ways, the MMS and SMS functionality of the product evolved separately, each focused on different customer needs. The option to process MMS messages via 2-way SMS commands was a relatively recent addition. I did a little more review and investigation and found that for MMS messages received via modem, the modem name is preserved to be reported as @@SMSCROUTE@@. For messages received from a VASP, the HDR file in MMS-IN will record the name of the account in a header "X-NowMMS-Received-From-VASP:". However, this value is not processed as a 2-way command variable. We will investigate whether it could be processed in a future update. -bn Bryce Norwood Now SMS/MMS Support | |||
| Bradley Shackleford New member Username: Bshackleford Post Number: 18 Registered: 02-2020 |
Hey Bryce, Just wanted to check-back in to see if this was a viable request to have added in for future updates? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8368 Registered: 10-2002 |
Hi Bradley, We did make a small change as a result of this, but it was not logged in our changes file, because our engineering team felt that my suggestion of how to handle this was incomplete. So, let me explain. A change was made, so that the inbound MMSC VASP account name (X-NowMMS-Received-From-VASP) is reported as the @@SMSCROUTE@@ if an MMS message gets routed to a 2-way SMS command. This raised two issues that they thought should be addressed or clarified before this was documented: 1.) As we know, the route in this case is not an SMS route. Should it be prefixed to indicate that it is an MMS route? (e.g., MMS:routename or VASP:routename) 2.) For MM4, at the moment, the inbound MMS route names are IP addresses. Should the "MM4 ACK Route" be returned instead of this IP address, so that the reply route could be known? I didn't have a good answer for those questions (and still do not). But, I can share an interim update which includes this and other recent changes: https://www.nowsms.com/download/nowsms20201015.zip Regards, Bryce Norwood Now SMS/MMS Support | |||
