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." =================================