| Yet another newbie question |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| George |
Hello, Like many webmasters in a quest for a next big thing I'm just trying to get a grip on the SMS/MMS technology. Sorry for maybe stupid question or incorrect terms. Is it possible to deploy/administrate the Now gateway on a remote ded server and provide a one way application-to-person MMS content via, say, clickatell service? if yes, a brief tech overview or hints would be helpful. Thank you in advance. | |||
| Bryce Norwood - NowSMS Support |
Hi George, I'm not really sure where to start ... other than to mention that instructions for configuring the Clickatell as an HTTP SMSC can be found at: http://support.nowsms.com/discus/messages/1/136.html#POST403 I understand that they now also support SMPP, which is a better choice for sending out binary messages. But I don't know the host name and port number to use Clickatell in that mode. When NowSMS is setup, basically you just issue HTTP requests to it to send out messages (MMS messages require an HTTP POST instead of a simple HTTP GET). -bn | |||
| George |
Thank you Bryce, you personally and this forum are of great help for a rookie. I'd like to clarify my understanding of the whole process. So, generally, the (WAP push?) MMS notifications can be delivered via a third party SMSC supporting binary SMS, right? Then a mobile user terminal is able to access an URL on our server (running MMSC software) and download MMS file? If that scheme is valid will it work with any/most of mobile operators? | |||
| Bryce Norwood - NowSMS Support |
George, Basically that is correct. This scheme will work, as long as the URL is accessible to the terminal via the settings configured on the terminal for MMS. Just like there are settings on a device for the WAP browser to connect, there are also settings for the MMS client. There is a setting for the MMSC URL (this is mostly used by the device when sending an MMS message), and then there are WAP settings as today's MMS clients connect via WAP ... so you have a GPRS Access Point Name (APN) and the IP address of a WAP gateway, among other optional settings. (Note: GPRS is not required for MMS, but some phones will only send/receive MMS over GPRS, even though the WAP browser in the phone might support GSM dial-up.) The problem area is that with the supplied MMS settings for some mobile operators, a separate GPRS APN is set up for MMS vs. regular WAP browser traffic. The "MMS APN" can only talk to a particular WAP gateway, and that WAP gateway can only talk to the operator MMSC. That is how some operators (most notably Orange in the UK, but there are quite a few others in other countries as well) have things configured. If you have this type of situation, the only ways around this are to submit MMS messages through the operator MMSC (we'll have a variety of options for doing this with our product in the next release) ... or use an alternative to MMS, like WAP push. (You can't do presentations with SMIL in WAP push, but it's a good solution for some other applications.) -bn | |||
