| How does DefaultMMSVersion parameter work? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Anne Hughes New member Username: Annehughes Post Number: 3 Registered: 03-2004 |
Hi Byrce, Can you tell me how the DefaultMMSVersion parameter works. According to the documentation about the parameter... "DefaultMMSVersion=1.0 (or 1.1 or 1.2) (v2006+) This setting specifies the default MMS version to be assumed when sending an MMS message to a user account that is not defined to the MMSC. The default setting is 1.0." This is my problem. We did not have DefaultMMSVersion defined in our MMSC.INI file. All mms 1.1 messages sent to NowSMS were being received by our simulator as mms 1.0 - even when the user account was defined in NowSMS. I found that the .ini file being produced had this entry - [Recipient MMS Version] outgoing phone no=1.0 and the [NotifyPDU] had the mms version set to 1.0 ( 0X90) If I set DefaultMMSVersion=1.2 then when I send a mms 1.0 message to NowSMS, I will get a mms 1.2 message sent to the simulator - even when the user account is defined in NowSMS. We need to test all the different mms versions, so how can we get a mms 1.1 message to be sent to NowSMS and still received by the simulator as mms 1.1 ? What should happen when the outgoing phone no. is defined as a user account in NowSMS and the DefaultMMSVersion is not defined ? I'm confused - so any help much appreciated, Anne | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6411 Registered: 10-2002 |
Hi Anne, I'm confused too. Or at least I was, as I think I've now figured it out. The DefaultMMSVersion setting is used when we do not know what the MMS version number is of the recipient. If you send an MMS message to a recipient that is not defined to the MMSC, then it is always going to go out with the DefaultMMSVersion. If you send an MMS message to a recipient that is defined to the MMSC, then NowSMS might know what version number that client supports. But if it doesn't, then the notification is going to go out with DefaultMMSVersion. The question is ... how does NowSMS know which version the client supports? Currently it does not know until the client sends a message through NowSMS as the MMSC. Every time this happens, the MMS version number associated with the message send request is checked against the MMS version number that we remembered (if any) for this client, and updated if necessary. Unfortunately, there is no way to manually update this value that is associated with an "MMSC Users" account. The only way to update it is for the MMSC to receive a send request which indicates a different MMS version. If you needed to change the MMS version for testing, the easiest way to do this would probably be to perform an HTTP POST with a dummy MMS message. From what I can see, the PDU only needs to include message_type, transaction_id, mms_version and content_type. If those headers are present, PDU validation will get to the vresion check. Don't include any recipient headers, and an error will be returned ... no message sent ... but the MMS version number associated with the account would be changed. We could also look at adding an option to the "MMSC Users" page to set the version number. But I'm not sure that could be done very quickly right now. -bn | |||
