Where is the MM1_notification

Where is the MM1_notification SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Where is the MM1_notification « Previous || Next »
Author Message
bobby
Unregistered guest
Posted on Wednesday, March 10, 2004 - 08:28 am:   

Hi,Bryce,I have an another problem:
I have stored a MM at my web server and got a URL, then I sent a MMS notification for it, it succeeded and "message submitted" appeared, but where was the notification sent to?
I want to capture and analyse it. help me please!
thx!

As I known,all the MM1 messages is transferred through Wap Gateway, and Http protocol will be used between MMSC and Wap Gw,so can I get the notifiction through a Tcp connection?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2061
Registered: 10-2002
Posted on Wednesday, March 10, 2004 - 03:24 pm:   

The notification is sent to the destination phone number that you specify, over SMS.

The web menu interface will also let you send a notification over IP to an IP address by specifying an IP address in the phone number field (but if you're trying to send the notification to an emulator running on the PC, note that our experience is that these emulators do not listen for notifications over IP ... and if you're trying to send the notification over IP to a real phone, note that most service providers assign private IP addresses to the phones, and allow the phones to access the internet via a network address translation, which means you cannot send a push over IP to them unless you are also on the operator's private IP network).

If you want to analyse the notification, you can find it in the SMS log files (SMS-yyyymmdd.LOG).


quote:

As I known,all the MM1 messages is transferred through Wap Gateway, and Http protocol will be used between MMSC and Wap Gw,so can I get the notifiction through a Tcp connection?




Except that the MMS notification is usually sent over SMS.

bobby
Unregistered guest
Posted on Thursday, March 11, 2004 - 12:04 am:   

Thanks, as you described,The MM notification is usually sent to SMSC directly, so the SMPP protocol is used,is that right?
but anyway the notification is sent over ip, how can I capture the PDU?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2077
Registered: 10-2002
Posted on Thursday, March 11, 2004 - 05:18 pm:   


quote:

Thanks, as you described,The MM notification is usually sent to SMSC directly, so the SMPP protocol is used,is that right?




Well, it uses whatever protocol the system is configured to use for sending SMS. If you are using an SMPP connection to your SMSC, then it would go via SMPP.

If you are sending messages through a GSM modem, then it would go over the GSM modem.


quote:

but anyway the notification is sent over ip, how can I capture the PDU?




I assumed that you were using NowSMS, and that is why I pointed you to the SMSOUT-yyyymmdd.LOG file, which would load the details of the SMS messages that were sent out.

If you need a general purpose protocol analyser, try Ethereal (www.ethereal.com).
bobby
Unregistered guest
Posted on Tuesday, March 16, 2004 - 06:06 am:   

Hi,I have captured the MM1_notification.req message using a fake SMSC, It is a SMPP PDU
the value of sm_length field is 125, and the sm field is listed behind:

06 05 04 0B ???
84 23 //Content-Type:application/vnd.wap.multipart.mixed? why not 0xA3?
F0 7C 06 22 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 65 00 AF 84 // .."application/vnd.wap.mms-message what's this??

I can the parse the following fields by myself,am I right?
8C 82 //Message-Type:m-notification-ind
98 31 32 33 34 00 //Transaction-Id:1234
8D 90 //MMS-Version
89 0E 80 32 30 30 34 30 33 31 35 31 36 30 38 00 //From ,what does the '0E' and '80' mean?
96 73 75 62 6A 65 63 74 00 //Subject:subject
8A 80 //Message-Class:Personal
8E 01 56 //Message-Size,length=1,value is 0x56
88 05 81 03 09 3A 80 //Expiry,length=5, but the value 0x8103093A80 is seemed too large!!!
83 68 74 74 70 3A 2F 2F 31 30 32 2E 31 36 38 2E 30 2E 35 32 2F 6D 6D 73 2F 74 65 73 74 2E 6D 6D 73 00 //Content-Location:http...

Thx!!!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2114
Registered: 10-2002
Posted on Tuesday, March 16, 2004 - 02:21 pm:   

You seem to be most confused by the headers.

Download the WAP 2.0 specs from the Open Mobile Alliance web site:

http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html

And keep in mind that what you are looking at an MMS Encapsulation message (the m-notification-ind), which is encapsulated inside of a WSP packet (connection-less push), which is sent via WDP (SMS over GSM).

So to decode all of the bits, you need to consult the WDP, WSP and MMS Encapsulation specification.

Here is another discussion thread out here from someone who had a little better handle on the WDP & WSP headers:

http://support.nowsms.com/discus/messages/12/501.html

For more information on the "From" field encoding, refer to the MMS Encapsulation specification.

-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics