Aarno Syv�nen wrote: > > 2. Is it possible to use OMNA WSP Content Type Number "0x3E" for > > "application/vnd.wap.mms-message" instead of encoding the whole string > > ? > > No, if you want to speak with all phones. S55 demands the string (Token > is part of wsp v 1.4, and this phone supports only v 1.3). But you can > drop > From, which is optional.
yep, Aarno is right here. There is a MMS conformance statement between major phone and gateway vendors to use WAP 1.2.1 (Jun00) as base reference, which includes WSP 1.3 and *not* 1.4, hence the content-type has to be encoded in full string. > > 3. Does the 140 byte limit per binary sms include &udh part or just the > > &text part in case of using sendsms ? > > Both text and udh (including SAR UDH) yep, so you usually won't get an M-notification.ind with a URL handled in one SMS, usually it will be two. Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 D�sseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
