| Sending MMS with multiple modems - how to specify the route? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| Paul Crick New member Username: Paulcrick Post Number: 5 Registered: 07-2011 |
We've been using NowSMS Lite and having great success with it. We're now looking at using the full NowSMS product but I wanted to clarify the routing capabilities when it comes to MMS. I'm currently using PHP to do an HTTP POST to NowSMS Lite and one of the form fields we send is MMSFrom, which we populate with the E.164 number from the SIM chip in use. From reading some of the documentation/wiki for NowSMS it seems for SMS I can specify a route on the URL line (when using GET), or have a "route lookup" call back that would get the route from an external web service. I'm wondering how this works for MMS though - do I have to always specify MMSFrom and populate with the right value (which would somehow trigger usage of the right modem?) Or can I omit the field, and either supply a route name, or use the external webservice to specify which route to use? My goal is "I want to send MMSs out, specifying which modem to use", where I'll vary this by recipient (based on internal logic to load balance between carriers). Any advice/pointers much appreciated. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3970 Registered: 08-2008 |
Hi Paul, It appears that the only way to do this on submission is by using the "MMSFrom" parameter. (As you mention, the routing callback is also an option, but that requires a separate external web service.) I know we have previously explored adding other options, but these appear to be the only solutions implemented at present. The "MMSFROM" phone number is matched up against the "Default Sender Address" property for establishing which route to use. I am slightly concerned that some mobile operator MMSCs require the sender address to be left blank when submitting an MMS message. So please test whether or not this is the case with the operators you are using. If it is a problem, I will escalate with engineering to get an alternate solution. -- Des NowSMS Support | |||
