R: MMS Push Problem
I tryed again with the conversion form that I found on the site but it's not working. 8c 82 // X-MMS-Message-Type: m-notification-ind 98 39 39 39 39 40 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00// X-MMS-Transaction-Id: [EMAIL PROTECTED] 8d 90 // X-MMS-Version: 1.0 8a 80 // X-MMS-Message-Class: Personal 8e 01 64 // X-MMS-Size: 100 88 06 80 04 3d 2b 32 4a // X-MMS-Expiry: an Absolute value, in the future 83 68 74 74 70 3a 2f 2f 77 77 77 2e 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 2f 00 // X-MMS-Content-Location: http://www.flyerone.com/ 84 be // Content-type: application/vnd.wap.mms-message Even if I copy the example of simple message that is on the site it's the same. test/test_http http://localhost:13013/cgi- > bin/sendsms?username=*'&'password=*'&' > to=*'&'udh=%06%05%04%0b%84%23%f0'&' > text=%0f%06%03%be%af%84%8c%82%98%39%39%39%35%40%66%6c%79%65%72 > %6f%6e%65%2e%6 > 3%6f%6d%00 > %8d%90%8a%80%8e%01%64%88%06%80%04%3d%64%8d%80% > 83%YourURI%00 I always get the messages but the telephone is dead! Thanx -Messaggio originale- Da: David Chkhartishvili [mailto:[EMAIL PROTECTED]] Inviato: mercoledì 11 settembre 2002 12.40 A: FERLA Alessandro Consultant Cc: '[EMAIL PROTECTED]' Oggetto: Re: MMS Push Problem Hi, You have to convert m-notification-ind.txt in binary form, otherwise you willn't get anything. FERLA Alessandro Consultant wrote: >Hi all, > I am trying to make working the MMS push but I have no results from >that. I write this command: > >./test_ppg -e base64 -a mms -c mms http://127.0.0.1:8080/wappush >notification-ind.txt papmms.txt > >With the content of the two files: > >notification-ind.txt: > >X-Mms-Message-Type: m-notification-ind >X-Mms-Transaction-Id: [EMAIL PROTECTED] >X-Mms-Version: 1.0 >X-Mms-Message-Class: Personal >X-Mms-Message-Size: 20 >X-Mms-Expiry: 2003 >X-Mms-Content-Location: http://www.brainstorm.co.uk/MMS >Subject: Test > > > >papmms.txt > > > >"http://www.wapforum.org/DTD/pap_1.0.dtd";> > > deliver-before-timestamp="2005-10-31T06:45:00Z" >deliver-after-timestamp="2001-02-28T06:45:00Z" >progress-notes-requested="false"> >address-value="[EMAIL PROTECTED]"> > > > > > >Kannel logs two messages sent but and the telephone seems to receive them >because when it is near my monitor I can see the image vibrate but nothing >happen. >The telephones I used are NOKIA7650 and Ericsson T68i > >Is there anyone that can help me? > >Thanx > >= >"STRICTLY PERSONAL AND CONFIDENTIAL > >This message may contain confidential and proprietary material for the sole >use of the intended recipient. Any review or distribution by others is >strictly prohibited. If you are not the intended recipient please contact >the sender and delete all copies. >The contents of this message that do not relate to the official business of >our company shall be understood as neither given nor endorsed by it." > >= > > > > -- David Chkhartishvili Tel: 995 99 182418 = "STRICTLY PERSONAL AND CONFIDENTIAL This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies. The contents of this message that do not relate to the official business of our company shall be understood as neither given nor endorsed by it." =
Re: R: MMS Push Problem
Are you sure that the expiry date is in the future ? Use date -r to check this. Aarno On Wednesday, September 11, 2002, at 07:02 PM, FERLA Alessandro Consultant wrote: > I tryed again with the conversion form that I found on the site but > it's not > working. > > > 8c 82 > // X-MMS-Message-Type: m-notification-ind > 98 39 39 39 39 40 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00// > X-MMS-Transaction-Id: [EMAIL PROTECTED] > 8d 90 > // X-MMS-Version: 1.0 > 8a 80 > // X-MMS-Message-Class: Personal > 8e 01 64 > // X-MMS-Size: 100 > 88 06 80 04 3d 2b 32 4a > // X-MMS-Expiry: an Absolute value, in the future > 83 68 74 74 70 3a 2f 2f 77 77 77 2e 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d > 2f 00 // X-MMS-Content-Location: http://www.flyerone.com/ > 84 be > // Content-type: application/vnd.wap.mms-message > > > > Even if I copy the example of simple message that is on the site it's > the > same. > > > > > test/test_http http://localhost:13013/cgi- >> bin/sendsms?username=*'&'password=*'&' >> to=*'&'udh=%06%05%04%0b%84%23%f0'&' >> text=%0f%06%03%be%af%84%8c%82%98%39%39%39%35%40%66%6c%79%65%72 >> %6f%6e%65%2e%6 >> 3%6f%6d%00 >> %8d%90%8a%80%8e%01%64%88%06%80%04%3d%64%8d%80% >> 83%YourURI%00 > > > I always get the messages but the telephone is dead! > > Thanx > > -Messaggio originale- > Da: David Chkhartishvili [mailto:[EMAIL PROTECTED]] > Inviato: mercoledì 11 settembre 2002 12.40 > A: FERLA Alessandro Consultant > Cc: '[EMAIL PROTECTED]' > Oggetto: Re: MMS Push Problem > > > Hi, > > You have to convert m-notification-ind.txt in binary form, otherwise > you > willn't get anything. > > FERLA Alessandro Consultant wrote: > >> Hi all, >> I am trying to make working the MMS push but I have no results from >> that. I write this command: >> >> ./test_ppg -e base64 -a mms -c mms http://127.0.0.1:8080/wappush >> notification-ind.txt papmms.txt >> >> With the content of the two files: >> >> notification-ind.txt: >> >> X-Mms-Message-Type: m-notification-ind >> X-Mms-Transaction-Id: [EMAIL PROTECTED] >> X-Mms-Version: 1.0 >> X-Mms-Message-Class: Personal >> X-Mms-Message-Size: 20 >> X-Mms-Expiry: 2003 >> X-Mms-Content-Location: http://www.brainstorm.co.uk/MMS >> Subject: Test >> >> >> >> papmms.txt >> >> >> >> > "http://www.wapforum.org/DTD/pap_1.0.dtd";> >> >> > deliver-before-timestamp="2005-10-31T06:45:00Z" >> deliver-after-timestamp="2001-02-28T06:45:00Z" >> progress-notes-requested="false"> >>> address-value="[EMAIL PROTECTED]"> >> >> >> >> >> >> Kannel logs two messages sent but and the telephone seems to receive >> them >> because when it is near my monitor I can see the image vibrate but >> nothing >> happen. >> The telephones I used are NOKIA7650 and Ericsson T68i >> >> Is there anyone that can help me? >> >> Thanx >> >> = >> "STRICTLY PERSONAL AND CONFIDENTIAL >> >> This message may contain confidential and proprietary material for >> the sole >> use of the intended recipient. Any review or distribution by others is >> strictly prohibited. If you are not the intended recipient please >> contact >> the sender and delete all copies. >> The contents of this message that do not relate to the official >> business of >> our company shall be understood as neither given nor endorsed by it." >> >> = >> >> >> >> > > > -- > David Chkhartishvili > Tel: 995 99 182418 > > > > = > "STRICTLY PERSONAL AND CONFIDENTIAL > > This message may contain confidential and proprietary material for the > sole > use of the intended recipient. Any review or distribution by others is > strictly prohibited. If you are not the intended recipient please > contact > the sender and delete all copies. > The contents of this message that do not relate to the official > business of > our company shall be understood as neither given nor endorsed by it." > > = >
R: R: MMS Push Problem
I tryed with "date -r filename" but I just get back the date of creation of the file. I can't understand how the X-MMS-Expiry date is encoded. Is there any documentation about that? Thank you. Alessandro. -Messaggio originale- Da: Aarno Syvänen [mailto:[EMAIL PROTECTED]] Inviato: giovedì 12 settembre 2002 9.03 A: FERLA Alessandro Consultant Cc: '[EMAIL PROTECTED]' Oggetto: Re: R: MMS Push Problem Are you sure that the expiry date is in the future ? Use date -r to check this. Aarno On Wednesday, September 11, 2002, at 07:02 PM, FERLA Alessandro Consultant wrote: > I tryed again with the conversion form that I found on the site but > it's not > working. > > > 8c 82 > // X-MMS-Message-Type: m-notification-ind > 98 39 39 39 39 40 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00// > X-MMS-Transaction-Id: [EMAIL PROTECTED] > 8d 90 > // X-MMS-Version: 1.0 > 8a 80 > // X-MMS-Message-Class: Personal > 8e 01 64 > // X-MMS-Size: 100 > 88 06 80 04 3d 2b 32 4a > // X-MMS-Expiry: an Absolute value, in the future > 83 68 74 74 70 3a 2f 2f 77 77 77 2e 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d > 2f 00 // X-MMS-Content-Location: http://www.flyerone.com/ > 84 be > // Content-type: application/vnd.wap.mms-message > > > > Even if I copy the example of simple message that is on the site it's > the > same. > > > > > test/test_http http://localhost:13013/cgi- >> bin/sendsms?username=*'&'password=*'&' >> to=*'&'udh=%06%05%04%0b%84%23%f0'&' >> text=%0f%06%03%be%af%84%8c%82%98%39%39%39%35%40%66%6c%79%65%72 >> %6f%6e%65%2e%6 >> 3%6f%6d%00 >> %8d%90%8a%80%8e%01%64%88%06%80%04%3d%64%8d%80% >> 83%YourURI%00 > > > I always get the messages but the telephone is dead! > > Thanx > > -Messaggio originale- > Da: David Chkhartishvili [mailto:[EMAIL PROTECTED]] > Inviato: mercoledì 11 settembre 2002 12.40 > A: FERLA Alessandro Consultant > Cc: '[EMAIL PROTECTED]' > Oggetto: Re: MMS Push Problem > > > Hi, > > You have to convert m-notification-ind.txt in binary form, otherwise > you > willn't get anything. > > FERLA Alessandro Consultant wrote: > >> Hi all, >> I am trying to make working the MMS push but I have no results from >> that. I write this command: >> >> ./test_ppg -e base64 -a mms -c mms http://127.0.0.1:8080/wappush >> notification-ind.txt papmms.txt >> >> With the content of the two files: >> >> notification-ind.txt: >> >> X-Mms-Message-Type: m-notification-ind >> X-Mms-Transaction-Id: [EMAIL PROTECTED] >> X-Mms-Version: 1.0 >> X-Mms-Message-Class: Personal >> X-Mms-Message-Size: 20 >> X-Mms-Expiry: 2003 >> X-Mms-Content-Location: http://www.brainstorm.co.uk/MMS >> Subject: Test >> >> >> >> papmms.txt >> >> >> >> > "http://www.wapforum.org/DTD/pap_1.0.dtd";> >> >> > deliver-before-timestamp="2005-10-31T06:45:00Z" >> deliver-after-timestamp="2001-02-28T06:45:00Z" >> progress-notes-requested="false"> >>> address-value="[EMAIL PROTECTED]"> >> >> >> >> >> >> Kannel logs two messages sent but and the telephone seems to receive >> them >> because when it is near my monitor I can see the image vibrate but >> nothing >> happen. >> The telephones I used are NOKIA7650 and Ericsson T68i >> >> Is there anyone that can help me? >> >> Thanx >> >> = >> "STRICTLY PERSONAL AND CONFIDENTIAL >> >> This message may contain confidential and proprietary material for >> the sole >> use of the intended recipient. Any review or distribution by others is >> strictly prohibited. If you are not the intended recipient please >> contact >> the sender and delete all copies. >> The contents of this message that do not relate to the official >> business of >> our company shall be understood as neither given nor endorsed by it." >> >> = >> >> >> >> > > > -- > David Chkhartishvili > Tel: 995 99 182418 > > > > = > "STRICTLY PERSONAL AND CONFIDENTIAL > > This message may contain confidential and proprietary material for the > sole > use of the intended recipient. Any review or distribution by others is > strictly prohibited. If you are not the intended recipient please > contact > the sender and delete all copies. > The contents of this message that do not relate to the official > business of > our company shall be understood as neither given nor endorsed by it." > > = > = "STRICTLY PERSONAL AND CONFIDENTIAL This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies. The contents of this message that do not relate to the official business of our company shall be understood as neither given nor endorsed by it." =
RE: R: MMS Push Problem
> I tryed with "date -r filename" but I just get back the date > of creation of > the file. I can't understand how the X-MMS-Expiry date is > encoded. Is there > any documentation about that? > Look at 7.2.10 of WAP-209-MMSEncapsulation-20020105-a for Expiry field encoding. Then look at WSP for long integer encoding.
R: R: MMS Push Problem
The result of the conversion is Sun, 29 Dec 2582 21:56:16 UTC I think it is correct but maybe something else is wrong in my message. This is my last encode of the message and obviously is not working. 8c82 9831423500 8d90 8a80 8e0164 880481020100 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D6172636F 2F706965727761702E6D6D7300 I expect the telephone to start to browse and go to retrieve the content. Is it correct? And the telephone seems to receive two messages but it doesn't do anything. And the pap file is always unchanged. Thank you again. Alessandro. -Messaggio originale- Da: Paul Keogh [mailto:[EMAIL PROTECTED]] Inviato: giovedì 12 settembre 2002 12.32 A: [EMAIL PROTECTED] Oggetto: RE: R: MMS Push Problem > I tryed with "date -r filename" but I just get back the date > of creation of > the file. I can't understand how the X-MMS-Expiry date is > encoded. Is there > any documentation about that? > Look at 7.2.10 of WAP-209-MMSEncapsulation-20020105-a for Expiry field encoding. Then look at WSP for long integer encoding. = "STRICTLY PERSONAL AND CONFIDENTIAL This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies. The contents of this message that do not relate to the official business of our company shall be understood as neither given nor endorsed by it." =
Re: R: R: MMS Push Problem
Hi, Remove last line, also try 9831323500 as expiry. FERLA Alessandro Consultant wrote: >The result of the conversion is Sun, 29 Dec 2582 21:56:16 UTC > >I think it is correct but maybe something else is wrong in my message. > >This is my last encode of the message and obviously is not working. > >8c82 >9831423500 >8d90 >8a80 >8e0164 >880481020100 >83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D6172636F >2F706965727761702E6D6D7300 > >I expect the telephone to start to browse and go to retrieve the content. Is >it correct? >And the telephone seems to receive two messages but it doesn't do anything. > > >And the pap file is always unchanged. > >Thank you again. > >Alessandro. > >-Messaggio originale- >Da: Paul Keogh [mailto:[EMAIL PROTECTED]] >Inviato: giovedì 12 settembre 2002 12.32 >A: [EMAIL PROTECTED] >Oggetto: RE: R: MMS Push Problem > > > > > >>I tryed with "date -r filename" but I just get back the date >>of creation of >>the file. I can't understand how the X-MMS-Expiry date is >>encoded. Is there >>any documentation about that? >> >> >> > >Look at 7.2.10 of WAP-209-MMSEncapsulation-20020105-a for Expiry field >encoding. > >Then look at WSP for long integer encoding. > > > >= >"STRICTLY PERSONAL AND CONFIDENTIAL > >This message may contain confidential and proprietary material for the sole >use of the intended recipient. Any review or distribution by others is >strictly prohibited. If you are not the intended recipient please contact >the sender and delete all copies. >The contents of this message that do not relate to the official business of >our company shall be understood as neither given nor endorsed by it." > >= > > > > -- David Chkhartishvili Tel: 995 99 182418
Re: R: R: MMS Push Problem
Your Expiry is 88 04 81 02 01 00 This means: 88: Expiry 04: Value-Length (of the header) 81: Expiry time relative, delta-seconds value expected 02: Length of delta-seconds value 01 00: delta seconds in hex Delta seconds is quite low, one day would be more normal. In addition, it would be better to use absolute time, in future, for testing purposes (absolute time token is 80). Aarno On Friday, September 13, 2002, at 10:06 AM, FERLA Alessandro Consultant wrote: > > The result of the conversion is Sun, 29 Dec 2582 21:56:16 UTC > > I think it is correct but maybe something else is wrong in my message. > > This is my last encode of the message and obviously is not working. > > 8c82 > 9831423500 > 8d90 > 8a80 > 8e0164 > 880481020100 > 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D617 > 2636F > 2F706965727761702E6D6D7300 > > I expect the telephone to start to browse and go to retrieve the > content. Is > it correct? > And the telephone seems to receive two messages but it doesn't do > anything. > > > And the pap file is always unchanged. > > Thank you again. > > Alessandro. > > -Messaggio originale- > Da: Paul Keogh [mailto:[EMAIL PROTECTED]] > Inviato: giovedì 12 settembre 2002 12.32 > A: [EMAIL PROTECTED] > Oggetto: RE: R: MMS Push Problem > > > >> I tryed with "date -r filename" but I just get back the date >> of creation of >> the file. I can't understand how the X-MMS-Expiry date is >> encoded. Is there >> any documentation about that? >> > > Look at 7.2.10 of WAP-209-MMSEncapsulation-20020105-a for Expiry field > encoding. > > Then look at WSP for long integer encoding. > > > > = > "STRICTLY PERSONAL AND CONFIDENTIAL > > This message may contain confidential and proprietary material for the > sole > use of the intended recipient. Any review or distribution by others is > strictly prohibited. If you are not the intended recipient please > contact > the sender and delete all copies. > The contents of this message that do not relate to the official > business of > our company shall be understood as neither given nor endorsed by it." > > = >
R: R: R: MMS Push Problem
Ok, thank you for your patience! I tryed again modifiyng the expiry date like in the example below. Now it should be correct. But nothing again. 8C82 9831323500 8D90 8A80 8E0164 8804800443B6044F 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D6172636F 2F706965727761702E6D6D7300 I get the usual two messages on the telephone but the telephone doesn't wake up. Thank you very much. Alessandro. -Messaggio originale- Da: Aarno Syvänen [mailto:[EMAIL PROTECTED]] Inviato: venerdì 13 settembre 2002 9.45 A: FERLA Alessandro Consultant Cc: [EMAIL PROTECTED]; 'Paul Keogh' Oggetto: Re: R: R: MMS Push Problem Your Expiry is 88 04 81 02 01 00 This means: 88: Expiry 04: Value-Length (of the header) 81: Expiry time relative, delta-seconds value expected 02: Length of delta-seconds value 01 00: delta seconds in hex Delta seconds is quite low, one day would be more normal. In addition, it would be better to use absolute time, in future, for testing purposes (absolute time token is 80). Aarno On Friday, September 13, 2002, at 10:06 AM, FERLA Alessandro Consultant wrote: > > The result of the conversion is Sun, 29 Dec 2582 21:56:16 UTC > > I think it is correct but maybe something else is wrong in my message. > > This is my last encode of the message and obviously is not working. > > 8c82 > 9831423500 > 8d90 > 8a80 > 8e0164 > 880481020100 > 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D617 > 2636F > 2F706965727761702E6D6D7300 > > I expect the telephone to start to browse and go to retrieve the > content. Is > it correct? > And the telephone seems to receive two messages but it doesn't do > anything. > > > And the pap file is always unchanged. > > Thank you again. > > Alessandro. > > -Messaggio originale- > Da: Paul Keogh [mailto:[EMAIL PROTECTED]] > Inviato: giovedì 12 settembre 2002 12.32 > A: [EMAIL PROTECTED] > Oggetto: RE: R: MMS Push Problem > > > >> I tryed with "date -r filename" but I just get back the date >> of creation of >> the file. I can't understand how the X-MMS-Expiry date is >> encoded. Is there >> any documentation about that? >> > > Look at 7.2.10 of WAP-209-MMSEncapsulation-20020105-a for Expiry field > encoding. > > Then look at WSP for long integer encoding. > > > > = > "STRICTLY PERSONAL AND CONFIDENTIAL > > This message may contain confidential and proprietary material for the > sole > use of the intended recipient. Any review or distribution by others is > strictly prohibited. If you are not the intended recipient please > contact > the sender and delete all copies. > The contents of this message that do not relate to the official > business of > our company shall be understood as neither given nor endorsed by it." > > = > = "STRICTLY PERSONAL AND CONFIDENTIAL This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies. The contents of this message that do not relate to the official business of our company shall be understood as neither given nor endorsed by it." =
R: R: R: R: MMS Push Problem
Thank you again for you patience. Now the file looks like that: 8C82 9831323500 8D90 8A80 8E0164 8806800443B6044F 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D6172636F 2F706965727761702E6D6D7300 And something changed: on the mobile Panasonic GD87 receive the two messages and the display light goes on and the display itself goes white. The telephone is locked and I have to switch it off. On the Nokia 7650 nothing changed so I receive the two messages but the telephone doesn't do anything. Where am I failing again? Thank you very much. Alessandro. -Messaggio originale- Da: Aarno Syvänen [mailto:[EMAIL PROTECTED]] Inviato: lunedì 16 settembre 2002 9.19 A: FERLA Alessandro Consultant Oggetto: Re: R: R: R: MMS Push Problem Now your Expiry header os 8804800443b6044f. It should start with 8806. Second byte is length of combined Expiry value. Aarno On Friday, September 13, 2002, at 12:30 PM, FERLA Alessandro Consultant wrote: > Ok, thank you for your patience! > > I tryed again modifiyng the expiry date like in the example below. Now > it > should be correct. But nothing again. > > 8C82 > 9831323500 > 8D90 > 8A80 > 8E0164 > 8804800443B6044F > 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D617 > 2636F > 2F706965727761702E6D6D7300 > > > I get the usual two messages on the telephone but the telephone > doesn't wake > up. > > Thank you very much. > > Alessandro. > > > > -Messaggio originale- > Da: Aarno Syvänen [mailto:[EMAIL PROTECTED]] > Inviato: venerdì 13 settembre 2002 9.45 > A: FERLA Alessandro Consultant > Cc: [EMAIL PROTECTED]; 'Paul Keogh' > Oggetto: Re: R: R: MMS Push Problem > > > Your Expiry is > > 88 04 81 02 01 00 > > This means: > 88: Expiry > 04: Value-Length (of the header) > 81: Expiry time relative, delta-seconds value expected > 02: Length of delta-seconds value > 01 00: delta seconds in hex > > Delta seconds is quite low, one day would be more normal. In addition, > it would be > better to use absolute time, in future, for testing purposes (absolute > time token is 80). > > Aarno > > On Friday, September 13, 2002, at 10:06 AM, FERLA Alessandro Consultant > wrote: > >> >> The result of the conversion is Sun, 29 Dec 2582 21:56:16 UTC >> >> I think it is correct but maybe something else is wrong in my message. >> >> This is my last encode of the message and obviously is not working. >> >> 8c82 >> 9831423500 >> 8d90 >> 8a80 >> 8e0164 >> 880481020100 >> 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D61 >> 7 >> 2636F >> 2F706965727761702E6D6D7300 >> >> I expect the telephone to start to browse and go to retrieve the >> content. Is >> it correct? >> And the telephone seems to receive two messages but it doesn't do >> anything. >> >> >> And the pap file is always unchanged. >> >> Thank you again. >> >> Alessandro. >> >> -Messaggio originale- >> Da: Paul Keogh [mailto:[EMAIL PROTECTED]] >> Inviato: giovedì 12 settembre 2002 12.32 >> A: [EMAIL PROTECTED] >> Oggetto: RE: R: MMS Push Problem >> >> >> >>> I tryed with "date -r filename" but I just get back the date >>> of creation of >>> the file. I can't understand how the X-MMS-Expiry date is >>> encoded. Is there >>> any documentation about that? >>> >> >> Look at 7.2.10 of WAP-209-MMSEncapsulation-20020105-a for Expiry field >> encoding. >> >> Then look at WSP for long integer encoding. >> >> >> >> = >> "STRICTLY PERSONAL AND CONFIDENTIAL >> >> This message may contain confidential and proprietary material for the >> sole >> use of the intended recipient. Any review or distribution by others is >> strictly prohibited. If you are not the intended recipient please >> contact >> the sender and delete all copies. >> The contents of this message that do not relate to the official >> business of >> our company shall be understood as neither given nor endorsed by it." >> >> = >> > > = > "STRICTLY PERSONAL AND CONFIDENTIAL > > This message may contain confidential and proprietary material for the > sole > use of the intended recipient. Any review or distribution by others is > strictly prohibited. If you are not the intended recipient please > contact > the sender and delete all copies. > The contents of this message that do not relate to the official > business of > our company shall be understood as neither given nor endorsed by it." > > = > = "STRICTLY PERSONAL AND CONFIDENTIAL This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies. The contents of this message that do not relate to the official business of our company shall be understood as neither given nor endorsed by it." =
RE: R: R: R: MMS Push Problem
Hello Alessandro Sorry for bothering you. I found this message on the kannel mailing list and I know its very old but I have one question. Do you solve the problem related to the GD87 and Nokia phone ? I have the same behaviour and some tips would be appreciated. Kind Regards Joerg > -Original Message- > From: [EMAIL PROTECTED] > [mailto:users-admin@;kannel.3glab.org] On Behalf Of FERLA > Alessandro Consultant > Sent: Wednesday, September 18, 2002 9:01 AM > To: 'Aarno Syvänen' > Cc: '[EMAIL PROTECTED]' > Subject: R: R: R: R: MMS Push Problem > > > Thank you again for you patience. Now the file looks like that: > > > 8C82 > 9831323500 > 8D90 > 8A80 > 8E0164 > 8806800443B6044F > 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265 > 732F6D6172636F > 2F706965727761702E6D6D7300 > > > And something changed: > > on the mobile Panasonic GD87 receive the two messages and the > display light goes on and the display itself goes white. The > telephone is locked and I have to switch it off. > > On the Nokia 7650 nothing changed so I receive the two > messages but the telephone doesn't do anything. > > Where am I failing again? > > Thank you very much. > > Alessandro. > > > -Messaggio originale----- > Da: Aarno Syvänen [mailto:aarno@;gni.ch] > Inviato: lunedì 16 settembre 2002 9.19 > A: FERLA Alessandro Consultant > Oggetto: Re: R: R: R: MMS Push Problem > > > Now your Expiry header os 8804800443b6044f. It should start > with 8806. > Second byte > is length of combined Expiry value. > > Aarno > > On Friday, September 13, 2002, at 12:30 PM, FERLA Alessandro > Consultant > wrote: > > > Ok, thank you for your patience! > > > > I tryed again modifiyng the expiry date like in the example > below. Now > > it > > should be correct. But nothing again. > > > > 8C82 > > 9831323500 > > 8D90 > > 8A80 > > 8E0164 > > 8804800443B6044F > > > 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D61 > > 7 > > 2636F > > 2F706965727761702E6D6D7300 > > > > > > I get the usual two messages on the telephone but the telephone > > doesn't wake > > up. > > > > Thank you very much. > > > > Alessandro. > > > > > > > > -Messaggio originale- > > Da: Aarno Syvänen [mailto:aarno@;gni.ch] > > Inviato: venerdì 13 settembre 2002 9.45 > > A: FERLA Alessandro Consultant > > Cc: [EMAIL PROTECTED]; 'Paul Keogh' > > Oggetto: Re: R: R: MMS Push Problem > > > > > > Your Expiry is > > > > 88 04 81 02 01 00 > > > > This means: > > 88: Expiry > > 04: Value-Length (of the header) > > 81: Expiry time relative, delta-seconds value expected > > 02: Length of delta-seconds value > > 01 00: delta seconds in hex > > > > Delta seconds is quite low, one day would be more normal. > In addition, > > it would be better to use absolute time, in future, for testing > > purposes (absolute time token is 80). > > > > Aarno > > > > On Friday, September 13, 2002, at 10:06 AM, FERLA Alessandro > > Consultant > > wrote: > > > >> > >> The result of the conversion is Sun, 29 Dec 2582 21:56:16 UTC > >> > >> I think it is correct but maybe something else is wrong in my > >> message. > >> > >> This is my last encode of the message and obviously is not working. > >> > >> 8c82 > >> 9831423500 > >> 8d90 > >> 8a80 > >> 8e0164 > >> 880481020100 > >> > 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D6 > >> 1 > >> 7 > >> 2636F > >> 2F706965727761702E6D6D7300 > >> > >> I expect the telephone to start to browse and go to retrieve the > >> content. Is it correct? > >> And the telephone seems to receive two messages but it doesn't do > >> anything. > >> > >> > >> And the pap file is always unchanged. > >> > >> Thank you again. > >> > >> Alessandro. > >> > >> -Messaggio originale- > >> Da: Paul Keogh [mailto:paul.keogh@;anam.com] > >> Inviato: giovedì 12 settembre 2002 12.32 > >> A: [EMAIL PROTECTED] > >> Oggetto: RE: R: MMS Push Problem > >> > >> > >> > >>> I tryed with "date -r filename" but I just get back the date of > >>
