Re: How to allow kannel to receive connections

[amalysh]

smpp server can be used to push messages as well (MOs). Please ask your smsc 
operator if they
mean outbind connection. But anyway Kannel doesn’t support outbind out of the 
box.

Thanks,
Alex


> Am 28.01.2019 um 15:11 schrieb Хиль Эдуард :
> 
> Maybe my question not complite correct...
> My kannel is SMPP client. With kannel i connects to many SMSc providers and 
> send my SMS through them. But now, we have one strange SMSc provider, who 
> wants connect to me, that allow to me send my SMS through him. So, i think 
> it's mean TCP layer connection. He wants to initiate TCP session with me, but 
> on SMPP proto i still as client. There is no way to do this with kannel? 
> Let's imagine, i'll install opensmppbox, so how i can _transmite_ my SMS to 
> this SMSc provider? I think opensmppbox needed to _receive_ SMS from someone, 
> isn't?
> 
> 
> Понедельник, 28 января 2019, 18:26 +05:00 от amal...@kannel.org:
> 
> Hi,
> 
> you need SMPP server instead of SMPP client. Check opensmppbox or commercial 
> alternatives like mine
> or Stipe’s.
> 
> Thanks,
> Alex
> 
>> Am 28.01.2019 um 13:53 schrieb Хиль Эдуард > >:
>> 
>> 
>> hi there!
>> It is possible to _receive_ connections from SMS providers by kannel?
>> I have kannel v1.4.4 and in config i have some block:
>> 
>> group=smsc
>> smsc=smpp
>> transceiver-mode=false
>> smsc-id=SMPP_ZAPVMA_R
>> host=192.168.50.37
>> port=0
>> receive-port=9081
>> smsc-username=SMPP_ZAPVMA_R
>> smsc-password=architech
>> system-type=SMPP
>> 
>> by this config, i expect that kannel will _receive_ connection from 
>> 192.168.50.37 (SMS provider) to kannel address (192.168.49.24) and port 9081 
>> - is this correct? All that i see in my logs:
>> ...
>> 
>> 2019-01-28 14:45:08 [7515] [6] ERROR: connect to <192.168.50.37> failed
>> 2019-01-28 14:45:08 [7515] [6] ERROR: System error 111: Connection refused
>> 2019-01-28 14:45:08 [7515] [6] ERROR: error connecting to server 
>> `192.168.50.37' at port `9081'
>> 2019-01-28 14:45:08 [7515] [6] ERROR: SMPP[SMPP_ZAPVMA_R]: Couldn't connect 
>> to server.
>> 2019-01-28 14:45:08 [7515] [6] ERROR: SMPP[SMPP_ZAPVMA_R]: Couldn't connect 
>> to SMS center (retrying in 10 seconds).
>> ...
>> 
>> The kannel try to connect to 192.168.50.37 port 9081 , but that's not what i 
>> want. It is possible to resolve this task?
>> 
>> --
>> Best regards,
>> Me.
>> 
>> 
> 
> 
> 
> -- 
> Хиль Эдуард

Re: How to allow kannel to receive connections

[amalysh]

Hi,

you need SMPP server instead of SMPP client. Check opensmppbox or commercial 
alternatives like mine
or Stipe’s.

Thanks,
Alex

> Am 28.01.2019 um 13:53 schrieb Хиль Эдуард :
> 
> 
> hi there!
> It is possible to _receive_ connections from SMS providers by kannel?
> I have kannel v1.4.4 and in config i have some block:
> 
> group=smsc
> smsc=smpp
> transceiver-mode=false
> smsc-id=SMPP_ZAPVMA_R
> host=192.168.50.37
> port=0
> receive-port=9081
> smsc-username=SMPP_ZAPVMA_R
> smsc-password=architech
> system-type=SMPP
> 
> by this config, i expect that kannel will _receive_ connection from 
> 192.168.50.37 (SMS provider) to kannel address (192.168.49.24) and port 9081 
> - is this correct? All that i see in my logs:
> ...
> 
> 2019-01-28 14:45:08 [7515] [6] ERROR: connect to <192.168.50.37> failed
> 2019-01-28 14:45:08 [7515] [6] ERROR: System error 111: Connection refused
> 2019-01-28 14:45:08 [7515] [6] ERROR: error connecting to server 
> `192.168.50.37' at port `9081'
> 2019-01-28 14:45:08 [7515] [6] ERROR: SMPP[SMPP_ZAPVMA_R]: Couldn't connect 
> to server.
> 2019-01-28 14:45:08 [7515] [6] ERROR: SMPP[SMPP_ZAPVMA_R]: Couldn't connect 
> to SMS center (retrying in 10 seconds).
> ...
> 
> The kannel try to connect to 192.168.50.37 port 9081 , but that's not what i 
> want. It is possible to resolve this task?
> 
> --
> Best regards,
> Me.
> 
> 

Re: TLS 1.2 support in kannel

[amalysh]

Hi,

please check userguide:
https://kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN482 


Special:
ssl-client-certkey-file (c) filenameA PEM encoded SSL certificate 
and private key file to be used with SSL client connections. This certificate 
is used for the HTTPS client side only, i.e. for SMS service requests to 
SSL-enabled HTTP servers.
ssl-server-cert-file (c)filenameA PEM encoded SSL certificate 
file to be used with SSL server connections. This certificate is used for the 
HTTPS server side only, i.e. for the administration HTTP server and the HTTP 
interface to send SMS messages.
ssl-server-key-file (c) filenameA PEM encoded SSL private key file to 
be used with SSL server connections. This key is associated to the specified 
certificate and is used for the HTTPS server side only.
ssl-trusted-ca-file filenameThis file contains the certificates 
Kannel is willing to trust when working as a HTTPS client. If this option is 
not set, certificates are not validated and those the identity of the server is 
not proven.
ssl-client-cipher-list  filenameDefines the list of encryption suites 
and ciphers to be used for client side connections. For further details please 
see https://www.openssl.org/docs/manmaster/man1/ciphers.html
ssl-server-cipher-list  filenameDefines the list of encryption suites 
and ciphers to be used for server side connections. For further details please 
see https://www.openssl.org/docs/manmaster/man1/ciphers.html

Thanks,
Alex


> Am 03.11.2018 um 17:25 schrieb info.ubichip :
> 
> Dear Alexander,
>  
> may you please help me to find any information about your added feature on 
> SSL/TLS, specially how to efine which SSL/TLS chiper suites to use ?
>  
> Thanks a lot for you answer
>  
> De : users [mailto:users-boun...@kannel.org 
> ] De la part de info.ubichip
> Envoyé : samedi 3 novembre 2018 17:14
> À : 'Web Min'
> Cc : users@kannel.org 
> Objet : RE: TLS 1.2 support in kannel
>  
> the email was gone too fast :
>  
> do you have any experience with the following added feature of the 1.4.5 
> specially the one in red (le last one) ?
>  
> * Added OpenSSL 1.1.x support.
>   
>   * Added support for chained certificate files.
>   
>   * Added support to define which SSL/TLS chipher suites to use.
>  
> De : info.ubichip [mailto:info.ubic...@free.fr ] 
> Envoyé : samedi 3 novembre 2018 17:12
> À : 'Web Min'
> Cc : 'users@kannel.org '
> Objet : RE: TLS 1.2 support in kannel
>  
> thanks,
>  
> it working with 
> ./configure --enable-start-stop-daemon --with-mysql --enable-ssl 
>  
> but not with :
>  
> ./configure --enable-start-stop-daemon --with-mysql --enable-ssl --with-ssl
> Configuring OpenSSL support ...
> configure: error: Unable to find OpenSSL libs and/or directories at yes
> 
>  
> Do you ha
>  
>  
> De : Web Min [mailto:meweb...@gmail.com] 
> Envoyé : samedi 3 novembre 2018 09:05
> À : info.ubic...@free.fr
> Cc : users@kannel.org
> Objet : Re: TLS 1.2 support in kannel
>  
> Hello,
>  
> In order to start with Ubuntu make sure the following packages are installed:
>  
> apt-get install libmysqlclient-dev libmysqld-dev libxml2 libxml2-dev bison 
> byacc libssh-dev libssl-dev
>  
> Best Regards,
>  
> On Sat, Nov 3, 2018 at 1:51 AM info.ubichip  > wrote:
>> hello,
>> 
>> I tried to reinstall a full clean machine with ubuntu 18.04 and last openssl
>> 1.1.0g (nov 2017)
>> and when I tried 
>> ./configure --enable-start-stop-daemon --with-mysql --enable-ssl --with-ssl
>> I got error :
>> Configuring OpenSSL support ...
>> configure: error: Unable to find OpenSSL libs and/or directories at yes
>> 
>> Does anyone got this error ?
>> 
>> thanks in advance
>> 
>> 
>> -Message d'origine-
>> De : users [mailto:users-boun...@kannel.org 
>> ] De la part de info.ubichip
>> Envoyé : vendredi 2 novembre 2018 16:41
>> À : users@kannel.org 
>> Objet : RE: TLS 1.2 support in kannel
>> 
>> Hello,
>> 
>> some update, I forgot to mention, I'm using kannel 1.4.5, and it has been
>> seen the following errors as well in smsbox log :
>> 
>> :SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
>> 
>> Does anyone have seen this issue so far ?
>> 
>> thanks in advance for your help
>> 
>> -Message d'origine-
>> De : users [mailto:users-boun...@kannel.org 
>> ] De la part de info.ubichip
>> Envoyé : vendredi 2 novembre 2018 09:42
>> À : users@kannel.org 
>> Objet : TLS 1.2 support in kannel
>> Importance : Haute
>> 
>> Hello,
>> 
>> I have similar issue with SSL and kannel, in SMSBOX it appears the following
>> errors :
>> 
>> 2018-10-01 21:11:12 [3345] [8] 

Re: Routing Traffic from One SMSC to another

[amalysh]

Hi,

you have two options:

