unsubscribe me
PLEASE !!! _ See how Windows® connects the people, information, and fun that are part of your life http://clk.atdmt.com/MRT/go/119463819/direct/01/
unsubscribe
This e-mail and all material transmitted with it are for the use of the intended recipient(s) ONLY and contains confidential and/or privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken pursuant to the contents of the present e-mail is strictly prohibited and is unlawful. The recipient acknowledges that Bharti Telesoft Limited or its management or directors, are unable to exercise control or ensure the integrity over /of the contents of the information contained in e-mail. Any views expressed herein are those of the individual sender only and no binding nature of the contents shall be implied or assumed unless the sender does so expressly with due authority of Bharti Telesoft Limited. E-mail and any contents transmitted with it are prone to viruses and related defects despite all efforts to avoid such by Bharti Telesoft Limited.
unsubscribe
RE: Falling send sms via balanced conections
Alejandro, Copy the logs. A clarification: the error response is sent by ESME on purpose. Regards. G DEBUG: new group created `smpp' DEBUG: SMPP[smsc2-TX]: Sending PDU: DEBUG: SMPP PDU 0x101527e0 dump: DEBUG: type_name: submit_sm DEBUG: command_id: 4 = 0x0004 DEBUG: command_status: 0 = 0x DEBUG: sequence_number: 64 = 0x0040 DEBUG: service_type: NULL DEBUG: source_addr_ton: 2 = 0x0002 DEBUG: source_addr_npi: 1 = 0x0001 DEBUG: source_addr: 77832274 DEBUG: dest_addr_ton: 2 = 0x0002 DEBUG: dest_addr_npi: 1 = 0x0001 DEBUG: destination_addr: 138000 DEBUG: esm_class: 0 = 0x DEBUG: protocol_id: 0 = 0x DEBUG: priority_flag: 0 = 0x DEBUG: schedule_delivery_time: NULL DEBUG: validity_period: NULL DEBUG: registered_delivery: 0 = 0x DEBUG: replace_if_present_flag: 0 = 0x DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 7 = 0x0007 DEBUG: short_message: TEST OK DEBUG: SMPP PDU dump ends. WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL. DEBUG: SMPP[smsc2-TX]: Got PDU: DEBUG: SMPP PDU 0x101b7ac0 dump: DEBUG: type_name: submit_sm_resp DEBUG: command_id: 2147483652 = 0x8004 DEBUG: command_status: 101 = 0x0065 DEBUG: sequence_number: 64 = 0x0040 DEBUG: message_id: NULL DEBUG: SMPP PDU dump ends. ERROR: SMPP[smsc2-TX]: SMSC returned error code 0x0065 (ESME Receiver Permanent App Error Code) in response to submit_sm. DEBUG: SMPP[smsc2-TX]: Sending PDU: DEBUG: SMPP PDU 0x100c6410 dump: DEBUG: type_name: submit_sm DEBUG: command_id: 4 = 0x0004 DEBUG: command_status: 0 = 0x DEBUG: sequence_number: 50 = 0x0032 DEBUG: service_type: NULL DEBUG: source_addr_ton: 2 = 0x0002 DEBUG: source_addr_npi: 1 = 0x0001 DEBUG: source_addr: 77832274 DEBUG: dest_addr_ton: 2 = 0x0002 DEBUG: dest_addr_npi: 1 = 0x0001 DEBUG: destination_addr: 138000 DEBUG: esm_class: 0 = 0x DEBUG: protocol_id: 0 = 0x DEBUG: priority_flag: 0 = 0x DEBUG: schedule_delivery_time: NULL DEBUG: validity_period: NULL DEBUG: registered_delivery: 0 = 0x DEBUG: replace_if_present_flag: 0 = 0x DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 7 = 0x0007 DEBUG: short_message: TEST OK DEBUG: SMPP PDU dump ends. DEBUG: SMPP[smsc2-TX]: Got PDU: DEBUG: SMPP PDU 0x1012c4f8 dump: DEBUG: type_name: submit_sm_resp DEBUG: command_id: 2147483652 = 0x8004 DEBUG: command_status: 255 = 0x00ff DEBUG: sequence_number: 50 = 0x0032 DEBUG: message_id: NULL DEBUG: SMPP PDU dump ends. ERROR: SMPP[smsc2-TX]: SMSC returned error code 0x00ff (Unknown Error) in response to submit_sm. From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: Wednesday, February 04, 2009 11:50 AM To: Villada, Gustavo Subject: Re: Falling send sms via balanced conections Gustavo, It depends on which error messages you're dealing with. Kannel fails on some and retries on others. For example, an invalid_dest_addr is a permanent error and kannel discards it, while a throttling_error is temporary and kannel retries. Please post log details showing the PDU's for the submit_sm and submit_sm_resp Regards, Alejandro On Wed, Feb 4, 2009 at 2:13 PM, Villada, Gustavo gvill...@telemediala.com wrote: Hi, We have load balanced connections ( 2RX 2TX connections with same provider) Kannel are working ok. But in homologation test cases with the provider, we have the next problem: On one TX connection the provider send us the submit_sm_resp message with error status, kannel receive this status and drop the sms. The ask is: What we do for recovering these failed messages or any other workaround for resend the failed messages? We need recover and resend this... Best regards Gustavo
Re: Reply addresses.
Hi, I don't know if this is what you are looking for, but in sms-service configuration you can specify faked-sender, which will substitute in for real sender in MO traffic. Additionally there are many more options with MT-traffic. BR, Nikos - Original Message - From: Falko Ziemann fal...@gmail.com To: Alvin Starr al...@iplink.net Cc: users@kannel.org Sent: Wednesday, February 04, 2009 8:42 AM Subject: Re: Reply addresses. Hello Alvin, there is no field with this name in SMPP SUBMIT_SM command. Please ask your supplier Which fields in SUBMIT_SM have to be set to which value to get a new sender Regards Falko Am 03.02.2009 um 22:29 schrieb Nikos Balkanas: Please use the users list for such questions. BR, Nikos - Original Message - From: Alvin Starr al...@iplink.net To: de...@kannel.org Sent: Tuesday, February 03, 2009 10:59 PM Subject: Reply addresses. Our SMPP connection supplier claims that it is possible to alter the reply address in an SMS message. Right now all we get is our short code showing up as a reply. I have yet to find a way other than alter the From field. Our supplier is not being much help. They are saying that I can use some alternate address field but don't seem to know what it is or where I can find any description of it. -- Alvin Starr || voice: (416)585-9971x690 Interlink Connectivity|| fax: (416)585-9974 al...@iplink.net ||
Falling send sms via balanced conections
Hi, We have load balanced connections ( 2RX 2TX connections with same provider) Kannel are working ok. But in homologation test cases with the provider, we have the next problem: On one TX connection the provider send us the submit_sm_resp message with error status, kannel receive this status and drop the sms. The ask is: What we do for recovering these failed messages or any other workaround for resend the failed messages? We need recover and resend this... Best regards Gustavo
Re: Can't find a port to receive link request in wap gateway
Hi Kao, You are doing fine with the mailing list. Plus you know how to use Wireshark on your own! This should be a breeze. Smells like a firewall issue. However it is not, since it would show in netstat. Let's look at some logs: Kill all bearerbox wapbox processes. Start from one shell: bearebox -v 0 conffile From another shell: wapbox -v 0 confile Cpature and post. Also please post your entire confile with * where you want to hide info. I can't see anything wrong with what you posted, so there might be something bad elsewhere. BR, Nikos - Original Message - From: Kao. Josh (GSM) To: Nikos Balkanas ; users@kannel.org Sent: Wednesday, February 04, 2009 4:45 AM Subject: RE: Can't find a port to receive link request in wap gateway Dear Nikos, Thanks for you suggestion! I’ve put password in my original kannel.conf, I am sorry that I should put some * mark in this column so that it wouldn’t misleading you, sorry again! I also try your suggestion command and it shows the pid and my bearerbox running command. I’ve tried to use wireshark (ethreal) to capture the incoming port 9201 packets and find the kernel will response a RST/ACK when it receives my cell phone’s link request. So I suppose for some reason kernel doesn’t have any record that there is a TCP process listening on the port 9201. Any idea about it? Please tell me if you need more information and please give me some suggestions if you have any idea. Thank you very much! Best Regards, Josh p.s: It’s my first time to use mail list, hope it is a proper way to post a reply message. -- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, February 03, 2009 9:23 PM To: Kao. Josh (GSM); us...@vm1.kannel.org Subject: Re: Can't find a port to receive link request in wap gateway Try pgrep -fl bearerbox. You shouldn't see anything running. Look at bearerbox.log to find the reason. You should find a panic because it is missing admin-password. Solution: Put an admin-password. BR, Nikos - Original Message - From: Kao. Josh (GSM) To: users@kannel.org Sent: Tuesday, February 03, 2009 7:43 AM Subject: Can't find a port to receive link request in wap gateway Dear all, I am trying setup Kannel to be a wap gateway for a long time, but I always have a problem when wap browser connects to Kannel. I find there doesn’t have a port to receive wap browser’s link request because wap browser always show the gateway timeout alert (I set port 9201 on the wap browser gateway port). I use “netstat” and can’t find any process listening wap related port such as 9200, 9201…etc. I’ve tried fake wap sender and it works fine. The following is my Kannel configuration; almost all of them are default value. group = core admin-port = 13000 wapbox-port = 13002 admin-password = wdp-interface-name = * log-file = /tmp/kannel.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 #admin-deny-ip = #admin-allow-ip = group = wapbox bearerbox-host = 127.0.0.1 log-file = /tmp/wapbox.log log-level = 0 syslog-level = none I already google this problem for a long time but can’t find any information. So, is there anyone have some idea about this situation? Any clue is appreciated! Thank you very much! Best Regards, Josh This message may contain information which is private, privileged or confidential of Compal Communications, Inc. If you are not the intended recipient of this message, please notify the sender and destroy/delete the message. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. This message may contain information which is private, privileged or confidential of Compal Communications, Inc. If you are not the intended recipient of this message, please notify the sender and destroy/delete the message. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the
[ANNOUNCE-URGENT] Kannel 1.4.3 stable release available (bug fix release)
The Kannel Group is urged to announce the availability of Kannel 1.4.3 stable
release via our web site at URL
http://www.kannel.org/download.shtml
This bug fix release for IMMEDIATE upgrade from 1.4.2. Please find attached the
NEWS file section for the 1.4.3 stable release.
Best Regards,
Stipe Tolj
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
NEWS about Kannel: Open Source WAP and SMS Gateway version 1.4.3
This is a STABLE version. It should be usable for production systems.
Please do report problems to the Kannel bug tracking system available at
http://bugs.kannel.org/ or send a mail to de...@kannel.org (the development
mailing list).
Changes since version 1.4.2:
Bugfixes:
* Fixed SMPP's DLR support, which was broken in 1.4.2 due to a modification.
Changes since version 1.4.1:
[*** Beware that the version move from 1.4.1 to 1.4.2 contains numerous
change sets, with major bug fixes and improvements. Following is a summary of
the
main issues. For a complete and detailed set of changes please refer to the
specific ChangeLog in the doc/ directory of the distribution. ***]
Compatibility breakers:
* Internal message payload encoding changed from LATIN1 to UTF-8, which
means any 1.4.2 boxes are unable to communicate with older versions.
* Re-defined logic for the 'smsbox-route' group that is used for MO
routing to different (identified) smsbox connections.
* Changed main message structure to include foreign (SMSC) ID to it,
breaking the access-log format and communication to older box versions.
New features:
* Added service routing based on account field, which allows routing of
MO messages depending on the account set by an aggregating SMSC provider.
* Added the new 'generic' system-type for HTTP SMSC, which allows the usage
of the escape code sequenced in send-url and regex parsing of HTTP
response.
* Added 'interactive' mode via stdin and stdout to allow a more human like
interaction with the fake smsc module.
* Added support to pass the 'from' source addr via 'X-Kannel-From' HTTP
header in the PPG request.
* Added generic DLR handling for type 'kannel' (HTTP SMSC), which allows
point-to-point DLR forwarding though the whole kannel instance chain.
* Added support for store spool directory.
* Added concatenation MO support.
* Added AT SMSC support for protocol 'type = telnet', which interprets telnet
escape sequenced compared to rawtcp.
* Added REGEX support for keyword matching.
* Added support for IBM AIX 64bit builds.
* Added SSL support for HTTP SMSC module server.
* Added bearerbox HTTP admin command 'reload-lists' to allow re-loading of
the '[white|black]-list' on the fly.
* Added support of concatenated, 8bit and Unicode messages over HTTP via
Clickatell.
Bugfixes:
* Fixed alias support for sms-service in smsbox scope.
* Fixed various MIME type handling bugs.
* Fixed security and race condition issue in HTTP module for keep-alive
connections.
* Fixed wrong length calculation for concatenated messages.
* Fixed bug that AT SMSC put UDH without UDH len.
* Fixed various memleaks, reported by valgrind.
* Fixed HTTP proxy scheme interpretation for SSL-enabled connections.
* Fixed OTA compiler, within WBXML compilation.
* Fixed encoding of 'Content-Id' WSP header.
* Fixed various segfaults in SMPP, logging modules.
* Fixed various AT command handling in AT module.
* Fixed 7bit encoding in AT SMSC.
Changes since version 1.4.0:
[*** Beware that the version move from 1.4.0 to 1.4.1 contains more then 200
change sets, with major bug fixes and improvements. Following is a summary of
the
main issues. For a complete and detailed set of changes please refer to the
specific ChangeLog in the doc/ directory of the distribution. ***]
Compatibility breakers:
* Format for wapbox's access-log format changed to include the MSISDN of
a client as second argument after client IP and before method.
* fakesmsc uses now -r to specify the remote port on bearerbox side. Option
-p is generally reserved for pid file creation.
* sendsms now obeys bearerbox's reply before indicating result to HTTP
caller. This breaks any application layer clients that rely on the HTTP
body response of sendsms. To enforce the old behaviour use config
directive 'immediate-sendsms-reply = true' in smsbox group.
* DLR via MySQL uses now also 'username' and 'password' for the
mysql-connection group in order to harmonize the config names.
New features:
*
Re: [ANNOUNCE-URGENT] Kannel 1.4.3 stable release available (bug fixrelease)
Hi,
Did that affected only DLR rerouting as was your original patch a week ago,
or corrects problem with all SMPP DLRs?
BR,
Nikos
- Original Message -
From: Stipe Tolj s...@tolj.org
To: 'Kannel Users' users@kannel.org; kannel_dev_mailinglist
de...@kannel.org; annou...@kannel.org
Sent: Wednesday, February 04, 2009 8:32 PM
Subject: [ANNOUNCE-URGENT] Kannel 1.4.3 stable release available (bug
fixrelease)
The Kannel Group is urged to announce the availability of Kannel 1.4.3
stable
release via our web site at URL
http://www.kannel.org/download.shtml
This bug fix release for IMMEDIATE upgrade from 1.4.2. Please find
attached the
NEWS file section for the 1.4.3 stable release.
Best Regards,
Stipe Tolj
--
---
Kφlner Landstrasse 419
40589 Dόsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
NEWS about Kannel: Open Source WAP and SMS Gateway version 1.4.3
This is a STABLE version. It should be usable for production systems.
Please do report problems to the Kannel bug tracking system available at
http://bugs.kannel.org/ or send a mail to de...@kannel.org (the
development
mailing list).
Changes since version 1.4.2:
Bugfixes:
* Fixed SMPP's DLR support, which was broken in 1.4.2 due to a
modification.
Changes since version 1.4.1:
[*** Beware that the version move from 1.4.1 to 1.4.2 contains numerous
change sets, with major bug fixes and improvements. Following is a summary
of the
main issues. For a complete and detailed set of changes please refer to
the
specific ChangeLog in the doc/ directory of the distribution. ***]
Compatibility breakers:
* Internal message payload encoding changed from LATIN1 to UTF-8, which
means any 1.4.2 boxes are unable to communicate with older versions.
* Re-defined logic for the 'smsbox-route' group that is used for MO
routing to different (identified) smsbox connections.
* Changed main message structure to include foreign (SMSC) ID to it,
breaking the access-log format and communication to older box versions.
New features:
* Added service routing based on account field, which allows routing of
MO messages depending on the account set by an aggregating SMSC
provider.
* Added the new 'generic' system-type for HTTP SMSC, which allows the
usage
of the escape code sequenced in send-url and regex parsing of HTTP
response.
* Added 'interactive' mode via stdin and stdout to allow a more human
like
interaction with the fake smsc module.
* Added support to pass the 'from' source addr via 'X-Kannel-From' HTTP
header in the PPG request.
* Added generic DLR handling for type 'kannel' (HTTP SMSC), which allows
point-to-point DLR forwarding though the whole kannel instance chain.
* Added support for store spool directory.
* Added concatenation MO support.
* Added AT SMSC support for protocol 'type = telnet', which interprets
telnet
escape sequenced compared to rawtcp.
* Added REGEX support for keyword matching.
* Added support for IBM AIX 64bit builds.
* Added SSL support for HTTP SMSC module server.
* Added bearerbox HTTP admin command 'reload-lists' to allow re-loading
of
the '[white|black]-list' on the fly.
* Added support of concatenated, 8bit and Unicode messages over HTTP via
Clickatell.
Bugfixes:
* Fixed alias support for sms-service in smsbox scope.
* Fixed various MIME type handling bugs.
* Fixed security and race condition issue in HTTP module for keep-alive
connections.
* Fixed wrong length calculation for concatenated messages.
* Fixed bug that AT SMSC put UDH without UDH len.
* Fixed various memleaks, reported by valgrind.
* Fixed HTTP proxy scheme interpretation for SSL-enabled connections.
* Fixed OTA compiler, within WBXML compilation.
* Fixed encoding of 'Content-Id' WSP header.
* Fixed various segfaults in SMPP, logging modules.
* Fixed various AT command handling in AT module.
* Fixed 7bit encoding in AT SMSC.
Changes since version 1.4.0:
[*** Beware that the version move from 1.4.0 to 1.4.1 contains more then
200
change sets, with major bug fixes and improvements. Following is a summary
of the
main issues. For a complete and detailed set of changes please refer to
the
specific ChangeLog in the doc/ directory of the distribution. ***]
Compatibility breakers:
* Format for wapbox's access-log format changed to include the MSISDN of
a client as second argument after client IP and before method.
* fakesmsc uses now -r to specify the remote port on bearerbox side.
Option
-p is generally reserved for pid file creation.
* sendsms now obeys
Re: [ANNOUNCE-URGENT] Kannel 1.4.3 stable release available (bug fixrelease)
Hi Stipe,
Sorry for bothering too much. Could you update the CVS head? I cannot find
any differences from last week.
BR,
Nikos
- Original Message -
From: Nikos Balkanas nbalka...@gmail.com
To: Stipe Tolj s...@tolj.org; 'Kannel Users' users@kannel.org
Sent: Wednesday, February 04, 2009 9:22 PM
Subject: Re: [ANNOUNCE-URGENT] Kannel 1.4.3 stable release available (bug
fixrelease)
Hi,
Did that affected only DLR rerouting as was your original patch a week
ago, or corrects problem with all SMPP DLRs?
BR,
Nikos
- Original Message -
From: Stipe Tolj s...@tolj.org
To: 'Kannel Users' users@kannel.org; kannel_dev_mailinglist
de...@kannel.org; annou...@kannel.org
Sent: Wednesday, February 04, 2009 8:32 PM
Subject: [ANNOUNCE-URGENT] Kannel 1.4.3 stable release available (bug
fixrelease)
The Kannel Group is urged to announce the availability of Kannel 1.4.3
stable
release via our web site at URL
http://www.kannel.org/download.shtml
This bug fix release for IMMEDIATE upgrade from 1.4.2. Please find
attached the
NEWS file section for the 1.4.3 stable release.
Best Regards,
Stipe Tolj
--
---
Kφlner Landstrasse 419
40589 Dόsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
NEWS about Kannel: Open Source WAP and SMS Gateway version 1.4.3
This is a STABLE version. It should be usable for production systems.
Please do report problems to the Kannel bug tracking system available at
http://bugs.kannel.org/ or send a mail to de...@kannel.org (the
development
mailing list).
Changes since version 1.4.2:
Bugfixes:
* Fixed SMPP's DLR support, which was broken in 1.4.2 due to a
modification.
Changes since version 1.4.1:
[*** Beware that the version move from 1.4.1 to 1.4.2 contains numerous
change sets, with major bug fixes and improvements. Following is a
summary of the
main issues. For a complete and detailed set of changes please refer to
the
specific ChangeLog in the doc/ directory of the distribution. ***]
Compatibility breakers:
* Internal message payload encoding changed from LATIN1 to UTF-8, which
means any 1.4.2 boxes are unable to communicate with older versions.
* Re-defined logic for the 'smsbox-route' group that is used for MO
routing to different (identified) smsbox connections.
* Changed main message structure to include foreign (SMSC) ID to it,
breaking the access-log format and communication to older box
versions.
New features:
* Added service routing based on account field, which allows routing of
MO messages depending on the account set by an aggregating SMSC
provider.
* Added the new 'generic' system-type for HTTP SMSC, which allows the
usage
of the escape code sequenced in send-url and regex parsing of HTTP
response.
* Added 'interactive' mode via stdin and stdout to allow a more human
like
interaction with the fake smsc module.
* Added support to pass the 'from' source addr via 'X-Kannel-From' HTTP
header in the PPG request.
* Added generic DLR handling for type 'kannel' (HTTP SMSC), which allows
point-to-point DLR forwarding though the whole kannel instance chain.
* Added support for store spool directory.
* Added concatenation MO support.
* Added AT SMSC support for protocol 'type = telnet', which interprets
telnet
escape sequenced compared to rawtcp.
* Added REGEX support for keyword matching.
* Added support for IBM AIX 64bit builds.
* Added SSL support for HTTP SMSC module server.
* Added bearerbox HTTP admin command 'reload-lists' to allow re-loading
of
the '[white|black]-list' on the fly.
* Added support of concatenated, 8bit and Unicode messages over HTTP via
Clickatell.
Bugfixes:
* Fixed alias support for sms-service in smsbox scope.
* Fixed various MIME type handling bugs.
* Fixed security and race condition issue in HTTP module for keep-alive
connections.
* Fixed wrong length calculation for concatenated messages.
* Fixed bug that AT SMSC put UDH without UDH len.
* Fixed various memleaks, reported by valgrind.
* Fixed HTTP proxy scheme interpretation for SSL-enabled connections.
* Fixed OTA compiler, within WBXML compilation.
* Fixed encoding of 'Content-Id' WSP header.
* Fixed various segfaults in SMPP, logging modules.
* Fixed various AT command handling in AT module.
* Fixed 7bit encoding in AT SMSC.
Changes since version 1.4.0:
[*** Beware that the version move from 1.4.0 to 1.4.1 contains more then
200
change sets, with major bug fixes and improvements. Following is a
summary of the
main issues. For a complete and detailed set of changes please
