Its great if this patch does not require recompilation. I can consider applying it to fulfill my custom requirement. Please correct me on the follwing :
What I have got is that you suggesting I need to add following params in smsc group and set the system-type='generic' > mo-to > mo-text . . . > mo-dlr-mask e.g # SMSC HTTP group = smsc smsc = http system-type = generic send-url = http://host:port/sms mo-to = destination mo-text = MsgData Will it work for both MO and MT type messages ? where & how do I need to apply this patch ? Thanks a lot. -Azhar On 9/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Send users mailing list submissions to > users@kannel.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.kannel.org/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Re: how to override sendsms http attribute names ? > (Alejandro Guerrieri) > 2. system error 0x00000008 + huge message queue (Daniel Aronne) > 3. DLR-URL (Jins) > 4. Re: DLR-URL (preeteesh kakkar) > 5. is %b the message id? (Iain Dooley) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 3 Sep 2007 23:32:51 -0300 > From: "Alejandro Guerrieri" <[EMAIL PROTECTED]> > Subject: Re: how to override sendsms http attribute names ? > To: "users@kannel.org" <users@kannel.org> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > This allows to set the parameters for the MT url, but the MO > parameters remains the Kannel defaults and cannot be changed, so you > have to ask the other party to use your parameters. > > I'm developing a patch to overcome this, but it's still undocumented > (and of course it's not part of any public CVS tree). > > I'm transcribing my previous message regarding the patch, maybe it helps you. > > Regards, > > Alejandro. > > ++++++++++++++++++++++++++++++++++++++++++++++++ > > It adds the following (optional) parameters to the smsc group with > system-type='generic' > > 1. Parameters for the incoming (MO) HTTP request: > > mo-from > mo-to > mo-text > mo-udh > mo-account > mo-binfo > mo-dlr-url > mo-dlr-mid > mo-flash > mo-mclass > mo-mwi > mo-coding > mo-validity > mo-deferred > mo-dlr-mask > > This allows to set a specific parameter name for all those values. If > missing, the default is used, so no changes are needed if you're using > the defaults. > > 2. Parameters for the return strings: > > mo-ret-accepted > mo-ret-denied > mo-ret-unknown-dlr > mo-ret-missing-args > mo-ret-udh-mismatch > mo-ret-udh-long > mo-ret-auth-failed > mo-ret-dlr-accepted > mo-ret-dlr-denied > > This allows to set specific strings to be return instead of "Sent.", > "Not Accepted", etc. If missing, the default strings are used, so no > changes are needed on conf files unless you really want to modify the > strings. > > The patch also allows to ignore the username and password for the MO > request. Just don't set "smsc-username" and "smsc-password" and the > request won't ask for those parameters. > > To download the patch, please go to: > > http://www.magicom-bcn.net/kannel/full-mo-http-params.patch > > I know there are many scenarios where this is not enough to accomodate > third parties' requirementes, but I think that a lot of "custom http > smsc's" could be implemented using this patch, without the need of > modifying the source code and recompiling Kannel. > > In my particular case, all but one of the many HTTP connections we > have could be implemented with this (being the one missing one using > synchronous messaging, so it needs a lot of "glue" to make it work). > > Please let me know what you think. I'll make proper userguide patches > as well if this have any chances of going into the main tree. > ++++++++++++++++++++++++++++++++++++++++++++++++ > > On 9/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > For http smsc, you create your own send and receive urls. > > > > In the http smsc part of your configuration file, set your operator url in > > "send-url" i.e the url through which you will send messages to your > > operator. e.g > > send-url = http://youroperator:operator_port > > > > Also set your port where you will receive messages from your operator. > > > > See user guide > > > > Tunrayo > > ----- Original Message ----- > > From: "Waseem Azhar" <[EMAIL PROTECTED]> > > To: <users@kannel.org> > > Sent: Monday, September 03, 2007 11:53 AM > > Subject: how to override sendsms http attribute names ? > > > > > > > Hi All, > > > > > > Is it possible to override http send sms interface's attributes. For > > > example : following are the standard attributes for send sms > > > (username,password,to,text etc..) > > > > > > > > http://smsbox.host.name:13013/cgi-bin/sendsms?username=foo&password=bar&to=0 > > 123456&text=Hello+world > > > > > > I want to override those attribute name like [MsgData insted of text], > > > [destination insted of to etc..] . Is this possible in Kannel > > > configuration ? I am using http relay smsc & service provider is > > > requiring his own set of http request attributes. like .. > > > > > > > > http://smsbox.host.name:13013/cgi-bin/sendsms?username=foo&password=bar&dest > > ination=0123456&MsgData=Hello+world > > > > > > > > > Please help me regarding this. > > > > > > > > > Thanks in advance. > > > > > > -Azhar > > > > > > > > > > > > -- > Alejandro Guerrieri > Magicom > http://www.magicom-bcn.net/ > LinkedIn: http://www.linkedin.com/in/aguerrieri > > > > ------------------------------ > > Message: 2 > Date: Mon, 3 Sep 2007 23:51:06 -0400 > From: "Daniel Aronne" <[EMAIL PROTECTED]> > Subject: system error 0x00000008 + huge message queue > To: users@kannel.org > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi guys, > > I'm getting sent messages queued after quite a bunch of pdu's with > "system error" 0x00000008. I have to restart kannel to have back to > normal but I've been having to do this quite often. Any ideas why this > is happening? I got v1.4.1. > Here's the SMSC connection log: > > 2007-09-03 21:44:27 [3356] [6] DEBUG: SMPP[TIGOHN]: Sending PDU: > 2007-09-03 21:44:27 [3356] [6] DEBUG: SMPP PDU 0x818efe0 dump: > 2007-09-03 21:44:27 [3356] [6] DEBUG: type_name: submit_sm > 2007-09-03 21:44:27 [3356] [6] DEBUG: command_id: 4 = 0x00000004 > 2007-09-03 21:44:27 [3356] [6] DEBUG: command_status: 0 = 0x00000000 > 2007-09-03 21:44:27 [3356] [6] DEBUG: sequence_number: 106 = 0x0000006a > 2007-09-03 21:44:27 [3356] [6] DEBUG: service_type: NULL > 2007-09-03 21:44:27 [3356] [6] DEBUG: source_addr_ton: 2 = 0x00000002 > 2007-09-03 21:44:27 [3356] [6] DEBUG: source_addr_npi: 1 = 0x00000001 > 2007-09-03 21:44:27 [3356] [6] DEBUG: source_addr: "4141" > 2007-09-03 21:44:27 [3356] [6] DEBUG: dest_addr_ton: 2 = 0x00000002 > 2007-09-03 21:44:27 [3356] [6] DEBUG: dest_addr_npi: 1 = 0x00000001 > 2007-09-03 21:44:27 [3356] [6] DEBUG: destination_addr: "5024061221" > 2007-09-03 21:44:27 [3356] [6] DEBUG: esm_class: 3 = 0x00000003 > 2007-09-03 21:44:27 [3356] [6] DEBUG: protocol_id: 0 = 0x00000000 > 2007-09-03 21:44:27 [3356] [6] DEBUG: priority_flag: 0 = 0x00000000 > 2007-09-03 21:44:27 [3356] [6] DEBUG: schedule_delivery_time: NULL > 2007-09-03 21:44:27 [3356] [6] DEBUG: validity_period: NULL > 2007-09-03 21:44:27 [3356] [6] DEBUG: registered_delivery: 0 = 0x00000000 > 2007-09-03 21:44:27 [3356] [6] DEBUG: replace_if_present_flag: 0 = 0x00000000 > 2007-09-03 21:44:27 [3356] [6] DEBUG: data_coding: 0 = 0x00000000 > 2007-09-03 21:44:27 [3356] [6] DEBUG: sm_default_msg_id: 0 = 0x00000000 > 2007-09-03 21:44:27 [3356] [6] DEBUG: sm_length: 104 = 0x00000068 > 2007-09-03 21:44:27 [3356] [6] DEBUG: short_message: > 2007-09-03 21:44:27 [3356] [6] DEBUG: Octet string at 0x818e6d0: > 2007-09-03 21:44:27 [3356] [6] DEBUG: len: 104 > 2007-09-03 21:44:27 [3356] [6] DEBUG: size: 105 > 2007-09-03 21:44:27 [3356] [6] DEBUG: immutable: 0 > 2007-09-03 21:44:27 [3356] [6] DEBUG: data: 45 6c 20 6e 75 6d 65 > 72 6f 20 64 65 20 72 65 66 El numero de ref > 2007-09-03 21:44:27 [3356] [6] DEBUG: data: 65 72 65 6e 63 69 61 > 20 6e 6f 20 65 73 20 76 61 erencia no es va > 2007-09-03 21:44:27 [3356] [6] DEBUG: data: 6c 69 64 6f 2e 20 43 > 6f 6d 70 72 61 20 75 6e 61 lido. Compra una > 2007-09-03 21:44:27 [3356] [6] DEBUG: data: 20 52 45 43 41 52 47 > 41 20 54 49 47 4f 20 79 20 RECARGA TIGO y > 2007-09-03 21:44:27 [3356] [6] DEBUG: data: 65 6e 76 69 61 20 65 > 6c 20 6d 65 6e 73 61 6a 65 envia el mensaje > 2007-09-03 21:44:27 [3356] [6] DEBUG: data: 20 61 6c 20 38 38 36 > 37 20 70 61 72 61 20 70 61 al 8867 para pa > 2007-09-03 21:44:27 [3356] [6] DEBUG: data: 72 74 69 63 69 70 61 > 72 rticipar > 2007-09-03 21:44:27 [3356] [6] DEBUG: Octet string dump ends. > 2007-09-03 21:44:27 [3356] [6] DEBUG: SMPP PDU dump ends. > 2007-09-03 21:44:29 [3356] [6] WARNING: SMPP: PDU NULL terminated > string has no NULL. > 2007-09-03 21:44:29 [3356] [6] DEBUG: SMPP[TIGOHN]: Got PDU: > 2007-09-03 21:44:29 [3356] [6] DEBUG: SMPP PDU 0x818efe0 dump: > 2007-09-03 21:44:29 [3356] [6] DEBUG: type_name: submit_sm_resp > 2007-09-03 21:44:29 [3356] [6] DEBUG: command_id: 2147483652 = 0x80000004 > 2007-09-03 21:44:29 [3356] [6] DEBUG: command_status: 8 = 0x00000008 > 2007-09-03 21:44:29 [3356] [6] DEBUG: sequence_number: 106 = 0x0000006a > 2007-09-03 21:44:29 [3356] [6] DEBUG: message_id: NULL > 2007-09-03 21:44:29 [3356] [6] DEBUG: SMPP PDU dump ends. > 2007-09-03 21:44:29 [3356] [6] ERROR: SMPP[TIGOHN]: SMSC returned > error code 0x00000008 (System Error) in response to submit_sm. > > > Thanks!! > > -- > Daniel > > > > ------------------------------ > > Message: 3 > Date: Tue, 4 Sep 2007 13:44:06 +0530 > From: Jins <[EMAIL PROTECTED]> > Subject: DLR-URL > To: "users@kannel.org" <users@kannel.org> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > How can i specify the dlr-url. whats the format..should i write my own code > for it to update the DB?how can i know the message id.. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://www.kannel.org/pipermail/users/attachments/20070904/a841f07c/attachment-0001.html > > ------------------------------ > > Message: 4 > Date: Tue, 4 Sep 2007 14:09:46 +0530 > From: "preeteesh kakkar" <[EMAIL PROTECTED]> > Subject: Re: DLR-URL > To: Jins <[EMAIL PROTECTED]> > Cc: "users@kannel.org" <users@kannel.org> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > dlr-url should contain the URL to which Kannel should place a HTTP requests > once the delivery report is ready to be delivered back to your system. > > An example transaction would work as following. > > - > > 1. you send a message using dlr-mask=7 and dlr-url= > http://www.xyz.com/cgi/dlr.php?type=%d > - > > 2. Kannel forwards the message to the SMSC and keeps track of the > message > - > > 3. The SMSC can not reach the phone and thus returns a buffered > message > - > > 4. Kannel calls http://www.xyz.com/cgi/dlr.php?type=4 to indicate the > message being buffered > - > > 5. The phone is switched on and the SMS gets delivered from the SMSC. > The SMSC reports this to Kannel > - > > 6. Kannel calls http://www.xyz.com/cgi/dlr.php?type=1 to indicate the > final success > > The delivery report types currently implemented are: > > - > > 1: delivery success > - > > 2: delivery failure > - > > 4: message buffered > - > > 8: smsc submit > - > > 16: smsc reject > > Depending on the SMSC type not all type of messages are supported. For > example a CIMD SMSC does not support buffered messages. Also some SMSC > drivers have not implemented all DLR types. > > Yes the PHP file has to be coded by you to update the db. > > Please note all of this is taken from Kannel Guide. Read the Guide and you > can have most of your answers :) > > > > On 9/4/07, Jins <[EMAIL PROTECTED]> wrote: > > > > > > How can i specify the dlr-url. whats the format..should i write my own > > code for it to update the DB?how can i know the message id.. > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://www.kannel.org/pipermail/users/attachments/20070904/d50b9f97/attachment-0001.html > > ------------------------------ > > Message: 5 > Date: Tue, 4 Sep 2007 19:06:05 +1000 (EST) > From: Iain Dooley <[EMAIL PROTECTED]> > Subject: is %b the message id? > To: users@kannel.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > if i put %b as a parameter in my dlr-url, will that return the message-id > for me? in the user guide it says: > > %b the original SMS message, in a binary form > > cheers > > iain > > > > ------------------------------ > > _______________________________________________ > users mailing list > users@kannel.org > http://www.kannel.org/mailman/listinfo/users > > > End of users Digest, Vol 16, Issue 15 > ************************************* >