1. Load balance SMSC1 and SMSC2. See allowed-smsc config option and name your 
SMSCs equal.
2. Fallback to SMSC2 if SMSC1 is down or full. See preferred-smsc config option.

Thanks,
Alexander 

> Am 22.08.2018 um 06:59 schrieb Rajesh Sahoo :
> 
> Hello all,
> I am facing one Issue something like below.
> Sometimes I get more traffic and according to routing logic (simple one user 
> to one SMSC)
> all messages are queued at kannel for a particular SMSC let name it 
> SMSC_PROVIDER1. 
> Form admin interface I know that another SMSC let name it SMSC_PROVIDER2 has 
> no load.
> 
> So Now I want to take some messages let 10K from SMSC_PROVIDER1 to 
> SMSC_PROVIDER2.
> 
> NOTE: I don't want to send all message to the other route SMSC_PROVIDER2
> 
> I need the suggestion for this, How to handle this scenario because I have to 
> process the message as early as possible.
> 
> Is any readymade tool available for this?
> 
> -- 
> Regards,
> Rajesh Kumar Sahoo | Designation: Technical Manager
> Hand Phone: +91-8884882772
> 
>      
> 3m Digital Networks Pvt. Ltd.
> Ph: 080-3007-2323 Extn:- 104
> A2P Messaging l Voice & Cloud Telephony l Digital l Technology 
> 
> Our Offices: Bengaluru l Hyderabad l Delhi l Bhubaneswar

Re: ERROR: SMPP[xxxx]: got DLR but could not find message or was not interested in it

[amalysh]

Hi,

do both Kannel share the same database and table ? they have to share DLR 
database.

Alex


> Am 03.08.2018 um 08:37 schrieb mahesh Lavanam :
> 
> Hi,
> 
> Please help me in resolving the DLR issue
> 
> I have a SMS Port with 2 TX & 2 RX sessions enabled.
> 
> I have configured these sessions in two kannel configurations with same smsc 
> id
> 
> kannel1.conf - 1TX & 1RX(SMSbox1 & Bearerbox1) 
> 
> #1st tx connection
> group = smsc
> smsc = smpp
> smsc-id = tran
> host = xxx.xxx.xxx.xx
> port = xxx
> smsc-username = x
> smsc-password = xx
> system-type = smpp
> connect-allow-ip = 127.0.0.1
> source-addr-ton = 0
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi = 1
> 
> 
> #1st Rx Connection
> group = smsc
> smsc = smpp
> smsc-id = tran
> host = xxx.xxx.xxx.xx
> port = xxx
> smsc-username = x
> smsc-password = xx
> system-type = smpp
> connect-allow-ip = 127.0.0.1
> source-addr-ton = 0
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi = 1
> 
> kannel2.conf  - 1TX & 1RX(SMSbox2 & Bearerbox2) 
> 
> #1st tx connection
> group = smsc
> smsc = smpp
> smsc-id = tran
> host = xxx.xxx.xxx.xx
> port = xxx
> smsc-username = x
> smsc-password = xx
> system-type = smpp
> connect-allow-ip = 127.0.0.1
> source-addr-ton = 0
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi = 1
> 
> 
> #1st Rx Connection
> group = smsc
> smsc = smpp
> smsc-id = tran
> host = xxx.xxx.xxx.xx
> port = xxx
> smsc-username = x
> smsc-password = xx
> system-type = smpp
> connect-allow-ip = 127.0.0.1
> source-addr-ton = 0
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi = 1
> 
> 
> In kannel2.log file, I see that kannel1's sms DLRs are receiving and seeing 
> the error as below:
> 
> DEBUG: DLR[internal]: Looking for DLR smsc=tran, ts=0160683811, 
> dst=919134556661, type=1
> WARNING: DLR[internal]: DLR from SMSC for DST<919134556661> not found.
> ERROR: SMPP[bsnl_tran]: got DLR but could not find message or was not 
> interested in it id<0160683811> dst<919134556661>, type<1>
> 
> Same error at kannel1.log file, when received the SMS DLRs of kannel2's 
> messages
> 
> Please help me to resolve the issue, to route the DLRs into its respective 
> kannel's i.e., Kannel1's sent sms dlr into kannel1 & kannel2's sent sms dlr 
> into kannel2.
> 
> Thanks,
> Mahesh
> 

Re: Keeping relative time format w/o conversion to absolute time format

[amalysh]

Hi Denis,

sorry but it make no sense to me. If Kannel send absolute time format than SMSC 
can do whatever
it want with it, recalculate to local time etc. Absolute time is not afffected 
if you are moving between TZs.

Alex


