Re: [PATCH] CIMD2 driver upgraded to smsconn api
> >and if yes, maybe we could add one more directive in the configuration > >file, like "use-dlr"? > > Concerning additional directives, I'm pretty much for it if they avoid real > life problems, to be able to use Kannel "our-of-the-box" (with the proper > config) without hacking with the code. And most of us like only more directives that can be addopted to more then one smsc module type ;) So you should always take care when thinking of adding more config directives. It will be easier as soon as we split of the config directive things by smsc specific configuration cfg.def etc. 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
RE: [PATCH] CIMD2 driver upgraded to smsconn api
>thanks for the answer. i want a little bit clarify things. i KNOW that my >SMSC has forbidden "status delivery report requests". so just thought >about "universal" patch for kannel's smsc_cimd2 driver. > >the question is "might defaults" be so or they might not? if no, then we >can comment out the line: > >packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0); > Ok, now I see. But I'm afraid there's no possibility from the outside to know the defaults/capabilities established in the smsc. >and if yes, maybe we could add one more directive in the configuration >file, like "use-dlr"? Concerning additional directives, I'm pretty much for it if they avoid real life problems, to be able to use Kannel "our-of-the-box" (with the proper config) without hacking with the code. Angel Fradejas Mediafusión España, S.A. [EMAIL PROTECTED] www.mediafusion.es Tel. +34 91 252 32 00 Fax +34 91 572 27 08
RE: [PATCH] CIMD2 driver upgraded to smsconn api
Angel,
thanks for the answer. i want a little bit clarify things. i KNOW that my
SMSC has forbidden "status delivery report requests". so just thought
about "universal" patch for kannel's smsc_cimd2 driver.
/* Explicitly ask not to get status reports.
* If we do not do this, the server's default might be to
* send status reports in some cases, and we don't do anything
* with those reports anyway. */
/* ask for the delivery reports if needed*/
the question is "might defaults" be so or they might not? if no, then we
can comment out the line:
packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0);
and if yes, maybe we could add one more directive in the configuration
file, like "use-dlr"?
it seems stupid, because why, according to CIMD2, "0" doesn't meen "NO"? :)
regards,
Dziugas Baltrunas
On Tue, 25 Mar 2003, Angel Fradejas wrote:
> Yep that's the same error the SMSC gives when, for example, I set parameter
> 064 Tariff class on some of my connections. It only says that the SMSC
> doesn't allow you to do it.
>
> I don't think there is a method to know if your smsc supports/allows
> delivery reports. You'll have to ask your provider.
>
> Even in the case that the SMSC accepts a message with
> P_STATUS_REPORT_REQUEST set, it does not guarantee you that SMSC will in
> fact pass your application the delivery report.
>
> Angel Fradejas
> Mediafusión Espa?a, S.A.
> [EMAIL PROTECTED]
> www.mediafusion.es
> Tel. +34 91 252 32 00
> Fax +34 91 572 27 08
>
>
> -Mensaje original-
> De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nombre de
> Dziugas Baltrunas
> Enviado el: martes 25 de marzo de 2003 16:53
> Para: Kannel Developers
> Asunto: RE: [PATCH] CIMD2 driver upgraded to smsconn api
>
>
> here is additional information what CIMD2 reports:
>
> 2003-03-25 17:50:47 [12] ERROR: CIMD2[mysmsc]: Submit message response
> contained error message:
> 2003-03-25 17:50:47 [12] ERROR: code 310: Incorrect status report request
> parameter usage
>
> regards,
> Dziugas Baltrunas
>
> On Tue, 25 Mar 2003, Dziugas Baltrunas wrote:
>
> > I would like to ask Angel, as CIMD2 guru, is there any way to check out
> > if CIMD2 SMSC supports status delivery report requests?
> >
> > currently the logic is simple:
> >
> > if (msg->sms.dlr_mask & 0x03)
> > {
> > packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 14);
> > }
> > else
> > packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0);
> >
> > the problem is that if CIMD2 doesn't support status report,
> > packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0) would
> > still cause a reject from SMSC not sending message at all. the only
> > solution I found was to send nothing about P_STATUS_REPORT_REQUEST (i.e.
> > commenting out the line).
> >
> > unfortunately I don't know if our provider has prohibited it using the
> > right issues (i.e. configuration file or something), so stating that my
> > operator's CIMD2 "doesn't support DLR" is not true. it's just forbidden :)
> >
> > regards,
> > Dziugas Baltrunas
> >
> > On Tue, 25 Mar 2003, Angel Fradejas wrote:
> >
> > > >I currently was writing a question to the mailing list about plans to
> > > >rewrite CIMD2 to smsconn :))
> > > >
> > > >great job, Angel.
> > > >
> > > >regards,
> > > >Dziugas Baltrunas
> > >
> > > not to worry anybody, but I'm currently debugging and optimizing
> some
> > > issues in the driver What I'd really like is to make it work the
> same
> > > way as SMPP in transceiver mode.
> > >
> > > Well, first I'll fix it, then think about new internal design.
> > >
> > > Angel Fradejas
> > > Mediafusión Espa?a, S.A.
> > > [EMAIL PROTECTED]
> > > www.mediafusion.es
> > > Tel. +34 91 252 32 00
> > > Fax +34 91 572 27 08
> > >
> > >
> > >
> > >
> >
>
RE: [PATCH] CIMD2 driver upgraded to smsconn api
Yep that's the same error the SMSC gives when, for example, I set parameter
064 Tariff class on some of my connections. It only says that the SMSC
doesn't allow you to do it.
I don't think there is a method to know if your smsc supports/allows
delivery reports. You'll have to ask your provider.
Even in the case that the SMSC accepts a message with
P_STATUS_REPORT_REQUEST set, it does not guarantee you that SMSC will in
fact pass your application the delivery report.
Angel Fradejas
Mediafusión España, S.A.
[EMAIL PROTECTED]
www.mediafusion.es
Tel. +34 91 252 32 00
Fax +34 91 572 27 08
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nombre de
Dziugas Baltrunas
Enviado el: martes 25 de marzo de 2003 16:53
Para: Kannel Developers
Asunto: RE: [PATCH] CIMD2 driver upgraded to smsconn api
here is additional information what CIMD2 reports:
2003-03-25 17:50:47 [12] ERROR: CIMD2[mysmsc]: Submit message response
contained error message:
2003-03-25 17:50:47 [12] ERROR: code 310: Incorrect status report request
parameter usage
regards,
Dziugas Baltrunas
On Tue, 25 Mar 2003, Dziugas Baltrunas wrote:
> I would like to ask Angel, as CIMD2 guru, is there any way to check out
> if CIMD2 SMSC supports status delivery report requests?
>
> currently the logic is simple:
>
> if (msg->sms.dlr_mask & 0x03)
> {
> packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 14);
> }
> else
> packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0);
>
> the problem is that if CIMD2 doesn't support status report,
> packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0) would
> still cause a reject from SMSC not sending message at all. the only
> solution I found was to send nothing about P_STATUS_REPORT_REQUEST (i.e.
> commenting out the line).
>
> unfortunately I don't know if our provider has prohibited it using the
> right issues (i.e. configuration file or something), so stating that my
> operator's CIMD2 "doesn't support DLR" is not true. it's just forbidden :)
>
> regards,
> Dziugas Baltrunas
>
> On Tue, 25 Mar 2003, Angel Fradejas wrote:
>
> > >I currently was writing a question to the mailing list about plans to
> > >rewrite CIMD2 to smsconn :))
> > >
> > >great job, Angel.
> > >
> > >regards,
> > >Dziugas Baltrunas
> >
> > not to worry anybody, but I'm currently debugging and optimizing
some
> > issues in the driver What I'd really like is to make it work the
same
> > way as SMPP in transceiver mode.
> >
> > Well, first I'll fix it, then think about new internal design.
> >
> > Angel Fradejas
> > Mediafusión Espa?a, S.A.
> > [EMAIL PROTECTED]
> > www.mediafusion.es
> > Tel. +34 91 252 32 00
> > Fax +34 91 572 27 08
> >
> >
> >
> >
>
RE: [PATCH] CIMD2 driver upgraded to smsconn api
here is additional information what CIMD2 reports:
2003-03-25 17:50:47 [12] ERROR: CIMD2[mysmsc]: Submit message response contained error
message:
2003-03-25 17:50:47 [12] ERROR: code 310: Incorrect status report request parameter
usage
regards,
Dziugas Baltrunas
On Tue, 25 Mar 2003, Dziugas Baltrunas wrote:
> I would like to ask Angel, as CIMD2 guru, is there any way to check out
> if CIMD2 SMSC supports status delivery report requests?
>
> currently the logic is simple:
>
> if (msg->sms.dlr_mask & 0x03)
> {
> packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 14);
> }
> else
> packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0);
>
> the problem is that if CIMD2 doesn't support status report,
> packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0) would
> still cause a reject from SMSC not sending message at all. the only
> solution I found was to send nothing about P_STATUS_REPORT_REQUEST (i.e.
> commenting out the line).
>
> unfortunately I don't know if our provider has prohibited it using the
> right issues (i.e. configuration file or something), so stating that my
> operator's CIMD2 "doesn't support DLR" is not true. it's just forbidden :)
>
> regards,
> Dziugas Baltrunas
>
> On Tue, 25 Mar 2003, Angel Fradejas wrote:
>
> > >I currently was writing a question to the mailing list about plans to
> > >rewrite CIMD2 to smsconn :))
> > >
> > >great job, Angel.
> > >
> > >regards,
> > >Dziugas Baltrunas
> >
> > not to worry anybody, but I'm currently debugging and optimizing some
> > issues in the driver What I'd really like is to make it work the same
> > way as SMPP in transceiver mode.
> >
> > Well, first I'll fix it, then think about new internal design.
> >
> > Angel Fradejas
> > Mediafusión Espa?a, S.A.
> > [EMAIL PROTECTED]
> > www.mediafusion.es
> > Tel. +34 91 252 32 00
> > Fax +34 91 572 27 08
> >
> >
> >
> >
>
RE: [PATCH] CIMD2 driver upgraded to smsconn api
I would like to ask Angel, as CIMD2 guru, is there any way to check out
if CIMD2 SMSC supports status delivery report requests?
currently the logic is simple:
if (msg->sms.dlr_mask & 0x03)
{
packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 14);
}
else
packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0);
the problem is that if CIMD2 doesn't support status report,
packet_add_int_parm(packet, P_STATUS_REPORT_REQUEST, 0) would
still cause a reject from SMSC not sending message at all. the only
solution I found was to send nothing about P_STATUS_REPORT_REQUEST (i.e.
commenting out the line).
unfortunately I don't know if our provider has prohibited it using the
right issues (i.e. configuration file or something), so stating that my
operator's CIMD2 "doesn't support DLR" is not true. it's just forbidden :)
regards,
Dziugas Baltrunas
On Tue, 25 Mar 2003, Angel Fradejas wrote:
> >I currently was writing a question to the mailing list about plans to
> >rewrite CIMD2 to smsconn :))
> >
> >great job, Angel.
> >
> >regards,
> >Dziugas Baltrunas
>
> not to worry anybody, but I'm currently debugging and optimizing some
> issues in the driver What I'd really like is to make it work the same
> way as SMPP in transceiver mode.
>
> Well, first I'll fix it, then think about new internal design.
>
> Angel Fradejas
> Mediafusión Espa?a, S.A.
> [EMAIL PROTECTED]
> www.mediafusion.es
> Tel. +34 91 252 32 00
> Fax +34 91 572 27 08
>
>
>
>
RE: [PATCH] CIMD2 driver upgraded to smsconn api
>I currently was writing a question to the mailing list about plans to >rewrite CIMD2 to smsconn :)) > >great job, Angel. > >regards, >Dziugas Baltrunas not to worry anybody, but I'm currently debugging and optimizing some issues in the driver What I'd really like is to make it work the same way as SMPP in transceiver mode. Well, first I'll fix it, then think about new internal design. Angel Fradejas Mediafusión España, S.A. [EMAIL PROTECTED] www.mediafusion.es Tel. +34 91 252 32 00 Fax +34 91 572 27 08
Re: [PATCH] CIMD2 driver upgraded to smsconn api
Dziugas Baltrunas schrieb: > > I currently was writing a question to the mailing list about plans to > rewrite CIMD2 to smsconn :)) now... that should go to recycle I guess ;) > great job, Angel. yep, he did ;) 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
Re: [PATCH] CIMD2 driver upgraded to smsconn api
I currently was writing a question to the mailing list about plans to rewrite CIMD2 to smsconn :)) great job, Angel. regards, Dziugas Baltrunas On Tue, 25 Mar 2003, Stipe Tolj wrote: > commited to cvs. Thanks a lot Angel! > > 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 >
Re: [PATCH] CIMD2 driver upgraded to smsconn api
commited to cvs. Thanks a lot Angel! 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
Re: [PATCH] CIMD2 driver upgraded to smsconn api
Angel Fradejas wrote: > > So, finally here it is. A first working version of the Nokia CIMD2 > driver upgraded to the more convenient api SMSCConn*. I took Kalle > Majorla's work on this issue as a starting point, then further > improved it. > > I have tested this with two providers, with every type of message I > could think of (binary, ems, class 0, concatenated and so on) and > works fine. patch applied cleanly. compiled and build cleanly. +1 for commiting this. Can you please provide us also a patch for the doc/userguide/userguide.xml for the CIMD section?! 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
