Re: [FYI] Post-XML
I have to say Bruno the new documentation is great - the XML POST, AT2
section, OTA and PUSH are subjects that need to be covered. Good stuff.
For everyone's interest I currently have two development changes in test
that I'll submit once I've fully tested them.
1. Addition of CMTI: reading of SIM stored messages from AT devices in
AT2. Needed to add support for the Motorola P7389i. Had to modify the
at2_pdu_extract to cope with the two.
2. SMPP validity, deferred and couple of other tidy ups.
Alex
On 30 Apr 2002, 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 and we have
> dlr-mask and dlr-url, so I've adjusted and set
>
> x
> http://
>
>
> and I've taked liberally the and (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)
>
>
--
Alex Judd
http://www.skywire.co.uk
Re: [FYI] Post-XML
>1. Addition of CMTI: reading of SIM stored messages from AT devices in >AT2. Needed to add support for the Motorola P7389i. Had to modify the >at2_pdu_extract to cope with the two. Hi Alex, This has really to be done. I already did it for myself, but didn't send any patch as Oded said there could be no +CMTI: if ta-te link is reserved. The other thing to do is dlr for at2 :-) Cheers Andrea
Re: [FYI] Post-XML
Works fine for me here and is definitely needed for phones that don't
support CMT:. The main bit of code (for those interested is below). Works
out which slot to read, requests the message, decodes it, then deletes it.
if (-1 != octstr_search(line, octstr_imm("+CMTI:"), 0))
{
buf = gw_malloc(5);
buf2 = gw_malloc(20);
octstr_get_many_chars(buf, line, octstr_len(line) - 3, 3); /* work out which
message to read */
buf[3] = '\0';
sprintf(buf2, "%s%s", "AT+CMGR=", buf);
at2_write_line(privdata, buf2);/* display message
contents */
line = at2_wait_line(privdata,1,0);/* read header */
line2 = at2_wait_line(privdata,1,0); /* read PDU */
if(line2 == NULL)
{
error(0,"AT2[%s]: got +CMTI but waiting for next line timed out",
octstr_get_cstr(privdata->name));
}
else
{
octstr_append_cstr(line,"\n");
octstr_append(line,line2);
at2_pdu_extract(privdata, &pdu, line);
if(pdu == NULL)
{
error(0,"AT2[%s]: got +CMTI but pdu_extract failed",
octstr_get_cstr(privdata->name));
}
else
{
msg = at2_pdu_decode(pdu, privdata);
if(msg != NULL)
{
msg->sms.smsc_id = octstr_duplicate(privdata->conn->id);
bb_smscconn_receive(privdata->conn, msg);
}
sprintf(buf2, "%s%s", "AT+CMGD=", buf); /* delete SMS */
at2_write_line(privdata, buf2);
line = at2_wait_line(privdata,1,0); /* read response */
}
}
}
Alex
On Tue, 30 Apr 2002, Andrea Viscovich wrote:
>
> >1. Addition of CMTI: reading of SIM stored messages from AT devices in
> >AT2. Needed to add support for the Motorola P7389i. Had to modify the
> >at2_pdu_extract to cope with the two.
>
> Hi Alex,
> This has really to be done. I already did it for myself,
> but didn't send any patch as Oded said there could be no +CMTI: if
> ta-te link is reserved.
> The other thing to do is dlr for at2 :-)
> Cheers
> Andrea
>
>
--
Alex Judd
http://www.skywire.co.uk
Re: [FYI] Post-XML
it's ok for me.
+1 to add this patch.
Andrea
- Original Message -
From: "Alex Judd" <[EMAIL PROTECTED]>
To: "Andrea Viscovich" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, April 30, 2002 12:54 PM
Subject: Re: [FYI] Post-XML
> Works fine for me here and is definitely needed for phones that don't
> support CMT:. The main bit of code (for those interested is below). Works
> out which slot to read, requests the message, decodes it, then deletes it.
>
>if (-1 != octstr_search(line, octstr_imm("+CMTI:"), 0))
>{
> buf = gw_malloc(5);
> buf2 = gw_malloc(20);
>
> octstr_get_many_chars(buf, line, octstr_len(line) - 3, 3); /* work
out which message to read */
> buf[3] = '\0';
> sprintf(buf2, "%s%s", "AT+CMGR=", buf);
> at2_write_line(privdata, buf2);/*
display message contents */
> line = at2_wait_line(privdata,1,0);/* read
header */
> line2 = at2_wait_line(privdata,1,0); /* read
PDU */
>
> if(line2 == NULL)
> {
> error(0,"AT2[%s]: got +CMTI but waiting for next line timed
out", octstr_get_cstr(privdata->name));
> }
> else
> {
> octstr_append_cstr(line,"\n");
> octstr_append(line,line2);
> at2_pdu_extract(privdata, &pdu, line);
>
> if(pdu == NULL)
> {
> error(0,"AT2[%s]: got +CMTI but pdu_extract failed",
octstr_get_cstr(privdata->name));
> }
> else
> {
> msg = at2_pdu_decode(pdu, privdata);
> if(msg != NULL)
> {
>msg->sms.smsc_id =
octstr_duplicate(privdata->conn->id);
>bb_smscconn_receive(privdata->conn, msg);
> }
> sprintf(buf2, "%s%s", "AT+CMGD=", buf); /*
delete SMS */
> at2_write_line(privdata, buf2);
> line = at2_wait_line(privdata,1,0); /*
read response */
> }
>}
>}
>
> Alex
>
> On Tue, 30 Apr 2002, Andrea Viscovich wrote:
>
> >
> > >1. Addition of CMTI: reading of SIM stored messages from AT devices in
> > >AT2. Needed to add support for the Motorola P7389i. Had to modify the
> > >at2_pdu_extract to cope with the two.
> >
> > Hi Alex,
> > This has really to be done. I already did it for myself,
> > but didn't send any patch as Oded said there could be no +CMTI: if
> > ta-te link is reserved.
> > The other thing to do is dlr for at2 :-)
> > Cheers
> > Andrea
> >
> >
>
> --
> Alex Judd
> http://www.skywire.co.uk
>
Re: [FYI] Post-XML
Apoligies - that's not the final patch :) I'll do a cvs diff -u later this week once I'm happy with it's stability and then we can get the group vote on it then. There are other files and functions that have slight modifications too. Alex -- Alex Judd http://www.skywire.co.uk
RE: [FYI] Post-XML
> -Original Message- > From: Andrea Viscovich [mailto:[EMAIL PROTECTED]] > > it's ok for me. > +1 to add this patch. > Andrea > - Original Message - > From: "Alex Judd" <[EMAIL PROTECTED]> > > > Works fine for me here and is definitely needed for phones > that don't > > support CMT:. The main bit of code (for those interested is > below). Works > > out which slot to read, requests the message, decodes it, > then deletes it. +1 from me too. > Hi Alex, > This has really to be done. I already did it for myself, > but didn't send any patch as Oded said there could be no +CMTI: if > ta-te link is reserved. > The other thing to do is dlr for at2 :-) > Cheers > Andrea > I have perliminary DLR support for AT2, meaning SMSC_SUCCESS and SMSC_BUFFERED support. expanding that to all types is pretty high on my list and assuming no hard tackles, it should be ready towards the end of the week or at most next week. want to see what I have now ? -- Oded Arbel m-Wise Inc. [EMAIL PROTECTED] (972)-67-340014 (972)-9-9581711 (ext: 116) ::.. Timing has an awful lot to do with the outcome of a raindance.
Re: [FYI] Post-XML
On Tue, 2002-04-30 at 11:04, Alex Judd wrote: > I have to say Bruno the new documentation is great - the XML POST, AT2 > section, OTA and PUSH are subjects that need to be covered. Good stuff. I guess snapshots aren't beeing built again. (Last build: Apr 26) Does the script stop with warnings ? The snapshot documentation: http://kannel.org/download/kannel-userguide-snapshot/userguide.html should contain everything that my documents have, except post-xml. To enable post-xml documentation build, download latest cvs and ./configure --enable-docs --enable-drafts (...)
Re: [FYI] Post-XML
Bruno David Simões Rodrigues wrote: > I guess snapshots aren't beeing built again. (Last build: Apr 26) > Does the script stop with warnings ? Yeah, simply a missing in userguide.xml. It got broken in 1.166. I just checked in a fix and ran the snapshot script. I've changed the daily "nag on failed build" script to also check that the documentation can be successfully built. Then you can all see when it goes wrong! Dave -- David Holland =*= Systems Manager =*= tel: +44 01223 478900 http://www.3glab.com/ =*=3G Lab, UK =*= fax: +44 01223 478901
Re: [FYI] Post-XML
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
Re: [FYI] Post-XML
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 and we have
> dlr-mask and dlr-url, so I've adjusted and set
>
> x
> http://
>
>
> and I've taked liberally the and (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:
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