> Am 19.07.2018 um 15:25 schrieb Денис Давыдов :
> 
> Alex, 
> 
> Thanks for the answer.
> 
> Firstly, the set of different validity_period is a requirement in our 
> business workflow. Secondly, our ESMEs is geographically in different TZs and 
> they are movable objects and we don't know ESME's location at the time of 
> sending the message. In this case our SMPP provider recommends us to use the 
> relative time format, because of the end provider's equipment that 
> interacting with ESME works in accordance with local time zone (it is verify 
> validity_period in it's retry sending schemes as I was informed). 
> 
> --
> Kind regards,
> Denis
> 
> 
> чт, 19 июл. 2018 г. в 12:18, mailto:amal...@kannel.org>>:
> Hi,
> 
> tha first question would be, why do you want to keep it in relative time 
> format?
> As answer to your question: no this is not possible now , because Kannel 
> converts
> timestamp to unix timestamp internally on the input side and afterwards to 
> absolute
> time format. Sure you make changes to the source code to send relative time 
> format…
> 
> Thanks,
> Alex
> 
> > Am 19.07.2018 um 08:51 schrieb Денис Давыдов  > >:
> > 
> > Hi all,
> > 
> > Is there a possibility to keep validity_period of MT which sending from 
> > opensmppbox to external SMSCs in the relative time format unchanged? For 
> > now, I see the kannel changing it to the absolute time format.
> > 
> > For example, this is a snippet from the opensmppbox logfile (this was a 
> > submit_sm where is the vp was set to 1 minute):
> > 
> > 2018-07-17 10:57:20 [29721] [421] DEBUG:   validity_period: 
> > "010R"
> > 
> > That is a snippet from SMSC log:
> > 
> > 2018-07-17 10:57:20 [2565] [25] DEBUG: SMPP PDU 0x7fe864004010 dump:
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   type_name: submit_sm
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   command_id: 4 = 0x0004
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   command_status: 0 = 0x
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   sequence_number: 225108 = 
> > 0x00036f54
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   service_type: "CMT"
> > ...
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   esm_class: 3 = 0x0003
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   protocol_id: 0 = 0x
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   priority_flag: 1 = 0x0001
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   schedule_delivery_time: NULL
> > 2018-07-17 10:57:20 [2565] [25] DEBUG:   validity_period: "18071710582+"
> > 
> > For me the goal is to keep relative time format keep unchanged while 
> > message leaves the kannel.
> > 
> > Any feedback is appreciated. Thanks!
> > 
> > --
> > Kind regards,
> > Denis
> 

Re: Keeping relative time format w/o conversion to absolute time format

[amalysh]

Hi,

tha first question would be, why do you want to keep it in relative time format?
As answer to your question: no this is not possible now , because Kannel 
converts
timestamp to unix timestamp internally on the input side and afterwards to 
absolute
time format. Sure you make changes to the source code to send relative time 
format…

Thanks,
Alex

> Am 19.07.2018 um 08:51 schrieb Денис Давыдов :
> 
> Hi all,
> 
> Is there a possibility to keep validity_period of MT which sending from 
> opensmppbox to external SMSCs in the relative time format unchanged? For now, 
> I see the kannel changing it to the absolute time format.
> 
> For example, this is a snippet from the opensmppbox logfile (this was a 
> submit_sm where is the vp was set to 1 minute):
> 
> 2018-07-17 10:57:20 [29721] [421] DEBUG:   validity_period: "010R"
> 
> That is a snippet from SMSC log:
> 
> 2018-07-17 10:57:20 [2565] [25] DEBUG: SMPP PDU 0x7fe864004010 dump:
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   type_name: submit_sm
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   command_id: 4 = 0x0004
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   command_status: 0 = 0x
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   sequence_number: 225108 = 0x00036f54
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   service_type: "CMT"
> ...
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   esm_class: 3 = 0x0003
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   protocol_id: 0 = 0x
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   priority_flag: 1 = 0x0001
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   schedule_delivery_time: NULL
> 2018-07-17 10:57:20 [2565] [25] DEBUG:   validity_period: "18071710582+"
> 
> For me the goal is to keep relative time format keep unchanged while message 
> leaves the kannel.
> 
> Any feedback is appreciated. Thanks!
> 
> --
> Kind regards,
> Denis

Re: SMS command_status for long MT messages

[amalysh]

Hi Jeff,

it makes maybe sense for your case but not for all cases, therefore I don’t see 
a sense to invest time into it.

Thanks,
Alex


> Am 02.06.2018 um 15:26 schrieb Jeff Thorn :
> 
> Hi Alex,
> Thanks for explaining, makes sense. 
> 
> The most common status we get is invalid destination address (0x000b). In 
> this case all 3 parts in your example would have the same status. Would it 
> make sense to include the status of it was the same for all parts?
> 
> Jeff Thorn
> CEO
> Thorn Technologies, LLC
> https://www.thorntech.com 
> On Sat, Jun 2, 2018, 8:09 AM mailto:amal...@kannel.org>> 
> wrote:
> Hi,
> 
> this is expected behaviour because we have to put all statuses into one DLR 
> message.
> Just imagine if you have 3 parts and each of this part will be rejected with 
> different error code,
> would you expect all 3 error codes in the status?
> 
> Thanks,
> Alex
> 
> 
>> Am 30.05.2018 um 20:50 schrieb Jeff Thorn > >:
>> 
>> Hi group, 
>> Looking for a little help on this The DLR command status flag (%A) 
>> appears blank when the original MT message was a long message ( > 160 
>> chars). 
>> 
>> Is there a solution to this issue?  Here is an example from our logs.
>> 
>> 2018-04-11 19:00:38 [30573] [6] ERROR: SMPP[]: SMSC returned error code 
>> 0x000b (Invalid Destination Address) in response to submit_sm PDU.
>> 2018-04-11 19:00:38 [30573] [6] DEBUG: Set split msg status to 3
>> 2018-04-11 19:00:38 [30573] [6] DEBUG: Parts of concatenated message failed.
>> 2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[]: creating DLR message
>> 2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[]: DLR = 
>> https://myurl/api/dlr?status=%d; 
>> code=%A=123456=%t
>> 
>> Normally for rejected messages the value of the %A parameter is something 
>> like:
>> 
>> NACK/0x000b/Invalid Destination Address
>> 
>> However, when the original MT message is a long message that gets split, the 
>> %A parameter in the DLR url looks like this:
>> 
>> NACK/
>> 
>> Any feedback is appreciated. Thanks!
>> 
>> 
>> Jeff Thorn
>> CEO / Principal Software Architect
>> Thorn Technologies, LLC
>> www.thorntech.com 
>> @thorntech  | LinkedIn 
>>  | Facebook 
>> 

Re: SMS command_status for long MT messages

[amalysh]

Hi,

this is expected behaviour because we have to put all statuses into one DLR 
message.
Just imagine if you have 3 parts and each of this part will be rejected with 
different error code,
would you expect all 3 error codes in the status?

Thanks,
Alex


> Am 30.05.2018 um 20:50 schrieb Jeff Thorn :
> 
> Hi group, 
> Looking for a little help on this The DLR command status flag (%A) 
> appears blank when the original MT message was a long message ( > 160 chars). 
> 
> Is there a solution to this issue?  Here is an example from our logs.
> 
> 2018-04-11 19:00:38 [30573] [6] ERROR: SMPP[]: SMSC returned error code 
> 0x000b (Invalid Destination Address) in response to submit_sm PDU.
> 2018-04-11 19:00:38 [30573] [6] DEBUG: Set split msg status to 3
> 2018-04-11 19:00:38 [30573] [6] DEBUG: Parts of concatenated message failed.
> 2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[]: creating DLR message
> 2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[]: DLR = 
> https://myurl/api/dlr?status=%d; 
> code=%A=123456=%t
> 
> Normally for rejected messages the value of the %A parameter is something 
> like:
> 
> NACK/0x000b/Invalid Destination Address
> 
> However, when the original MT message is a long message that gets split, the 
> %A parameter in the DLR url looks like this:
> 
> NACK/
> 
> Any feedback is appreciated. Thanks!
> 
> 
> Jeff Thorn
> CEO / Principal Software Architect
> Thorn Technologies, LLC
> www.thorntech.com 
> @thorntech  | LinkedIn 
>  | Facebook 
> 

Re: Incoming MO UDH

[amalysh]

Hi,

udh are identical except coding, the first one is hex encoded the second is 
binary url encoded.

Thanks,
Alex


> Am 02.05.2018 um 03:33 schrieb Wan Md Arif Noor Bin. Wan Nizam 
> :
> 
> Hi Kannel User,
>  
> Based from the user guide using sms-combine-concatenated-mo to true will 
> instruct kannel to combine MO before sending to smsbox, however I want kannel 
> to forward the MO our application without combining it thus I set it to false,
> Here is the issue, the UDH from smsbox is weird. In the access logs it looked 
> fine but the one in smsbox isn’t
>  
> In access log :  udh:0500036C0201
> In smsbox log : udh=%05%00%03l%02%01
>  
> Why it become like that and is there any configuration that I need to set so 
> it doesn’t become like that? Thanks.
>  
> Regards,
> Arif Noor

Re: bootstrap.sh error

[amalysh]

Hi,

this is a list of packages I need to install to build kannel in docker 
container ubuntu 16.04:

build-essential subversion ntp nano wget cvs subversion curl git-core 
unzip autoconf \
automake1.11 libtool flex debhelper pkg-config libpam0g-dev intltool 
checkinstall docbook docbook-xsl \
build-essential libpcre3 libpcre3-dev libc6-dev g++ gcc autotools-dev 
bison libncurses5-dev m4 tex-common \
texi2html texinfo libxml2-dev \
openssl libssl-dev locales libmysqlclient-dev libmysql++-dev supervisor 
libtool libtool-bin \
vim

Thanks,
Alex


> Am 21.04.2018 um 02:48 schrieb Willy Mularto :
> 
> Hi Alex,
> Thanks for the reply. I'm not sure it's available on Ubuntu 16.04, already 
> searched it and found none for gettext-devel. Is there any other solution? 
> 
> 
> 
> So Far Express VPN still the fastest
> https://www.expressrefer.com/refer-friend?referrer_id=15939000_campaign=referrals_medium=copy_link_source=referral_dashboard
>  
> 
> 
> 
> On Thu, Apr 19, 2018 at 4:00 PM  > wrote:
> Hi,
> 
> you have to install gettext-devel package.
> 
> Thanks,
> Alex
> 
> 
>> Am 18.04.2018 um 06:56 schrieb Willy Mularto > >:
>> 
>> Hi,
>> I receive this error during bootstrap.sh, any clue to solve?
>> 
>> + export WANT_AUTOMAKE=1.8
>> + which glibtoolize
>> + 
>> + libtoolize --copy --automake --force
>> + aclocal
>> aclocal: warning: autoconf input should be named 'configure.ac 
>> ', not 'configure.in '
>> configure.in:261 : warning: macro 'AM_ICONV' not 
>> found in library
>> + autoheader
>> autoheader: warning: missing template: ENABLE_COOKIES
>> autoheader: Use AC_DEFINE([ENABLE_COOKIES], [], [Description])
>> autoheader: warning: missing template: GW_NAME
>> autoheader: warning: missing template: GW_VERSION
>> autoheader: warning: missing template: HAVE_CASS
>> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_3
>> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_5
>> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_6
>> autoheader: warning: missing template: HAVE_GSOAP
>> autoheader: warning: missing template: HAVE_MYSQL
>> autoheader: warning: missing template: HAVE_NFTW
>> autoheader: warning: missing template: HAVE_PCRE
>> autoheader: warning: missing template: HAVE_PGSQL
>> autoheader: warning: missing template: HAVE_PTHREAD_RWLOCK
>> autoheader: warning: missing template: HAVE_PTHREAD_SPINLOCK_T
>> autoheader: warning: missing template: HAVE_REDIS
>> autoheader: warning: missing template: HAVE_REGEX
>> autoheader: warning: missing template: HAVE_SDB
>> autoheader: warning: missing template: HAVE_SEMAPHORE
>> autoheader: warning: missing template: HAVE_SQLITE
>> autoheader: warning: missing template: HAVE_SQLITE3
>> autoheader: warning: missing template: HAVE_UCONTEXT
>> autoheader: warning: missing template: HAVE_WTLS_OPENSSL
>> autoheader: warning: missing template: HAVE___FUNCTION__
>> autoheader: warning: missing template: HAVE___FUNC__
>> autoheader: warning: missing template: LIBPCRE_VERSION
>> autoheader: warning: missing template: LIBSDB_VERSION
>> autoheader: warning: missing template: LOG_TIMESTAMP_LOCALTIME
>> autoheader: warning: missing template: MUTEX_STATS
>> autoheader: warning: missing template: NO_GWASSERT
>> autoheader: warning: missing template: NO_SMS
>> autoheader: warning: missing template: NO_WAP
>> autoheader: warning: missing template: SUFFIX
>> autoheader: warning: missing template: USE_GWMEM_CHECK
>> autoheader: warning: missing template: USE_GWMEM_NATIVE
>> autoheader: warning: missing template: USE_GWMEM_SLOW
>> autoheader: warning: missing template: USE_KEEPALIVE
>> autoheader: warning: missing template: WS_DEBUG
>> + autoconf
>> configure.in:261 : error: possibly undefined 
>> macro: AM_ICONV
>>   If this token and others are legitimate, please use m4_pattern_allow.
>>   See the Autoconf documentation.
>> + automake --add-missing --copy --gnu
>> automake: warning: autoconf input should be named 'configure.ac 
>> ', not 'configure.in '
>> configure.in:89 : warning: AM_INIT_AUTOMAKE: two- 
>> and three-arguments forms are deprecated.  For more info, see:
>> configure.in:89 : 
>> http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
>>  
>> 
>> configure.in:92 : installing './compile'
>> configure.in:89 : installing './missing'
>> 

Re: bootstrap.sh error

[amalysh]

Hi,

you have to install gettext-devel package.

Thanks,
Alex


> Am 18.04.2018 um 06:56 schrieb Willy Mularto :
> 
> Hi,
> I receive this error during bootstrap.sh, any clue to solve?
> 
> + export WANT_AUTOMAKE=1.8
> + which glibtoolize
> + 
> + libtoolize --copy --automake --force
> + aclocal
> aclocal: warning: autoconf input should be named 'configure.ac 
> ', not 'configure.in '
> configure.in:261 : warning: macro 'AM_ICONV' not 
> found in library
> + autoheader
> autoheader: warning: missing template: ENABLE_COOKIES
> autoheader: Use AC_DEFINE([ENABLE_COOKIES], [], [Description])
> autoheader: warning: missing template: GW_NAME
> autoheader: warning: missing template: GW_VERSION
> autoheader: warning: missing template: HAVE_CASS
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_3
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_5
> autoheader: warning: missing template: HAVE_FUNC_GETHOSTBYNAME_R_6
> autoheader: warning: missing template: HAVE_GSOAP
> autoheader: warning: missing template: HAVE_MYSQL
> autoheader: warning: missing template: HAVE_NFTW
> autoheader: warning: missing template: HAVE_PCRE
> autoheader: warning: missing template: HAVE_PGSQL
> autoheader: warning: missing template: HAVE_PTHREAD_RWLOCK
> autoheader: warning: missing template: HAVE_PTHREAD_SPINLOCK_T
> autoheader: warning: missing template: HAVE_REDIS
> autoheader: warning: missing template: HAVE_REGEX
> autoheader: warning: missing template: HAVE_SDB
> autoheader: warning: missing template: HAVE_SEMAPHORE
> autoheader: warning: missing template: HAVE_SQLITE
> autoheader: warning: missing template: HAVE_SQLITE3
> autoheader: warning: missing template: HAVE_UCONTEXT
> autoheader: warning: missing template: HAVE_WTLS_OPENSSL
> autoheader: warning: missing template: HAVE___FUNCTION__
> autoheader: warning: missing template: HAVE___FUNC__
> autoheader: warning: missing template: LIBPCRE_VERSION
> autoheader: warning: missing template: LIBSDB_VERSION
> autoheader: warning: missing template: LOG_TIMESTAMP_LOCALTIME
> autoheader: warning: missing template: MUTEX_STATS
> autoheader: warning: missing template: NO_GWASSERT
> autoheader: warning: missing template: NO_SMS
> autoheader: warning: missing template: NO_WAP
> autoheader: warning: missing template: SUFFIX
> autoheader: warning: missing template: USE_GWMEM_CHECK
> autoheader: warning: missing template: USE_GWMEM_NATIVE
> autoheader: warning: missing template: USE_GWMEM_SLOW
> autoheader: warning: missing template: USE_KEEPALIVE
> autoheader: warning: missing template: WS_DEBUG
> + autoconf
> configure.in:261 : error: possibly undefined macro: 
> AM_ICONV
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> + automake --add-missing --copy --gnu
> automake: warning: autoconf input should be named 'configure.ac 
> ', not 'configure.in '
> configure.in:89 : warning: AM_INIT_AUTOMAKE: two- 
> and three-arguments forms are deprecated.  For more info, see:
> configure.in:89 : 
> http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
>  
> 
> configure.in:92 : installing './compile'
> configure.in:89 : installing './missing'
> utils/Makefile.am: installing './depcomp'
> automake: warning: autoconf input should be named 'configure.ac 
> ', not 'configure.in '
> 
> Thanks
> 
> 
> 
> So Far Express VPN still the fastest
> https://www.expressrefer.com/refer-friend?referrer_id=15939000_campaign=referrals_medium=copy_link_source=referral_dashboard
>  
> 

Re: Inverted Exclamation mark and question mark issue.

[amalysh]

Hi,

you have to send in UTF-8 with coding=0 (for inverted exclamation mark: 
text=%C2%A1=0).
If it doesn’t work please check your smpp debug logs and check if submit_sm has 
correct values in message body
and if yes then SMSC doing something wrong.

Thanks,
Alex


> Am 04.04.2018 um 07:27 schrieb Wan Md Arif Noor Bin. Wan Nizam 
> :
> 
> Hello Users,
>  
> I’m having an issue with sending both inverted exclamation mark (¡) and 
> inverted question mark (¿) , it seems like it was converted to B! and B? 
> instead.
>  
> Tried with all below parameter but none working except for UCS-2 which I want 
> to avoid.
>  
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿
>  
> "
>   Result : B?
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=%C2%BF
>  
> "
>  Result :B?
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿=0=1
>  
> "
>  Result : ‘
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=%C2%BF=0=1
>  
> "
>  Result : ‘
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿=0=0
>  
> "
>  Result : B?
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=%C2%BF=0=0
>  
> "
>  Result : B?
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿=0=ISO-8859-1=1
>  
> "Result
>  : ?’
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿=0=ISO-8859-1=1
>  
> "Result
>  : ?’
>  
> Tried with charset UTF-8 and ASCII, but same with same result. Please advise 
> what else can be done to get this working?
>  
> Config:
>  
> group = core
> admin-port = 13005
> smsbox-port = 13007
> sms-resend-retry = 10
> admin-password = admin
> box-deny-ip = "*.*.*.*"
> box-allow-ip = ""
> access-log = /opt/kannel/smpp_access.log
> access-log-format = "[SMSC:%i] [from:%p] [to:%P] [msg:%L:%b] [FID:%F]"
> store-type = file
> store-location = "/opt/kannel/smpp.store"
> store-dump-freq = 100
>  
> group = smsbox
> bearerbox-host = 127.0.0.1
> sendsms-port = 13017
> http-request-retry = 3
> http-queue-delay = 5
> reply-couldnotfetch = "Please wait"
> log-file = "/opt/kannel/smsbox/smsbox.log"
> log-level = 0
>  
> group = smsc
> smsc = smpp
> smsc-id = smppConnection2
> allowed-smsc-id = "smppConnection2"
> host =
> port =
> system-type = ""
> address-range = "1234"
> smsc-username = ""
> smsc-password = ""
> source-addr-ton = 0
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi = 1
> interface-version = 52
> throughput = 15
> alt-charset = "utf-8"
> connection-timeout = 60
> max-pending-submits = 10
> enquire-link-interval = 20
> transceiver-mode = 0
> log-file = "/opt/kannel/bearerbox/debug.log"
> log-level = 0
> reconnect-delay = 2
>  
> group = sendsms-user
> username = smsSMPP2
> password = smsPass
> max-messages  = 10
> concatenation = true
> default-smsc = smppConnection2
>  
> group = sms-service
> keyword = default
> accepted-smsc = smppConnection2
> get-url = "
> max-messages = 0
>   concatenation = true

Re: Inverted Exclamation mark and question mark issue.

[amalysh]

This is in most cases wrong:

2018-04-04 17:17:39 [10745] [7] DEBUG:   short_message:
2018-04-04 17:17:39 [10745] [7] DEBUG:Octet string at 0x7efe78000c40:
2018-04-04 17:17:39 [10745] [7] DEBUG:  len:  2
2018-04-04 17:17:39 [10745] [7] DEBUG:  size: 3
2018-04-04 17:17:39 [10745] [7] DEBUG:  immutable: 0
2018-04-04 17:17:39 [10745] [7] DEBUG:  data: c2 a1 
..
2018-04-04 17:17:39 [10745] [7] DEBUG:Octet string dump ends.

You are sending as UTF-8. Please align your alt-charset with a smsc default 
charset.

> dest-addr-ton = 1
> dest-addr-npi = 1
> interface-version = 52
> throughput = 15
> alt-charset = "utf-8"

^

Thanks,
Alex




> Am 04.04.2018 um 12:24 schrieb Wan Md Arif Noor Bin. Wan Nizam 
> :
> 
> Hi There,
>  
> Thanks for replying, I already tested using that parameter, but I keep 
> receiving “B?”.
> Below are the debug log.
>  
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=601132495424=%C2%A1=0=UTF-8
>  
> "
>  
> 2018-04-04 17:17:39 [10745] [7] DEBUG: SMPP PDU 0x7efe78000a10 dump:
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   type_name: submit_sm
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   command_id: 4 = 0x0004
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   command_status: 0 = 0x
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   sequence_number: 56414 = 0xdc5e
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   service_type: NULL
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   source_addr_ton: 0 = 0x
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   source_addr_npi: 1 = 0x0001
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   source_addr: "6"
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   destination_addr: "601132495424"
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   esm_class: 3 = 0x0003
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   protocol_id: 0 = 0x
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   priority_flag: 0 = 0x
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   schedule_delivery_time: NULL
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   validity_period: NULL
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   registered_delivery: 0 = 0x
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   replace_if_present_flag: 0 = 
> 0x
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   data_coding: 0 = 0x
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   sm_default_msg_id: 0 = 0x
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   sm_length: 2 = 0x0002
> 2018-04-04 17:17:39 [10745] [7] DEBUG:   short_message:
> 2018-04-04 17:17:39 [10745] [7] DEBUG:Octet string at 0x7efe78000c40:
> 2018-04-04 17:17:39 [10745] [7] DEBUG:  len:  2
> 2018-04-04 17:17:39 [10745] [7] DEBUG:  size: 3
> 2018-04-04 17:17:39 [10745] [7] DEBUG:  immutable: 0
> 2018-04-04 17:17:39 [10745] [7] DEBUG:  data: c2 a1   
>   ..
> 2018-04-04 17:17:39 [10745] [7] DEBUG:Octet string dump ends.
> 2018-04-04 17:17:39 [10745] [7] DEBUG: SMPP PDU dump ends.
>  
> However it works correctly when sending with coding=2, but by using that it 
> halved the SMS length.  Appreciate your help in this.
>  
> Cheers,
> Arif Noor
>  
> From: Alexander Malysh  On Behalf Of amal...@kannel.org
> Sent: Wednesday, April 04, 2018 4:40 PM
> To: Wan Md Arif Noor Bin. Wan Nizam 
> Cc: users@kannel.org
> Subject: Re: Inverted Exclamation mark and question mark issue.
>  
> Hi,
>  
> you have to send in UTF-8 with coding=0 (for inverted exclamation mark: 
> text=%C2%A1=0).
> If it doesn’t work please check your smpp debug logs and check if submit_sm 
> has correct values in message body
> and if yes then SMSC doing something wrong.
>  
> Thanks,
> Alex
>  
> 
> 
> Am 04.04.2018 um 07:27 schrieb Wan Md Arif Noor Bin. Wan Nizam 
> >:
>  
> Hello Users,
>  
> I’m having an issue with sending both inverted exclamation mark (¡) and 
> inverted question mark (¿) , it seems like it was converted to B! and B? 
> instead.
>  
> Tried with all below parameter but none working except for UCS-2 which I want 
> to avoid.
>  
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=¿
>  
> "
>   Result : B?
> curl 
> "http://localhost:13017/cgi-bin/sendsms?username=smsSMPP2=smsPass=6=60113**=%C2%BF
>  
> "
>  Result :B?
> curl 
> 

Re: Compile Error: No rule to make target 'am--refresh'

[amalysh]

no objections, go for it.

Thanks,
Alex


> Am 06.03.2018 um 11:51 schrieb Stipe Tolj :
> 
> Am 06.03.2018 11:18, schrieb Alexander Malysh:
>> Hi,
>> 
>> we have to delete configure and stuff because it should not be there only in 
>> the release tar archive.
> 
> ok, agree. Let's add this to an BUILD file so people know how to deal with it 
> when they do svn trunk checkouts.
> 
> Shall I proceed and also roll for a new devel release? I guess we want to go 
> for the 1.6.0 branch rather then staying in 1.5.x.
> 
> Any objections?
> 
> Cheers,
> Stipe
> 
> -- 
> Best Regards,
> Stipe Tolj
> 
> ---
> Düsseldorf, NRW, Germany
> 
> Kannel Foundation tolj.org system architecture
> http://www.kannel.org/http://www.tolj.org/
> 
> stolj at kannel.org   st at tolj.org
> ---
> 

Re: Compile Error: No rule to make target 'am--refresh'

[amalysh]

Hi,

please call: ./bootstrap.sh before configure.

Thanks,
Alex


> Am 03.03.2018 um 18:41 schrieb Willy Mularto :
> 
> Hi list,
> I'm not sure what's going on, I just tried to install Kannel (snapshot 
> version) on to a fresh Ubuntu LTS 16.04 (Xenial Xerus), somehow it stop 
> during make with error: "No rule to make target 'am--refresh'". Does anybody 
> experience this error? Any solution to this matter? Thanks.
> 

Re: Different TImezone on default log format vs custom log format

[amalysh]

Hi,

sure it will impact, or we leave %t as is (GMT) and add new escape sequence…

Alex


> Am 18.01.2018 um 23:49 schrieb Willy Mularto :
> 
> Hi Alex,
> Thanks for the reply, I think it's not a major issue but will be good if we 
> can do a fix. BTW what do you mean with "will break many installations"? will 
> it impact current installation when someone upgrade it? 
> 
> On Thu, Jan 18, 2018 at 11:19 PM,  > wrote:
> Hi Willy,
> 
> yes, you are right, this is not expected and looks like a bug BUT if we fix 
> it, it will break many installations :-(
> 
> We have to synchronise and merge URL and access log format escape codes.
> 
> Thanks,
> Alex
> 
> 
>> Am 18.01.2018 um 01:21 schrieb Willy Mularto > >:
>> 
>> Hi All,
>> I found that there's difference timezone used on log file by Kannel when we 
>> set it as default and when we set a custom log format. What makes this 
>> happen? I am on GMT+7 when I use custom log the result will be like this 
>> (use GMT which is not expected):
>> 
>> 2018-01-17 23:52:25 Sent SMS [SMSC:XXX].
>> 018-01-17 23:52:25 Receive DLR [SMSC:XXX]
>> 
>> But when use default log format will be  (use GMT+7 which is correct based 
>> on my localtime):
>> 
>> 2018-01-18 07:01:20 Sent SMS [SMSC:XXX]
>> 2018-01-18 07:01:20 Receive DLR [SMSC:XXX]
> 
> 

Re: Different TImezone on default log format vs custom log format

[amalysh]

Hi Willy,

yes, you are right, this is not expected and looks like a bug BUT if we fix it, 
it will break many installations :-(

We have to synchronise and merge URL and access log format escape codes.

Thanks,
Alex

> Am 18.01.2018 um 01:21 schrieb Willy Mularto :
> 
> Hi All,
> I found that there's difference timezone used on log file by Kannel when we 
> set it as default and when we set a custom log format. What makes this 
> happen? I am on GMT+7 when I use custom log the result will be like this (use 
> GMT which is not expected):
> 
> 2018-01-17 23:52:25 Sent SMS [SMSC:XXX].
> 018-01-17 23:52:25 Receive DLR [SMSC:XXX]
> 
> But when use default log format will be  (use GMT+7 which is correct based on 
> my localtime):
> 
> 2018-01-18 07:01:20 Sent SMS [SMSC:XXX]
> 2018-01-18 07:01:20 Receive DLR [SMSC:XXX]

Re: Asterisk-Kannel integration project version 0.0.1 release notes

[amalysh]

Hi,

what I mean, is there a possibility in Asterisk to call HTTP url instead of 
this plugin?
If there is a possibility , then it should be used with smsbox or http smsc 
module in bearerbox instead of using internal
Kannel structs and compile a new plugin each time kannel changes its internal 
struct.

Thanks,
Alex


> Am 21.12.2017 um 18:40 schrieb mosbah abdelkader 
> :
> 
> Hello Alex,
> 
> Thank you for your feedback.
> 
> May be I havn't understood exactly your meaning by http url call in
> asterisk and its relation to the project. But, the main idea behind
> this project is to give asterisk users another way to send sms from
> dialplan. Because, the actual implementation within asterisk to send
> sms is by using app_sms which only sends sms using an external modem
> (no smpp and other protocols that kannel supports).
> 
> BR.
> 
> On 12/21/17, amal...@kannel.org  
> > wrote:
>> Hi,
>> 
>> thanks for interest on kannel project!
>> Does Asterisk doesn’t support HTTP URL call ? I just ask because with this
>> module you will use Kannel internal structs, what is not a preferred method
>> to
>> communicate with Kannel.
>> 
>> Thanks,
>> Alex
>> 
>> 
>>> Am 21.12.2017 um 09:00 schrieb mosbah abdelkader
>>> :
>>> 
>>> Hello,
>>> 
>>> We are proud to announce the first release 0.0.1 version of
>>> kannel-asterisk integration project. The goal of this project is to allow
>>> asterisk users to use kannel capabilities like SMS sending and receiving.
>>> Please visit https://asterisk-kannel.sourceforge.io/
>>> >> > for more information. You can
>>> download the release files at:
>>> https://sourceforge.net/projects/asterisk-kannel/files/ 
>>> 
>>> >> >
>>> 
>>> This version 0.0.1 includes an asterisk app module called app_mt.c which
>>> can be used from the dial plan to send SMS MT (mobile terminated).
>>> 
>>> ---technical details:
>>> app_mt.c is an asterisk module (a dialplan app called mt) that uses kannel
>>> C API to connect to kannel bearerbox as an smsbox and send sms mt
>>> messages. It also integrates a thread for receiving ack's and delivery
>>> reports (dlr) from bearerbox.
>>> 
>>> ---requirements:
>>> -Asterisk source.
>>> -Kannel compiled libs and header files (compilation of kannel is not
>>> covered here).
>>> 
>>> ---config:
>>> -actually the config is done in the source code itself. Adjust the
>>> following parameters to fit your setup before compiling and linking the
>>> app:
>>> static char* dflt_bb_host = "#";//default kannel bearerbox IP
>>> address
>>> static long dflt_bb_port = 13001;//kannel bearerbox smsbox-port port
>>> static int dflt_bb_ssl = 0;//default kannel bearerbox smsbox-port ssl let
>>> it 0 if you don't want to use ssl
>>> static char* dflt_smsbox_id = "astb";//default smsbox id
>>> static char* dflt_service = "csvc";//default service name
>>> static char* dflt_account = "supacc";//default account name
>>> static char* dflt_from = "18555";//default sender number
>>> static char* dflt_to = "1";//default receiver number
>>> static char* dflt_smsc_id = "fake-smsc-1";//default smsc-id used to route
>>> the sms
>>> static char* dflt_dlr_url = "http://127.0.0.1:40001 
>>> 
>>> ";//default dlr url
>>> static int dflt_dlr_mask = 31;//default dlr mask
>>> static char* dflt_sms = "Dialplan extension 400 get executed!";//default
>>> sms text
>>> 
>>> ---compiling:
>>> compilation is similar to any other asterisk module. Just copy the source
>>> file to asterisk apps folder, modify your toolchain by adding kannel
>>> header files and libs locations. Compile asterisk as usual. you will get
>>> app_mt.so generated.
>>> 
>>> ---using:
>>> -# cp app_mt.so /usr/lib/asterisk/modules
>>> -# asterisk -x "module load app_mt.so"
>>> -modify your dialplan to add a test extension for app_mt:
>>> exten => 400,1,mt()
>>>same => n,Hangup()
>>> -call extension 400 from your device, an sms mt will be sent to the
>>> receiver number configured above.
>>> 
>>> ---roadmap:
>>> -read default config parameters from file.
>>> -pass sms parameters from the dialplan.
>>> -send sms from cli/manager/rest/...etc.
>>> -...etc. Any suggestion is welcome.
>>> 
>>> Any feedback is welcome.
>>> 
>>> Best regards.

Re: Multipart sms sending behaviour - Sending all the parts of a multipart 1 after the other

[amalysh]

Hi Grant,

as far as I see 1.4.4 already using prio queue and Kannel does it best to send 
all messages/parts in the right order but it’s impossible to do
in all the cases. What you can do, as a workaround, to add a delay between 
sending, e.g. 20 longs msgs then min 1 sec delay and other 20 msgs.

Thanks,
Alex


> Am 20.12.2017 um 08:25 schrieb Grant Saicom :
> 
> Hi Alex
> 
> Thank you for your reply and time. Kannel is splitting the messages before 
> sending them down the bind to the SMSC. The whole messages arrives via smsbox 
> and is then passed to bearerbox for delivery to SMSC via smpp.
> 
> The problem is that if I have more than 40 multipart messages in the queue, 
> the sending will stop as bearerbox submits one part of each queued message as 
> described. Because of the way the server works, it locks up all the available 
> max pending sessions.
> 
> I need kannel to send each multipart of the whole sequentially. Borrowing 
> from printing jargon, I need the multipart sending to be collated: a1, a2, a3 
> ; b1, b2, b3 ; c1, c2 ; d1, d2, d3
> 
> Thanks,
> Grant
>> On 20 Dec 2017, at 00:37, amal...@kannel.org wrote:
>> 
>> Hi,
>> 
>> who is responsible for splitting long messages? you should let Kannel do it 
>> for you, then Kannel take care to send
>> all parts via the same SMSC and in the right order.
>> 
>> Thanks,
>> Alex
>> 
>> 
>>> Am 19.12.2017 um 14:32 schrieb Grant Saicom :
>>> 
>>> Hi Kannel Users
>>> 
>>> I have an issue which I need to address with respect to how kannel(1.44) 
>>> sends multipart messages to a SMSC.
>>> 
>>> Let me explain the situation/limitations:
>>> 
>>> -I have a server which manages and distributes smses to my modems.
>>> -I communicate to this server via smpp using bearerbox.
>>> -These modems are hosted on gateways at various locations linked via IP.
>>> -The server sends the messages to the gateways which then send to the 
>>> modems via serial.
>>> -The server requires that it has the entire message (all multiparts) before 
>>> it can send it to the gateway and ultimately the modem for sending via GSM.
>>> -I have a max pending sms limit of 40 on the server. This is the licensing 
>>> model.
>>> 
>>> Example Scenario of the issue:
>>> If I have 100 messages with 200 characters in them, kannel sends the first 
>>> part of the first 40 messages i.e.
>>> 
>>> message1 : 1 of 2
>>> message2 : 1 of 2
>>> message3 : 1 of 2
>>> message4 : 1 of 2
>>> …
>>> message39 : 1 of 2
>>> message40 : 1 of 2
>>> 
>>> The server acks these messages, but it starts rejecting any further 
>>> messages because its max pending queue is now full. None of these messages 
>>> will go out. The client side will eventually time-out these messages and 
>>> fail them.
>>> 
>>> How do I get bearerbox to send the messages like this:
>>> 
>>> message1 : 1 of 2
>>> message1 : 1 of 2
>>> message2 : 1 of 2
>>> message2 : 2 of 2
>>> …
>>> 
>>> message39 : 1 of 2
>>> message39 : 2 of 2
>>> message40 : 1 of 2
>>> message40 : 2 of 2
>>> 
>>> I have not found anything in the documentation that indicates how I could 
>>> do this.
>>> 
>>> Kind regards
>>> Grant
>>> 
>>> 
>> 
> 

Re: Asterisk-Kannel integration project version 0.0.1 release notes

[amalysh]

Hi,

thanks for interest on kannel project!
Does Asterisk doesn’t support HTTP URL call ? I just ask because with this 
module you will use Kannel internal structs, what is not a preferred method to
communicate with Kannel.

Thanks,
Alex


> Am 21.12.2017 um 09:00 schrieb mosbah abdelkader 
> :
> 
> Hello,
> 
> We are proud to announce the first release 0.0.1 version of kannel-asterisk 
> integration project. The goal of this project is to allow asterisk users to 
> use kannel capabilities like SMS sending and receiving. Please visit 
> https://asterisk-kannel.sourceforge.io/ 
>  for more information. You can 
> download the release files at: 
> https://sourceforge.net/projects/asterisk-kannel/files/ 
> 
> 
> This version 0.0.1 includes an asterisk app module called app_mt.c which can 
> be used from the dial plan to send SMS MT (mobile terminated).
> 
> ---technical details:
> app_mt.c is an asterisk module (a dialplan app called mt) that uses kannel C 
> API to connect to kannel bearerbox as an smsbox and send sms mt messages. It 
> also integrates a thread for receiving ack's and delivery reports (dlr) from 
> bearerbox.
> 
> ---requirements:
> -Asterisk source.
> -Kannel compiled libs and header files (compilation of kannel is not covered 
> here).
> 
> ---config:
> -actually the config is done in the source code itself. Adjust the following 
> parameters to fit your setup before compiling and linking the app:
> static char* dflt_bb_host = "#";//default kannel bearerbox IP 
> address
> static long dflt_bb_port = 13001;//kannel bearerbox smsbox-port port
> static int dflt_bb_ssl = 0;//default kannel bearerbox smsbox-port ssl let it 
> 0 if you don't want to use ssl
> static char* dflt_smsbox_id = "astb";//default smsbox id
> static char* dflt_service = "csvc";//default service name
> static char* dflt_account = "supacc";//default account name
> static char* dflt_from = "18555";//default sender number
> static char* dflt_to = "1";//default receiver number
> static char* dflt_smsc_id = "fake-smsc-1";//default smsc-id used to route the 
> sms
> static char* dflt_dlr_url = "http://127.0.0.1:40001 
> ";//default dlr url
> static int dflt_dlr_mask = 31;//default dlr mask
> static char* dflt_sms = "Dialplan extension 400 get executed!";//default sms 
> text
> 
> ---compiling:
> compilation is similar to any other asterisk module. Just copy the source 
> file to asterisk apps folder, modify your toolchain by adding kannel header 
> files and libs locations. Compile asterisk as usual. you will get app_mt.so 
> generated.
> 
> ---using:
> -# cp app_mt.so /usr/lib/asterisk/modules
> -# asterisk -x "module load app_mt.so"
> -modify your dialplan to add a test extension for app_mt: 
> exten => 400,1,mt()
> same => n,Hangup()
> -call extension 400 from your device, an sms mt will be sent to the receiver 
> number configured above.
> 
> ---roadmap:
> -read default config parameters from file.
> -pass sms parameters from the dialplan.
> -send sms from cli/manager/rest/...etc.
> -...etc. Any suggestion is welcome.
> 
> Any feedback is welcome.
> 
> Best regards.
> 

Re: Multipart sms sending behaviour - Sending all the parts of a multipart 1 after the other

[amalysh]

Hi,

who is responsible for splitting long messages? you should let Kannel do it for 
you, then Kannel take care to send
all parts via the same SMSC and in the right order.

Thanks,
Alex
 

> Am 19.12.2017 um 14:32 schrieb Grant Saicom :
> 
> Hi Kannel Users
> 
> I have an issue which I need to address with respect to how kannel(1.44) 
> sends multipart messages to a SMSC.
> 
> Let me explain the situation/limitations:
> 
> -I have a server which manages and distributes smses to my modems.
> -I communicate to this server via smpp using bearerbox.
> -These modems are hosted on gateways at various locations linked via IP.
> -The server sends the messages to the gateways which then send to the modems 
> via serial.
> -The server requires that it has the entire message (all multiparts) before 
> it can send it to the gateway and ultimately the modem for sending via GSM.
> -I have a max pending sms limit of 40 on the server. This is the licensing 
> model.
> 
> Example Scenario of the issue:
> If I have 100 messages with 200 characters in them, kannel sends the first 
> part of the first 40 messages i.e.
> 
> message1 : 1 of 2
> message2 : 1 of 2
> message3 : 1 of 2
> message4 : 1 of 2
> …
> message39 : 1 of 2
> message40 : 1 of 2
> 
> The server acks these messages, but it starts rejecting any further messages 
> because its max pending queue is now full. None of these messages will go 
> out. The client side will eventually time-out these messages and fail them.
> 
> How do I get bearerbox to send the messages like this:
> 
> message1 : 1 of 2
> message1 : 1 of 2
> message2 : 1 of 2
> message2 : 2 of 2
> …
> 
> message39 : 1 of 2
> message39 : 2 of 2
> message40 : 1 of 2
> message40 : 2 of 2
> 
> I have not found anything in the documentation that indicates how I could do 
> this.
> 
> Kind regards
> Grant
> 
> 

Re: SSL via SMPP for SMSC connection

[amalysh]

Hi,use-ssl = true  in smsc group ?Thanks,AlexAm 18.07.2017 um 10:28 schrieb Denis Lezgin :Hi all,I'm trying to connect to supplier using SSL but Kannel wont do that and showing me following error:2017-07-11 13:13:22 [7667] [291] ERROR: conn_open_ssl: private key isn't consistent with the certificate from file /opt/kannel/etc/smsc.d/certs/cert.pem (or failed reading the file)That could be related to key itself however I'd like to know if there is any option to be connected to supplier via SSL?Like it does for ESME connections:smppbox-ssl-port = 7400ssl-server-cert-file = "/opt/kannel/etc/cert.d/cert.pem"ssl-server-key-file = "/opt/kannel/etc/cert.d/key.pem"Thank you in advance!Best Regards,

Re: Thoughput Error

[amalysh]

Hi,

please try SVN version, just fixed.

Thanks,
Alex


> Am 19.08.2016 um 08:24 schrieb Mohammed Saleem :
> 
> This is really weird. You need to trace the code how this is calculated. But 
> have you tried to increase this limit? The throughput limit doesn't limit the 
> number of MT messages. It limits the number of SMS parts. A message with 2 
> parts considered 2 not 1. Try setting the throughput to some higher value. If 
> this didn't help figuring out the issue you need to trace the code and fix 
> the math equation.
> 
> 
> On Aug 19, 2016 4:45 AM, "Arif Noor"  > wrote:
> Hi,
> 
>  
> 
> Yes I do as you can see from the log itself. My concern is the throughput 
> glitch that I already show previously. I just sending 1 MT and see what the 
> log shows.
> 
>  
> 
> “throughput limit exceeded (2695.57,2.00)”
> 
>  
> 
>  
> 
>  
> 
> From: Mohammed Saleem [mailto:mohammedsl...@gmail.com 
> ] 
> Sent: Thursday, August 18, 2016 2:08 PM
> To: Arif Noor
> Cc: users@kannel.org ; vinayak mv; ha...@aeon.pk 
> 
> Subject: RE: Thoughput Error
> 
>  
> 
> Hello Arif
> Are you setting throughput limit in your SMPP  config?
> 
>  
> 
> On Aug 18, 2016 4:24 AM, "Arif Noor"  > wrote:
> 
> Hi Hamza,
> 
>  
> 
> It’s not really about the throttling, the issue is I’m sending 1 MT and it 
> logged as 2k which Is absolutely weird. Kindly view the log again.
> 
> 3228010:2016-08-12 12:31:26 [11927] [8] DEBUG: SMPP[smppConnection3]: 
> throughput limit exceeded (2695.57,2.00)
> 
>  
> 
> Best Regards,
> 
> Arif Noor,
> 
>  
> 
> From: ha...@aeon.pk  [mailto:ha...@aeon.pk 
> ] 
> Sent: Wednesday, August 17, 2016 4:24 PM
> To: vinayak mv
> Cc: Arif Noor; users@kannel.org 
> Subject: Re: Thoughput Error
> 
>  
> 
> Your operator is throttling your traffic. Ask them to check either TPS or 
> window size against your connection.
> 
>  
> 
> On Mon, Aug 15, 2016 at 7:49 AM, vinayak mv  > wrote:
> 
> Hi,
> 
> Im using Kannel version svn-r5164 , when i found the same throttling 
> performance issue in kannel 1.4.4 .
> 
>  
> 
> On Mon, Aug 15, 2016 at 7:10 AM, Arif Noor  > wrote:
> 
> Hi Kannel Users,
> 
>  
> 
> I have noticed this weird throughput limit error when sending even 1 MT in 
> the latest svn build, is this a bug?
> 
>  
> 
> Kannel Version `svn-r5166'.
> 
>  
> 
> 3227969:2016-08-12 12:31:26 [11927] [8] DEBUG: SMPP[smppConnection3]: Sending 
> PDU:
> 
> 3227970:2016-08-12 12:31:26 [11927] [8] DEBUG: SMPP PDU 0x7f554006a320 dump:
> 
> 3227971:2016-08-12 12:31:26 [11927] [8] DEBUG:   type_name: submit_sm
> 
> 3227972:2016-08-12 12:31:26 [11927] [8] DEBUG:   command_id: 4 = 0x0004
> 
> 3227973:2016-08-12 12:31:26 [11927] [8] DEBUG:   command_status: 0 = 
> 0x
> 
> 3227974:2016-08-12 12:31:26 [11927] [8] DEBUG:   sequence_number: 45817 = 
> 0xb2f9
> 
> 3227975:2016-08-12 12:31:26 [11927] [8] DEBUG:   service_type: NULL
> 
> 3227976:2016-08-12 12:31:26 [11927] [8] DEBUG:   source_addr_ton: 0 = 
> 0x
> 
> 3227977:2016-08-12 12:31:26 [11927] [8] DEBUG:   source_addr_npi: 1 = 
> 0x0001
> 
> 3227978:2016-08-12 12:31:26 [11927] [8] DEBUG:   source_addr: "xxx"
> 
> 3227979:2016-08-12 12:31:26 [11927] [8] DEBUG:   dest_addr_ton: 1 = 0x0001
> 
> 3227980:2016-08-12 12:31:26 [11927] [8] DEBUG:   dest_addr_npi: 1 = 0x0001
> 
> 3227981:2016-08-12 12:31:26 [11927] [8] DEBUG:   destination_addr: "x"
> 
> 3227982:2016-08-12 12:31:26 [11927] [8] DEBUG:   esm_class: 67 = 0x0043
> 
> 3227983:2016-08-12 12:31:26 [11927] [8] DEBUG:   protocol_id: 0 = 0x
> 
> 3227984:2016-08-12 12:31:26 [11927] [8] DEBUG:   priority_flag: 0 = 0x
> 
> 3227985:2016-08-12 12:31:26 [11927] [8] DEBUG:   schedule_delivery_time: NULL
> 
> 3227986:2016-08-12 12:31:26 [11927] [8] DEBUG:   validity_period: NULL
> 
> 3227987:2016-08-12 12:31:26 [11927] [8] DEBUG:   registered_delivery: 1 = 
> 0x0001
> 
> 3227988:2016-08-12 12:31:26 [11927] [8] DEBUG:   replace_if_present_flag: 0 = 
> 0x
> 
> 3227989:2016-08-12 12:31:26 [11927] [8] DEBUG:   data_coding: 0 = 0x
> 
> 3227990:2016-08-12 12:31:26 [11927] [8] DEBUG:   sm_default_msg_id: 0 = 
> 0x
> 
> 3227991:2016-08-12 12:31:26 [11927] [8] DEBUG:   sm_length: 159 = 0x009f
> 
> 3227992:2016-08-12 12:31:26 [11927] [8] DEBUG:   short_message:
> 
> 3227993:2016-08-12 12:31:26 [11927] [8] DEBUG:Octet string at 
> 0x7f5540023ad0:
> 
> 3227994:2016-08-12 12:31:26 [11927] [8] DEBUG:  len:  159
> 
> 3227995:2016-08-12 12:31:26 [11927] [8] DEBUG:  size: 1024
> 
> 3227996:2016-08-12 

Re: Store size increasing on MO

[amalysh]

comment out smsbox-route because as far as I see you don’t need it for only one 
smsbox.

Alex

> Am 25.05.2016 um 08:30 schrieb conandor :
> 
> I unable to start kannel if i comment out smsbox-id.
> 
> 2016-05-25 12:27:20 [15033] [0] PANIC: 'smsbox-route' group without valid 
> 'smsbox-id' directive!
> 
> ~ KH
> 
>> On 24 May 2016, at 7:52 PM, amal...@kannel.org  
>> wrote:
>> 
>> Hi,
>> 
>> looks like you MO routing is broken. Try to comment out smsbox-id = „mo“ in 
>> your config.
>> 
>> Alex
>> 
>>> Am 18.05.2016 um 05:12 schrieb conandor >> >:
>>> 
>>> I have a kannel bearerbox dedicated to MO only. And I notice the store size 
>>> keep increasing. Why is it so?
>>> 
>>> Kannel bearerbox version `1.4.4'.
>>> Build `Oct  9 2015 03:35:52', compiler `4.4.7 20120313 (Red Hat 4.4.7-16)'.
>>> System Linux, release 2.6.32-573.8.1.el6.x86_64, version #1 SMP Fri Sep 25 
>>> 19:24:22 EDT 2015, machine x86_64.
>>> Hostname localhost, IP 127.0.0.1.
>>> Libxml version 2.7.6.
>>> Using native malloc.
>>> 
>>> 
>>> Status: running, uptime 0d 0h 9m 19s
>>> 
>>> WDP: received 0 (0 queued), sent 0 (0 queued)
>>> 
>>> SMS: received 21022 (0 queued), sent 0 (1 queued), store size 1101
>>> SMS: inbound (36.59,38.03,37.61) msg/sec, outbound (0.00,0.00,0.00) msg/sec
>>> 
>>> DLR: received 0, sent 0
>>> DLR: inbound (0.00,0.00,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec
>>> DLR: 0 queued, using internal storage
>>> 
>>> Box connections:
>>> smsbox:mo, IP 127.0.0.1 (0 queued), (on-line 0d 0h 9m 17s)  
>>> 
>>> 
>>> SMSC connections:
>> 
> 

Re: kannel services

[amalysh]

/usr/local/sbin/bearerbox -v 1 /path/to/kannel.conf &

is not a good style. Kannel has it’s own daemon switch ‚-d‘

Alex

> Am 17.05.2016 um 09:53 schrieb Mike Nwaogu :
> 
> Sorry John,
> I guess everyone was waiting for you to figure it out.
> This is what I used sometime back. Change the path to match yours.
> 
> #=
> /usr/local/sbin/bearerbox -v 1 /path/to/kannel.conf &
> /usr/local/sbin/smsbox -v 1 /path/to/kannel.conf &
> #=
> Best Regards,
> 
> 
> 
> On Monday, May 16, 2016 3:49 PM, John Mwale  wrote:
> 
> 
> good day,
> 
> Has some one from this group managed to add kannel service to /etc/rc.local?
> -- 
> Tapiwa Mwale,
> mobile number +260 97 9 947571
> 
> 
> 

Re: Store size increasing on MO

[amalysh]

Hi,

looks like you MO routing is broken. Try to comment out smsbox-id = „mo“ in 
your config.

Alex

> Am 18.05.2016 um 05:12 schrieb conandor :
> 
> I have a kannel bearerbox dedicated to MO only. And I notice the store size 
> keep increasing. Why is it so?
> 
> Kannel bearerbox version `1.4.4'.
> Build `Oct  9 2015 03:35:52', compiler `4.4.7 20120313 (Red Hat 4.4.7-16)'.
> System Linux, release 2.6.32-573.8.1.el6.x86_64, version #1 SMP Fri Sep 25 
> 19:24:22 EDT 2015, machine x86_64.
> Hostname localhost, IP 127.0.0.1.
> Libxml version 2.7.6.
> Using native malloc.
> 
> 
> Status: running, uptime 0d 0h 9m 19s
> 
> WDP: received 0 (0 queued), sent 0 (0 queued)
> 
> SMS: received 21022 (0 queued), sent 0 (1 queued), store size 1101
> SMS: inbound (36.59,38.03,37.61) msg/sec, outbound (0.00,0.00,0.00) msg/sec
> 
> DLR: received 0, sent 0
> DLR: inbound (0.00,0.00,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec
> DLR: 0 queued, using internal storage
> 
> Box connections:
> smsbox:mo, IP 127.0.0.1 (0 queued), (on-line 0d 0h 9m 17s)  
> 
> 
> SMSC connections:

Re: Queuing Messages

[amalysh]

Hi,

more infos would be great. Version, which SMSC module, what is the config, etc.

Without infos, nobody can help you.

Alex

> Am 19.05.2016 um 13:02 schrieb Amelye Chatila :
> 
> Hello,
> 
> Messages get queued, we found that it is because of an I/O Error below
> 
> smsc-one.log 
>  
> 2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: I/O error or other 
> error. Re-connecting. 
> 2016-05-18 08:23:53 [6095] [41] ERROR: SMPP[smsc-one]: Couldn't connect to 
> SMS center (retrying in 10 seconds). 
>  
> bearerbox.log 
>  
> 2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued. 
> 2016-05-18 08:25:10 [6095] [10] DEBUG: Routing failed, re-queued.
> 
> Routing failed means can not find the smsc but the smsc is up. The only 
> solution we have so far is to restart.
> 
> The issue why the queue is not emptied when the bind is up again? Is this I/O 
> Error a connection error to SMSC?
> 
> Thank you!
> 

Re: Not work "priority" in settings SMSC

[amalysh]

Hi,

priority parameter is used to set prio for a message itself that is then just 
forwarded to SMSC => not your case.

what you need is preferred SMSC. Please check userguide for preferred-smsc 
config option.

Thanks,
Alex

P.S. Pogaluysta pishiti tut tolko na english, ne vse ponimayut russkij :-)
P.P.S. This question belongs to users@kannel.org  
instead of devel. 

> Am 11.02.2016 um 06:34 schrieb Беляев Владимир Николаевич :
> 
> I have 2 SMSC - the main and reserve.
> It is necessary to disable SMS with the main SMSC is automatically sent 
> through the backup SMSC.
> After the restoration of connection with the main SMSC came sms return to it.
> SMS sent via SMPP
> 
> --
> С уважением,
> Беляев В.Н.
> 
> From: spameden [mailto:spame...@gmail.com] 
> Sent: Thursday, February 11, 2016 10:29 AM
> To: Беляев Владимир Николаевич
> Cc: users@kannel.org
> Subject: Re: Not work "priority" in settings SMSC
>  
>  
>  
> 2016-02-11 7:31 GMT+03:00 Беляев Владимир Николаевич  >:
>> While you can install one primary center and the other - a reserve that it 
>> went SMS only in case of unavailability of the ground?
>  
> If I got you right you want to have multiple SMSC connections and balance 
> between them if ONLY one of the link goes down?
>  
> You can do this if you assign different smsc-id for each SMSC connection and 
> specify smsc-id at your application level, e.g.:
> for smsbox: http://.../sendsms?receiver=..._id=smscid1 
>  
> sendsms?receiver=..._id=smscid2
>  
> or for sqlbox: you can just set smsc-id="smscid1" upon INSERT.
>  
> You can monitor current state of SMSC uplinks via berearebox status page.
>> 
>> --
>> С уважением,
>> Беляев В.Н.
>> 
>> -Original Message-
>> From: users [mailto:users-boun...@kannel.org 
>> ] On Behalf Of Milan P. Stanic
>> Sent: Wednesday, February 10, 2016 11:05 PM
>> To: users@kannel.org 
>> Subject: Re: Not work "priority" in settings SMSC
>> 
>> On Wed, 2016-02-10 at 16:31, Беляев Владимир Николаевич wrote:
>> > Option does not work "priority" in settings SMSC.
>> >
>> > I set up the SMSC1 priority=0, SMSC2 priority=3, but SMS is
>> > distributed evenly.
>> >
>> > Why can this be?
>> 
>> I don't have time to look into the code but from memory I think that the 
>> priority parameter is for setting default message priority for particular 
>> SMSC and is not global parameter which set priorities between SMSCs. But, I 
>> could be wrong.
>> 
>> > Kannel 1.5.0
>> >
>> > Config:
>> > group=smsc
>> > smsc=smpp
>> >
>> > smsc-id=devino_mrk
>> >
>> > system-type=
>> >
>> > interface-version=34
>> >
>> > enquire-link-interval=270
>> >
>> > source-addr-ton=5
>> >
>> > source-addr-npi=1
>> >
>> > dest-addr-ton=1
>> >
>> > dest-addr-npi=1
>> >
>> > msg-id-type=0x00
>> >
>> > log-file="/var/log/kannel/devino_mrk.log"
>> >
>> > log-level=0
>> >
>> > priority=0
>> >
>> >
>> >
>> > # СМС-Трафик тест
>> >
>> > group=smsc
>> >
>> > smsc=smpp
>> >
>> > smsc-id=smstraffic_test
>> >
>> > system-type=smpp
>> >
>> > interface-version=34
>> >
>> > enquire-link-interval=270
>> >
>> > source-addr-ton=1
>> >
>> > source-addr-npi=1
>> >
>> > dest-addr-ton=1
>> >
>> > dest-addr-npi=1
>> >
>> > msg-id-type=0x00
>> >
>> > log-file="/var/log/kannel/smstraffic_test.log"
>> >
>> > log-level=0
>> >
>> > priority=3
>> 

Re: Not ACKED message found, will retransmit.

[amalysh]

Hi,

check your logs whether you received ACK/NACK for those sequence numbers and if 
not
ask by SMSC operator why you don’t receive ACK/NACK within > 60 sec.

Alex


> Am 14.12.2015 um 11:33 schrieb Amit Sharma (VAS) :
> 
> Hi,
> I am getting following error of “Not ACKED message found, will retransmit” 
> again and again due to which at times a single number receives multiple sms. 
> In below case “9142294005” number received 9 msgs.
>  
> Please suggest the reason for the below error & rectification to be done 
> accordingly.
>  
>  
> 2015-12-13 09:36:49 [15072] [18] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:37:55 [15072] [18] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<66>sec. ago, SEQ<187878>, DST<9142294005>
> 2015-12-13 09:40:16 [15072] [22] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:41:20 [15072] [22] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<64>sec. ago, SEQ<189768>, DST<9142294005>
> 2015-12-13 09:43:44 [15072] [8] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:46:04 [15072] [10] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:47:06 [15072] [10] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<62>sec. ago, SEQ<189281>, DST<9142294005>
> 2015-12-13 09:48:10 [15072] [16] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:49:17 [15072] [16] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<67>sec. ago, SEQ<189655>, DST<9142294005>
> 2015-12-13 09:51:18 [15072] [8] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:52:36 [15072] [8] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<78>sec. ago, SEQ<188844>, DST<9142294005>
> 2015-12-13 09:53:42 [15072] [20] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:56:09 [15072] [6] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:57:13 [15072] [6] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<64>sec. ago, SEQ<189816>, DST<9142294005>
> 2015-12-13 09:58:14 [15072] [8] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 09:59:15 [15072] [8] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<61>sec. ago, SEQ<189177>, DST<9142294005>
> 2015-12-13 10:01:47 [15072] [20] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 10:04:14 [15072] [20] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 10:05:23 [15072] [20] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<69>sec. ago, SEQ<189456>, DST<9142294005>
> 2015-12-13 10:08:14 [15072] [12] DEBUG:   destination_addr: "9142294005"
> 2015-12-13 10:09:20 [15072] [12] WARNING: SMPP[MTS]: Not ACKED message found, 
> will retransmit. SENT<66>sec. ago, SEQ<190251>, DST<9142294005>
>  
> Configuration is as follows:
>  
> group = core
> admin-port = 13010
> smsbox-port = 13012
> log-file = "/u03/kannel/logs/bearerbox.log"
> box-allow-ip = "10.130.252.160,127.0.0.1"
> access-log = "/u03/kannel/logs/bearerbox_access.log"
> dlr-storage = internal
>  
> ##TX-1##
> group = smsc
> smsc-id ="MT"
> smsc = smpp
> host =10.10.22.10
> port = 5016
> system-type = "INAPPS"
> interface-version = 34
> receive-port =0
> source-addr-ton = 1
> source-addr-npi = 1 
> dest-addr-ton = 1
> dest-addr-npi = 1
> keepalive = 30
> log-level =0
> throughput = 50
> max-pending-submits=50
> reconnect-delay = 60
> reroute = true
> log-file = "/u03/kannel/logs/smsc_conn.log"
>  
>  
> ##RX-1
> group = smsc
> smsc-id ="MTS"
> smsc = smpp
> host =10.10.22.10
> port = 0
> system-type = "INAPPS"
> receive-port =5016
> interface-version = 34
> source-addr-ton = 1
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi = 1
> keepalive = 30
> log-level =0
> reconnect-delay = 60
> reroute = true
> log-file = "/u03/kannel/logs/smsc_conn.log"
>  
> group = smsbox
> bearerbox-host = 127.0.0.1
> sendsms-port = 13013
> global-sender = YD-MTS
> log-file = "/u03/kannel/logs/smsbox.log"
> log-level = 0
>  
> #SMSBOX ROUTING
> group = smsbox-route
> smsbox-id = smsbox
> smsc-id ="MT"
>  
> group = sendsms-user
> username = smsg
> password = smsg@123
> default-smsc="MT"
> concatenation= true
> max-messages = 6
>  
>  
> group = sms-service
> keyword = default
> url = http://10.130.250.58/receivesms.php?sender=%p=%b 
> 
> catch-all = true
> max-messages = 1
> text = "This is a reply"
>  
>  
>  
>  
>  
> Best regards
> 
> Amit Sharma (VAS)
> Head, IN & VAS Operations Division
> IT Shared Service Center, CORPORATE CENTER
> 
> Sistema Shyam Teleservices Limited
> MTS Tower2 Building No. 313, Udyog Vihar Phase IV,Gurgaon 
> 
> MTS+91 913 600 6473
> Direct +91 124 481 2500
> Email:   amit.shar...@mtsindia.in 
> 
>  
>  
> 
> 
> This E-Mail may contain Confidential 

Re: Kannel SMPP integration

[amalysh]

Hi,

you mean by SMPP layer Kannel? :-) I ask because on the web site I read: Based 
on kannel.

Alex

> Am 12.11.2015 um 06:58 schrieb Saurabh Pandey :
> 
> Hi, I was the lead developer in this. There are few shortcoming like Operator 
> wise charging isn't there, but operator wise routing is there. The SMPP 
> client layer is excellent. Very high performance but the SMPP server 
> component has few shortcomings like:
> 
> 1. You cannot control the number of sessions available to smpp client
> 2. You cannot control the TPS allowed for SMPP client, yes you can achieve 
> this by setting a throughput on your own SMPP.
> 
> Other than these points the apps are great. Around 25-30 clients are using it 
> worldwide without any complaints. I know it a small number but its a 
> relatively new product.
> 
> -Cheers
> Sam
> 
> 
> 
> 
> 
> On Mon, Nov 9, 2015 at 8:40 PM, info.ubichip  > wrote:
> Hello all,
> 
>  
> 
> I was wondering if anyone has tested this SMPP layer on kannel :
> 
> http://www.smppcube.com 
> I'm not making any ads on it, just to know if anyone have some feedback on 
> this php layer ?
> 
>  
> 
> Best regards
> 
>  
> 
>