Hi, I would like to differenciate sendsms requests for a unique sendsms user defined (there will be several users of a unique sendmsms account). I can't use &from variable or &text or &smsc which are used for another aim. Is there any other variable to do that ? Is someone interesting to add it ?
Thanks in advance for your help. Gildas. -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de James Ewing Envoyé : mercredi 19 décembre 2001 14:06 À : Pierre Chehwan; [EMAIL PROTECTED] Objet : Re: SMS PDU for OTA-WSP connectionless Wap Push Hi Pierre, I found that the Ericsson GPRS phones seem to require both. If I send SMS WAP Push with either of these (or with the app-id field set incorrectly) they are apparently ignored by the phones. It could have been brain lock on my part as well tho - give it a try and see. Best, James Ewing ----- Original Message ----- From: "Pierre Chehwan" <[EMAIL PROTECTED]> To: "'James Ewing'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, December 19, 2001 12:02 PM Subject: RE: SMS PDU for OTA-WSP connectionless Wap Push > Thanks James. > > Are'nt these optionnal Push headers ? and By default X-Wap-Application-Id is > the wml user agent ? > > Puting them is WSP headers did not change anything. > > I think I have a brain blocking, and my probleme is somewhere in the WSP > header coding, and the mandatory headers of connectionnless push. > > > Pierre > > > > -----Message d'origine----- > De : James Ewing [mailto:[EMAIL PROTECTED]] > Envoyé : mercredi 19 décembre 2001 08:49 > À : Pierre Chehwan; [EMAIL PROTECTED] > Objet : Re: SMS PDU for OTA-WSP connectionless Wap Push > > > You are missing two WSP header fields - "X-Wap-Application-Id" and > "Push-Flag". > > James Ewing > > > ------------------------------------------------------------- > This Message and any attachments are confidential and intended > solely for the addressees. And unauthorised use or dissemination > are prohibited. Emails are suceptible to alteration. Therefore > neither SWAPCOM nor any of its subsidiaries or affiliates shall > be liable for the message if altered, changed or falsified. > >