| Now SMS/MMS Gateway v5.0 Beta Delay |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Bryce Norwood - NowSMS Support |
Argh ... Well, the beta release of the Now SMS/MMS Gateway v5.0 will not be ready for this week after all. Our internal testing showed that we hadn't adequately considered a few scenarios, particularly in the area of processing of received MMS messages, and how the routing works when MMS messages are routed to an external MMSC. We're making some adjustments in the software, and doing more internal testing. But at this point, it does not look like we will be able to release a beta until early next week. I do think it will be worth the wait. Sorry for the inconvenience! If you do want to be notified by e-mail when the beta release is posted to the web site, please fill in your e-mail address on the "Newsletter Form" on our home page. Thanks! -bn | |||
| Bryce Norwood - NowSMS Support |
And a note of progress. The software development work has been completed for the upcoming beta release. Now we just have to complete some documentation on how to configure the new features. The primary new features of the v5.0 release: 1.) Support for routing MMS messages via external MMSC connections. Similar to how routing prefixes can be defined for routing SMS messages to different SMSCs, this version supports routing MMS messages to different MMSC connections with support for:
2.) When receiving MMS messages, NowSMS can now automatically initiate a GPRS connection and fetch the MMS message content from the operator MMSC over GPRS and WAP. (This is necessary to enable the receipt of MMS messages from many operator systems.) 3.) Outbound MMS messages can be routed via an MM1 connection to an operator MMSC over GPRS and WAP, allowing messages to be submitted into an operator MMSC over a GPRS/GSM modem. 4.) When receiving MMS messages, in addition to the file-based interface, NowSMS can be configured to automatically parse the MMS content and forward it to an e-mail address, or to an MM7 client. 5.) VASP (Value Added Service Provider) accounts can be enabled on the gateway which allow other applications to submit messages to the gateway using MM7, MM4, MM1 or EAIF. There are other new features as well, we will include a more detailed list of enhancements closer to official product release. The primary new features of this release are the MMS related features described above. We expect to finally be posting a publicly accessible beta release to the web site late night on Monday (July 21), or possibly on Tuesday (July 22). -bn | |||
| Bryce Norwood - NowSMS Support |
Additional features worth noting since a couple of people have asked me ... We've also added additional interfaces for sending configuration settings messages to mobile devices. The v5.0 release will support the sending of SyncML Settings per the Nokia/Ericsson OTA Specification. It will also support OMA WAP Provisioning Content, as defined by the OMA WAP Provisioning Content Specification. For all of the settings interfaces, in addition to providing web forms to specify commonly used settings parameters, we've also added an option in the web menu interface where you can directly post a settings document, and have the gateway encode it to binary format for delivery. -bn | |||
| lars mService |
Fantastic  Just can't wait. ;)Lars | |||
| Anonymous |
Hello ! I'm a uni student. Can you guide me to how i could use an SMTP interface to communication betwen two MMSC ? this is my final exercrise ,please help me in detail !!! Thank you very much ! | |||
| Bryce Norwood - NowSMS Support |
Well, basically the 3GPP specifications document an interface called MM4 for this purpose. MM4 is an SMTP based interface, it essentially just documents some standards for names of SMTP message headers to be used for MMS messages. If you were going to configure the Now SMS/MMS Gateway v5.0 for this type of connection, you would do it like this ... Each bi-directional MMSC connection is going to require two definitions within the Now SMS/MMS Gateway configuration: 1.) An "MMSC Routing" defintion defines how the NowSMS gateway routes MMS messages out to another MMSC. 2.) An "MMSC VASP" definition defines how the NowSMS gateway will accept MMS messages for delivery that originate with another MMSC. On the "MMSC Routing" side of things, you're going to define an MM4 connection. Then you'll specify a "Server Address" which is the host name or IP address of the other MMSC. If the other MMSC supports SMTP AUTH, then you can supply a "login name" and "password" for making the connection. The "E-Mail Domain" parameter refers to an e-mail domain name that is automatically appended to any phone numbers so that recipient addresses can be considered to be in a legal SMTP format. You also need to configure phone number masks for which recipient addresses get routed for delivery via this particular connection. On the "MMSC VASP" side of things, if the sending system supports "SMTP AUTH", then specify an "Account Name" and "password" that the other system will use when it makes its SMTP/MM4 connections. If the other system does not support "SMTP AUTH", then you must specify the IP address of the other system as the "Account Name". Normally you would configure the account to accept MM4/SMTP connections only, and you would "Allow Sender Address Override" on the connection (which means that the sending system is allowed to specify a sender address for its messages). "MMSC Routing for received messages" would specify "Standard MMS Delivery". How this type of connection gets configured in other products is likely to vary considerably, but that should give you the basic ideas of how it works. -bn | |||
