Bruno David Simões Rodrigues wrote:
> 
> As I don't yet have simple functions to parse xml, I've finished
> (almost) the xml post code.
> 
> There's some differences for latest
> http://www.ietf.org/internet-drafts/draft-koponen-sms-xml-03.txt
> IETF draft, like it just define a <statusrequest> and we have
> dlr-mask and dlr-url, so I've adjusted and set
> <statusrequest>
>         <dlr-mask>x</dlr-mask>
>         <dlr-url>http://....</dlr-url>
> </statusrequest>
> 
> and I've taked liberally the <from> and <to> (smsc directives) tags to
> have:
> kannel->appl: from = smsc-id, to=service-name
> appl->kannel: from = authentication, to=smsc-id
> 
> Please compile documentation with --enable-docs --enable-drafts or check
> at http://litux.org/~bruno/userguide.{html|rtf|pdf} and give me
> suggestions, critics, flames, anything.
> 
> I'll need this (or something alike) for the end of the week.....
> 
> On sendsms-user, it supports multiple destinations, altough I've yet not
> tested how many destinations we could have
> (BTW: do we have any string limit in octstr ? internally, multiple
> destinations is a string with numbers separated by space)

Ok, Bruno does the XML-Post routines and I do the XML-RPC routines,
which is not the same. The IETF draft you refer is ment for SMS
requests via XML only. XML-RPC is a general approach for remote
procedure calls via HTTP transport.

So we're going to have 2 URIs refering to the different XML processing
routines.

Stipe

[EMAIL PROTECTED]
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
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 - X-Mozilla-Status: 0009om - Tue Apr 30 13:02:48 2002
X-Mozilla-Status: 0801
X-Mozilla-Status2: 00000000
FCC: /d|/mozilla/Stipe Tolj/mail/Sent
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 30 Apr 2002 13:02:48 +0200
From: Stipe Tolj <[EMAIL PROTECTED]>
Organization: Wapme Systems AG
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0; html=0; 
linewidth=0
X-Mailer: Mozilla 4.78 [de] (Windows NT 5.0; U)
X-Accept-Language: de
MIME-Version: 1.0
To: Andrea Viscovich <[EMAIL PROTECTED]>
CC: Alex Judd <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: [FYI] Post-XML
References: <[EMAIL PROTECTED]> 
<012601c1f032$3f56f8e0$[EMAIL PROTECTED]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Andrea Viscovich wrote:
> 
> The other thing to do is dlr for at2 :-)

yep, that would be great. Is DLR processing supported by all GSM
modems we currently support, or to turn it the other way, is DLR
processing within GSM AT calls defined?

Stipe

[EMAIL PROTECTED]
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
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



Reply via email to