| Notification message |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Toma New member Username: Toma Post Number: 5 Registered: 11-2003 |
Hello everybody, I have a question here on the matter of notification message. When the PPG or MMSC server sends the push or notification message to the cell phone, i hear that it sends it over SMS. 1. Does this mean that the PPG or MMSC sends the message to the SMSC server which then relays it to the cell phone? 2. When the message gets to the cell phone, the client software will read the type to see how to handle the message and display the appropriate menu item/option to the user? (download for mms, view in wap browser for url?) And if there the phone is not mms enabled, it will display the text message but no option to download is displayed? Thanks. | |||
| hejinping New member Username: Hejinping Post Number: 1 Registered: 11-2003 |
You can refer to Nokia7650. Generally, when thenotification reach the cell phone, the user doesn't konw the notofication. Only the mms is downloaded sucessfully, the user know the new mms. If the phone does not support mms, it will display sms. If user want to know the mms,he can read the mms in Internet by the url included in the two sms. Emal address: hejinping@yulong.com | |||
| Toma New member Username: Toma Post Number: 8 Registered: 11-2003 |
I see, thanks Hejinping. So does the notification message go to the smsc server before it gets to the cell phone? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1271 Registered: 10-2002 |
This behaviour is phone specific. It is like this on the Nokia series 60 phones (although I have noticed that the Nokia 3650 beeps and displays "retrieving message" for a couple of seconds each time it attempts to fetch an MMS message). However, on other phones, you can see that notifications have been received even if the MMS content could not be retrieved. I'm thinking primarily of the SonyEricsson T68i and the Panasonic GD87 that behave like this. When the notification is sent over SMS (which is almost always the case), an SMSC is going to actually deliver that notification to the phone. | |||
| Sooryanarayanan Venkatesh New member Username: Wapseeker Post Number: 1 Registered: 02-2004 |
Hi all, I am a new member to this discussion board. I find that the participation level both from Bryce and other people to this discussion board is enormous. We are using NowSMS for testing MMS PDU's and their fields. We are able to see some of the packets like M-Send.req, M-Send.conf and M-retrieve.conf using the sniffer tools like Ethereal. My question is does NowSMS provides a facility to see the other packets in the form of logs and if yes, the location where I can see those logs. Ofcourse I went through the SMSOUT files which was greek and latin to me. For example where can I see the M-Notification.ind PDU packet in the NowSMS log? Thanks in advance and your inputs will be highly appreciated. With regards Wapseeker | |||
| Sooryanarayanan Venkatesh New member Username: Wapseeker Post Number: 2 Registered: 02-2004 |
Hi all, I am a new member to this discussion board. I find that the participation level both from Bryce and other people to this discussion board is enormous. We are using NowSMS for testing MMS PDU's and their fields. We are able to see some of the packets like M-Send.req, M-Send.conf and M-retrieve.conf using the sniffer tools like Ethereal. My question is does NowSMS provides a facility to see the other packets in the form of logs and if yes, the location where I can see those logs. Ofcourse I went through the SMSOUT files which was greek and latin to me. For example where can I see the M-Notification.ind PDU packet in the NowSMS log? Thanks in advance and your inputs will be highly appreciated. With regards Wapseeker | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1781 Registered: 10-2002 |
Well, the MMS notification PDU is included in the SMS messages that are generated by the gateway, so you can see them in the SMSOUT log files. Frequently, the MMS notification must be split over 2 or more SMS messages because the data is too large to fit into a single SMS. When notifications are sent over SMS, relevant port numbers are encoded in the UDH (user data header) of the SMS. If a single logical message must be split into multiple SMS messages, this control information also goes into the SMS UDH. For more information, consult the relevant OMA (Open Mobile Alliance) WAP specifications, which would be as follows: MMS Encapsulation Specification - This covers the format of the MMS notifiation PDU. Wireless Session Protocol (WSP) - The MMS notification PDU is encapsulated in a WAP push message. The connection-less WAP Push PDU format is documented in WSP. Wireless Datagram Protocol (WDP) - The WAP push message is transmitted over WDP. In the IP environment, WDP maps directly to UDP. However, WDP can also be mapped to other transport protocols, such as GSM SMS. See the section of the WDP spec that covers this mapping to GSM SMS, which will provide more information on the UDH that I referenced above. -bn | |||
| Sooryanarayanan Venkatesh New member Username: Wapseeker Post Number: 3 Registered: 02-2004 |
Hi Bryce, Thanx for your valuable information. We use your tool to set up the test environment. I went through the SMSOUT log file and it seems it sends the Notification message to the mobile client. But I am not able to decipher the entry in the SMSOUT log file pertaining to Notification message. I am attaching the entry from the SMSOUT log file. Can you please tell me that whether the attached entry is ofcourse the Notification message? Or can you provide me a sample Notification message from the SMSOUT log file? We are using Sony Ericsson Z600 for our testing purposes. 2004-02-05 13:40:34,SAR-9840410504-e9-2-1.req,MMS user 567456423189 (test),9840410504,OK -- COM2:,Binary=1;DCS=F5;UDH=0B05040B8423F00003E90201;Data=E906226170706C6963617469 6F6E2F766E642E7761702E6D6D732D6D65737361676500AF848C82983230413531314444008D9089 18803536373435363432333138392F545950453D504C4D4E008A808E02028F88058103093A808368 7474703A2F2F31302E3134352E332E3234372F32303034303230352F31322F3230413531 With regards Soorya | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1854 Registered: 10-2002 |
Soorya, That looks like part 1 of a notification message. MMS notification messages usually are 2 part messages. -bn | |||
| Sooryanarayanan Venkatesh New member Username: Wapseeker Post Number: 4 Registered: 02-2004 |
Hi Bryce, Sorry for that. Here goes the 2 part entry from the SMSOUT log file. 2004-02-05 16:12:23,SAR-9840410504-ec-2-1.req,MMS user 567456423189 (test),9840410504,OK -- COM2:,Binary=1;DCS=F5;UDH=0B05040B8423F00003EC0201;Data=EC06226170706C6963617469 6F6E2F766E642E7761702E6D6D732D6D65737361676500AF848C82983842454245424438008D9089 18803536373435363432333138392F545950453D504C4D4E008A808E02028F88058103093A808368 7474703A2F2F31302E3134352E332E3234372F32303034303230352F31362F3842454245 2004-02-05 16:12:26,SAR-9840410504-ec-2-2.req,MMS user 567456423189 (test),9840410504,OK -- COM2:,Binary=1;DCS=F5;UDH=0B05040B8423F00003EC0202;Data=4244382E4D4D533F69643D39 38343034313035303400 So can you confirm whether the above said message does ofcourse refers to M-Notification.ind? If you can decipher it and tell us it will be well appreciated. I have one more query regarding NowSMS. Can I see the other Push messages like M-Delivery.ind, M-Read-Orig.ind in the SMSOUT log files? Please clarify. Thanx in advance Soorya | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1882 Registered: 10-2002 |
Soorya, I can tell that it is because I see the WAP push port as the destination in the UDH (destination port 0x0B84 = 2948). And I see the MMS content type in the push header (6170706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676500 = application/vnd.wap.mms-message). I can see that the push content starts with 8C82, which is X-Mms-Message-Type = m-notification-ind. But a full decode, well, that's what the specs are for. Trust me, it's more fun when you do it yourself. (Can you tell it is Friday, and I want a beer?) M-Delivery.ind messages will also be generated in this fashion. Currently we do not generate M-read-orig.ind transactions. (This is a complicated issue, as it requires that the MMSC keep track of what MMS version is in use by each connected client. We have to start tracking this in order to support this transaction.) -bn | |||
| Sooryanarayanan Venkatesh New member Username: Wapseeker Post Number: 6 Registered: 02-2004 |
Hi Bryce, Gr8 help rendered. It is indeed fun to decode and we are successful in decoding the M-Notification.ind and M-Delivery.ind messages. Thanx for the support. With regards Soorya P.S. How about a Beer coming week-end dude???!!  | |||
