Re: meta-data TLV for USSD
Hello, Yes Michael using data SM is more appropriate, but as far as I know many commercial SMPP gateways are also trying to adapt submit and deliver SM by using TLV to communicate with USSD. So I dont guess Kannel is inferior to these other products. I have partially succeded to connect to USSD, sending MO requests, but then I`m stuck, sessions remains open until it is droped by Core Network. Anyway if you have any conf sample would be a lot of help. Thanks Elton On Thu, Dec 3, 2009 at 12:46 AM, Michael Bochkaryov mi...@rattler.kiev.uawrote: Hello, I've tried to connect Kannel with USSD server. In my case it was enough to use ussd_service_op TLV (see SMPP 3.4 spec. p.5.3.2.44). Anyway Kannel is not good solution to implement USSD services because of: a) mostly USSD centers require data_sm instead of submit_sm/deliver_sm PDUs; b) Kannel includes some SMS-related logic (mostly exceptions processing) that doesn't suite for USSD I'll try to find configuration if nobody removed this yet. But I've personally switched to own small Net::SMPP based application. -- Regards, Michael Bochkaryov www.rattler.kiev.ua 2009/12/2 Elton Hoxha elt...@gmail.com Thanks Alex, Does anyone else has experience with USSD applications? Regards Elton On Wed, Dec 2, 2009 at 11:55 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: Elton, I don't have much experience with USSD honestly, I don't know how is the session started/ended. Kannel's not really designed to work as an USSD gateway, so I'm not sure if you're stumbling with something needing a patch or not. Regarding tags, SMPP Spec 3.4 has a list of the standard values. However, there's a user defined segment (starting 0x1400) where vendors can implement their proprietary tags. There's a copy of the spec here: http://www.nowsms.com/discus/messages/1/SMPP_v3_4_Issue1_2-24857.pdf Hope it helps, Alex On Wed, Dec 2, 2009 at 11:45 AM, Elton Hoxha elt...@gmail.com wrote: Thanks Alex, Actually, for MT cases, Im calling the HTTP using the example in the guide; meta-data=%3Fsmpp%3Fmy-data%3DHello%2BWorld but I receive some SMSC returned errors like invalid destinations, which of course has not to do with kannel. I have two ambigous cases in my head; -How can I terminate the session initialized by MO request? When I throw a request, lets say by dialing *200#, I`m able to call my application sending there %D values, but it lasts many seconds until HLR terminates it by itself. Also If multiple requests in paralel are initialised, how Kannel can keep records of each session, so when I will reply back from cgi-bin, kannel will understand the respective session and drop it? - How can I find the related specifications for Tag parameter? I see many combinations in hexadecimal but withput understanding their meaning. Is there any explanations for each hexa code? Thank You, Elton On Wed, Dec 2, 2009 at 11:23 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: You need to pass the value on the meta-data field. For example: meta-data=?smpp?my-custom-var=1 (urlencoded of course) Regards, Alex On Wed, Dec 2, 2009 at 9:01 AM, Elton Hoxha elt...@gmail.com wrote: Hi guys, I`m trying to use kannel for sending ussd request and receiving back using SMPP. my conf for TLV is: group = smpp-tlv name = my-custom-var tag = 0x0501 type = integer length = 2 smsc-id = test Using this I`m able to call my application by dialing ussd shortcodes, but I`m not able to terminate the session immediately. Also the values of ussd parameters take place under the VALUE parameter of TLV itself which is not present in the above conf. How can I manipulate this parameter if its not configurable in kannel? P.S this is an example I found googling around; Field Size Octets Type Description Parameter Tag 2 Integer 0x0501 Length 2 Integer Length of value part in octets Value 1 Integer This value can be one of the following values: 0 = PSSD Indication 1 = PSSR Indication 2 = USSR Request 3 = USSN Request 4 to 15 = Reserved 16 = PSSD Response 17 = PSSR Response 18 = USSR Confirm 19 = USSN Confirm 20 to 31 = Reserved 32 to 255 = Vendor specific operations
Re: Kannel timeouts / connectivity issues
Hi Nikos, the issue is that when you set timeout in configuration it's valid for _all_ http client connections. If you think it this config option would be useful, please provide patch for this because I'm too busy now :) I would suggest to set it in group = core for bearerbox and group = smsbox for smsbox. Thanks, Alexander Malysh Am 03.12.2009 um 05:22 schrieb Nikos Balkanas: Hi, According to Changelog, Alexander M. on 6/8/2006 added a function in gwlib/http.c: void http_set_client_timeout(long timeout) which sets the timeout for the http outgoing connections. Unfortunately it is ghost and not used anywhere in the code or configuration. As a result the http_client_timeout is hardwired into the code: static int http_client_timeout = 240; It's a rather trivial matter to add it in the configuration, but I think that Alex, the original contributor, should do it. If he cannot I could. What do you say Alex? Of course 15' timeout seems an overexaggeration. The OS kernel should drop the connection before that. BR, Nikos - Original Message - From: David Ritchie To: users@kannel.org Sent: Thursday, December 03, 2009 12:06 AM Subject: Kannel timeouts / connectivity issues Anybody know what Kannel’s expected behavior when HTTP connections timeout or fail? We have a situation with 120+ “sms-service” services defined, but have noticed a few of them behave in a peculiar manner where, very occasionally, HTTP requests don’t occur until 16 minutes after being received by Kannel. This will happen “out of the blue” without any errors logged in smsbox.log or kannel.log. This occurs in a transient fashion – there doesn’t appear to be any rhyme or reason to when this occurs. This only appears to happen with a particular subset of SMS services which happen to be hosted outside of our immediate hosting environment, suggesting there’s some sort of network disruption causing this problem. Potentially this is some of retry based on a 1-minute timeout, followed by a retry 15 minutes later; however this would be “out of character” since in my experience with Kannel most timeouts / 404s / 500s usually generate everyone’s favourite “Couldn’t fetch content, sorry”-type messages. I also can’t find any reference to timeouts of these values in the user’s guide or the configuration files. Until recently the get-urls for these services had the SMSC included in the URLs (i.e. “smsc=%i”) but, as these were the only services using this, I’ve removed this in case there’s some sort of problem caused by this. Has anybody else had a similar situation where these sorts of delays have happened? David
Re: Kannel timeouts / connectivity issues
Hi Alex, Right now all client connections have a set limit of 240 hardwired in code. It is easy to make this configurable globally, and I think it would be an improvement over the hardcoded one. Now, from your sayings, this should be done /box (let's not forget wapbox) and this is more of a hussle. Smsbox wapbox can use the same setting, and i don't know of any bb http client connections. Do you? Besides I don't have time right now for /box timeout support. But the global one is trivial to do and can do it. Is this OK? I don't need it, but it seems that David does. BR, Nikos - Original Message - From: Alexander Malysh To: Nikos Balkanas Cc: users@kannel.org Sent: Thursday, December 03, 2009 11:35 AM Subject: Re: Kannel timeouts / connectivity issues Hi Nikos, the issue is that when you set timeout in configuration it's valid for _all_ http client connections. If you think it this config option would be useful, please provide patch for this because I'm too busy now :) I would suggest to set it in group = core for bearerbox and group = smsbox for smsbox. Thanks, Alexander Malysh Am 03.12.2009 um 05:22 schrieb Nikos Balkanas: Hi, According to Changelog, Alexander M. on 6/8/2006 added a function in gwlib/http.c: void http_set_client_timeout(long timeout) which sets the timeout for the http outgoing connections. Unfortunately it is ghost and not used anywhere in the code or configuration. As a result the http_client_timeout is hardwired into the code: static int http_client_timeout = 240; It's a rather trivial matter to add it in the configuration, but I think that Alex, the original contributor, should do it. If he cannot I could. What do you say Alex? Of course 15' timeout seems an overexaggeration. The OS kernel should drop the connection before that. BR, Nikos - Original Message - From: David Ritchie To: users@kannel.org Sent: Thursday, December 03, 2009 12:06 AM Subject: Kannel timeouts / connectivity issues Anybody know what Kannel’s expected behavior when HTTP connections timeout or fail? We have a situation with 120+ “sms-service” services defined, but have noticed a few of them behave in a peculiar manner where, very occasionally, HTTP requests don’t occur until 16 minutes after being received by Kannel. This will happen “out of the blue” without any errors logged in smsbox.log or kannel.log. This occurs in a transient fashion – there doesn’t appear to be any rhyme or reason to when this occurs. This only appears to happen with a particular subset of SMS services which happen to be hosted outside of our immediate hosting environment, suggesting there’s some sort of network disruption causing this problem. Potentially this is some of retry based on a 1-minute timeout, followed by a retry 15 minutes later; however this would be “out of character” since in my experience with Kannel most timeouts / 404s / 500s usually generate everyone’s favourite “Couldn’t fetch content, sorry”-type messages. I also can’t find any reference to timeouts of these values in the user’s guide or the configuration files. Until recently the get-urls for these services had the SMSC included in the URLs (i.e. “smsc=%i”) but, as these were the only services using this, I’ve removed this in case there’s some sort of problem caused by this. Has anybody else had a similar situation where these sorts of delays have happened? David
Re: Kannel timeouts / connectivity issues
http smsc's works from bearerbox I think 2009/12/3 Nikos Balkanas n...@amdtelecom.net Hi Alex, Right now all client connections have a set limit of 240 hardwired in code. It is easy to make this configurable globally, and I think it would be an improvement over the hardcoded one. Now, from your sayings, this should be done /box (let's not forget wapbox) and this is more of a hussle. Smsbox wapbox can use the same setting, and i don't know of any bb http client connections. Do you? Besides I don't have time right now for /box timeout support. But the global one is trivial to do and can do it. Is this OK? I don't need it, but it seems that David does. BR, Nikos - Original Message - *From:* Alexander Malysh amal...@kannel.org *To:* Nikos Balkanas nbalka...@gmail.com *Cc:* users@kannel.org *Sent:* Thursday, December 03, 2009 11:35 AM *Subject:* Re: Kannel timeouts / connectivity issues Hi Nikos, the issue is that when you set timeout in configuration it's valid for _all_ http client connections. If you think it this config option would be useful, please provide patch for this because I'm too busy now :) I would suggest to set it in group = core for bearerbox and group = smsbox for smsbox. Thanks, Alexander Malysh Am 03.12.2009 um 05:22 schrieb Nikos Balkanas: Hi, According to Changelog, Alexander M. on 6/8/2006 added a function in gwlib/http.c: void http_set_client_timeout(long timeout) which sets the timeout for the http outgoing connections. Unfortunately it is ghost and not used anywhere in the code or configuration. As a result the http_client_timeout is hardwired into the code: static int http_client_timeout = 240; It's a rather trivial matter to add it in the configuration, but I think that Alex, the original contributor, should do it. If he cannot I could. What do you say Alex? Of course 15' timeout seems an overexaggeration. The OS kernel should drop the connection before that. BR, Nikos - Original Message - *From:* David Ritchie david.ritc...@runthered.com *To:* users@kannel.org *Sent:* Thursday, December 03, 2009 12:06 AM *Subject:* Kannel timeouts / connectivity issues Anybody know what Kannel’s expected behavior when HTTP connections timeout or fail? We have a situation with 120+ “sms-service” services defined, but have noticed a few of them behave in a peculiar manner where, very occasionally, HTTP requests don’t occur until 16 minutes after being received by Kannel. This will happen “out of the blue” without any errors logged in smsbox.log or kannel.log. This occurs in a transient fashion – there doesn’t appear to be any rhyme or reason to when this occurs. This only appears to happen with a particular subset of SMS services which happen to be hosted outside of our immediate hosting environment, suggesting there’s some sort of network disruption causing this problem. Potentially this is some of retry based on a 1-minute timeout, followed by a retry 15 minutes later; however this would be “out of character” since in my experience with Kannel most timeouts / 404s / 500s usually generate everyone’s favourite “Couldn’t fetch content, sorry”-type messages. I also can’t find any reference to timeouts of these values in the user’s guide or the configuration files. Until recently the get-urls for these services had the SMSC included in the URLs (i.e. “smsc=%i”) but, as these were the only services using this, I’ve removed this in case there’s some sort of problem caused by this. Has anybody else had a similar situation where these sorts of delays have happened? David
Re: meta-data TLV for USSD
2009/12/3 Elton Hoxha elt...@gmail.com Hello, ... I have partially succeded to connect to USSD, sending MO requests, but then I`m stuck, sessions remains open until it is droped by Core Network. Anyway if you have any conf sample would be a lot of help. Hey all, we are using kannel as gateway for USSD services with success. Generally if you want to use just USSD strings conf may look like this: group = smsc smsc-id = MVNO-USSD-STRING smsc = smpp host = 10.10.10.10 port = 5014 smsc-username = foo smsc-password = bar system-type = VMA service-type = EA log-file= /var/log/kannel-ussd/ussd_strings.log log-level = 0 wait-ack-expire = 1 If you need menu based services just change: service-type = CR It works pretty with Hu*wei USSDC. Soon I'll be ready to release HTTP backend which can be used in sms-service (nifty GUI, menus, games, polls, etc.). If you are interested in such solution just let me know - i'll try to speed things up ;-) Regards, -- Marcin Boćkowski tel. +48 79 69 0 69 79
Re: Kannel timeouts / connectivity issues
You are absolutely right. In fact it is easier than i thought. I will get right to it. And let's make default timeout to something easier on the eye, ie 60. BR, Nikos - Original Message - From: Alejandro Guerrieri To: Nikos Balkanas Cc: Alexander Malysh ; users@kannel.org Sent: Thursday, December 03, 2009 1:24 PM Subject: Re: Kannel timeouts / connectivity issues http smsc's works from bearerbox I think 2009/12/3 Nikos Balkanas n...@amdtelecom.net Hi Alex, Right now all client connections have a set limit of 240 hardwired in code. It is easy to make this configurable globally, and I think it would be an improvement over the hardcoded one. Now, from your sayings, this should be done /box (let's not forget wapbox) and this is more of a hussle. Smsbox wapbox can use the same setting, and i don't know of any bb http client connections. Do you? Besides I don't have time right now for /box timeout support. But the global one is trivial to do and can do it. Is this OK? I don't need it, but it seems that David does. BR, Nikos - Original Message - From: Alexander Malysh To: Nikos Balkanas Cc: users@kannel.org Sent: Thursday, December 03, 2009 11:35 AM Subject: Re: Kannel timeouts / connectivity issues Hi Nikos, the issue is that when you set timeout in configuration it's valid for _all_ http client connections. If you think it this config option would be useful, please provide patch for this because I'm too busy now :) I would suggest to set it in group = core for bearerbox and group = smsbox for smsbox. Thanks, Alexander Malysh Am 03.12.2009 um 05:22 schrieb Nikos Balkanas: Hi, According to Changelog, Alexander M. on 6/8/2006 added a function in gwlib/http.c: void http_set_client_timeout(long timeout) which sets the timeout for the http outgoing connections. Unfortunately it is ghost and not used anywhere in the code or configuration. As a result the http_client_timeout is hardwired into the code: static int http_client_timeout = 240; It's a rather trivial matter to add it in the configuration, but I think that Alex, the original contributor, should do it. If he cannot I could. What do you say Alex? Of course 15' timeout seems an overexaggeration. The OS kernel should drop the connection before that. BR, Nikos - Original Message - From: David Ritchie To: users@kannel.org Sent: Thursday, December 03, 2009 12:06 AM Subject: Kannel timeouts / connectivity issues Anybody know what Kannel’s expected behavior when HTTP connections timeout or fail? We have a situation with 120+ “sms-service” services defined, but have noticed a few of them behave in a peculiar manner where, very occasionally, HTTP requests don’t occur until 16 minutes after being received by Kannel. This will happen “out of the blue” without any errors logged in smsbox.log or kannel.log. This occurs in a transient fashion – there doesn’t appear to be any rhyme or reason to when this occurs. This only appears to happen with a particular subset of SMS services which happen to be hosted outside of our immediate hosting environment, suggesting there’s some sort of network disruption causing this problem. Potentially this is some of retry based on a 1-minute timeout, followed by a retry 15 minutes later; however this would be “out of character” since in my experience with Kannel most timeouts / 404s / 500s usually generate everyone’s favourite “Couldn’t fetch content, sorry”-type messages. I also can’t find any reference to timeouts of these values in the user’s guide or the configuration files. Until recently the get-urls for these services had the SMSC included in the URLs (i.e. “smsc=%i”) but, as these were the only services using this, I’ve removed this in case there’s some sort of problem caused by this. Has anybody else had a similar situation where these sorts of delays have happened? David
Re: meta-data TLV for USSD
Hello Marcin, I am intrested 2009/12/3 Marcin Bockowski boc...@gmail.com 2009/12/3 Elton Hoxha elt...@gmail.com Hello, ... I have partially succeded to connect to USSD, sending MO requests, but then I`m stuck, sessions remains open until it is droped by Core Network. Anyway if you have any conf sample would be a lot of help. Hey all, we are using kannel as gateway for USSD services with success. Generally if you want to use just USSD strings conf may look like this: group = smsc smsc-id = MVNO-USSD-STRING smsc = smpp host = 10.10.10.10 port = 5014 smsc-username = foo smsc-password = bar system-type = VMA service-type = EA log-file= /var/log/kannel-ussd/ussd_strings.log log-level = 0 wait-ack-expire = 1 If you need menu based services just change: service-type = CR It works pretty with Hu*wei USSDC. Soon I'll be ready to release HTTP backend which can be used in sms-service (nifty GUI, menus, games, polls, etc.). If you are interested in such solution just let me know - i'll try to speed things up ;-) Regards, -- Marcin Boćkowski tel. +48 79 69 0 69 79
Re: Kannel timeouts / connectivity issues
I don't know what you mean by configurable globally? each box has it's own global config... Thanks, Alexander Malysh Am 03.12.2009 um 12:47 schrieb Nikos Balkanas: You are absolutely right. In fact it is easier than i thought. I will get right to it. And let's make default timeout to something easier on the eye, ie 60. BR, Nikos - Original Message - From: Alejandro Guerrieri To: Nikos Balkanas Cc: Alexander Malysh ; users@kannel.org Sent: Thursday, December 03, 2009 1:24 PM Subject: Re: Kannel timeouts / connectivity issues http smsc's works from bearerbox I think 2009/12/3 Nikos Balkanas n...@amdtelecom.net Hi Alex, Right now all client connections have a set limit of 240 hardwired in code. It is easy to make this configurable globally, and I think it would be an improvement over the hardcoded one. Now, from your sayings, this should be done /box (let's not forget wapbox) and this is more of a hussle. Smsbox wapbox can use the same setting, and i don't know of any bb http client connections. Do you? Besides I don't have time right now for /box timeout support. But the global one is trivial to do and can do it. Is this OK? I don't need it, but it seems that David does. BR, Nikos - Original Message - From: Alexander Malysh To: Nikos Balkanas Cc: users@kannel.org Sent: Thursday, December 03, 2009 11:35 AM Subject: Re: Kannel timeouts / connectivity issues Hi Nikos, the issue is that when you set timeout in configuration it's valid for _all_ http client connections. If you think it this config option would be useful, please provide patch for this because I'm too busy now :) I would suggest to set it in group = core for bearerbox and group = smsbox for smsbox. Thanks, Alexander Malysh Am 03.12.2009 um 05:22 schrieb Nikos Balkanas: Hi, According to Changelog, Alexander M. on 6/8/2006 added a function in gwlib/http.c: void http_set_client_timeout(long timeout) which sets the timeout for the http outgoing connections. Unfortunately it is ghost and not used anywhere in the code or configuration. As a result the http_client_timeout is hardwired into the code: static int http_client_timeout = 240; It's a rather trivial matter to add it in the configuration, but I think that Alex, the original contributor, should do it. If he cannot I could. What do you say Alex? Of course 15' timeout seems an overexaggeration. The OS kernel should drop the connection before that. BR, Nikos - Original Message - From: David Ritchie To: users@kannel.org Sent: Thursday, December 03, 2009 12:06 AM Subject: Kannel timeouts / connectivity issues Anybody know what Kannel’s expected behavior when HTTP connections timeout or fail? We have a situation with 120+ “sms-service” services defined, but have noticed a few of them behave in a peculiar manner where, very occasionally, HTTP requests don’t occur until 16 minutes after being received by Kannel. This will happen “out of the blue” without any errors logged in smsbox.log or kannel.log. This occurs in a transient fashion – there doesn’t appear to be any rhyme or reason to when this occurs. This only appears to happen with a particular subset of SMS services which happen to be hosted outside of our immediate hosting environment, suggesting there’s some sort of network disruption causing this problem. Potentially this is some of retry based on a 1-minute timeout, followed by a retry 15 minutes later; however this would be “out of character” since in my experience with Kannel most timeouts / 404s / 500s usually generate everyone’s favourite “Couldn’t fetch content, sorry”-type messages. I also can’t find any reference to timeouts of these values in the user’s guide or the configuration files. Until recently the get-urls for these services had the SMSC included in the URLs (i.e. “smsc=%i”) but, as these were the only services using this, I’ve removed this in case there’s some sort of problem caused by this. Has anybody else had a similar situation where these sorts of delays have happened? David
Re: meta-data TLV for USSD
Hi Marcin, I am very interested. Have you documented this anywhere? P. On Dec 3, 2009, at 3:04 PM, James Mutuku wrote: Hello Marcin, I am intrested 2009/12/3 Marcin Bockowski boc...@gmail.com 2009/12/3 Elton Hoxha elt...@gmail.com Hello, ... I have partially succeded to connect to USSD, sending MO requests, but then I`m stuck, sessions remains open until it is droped by Core Network. Anyway if you have any conf sample would be a lot of help. Hey all, we are using kannel as gateway for USSD services with success. Generally if you want to use just USSD strings conf may look like this: group = smsc smsc-id = MVNO-USSD-STRING smsc = smpp host = 10.10.10.10 port = 5014 smsc-username = foo smsc-password = bar system-type = VMA service-type = EA log-file= /var/log/kannel-ussd/ussd_strings.log log-level = 0 wait-ack-expire = 1 If you need menu based services just change: service-type = CR It works pretty with Hu*wei USSDC. Soon I'll be ready to release HTTP backend which can be used in sms-service (nifty GUI, menus, games, polls, etc.). If you are interested in such solution just let me know - i'll try to speed things up ;-) Regards, -- Marcin Boćkowski tel. +48 79 69 0 69 79
Re: Kannel timeouts / connectivity issues
Yeap. That's what i meant by easier. Each process has its own settings ;-) Therefore only a configuration/initialization issue. If it were a shared library on the other hand... BR, Nikos - Original Message - From: Alexander Malysh To: Nikos Balkanas Cc: users@kannel.org Sent: Thursday, December 03, 2009 2:10 PM Subject: Re: Kannel timeouts / connectivity issues I don't know what you mean by configurable globally? each box has it's own global config... Thanks, Alexander Malysh Am 03.12.2009 um 12:47 schrieb Nikos Balkanas: You are absolutely right. In fact it is easier than i thought. I will get right to it. And let's make default timeout to something easier on the eye, ie 60. BR, Nikos - Original Message - From: Alejandro Guerrieri To: Nikos Balkanas Cc: Alexander Malysh ; users@kannel.org Sent: Thursday, December 03, 2009 1:24 PM Subject: Re: Kannel timeouts / connectivity issues http smsc's works from bearerbox I think 2009/12/3 Nikos Balkanas n...@amdtelecom.net Hi Alex, Right now all client connections have a set limit of 240 hardwired in code. It is easy to make this configurable globally, and I think it would be an improvement over the hardcoded one. Now, from your sayings, this should be done /box (let's not forget wapbox) and this is more of a hussle. Smsbox wapbox can use the same setting, and i don't know of any bb http client connections. Do you? Besides I don't have time right now for /box timeout support. But the global one is trivial to do and can do it. Is this OK? I don't need it, but it seems that David does. BR, Nikos - Original Message - From: Alexander Malysh To: Nikos Balkanas Cc: users@kannel.org Sent: Thursday, December 03, 2009 11:35 AM Subject: Re: Kannel timeouts / connectivity issues Hi Nikos, the issue is that when you set timeout in configuration it's valid for _all_ http client connections. If you think it this config option would be useful, please provide patch for this because I'm too busy now :) I would suggest to set it in group = core for bearerbox and group = smsbox for smsbox. Thanks, Alexander Malysh Am 03.12.2009 um 05:22 schrieb Nikos Balkanas: Hi, According to Changelog, Alexander M. on 6/8/2006 added a function in gwlib/http.c: void http_set_client_timeout(long timeout) which sets the timeout for the http outgoing connections. Unfortunately it is ghost and not used anywhere in the code or configuration. As a result the http_client_timeout is hardwired into the code: static int http_client_timeout = 240; It's a rather trivial matter to add it in the configuration, but I think that Alex, the original contributor, should do it. If he cannot I could. What do you say Alex? Of course 15' timeout seems an overexaggeration. The OS kernel should drop the connection before that. BR, Nikos - Original Message - From: David Ritchie To: users@kannel.org Sent: Thursday, December 03, 2009 12:06 AM Subject: Kannel timeouts / connectivity issues Anybody know what Kannel’s expected behavior when HTTP connections timeout or fail? We have a situation with 120+ “sms-service” services defined, but have noticed a few of them behave in a peculiar manner where, very occasionally, HTTP requests don’t occur until 16 minutes after being received by Kannel. This will happen “out of the blue” without any errors logged in smsbox.log or kannel.log. This occurs in a transient fashion – there doesn’t appear to be any rhyme or reason to when this occurs. This only appears to happen with a particular subset of SMS services which happen to be hosted outside of our immediate hosting environment, suggesting there’s some sort of network disruption causing this problem. Potentially this is some of retry based on a 1-minute timeout, followed by a retry 15 minutes later; however this would be “out of character” since in my experience with Kannel most timeouts / 404s / 500s usually generate everyone’s favourite “Couldn’t fetch content, sorry”-type messages. I also can’t find any reference to timeouts of these values in the user’s guide or the configuration files. Until recently the get-urls for these services had the SMSC included in the URLs (i.e. “smsc=%i”) but, as these were the only services using this, I’ve removed this in case there’s some sort of problem caused by this. Has anybody else had a similar situation where these sorts of delays have happened? David
Re: users Digest, Vol 40, Issue 11
a rather trivial matter to add it in the configuration, but I think that Alex, the original contributor, should do it. If he cannot I could. What do you say Alex? Of course 15' timeout seems an overexaggeration. The OS kernel should drop the connection before that. BR, Nikos - Original Message - From: David Ritchie To: users@kannel.org Sent: Thursday, December 03, 2009 12:06 AM Subject: Kannel timeouts / connectivity issues Anybody know what Kannel?s expected behavior when HTTP connections timeout or fail? We have a situation with 120+ ?sms-service? services defined, but have noticed a few of them behave in a peculiar manner where, very occasionally, HTTP requests don?t occur until 16 minutes after being received by Kannel. This will happen ?out of the blue? without any errors logged in smsbox.log or kannel.log. This occurs in a transient fashion ? there doesn?t appear to be any rhyme or reason to when this occurs. This only appears to happen with a particular subset of SMS services which happen to be hosted outside of our immediate hosting environment, suggesting there?s some sort of network disruption causing this problem. Potentially this is some of retry based on a 1-minute timeout, followed by a retry 15 minutes later; however this would be ?out of character? since in my experience with Kannel most timeouts / 404s / 500s usually generate everyone?s favourite ?Couldn?t fetch content, sorry?-type messages. I also can?t find any reference to timeouts of these values in the user?s guide or the configuration files. Until recently the get-urls for these services had the SMSC included in the URLs (i.e. ?smsc=%i?) but, as these were the only services using this, I?ve removed this in case there?s some sort of problem caused by this. Has anybody else had a similar situation where these sorts of delays have happened? David -- next part -- An HTML attachment was scrubbed... URL: http://www.kannel.org/pipermail/users/attachments/20091203/873d0dc3/attachment-0001.html -- Message: 3 Date: Thu, 3 Dec 2009 15:04:31 +0300 From: James Mutuku jnmut...@gmail.com Subject: Re: meta-data TLV for USSD To: Marcin Bockowski boc...@gmail.com Cc: kannel users users@kannel.org Message-ID: 8125e0c80912030404s36a0d04fr4356f78465d51...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-2 Hello Marcin, I am intrested 2009/12/3 Marcin Bockowski boc...@gmail.com 2009/12/3 Elton Hoxha elt...@gmail.com Hello, ... I have partially succeded to connect to USSD, sending MO requests, but then I`m stuck, sessions remains open until it is droped by Core Network. Anyway if you have any conf sample would be a lot of help. Hey all, we are using kannel as gateway for USSD services with success. Generally if you want to use just USSD strings conf may look like this: group = smsc smsc-id = MVNO-USSD-STRING smsc = smpp host = 10.10.10.10 port = 5014 smsc-username = foo smsc-password = bar system-type = VMA service-type = EA log-file= /var/log/kannel-ussd/ussd_strings.log log-level = 0 wait-ack-expire = 1 If you need menu based services just change: service-type = CR It works pretty with Hu*wei USSDC. Soon I'll be ready to release HTTP backend which can be used in sms-service (nifty GUI, menus, games, polls, etc.). If you are interested in such solution just let me know - i'll try to speed things up ;-) Regards, -- Marcin Bo?kowski tel. +48 79 69 0 69 79 -- next part -- An HTML attachment was scrubbed... URL: http://www.kannel.org/pipermail/users/attachments/20091203/a4d3b56f/attachment.html -- ___ users mailing list users@kannel.org http://www.kannel.org/mailman/listinfo/users End of users Digest, Vol 40, Issue 11 *
Can I get help online about kannel? MSN
Hi Friends, I post a paper named 'Kannel confuse me for two weeks, I need your help' the day before yesterday. Many friends in this list replied my email. But I can't solve my problem yet. I hope that some friend help me by remote access to my computer. In this way, you can find some detailed information ignored by me. Who can help me? chen bo
Kannel CVS and DLRs MySQL storage / can not decode PDU to a message
Hi everybody, Below an issue I am faced trying to configure DLR management and kannel. Environnement: Kannel CVS 20091124 installed using RPM patch from Alejandro MySQL DLR storage configured Issue: can not decode PDU to a message I have configure DLR to use mysql (config file below) I send a SMS using this command: # lynx -dump http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarfrom=%2B687755632to=%2B687773502text=SMStestdepuisNavettedlr-mask=31 Firstly I saw the following error in kannel.log 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: -- +CDS: 24 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: -- 0629099186773705F2902140313504449021403135044400 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: received message from SMSC: 09019687773 2009-12-04 13:41:59 [4163] [6] ERROR: AT2[SiemensM20]: got +CMT but pdu_extract failed I check some forum about this issue and I set one parameter in modems.conf: broken = true And I see in the kannel.log file now the following error: 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- +CDS: 24 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- 0628099186773705F2902140316471449021403164714400 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: received message from SMSC: 09019687773 2009-12-04 13:34:35 [4088] [6] ERROR: AT2[SiemensM20]: could not decode PDU to a message. And 09019687773 seems to be my destination number 09019 (unknown???) 687773 but the end 502 are missing. The destination is +687773502. I did not find any solution to my issue...any idea, it seems Siemens M20 modem can not decode DLR PDU ? BTW for what is dedicated the dlr-url parameter ? To execute some script in order to process DLR info in a third party application database? If juste kannel is used, is the dlr table enough usefull to get the SMS delivery status? (always 0 in my case, even if mobile is switch off) Regards, -- Emmanuel @email : emmanuelchan...@gmail.com kannel.conf Description: Binary data modems.conf Description: Binary data
Re: Kannel CVS and DLRs MySQL storage / can not decode PDU to a message
Adding some informations, I notice when using a Nokia 6230 on another kannel server that it works well and I have the following: == /var/log/kannel/access.log == 2009-12-04 14:08:20 Receive DLR [SMSC:nokia6230] [SVC:alt] [ACT:] [BINF:] [FID:48] [from:687971204] [to:+687773502] [flags:-1:-1:-1:-1:1] [msg:7:Success] [udh:0:] == /var/log/kannel/kannel.log == 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: -- +CDS: 24 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: -- 069186770720F10630099186773705F2902140410291449021404102914400 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: received message from SMSC: +687770021 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: got STATUS-REPORT for message 48: 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: Numeric receiver (international) +687773502 2009-12-04 14:08:20 [11952] [6] DEBUG: DLR[internal]: Looking for DLR smsc=nokia6230, ts=48, dst=+687773502, type=1 2009-12-04 14:08:20 [11952] [6] DEBUG: DLR[internal]: created DLR message for URL 2009-12-04 14:08:20 [11952] [10] DEBUG: send_msg: sending msg to box: 127.0.0.1 2009-12-04 14:08:20 [11952] [10] DEBUG: boxc_sender: sent message to 127.0.0.1 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: -- AT+CNMA^M 2009-12-04 14:08:20 [11952] [9] DEBUG: boxc_receiver: got ack 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: -- OK instead of this for Siemens M20 modem: 2009-12-04 13:34:28 Receive DLR [SMSC:SiemensM20] [SVC:tester] [ACT:] [BINF:] [FID:40] [META:] [from:+687755632] [to:+687773502] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [udh:0:] 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- +CDS: 24 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- 0628099186773705F2902140316471449021403164714400 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: received message from SMSC: 09019687773 2009-12-04 13:34:35 [4088] [6] ERROR: AT2[SiemensM20]: could not decode PDU to a message. You can notice that there is 62 - 48 characters missing in the second test: Nokia phone has send a DLR with 62 char: 069186770720F10630099186773705F2902140410291449021404102914400 and Siemens M20 only 48 char (the last 48 in fact I think): ??0628099186773705F2902140316471449021403164714400 and can not decode PDU. (48 char) Any idea why ? Emmanuel 2009/12/4 Emmanuel CHANSON emmanuelchan...@gmail.com Hi everybody, Below an issue I am faced trying to configure DLR management and kannel. Environnement: Kannel CVS 20091124 installed using RPM patch from Alejandro MySQL DLR storage configured Issue: can not decode PDU to a message I have configure DLR to use mysql (config file below) I send a SMS using this command: # lynx -dump http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarfrom=%2B687755632to=%2B687773502text=SMStestdepuisNavettedlr-mask=31 Firstly I saw the following error in kannel.log 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: -- +CDS: 24 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: -- 0629099186773705F2902140313504449021403135044400 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: received message from SMSC: 09019687773 2009-12-04 13:41:59 [4163] [6] ERROR: AT2[SiemensM20]: got +CMT but pdu_extract failed I check some forum about this issue and I set one parameter in modems.conf: broken = true And I see in the kannel.log file now the following error: 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- +CDS: 24 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- 0628099186773705F2902140316471449021403164714400 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: received message from SMSC: 09019687773 2009-12-04 13:34:35 [4088] [6] ERROR: AT2[SiemensM20]: could not decode PDU to a message. And 09019687773 seems to be my destination number 09019 (unknown???) 687773 but the end 502 are missing. The destination is +687773502. I did not find any solution to my issue...any idea, it seems Siemens M20 modem can not decode DLR PDU ? BTW for what is dedicated the dlr-url parameter ? To execute some script in order to process DLR info in a third party application database? If juste kannel is used, is the dlr table enough usefull to get the SMS delivery status? (always 0 in my case, even if mobile is switch off) Regards, -- Emmanuel @email : emmanuelchan...@gmail.com -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com dlr-test.log Description: Binary data
Re: Kannel CVS and DLRs MySQL storage / can not decode PDU to a message
Hi, You obviously don't set dlr-url in your configuration or ssendsms URL. DLR table is just used for internal kannel processing. Once the final DLR (success or fail, 1 or 2) is received, the entry is deleted. That's why you cannot use it for permanent DLR storage. Of course you always get your permanent DLR records in your access logs, however, you might want the in your DB for greater customization/flexibility/ manipulation. That's what dlr-url does for you. It is your responsibility to provide the web service customized the way you want, to display to your clients. As the rest goes, the advice is simple: Use another modem. If you want to debug it, append to init-string in your modem definition: ...;+CMEE=1 or 2. But it seems to me a waste of time. BR, Nikos - Original Message - From: Emmanuel CHANSON To: users Sent: Friday, December 04, 2009 5:39 AM Subject: Re: Kannel CVS and DLRs MySQL storage / can not decode PDU to a message Adding some informations, I notice when using a Nokia 6230 on another kannel server that it works well and I have the following: == /var/log/kannel/access.log == 2009-12-04 14:08:20 Receive DLR [SMSC:nokia6230] [SVC:alt] [ACT:] [BINF:] [FID:48] [from:687971204] [to:+687773502] [flags:-1:-1:-1:-1:1] [msg:7:Success] [udh:0:] == /var/log/kannel/kannel.log == 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: -- +CDS: 24 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: -- 069186770720F10630099186773705F2902140410291449021404102914400 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: received message from SMSC: +687770021 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: got STATUS-REPORT for message 48: 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: Numeric receiver (international) +687773502 2009-12-04 14:08:20 [11952] [6] DEBUG: DLR[internal]: Looking for DLR smsc=nokia6230, ts=48, dst=+687773502, type=1 2009-12-04 14:08:20 [11952] [6] DEBUG: DLR[internal]: created DLR message for URL 2009-12-04 14:08:20 [11952] [10] DEBUG: send_msg: sending msg to box: 127.0.0.1 2009-12-04 14:08:20 [11952] [10] DEBUG: boxc_sender: sent message to 127.0.0.1 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: -- AT+CNMA^M 2009-12-04 14:08:20 [11952] [9] DEBUG: boxc_receiver: got ack 2009-12-04 14:08:20 [11952] [6] DEBUG: AT2[nokia6230]: -- OK instead of this for Siemens M20 modem: 2009-12-04 13:34:28 Receive DLR [SMSC:SiemensM20] [SVC:tester] [ACT:] [BINF:] [FID:40] [META:] [from:+687755632] [to:+687773502] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [udh:0:] 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- +CDS: 24 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- 0628099186773705F2902140316471449021403164714400 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: received message from SMSC: 09019687773 2009-12-04 13:34:35 [4088] [6] ERROR: AT2[SiemensM20]: could not decode PDU to a message. You can notice that there is 62 - 48 characters missing in the second test: Nokia phone has send a DLR with 62 char: 069186770720F10630099186773705F2902140410291449021404102914400 and Siemens M20 only 48 char (the last 48 in fact I think): ??0628099186773705F2902140316471449021403164714400 and can not decode PDU. (48 char) Any idea why ? Emmanuel 2009/12/4 Emmanuel CHANSON emmanuelchan...@gmail.com Hi everybody, Below an issue I am faced trying to configure DLR management and kannel. Environnement: Kannel CVS 20091124 installed using RPM patch from Alejandro MySQL DLR storage configured Issue: can not decode PDU to a message I have configure DLR to use mysql (config file below) I send a SMS using this command: # lynx -dump http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarfrom=%2B687755632to=%2B687773502text=SMStestdepuisNavettedlr-mask=31; Firstly I saw the following error in kannel.log 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: -- +CDS: 24 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: -- 0629099186773705F2902140313504449021403135044400 2009-12-04 13:41:59 [4163] [6] DEBUG: AT2[SiemensM20]: received message from SMSC: 09019687773 2009-12-04 13:41:59 [4163] [6] ERROR: AT2[SiemensM20]: got +CMT but pdu_extract failed I check some forum about this issue and I set one parameter in modems.conf: broken = true And I see in the kannel.log file now the following error: 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- +CDS: 24 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: -- 0628099186773705F2902140316471449021403164714400 2009-12-04 13:34:35 [4088] [6] DEBUG: AT2[SiemensM20]: received message from SMSC: 09019687773 2009-12-04 13:34:35 [4088] [6] ERROR: AT2[SiemensM20]: could not decode PDU to a message. And 09019687773 seems to be my destination number 09019 (unknown???)
How to display sms text message in tv
Hi All, How to display sms text message in Television. How to do this ? -- Regards, Kiran Reddy http://bit.ly/FNDC09
Re: How to display sms text message in tv
You should use kannel. kiran.re...@mpowerglobal.in wrote: Hi All, How to display sms text message in Television. How to do this ?
