| Please refer me to a newsgroup to answer my questions |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Jeff Rhodes Unregistered guest |
I stumbled across this bb via google. Please forgive me for being such a newbie with respect to MMS. Can someone point me in the right direction for help concerning: 1.What is "protocol negotiation" for GSM, I think this has something to do with TCAP. I ran into a problem where "version 2 can't talk to version 3 unless the version 3 side supports protocol negotiation"? Does that make any sense? 2. I think that MMS requires an SMS message to "kick things off", at least that would make sense for incoming messages to an idle mobile. Is that right? If so, does the SMSC have to be "version 3" or will MMS work fine with a "version 2" SMSC? 3. Is there a correlation between "version" and GSM standards "release" numbers. TIA, Jeff Rhodes jrhodes@wirelesscorp.com | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3482 Registered: 10-2002 |
Hi Jeff, I'm not sure where a good newsgroup would be for these types of questions. In general, I don't find very many good resources for this type of indepth technical queries. Also, I'm not sure what the version numbers are that you are referring to. But, I can give you an idea of how MMS works. A real basic overview can be found at the following link: http://www.nowsms.com/howmmsworks.htm There is an SMS message that kicks off the delivery process. I'm not aware of any version number issues in that SMS message. It is the content of the message that triggers the MMS client. In the GSM environment, the UDH (user data header) of the SMS message contains a destination port number reference of 2948. This indicates that the message is a WAP push message. WAP Push messages can be of different content types, and the content type is evaluated to determine that it is an MMS notification message that needs to be routed to the MMS client. The relevant specifications are available from the Open Mobile Alliance (http://www.openmobilealliance.org). MMS Encapsulation defines the format of MMS messages. WAP Push uses the Wireless Session Protocol (WSP). And WSP is sent over the air using the Wireless Datagram Protocol (WDP), where the WDP spec defines how this protocol is adapted to different bearers, such as GSM SMS. -bn | |||
| Jeff Rhodes Unregistered guest |
Thanks very much Bryce, this is very helpful information. With respect to "versions" I notice that 29-002 Table 5.1/2 shows some messages with v1, v2, v3 associations. For example, MSC/VLR shows MT-ForwardSM as v3 but ForwardSM as v1/v2. Maybe this is related to what I am looking for? In other words, the type of SMS message that is sent to the mobile via the MSC/VLR to "kick things off" is dependent on the MSC/VLR version number? But from what you have described, it is merely the SMS_BearerData that contains a precisely formatted message that will cause the mobile to seek the WAP push. Thanks, again. Jeff | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3497 Registered: 10-2002 |
Jeff, I wouldn't see anything MMS specific in those references ... nothing version number specific. What might be confusing is that in some documents they talk about RP-MMS and TP-MMS elements, where there are some MAP version issues. But MMS in that context means "More Messages to Send". If you are encountering a version number issue at this level, I would expect it to apply to all SMS message traffic. One of my general pieces of advice for people trying to setup our software to send MMS is this ... First verify that you can send text SMS messages correctly. Next, verify that you can send binary SMS messages correctly, where the easiest thing to do is to send a simple WAP Push (Service Indication). Then, assuming that is all ok, move on to troubleshooting MMS. (And for intial MMS troubleshooting, I recommend using a SonyEricsson T68i, T610, or T630 family device if possible. The nice thing about those devices is that they will show you if the MMS notification part of the transaction was received, even if it the full MMS delivery process is not working. Many other devices won't tell you that an MMS notification was received until the MMS content can be successfully retrieved, making it harder to troubleshoot.) -bn | |||
