| MMSC Response Status |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| MMSCer |
Hi, I tried to post a precompiled MMS M-Send.req PDU to nowsms MMSC, and got a M-Send.conf response, but with the value of "X-Mms-Response-Status" field as 0x84, that would means "Error-sending-address-unresolved". what would be the possible reason for such a response? I think I had followed the MMS Encapsulation protocol strictly. Thanks! | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Even if you included a sender address in your MMS encapsulated message, the gateway will not accept your message without authorisation. (A gateway that would accept any MMS message send request without authorisation would be a serious security problem.) You can submit a message using the MM1 interface (that's the interface that you are using) if you include a username and password for authorisation in the HTTP path that you are posting to (POST to /username=password). However, in the current version, when you submit via the MM1 interface, you canNOT override the sender address. The MMSC will overwrite your sender address with the one configured for the account. We have a new release that is due out for beta testing shortly (we'll post a notice here on the site), and it will support more flexibility for applications to submit MMS messages. Among other interfaces supported in the upcoming v5.0 release, apps will be able to submit via MM1 (or use the Nokia EAIF headers to wrap MM1), and it will be possible to override the sender address. -bn | |||
