| MM1 Control Messages |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Stewart |
Does anyone have know what the impact would be on an operator's MMSC for messages received from an 'off-net' MMSC? Does the handset send the MM1 control messages to the URL configured on the phone *or* the URL in the delivered MMS? Does anyone know what impact this would have on the operator's MMSC? Would the MMSC get confused by control messages for MMS's it never sent? Thanks, Stew | |||
| Bryce Norwood - NowSMS Support |
Stew, I assume that you're referring to the "m-notifyresp-ind" message that is sent back to the MMSC configured in the phone settings after an MMS message is retrieved. The worst case scenario is that the MMSC returns an error response if it does not know the message-id. According to the specification, clients are supposed to ignore any response returned to the "m-notifyresp-ind" message. Out of curiosity, I tried against an operator MMSC that I know is running a Nokia MMSC. The new version of the Now SMS/MMS Gateway has the ability to act as an MMS client and can retrieve MMS messages from an operator MMSC over GPRS. So I sent an MMS message to a GPRS modem attached to the gateway with a notification for an MMS message that did not pass through the operator MMSC. When the "m-notifyresp-ind" message was sent to acknowledge the message receipt, a 502 error came back. In practice, as the MMS client is supposed to ignore whatever response comes back from the "m-notifyresp-ind", I've never seen this cause an error message to be displayed with any of the different handsets I've tried with this operator. -bn | |||
| Vijay N S |
What are all the different Message Types and Information Elements in any MMS traffic across a network? | |||
