Re: SMSC - Maximum retries for message exceeded, discarding it!
alright, thanks for your help! Best Regards, On Mon, 23 Sep 2019 at 12:26, Rene Kluwen wrote: > If you want the message the be retried, then yes you can increase it. > > If you omit the option to begin with, it’s retried until the expiry time. > > > > *Van:* Denis Lezgin > *Verzonden:* maandag 23 september 2019 11:16 > *Aan:* Rene Kluwen > *CC:* users@kannel.org > *Onderwerp:* Re: SMSC - Maximum retries for message exceeded, discarding > it! > > > > alright, that makes more sense now. our config set as following: > > > > sms-resend-retry = 1 > > > > which means we should increase it? > > > > thanks > > > > Best Regards, > > > > > > [image: Afbeelding verwijderd door afzender.] > > > > > > On Mon, 23 Sep 2019 at 12:06, Rene Kluwen wrote: > > It means that you have the configuration option sms-resend-retry set in > your group = core from your Kannel config. > > It defines the number that bearerbox tries to deliver the message before > giving up. > > > > Rene Kluwen > > > > > > *Van:* Denis Lezgin > *Verzonden:* maandag 23 september 2019 11:00 > *Aan:* Rene Kluwen > *CC:* users@kannel.org > *Onderwerp:* Re: SMSC - Maximum retries for message exceeded, discarding > it! > > > > I see, the question is not regarding the 0x0008 error code as we know > its description and how to process it but the question is regarding the > "Maximum retries for message exceeded, discarding it!" > > > > Best Regards, > > > > > > [image: Afbeelding verwijderd door afzender.] > > > > > > On Mon, 23 Sep 2019 at 11:58, Rene Kluwen wrote: > > No, the smsc returns error code 0x0008. > > Kannel calls it a “system error” but the real meaning depends on your smsc. > > > > == Rene Kluwen > > > > *Van:* Denis Lezgin > *Verzonden:* maandag 23 september 2019 10:56 > *Aan:* Rene Kluwen > *CC:* users@kannel.org > *Onderwerp:* Re: SMSC - Maximum retries for message exceeded, discarding > it! > > > > Hi Rene, > > > > Thanks for quick response. > > > > You mean that the " Maximum retries for message exceeded, discarding it! " > is coming from SMSC? as for me it looks like Kannel response. > > > > Thanks > > > > Best Regards, > > > > > > [image: Afbeelding verwijderd door afzender.] > > > > > > On Mon, 23 Sep 2019 at 11:54, Rene Kluwen wrote: > > Hi Denis, > > > > It can mean different things. It’s best to inquire with your smsc > themselves to ask them what this message means. > > > > Regards, > > > > Rene Kluwen > > > > > > *Van:* users *Namens *Denis Lezgin > *Verzonden:* maandag 23 september 2019 10:51 > *Aan:* users@kannel.org > *Onderwerp:* SMSC - Maximum retries for message exceeded, discarding it! > > > > Hi guys, > > > > I noticed strange behavior of bearerbox (SMSC side of it) that most likely > have been occurring for some long time but I just noticed it. > > > > In smsc log i see following warning message: > > > > "Maximum retries for message exceeded, discarding it!" > > > > and it comes right after submit_sm_resp that has an error from SMSC within > it, for example: > > > > 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU 0x7f209a72a760 dump: > > 2019-09-23 08:29:03 [11913] [86] DEBUG: type_name: submit_sm_resp > > 2019-09-23 08:29:03 [11913] [86] DEBUG: command_id: 2147483652 = > 0x8004 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: command_status: 8 = 0x0008 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: sequence_number: 1840687 = > 0x001c162f > > 2019-09-23 08:29:03 [11913] [86] DEBUG: message_id: > > 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string at 0x7f209a78aba0: > > 2019-09-23 08:29:03 [11913] [86] DEBUG: len: 2 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: size: 3 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: immutable: 0 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: data: 04 > 23 .# > > 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string dump ends. > > 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU dump ends. > > 2019-09-23 08:29:03 [11913] [86] ERROR: SMPP[]: SMSC returned error code > 0x0008 (System Error) in response to submit_sm PDU. > > 2019-09-23 08:29:03 [11913] [86] WARNING: Maximum retries for message > exceeded, discarding it! > > > > SMSC conf: > > > > group = smsc > smsc = sm
Re: SMSC - Maximum retries for message exceeded, discarding it!
alright, that makes more sense now. our config set as following: sms-resend-retry = 1 which means we should increase it? thanks Best Regards, On Mon, 23 Sep 2019 at 12:06, Rene Kluwen wrote: > It means that you have the configuration option sms-resend-retry set in > your group = core from your Kannel config. > > It defines the number that bearerbox tries to deliver the message before > giving up. > > > > Rene Kluwen > > > > > > *Van:* Denis Lezgin > *Verzonden:* maandag 23 september 2019 11:00 > *Aan:* Rene Kluwen > *CC:* users@kannel.org > *Onderwerp:* Re: SMSC - Maximum retries for message exceeded, discarding > it! > > > > I see, the question is not regarding the 0x0008 error code as we know > its description and how to process it but the question is regarding the > "Maximum retries for message exceeded, discarding it!" > > > > Best Regards, > > > > > > [image: Afbeelding verwijderd door afzender.] > > > > > > On Mon, 23 Sep 2019 at 11:58, Rene Kluwen wrote: > > No, the smsc returns error code 0x0008. > > Kannel calls it a “system error” but the real meaning depends on your smsc. > > > > == Rene Kluwen > > > > *Van:* Denis Lezgin > *Verzonden:* maandag 23 september 2019 10:56 > *Aan:* Rene Kluwen > *CC:* users@kannel.org > *Onderwerp:* Re: SMSC - Maximum retries for message exceeded, discarding > it! > > > > Hi Rene, > > > > Thanks for quick response. > > > > You mean that the " Maximum retries for message exceeded, discarding it! " > is coming from SMSC? as for me it looks like Kannel response. > > > > Thanks > > > > Best Regards, > > > > > > [image: Afbeelding verwijderd door afzender.] > > > > > > On Mon, 23 Sep 2019 at 11:54, Rene Kluwen wrote: > > Hi Denis, > > > > It can mean different things. It’s best to inquire with your smsc > themselves to ask them what this message means. > > > > Regards, > > > > Rene Kluwen > > > > > > *Van:* users *Namens *Denis Lezgin > *Verzonden:* maandag 23 september 2019 10:51 > *Aan:* users@kannel.org > *Onderwerp:* SMSC - Maximum retries for message exceeded, discarding it! > > > > Hi guys, > > > > I noticed strange behavior of bearerbox (SMSC side of it) that most likely > have been occurring for some long time but I just noticed it. > > > > In smsc log i see following warning message: > > > > "Maximum retries for message exceeded, discarding it!" > > > > and it comes right after submit_sm_resp that has an error from SMSC within > it, for example: > > > > 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU 0x7f209a72a760 dump: > > 2019-09-23 08:29:03 [11913] [86] DEBUG: type_name: submit_sm_resp > > 2019-09-23 08:29:03 [11913] [86] DEBUG: command_id: 2147483652 = > 0x8004 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: command_status: 8 = 0x0008 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: sequence_number: 1840687 = > 0x001c162f > > 2019-09-23 08:29:03 [11913] [86] DEBUG: message_id: > > 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string at 0x7f209a78aba0: > > 2019-09-23 08:29:03 [11913] [86] DEBUG: len: 2 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: size: 3 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: immutable: 0 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: data: 04 > 23 .# > > 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string dump ends. > > 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU dump ends. > > 2019-09-23 08:29:03 [11913] [86] ERROR: SMPP[]: SMSC returned error code > 0x0008 (System Error) in response to submit_sm PDU. > > 2019-09-23 08:29:03 [11913] [86] WARNING: Maximum retries for message > exceeded, discarding it! > > > > SMSC conf: > > > > group = smsc > smsc = smpp > smsc-id = > smsc-admin-id = > allowed-smsc-id = > host = > port = > transceiver-mode = true > throughput = 30 > smsc-username = > smsc-password = > interface-version = 34 > system-type = "ESME" > source-addr-ton = 3 > source-addr-npi = 9 > dest-addr-ton = 1 > dest-addr-npi = 1 > reconnect-delay = 10 > enquire-link-interval = 60 > address-range = "" > log-file = "/opt/kannel/var/log/smsc_.log" > log-level = 0 > msg-id-type = 0x01 > source-addr-autodetect = yes > > > > The "0x0008 (System Error)" is ok, we know what this error means and > how to process it. > > > > I searched a lot about this warning message over the internet but couldn't > find anything. > > > > Is there anyway to overcome this issue maybe? > > > > > > Our system information: > > Kannel bearerbox version `svn-r5180M' > > OS: Ubuntu 14.04.4 LTS > > > > > > Thanks in advance! > > > > Best Regards, > > > > > > [image: Afbeelding verwijderd door afzender.] > >
Re: SMSC - Maximum retries for message exceeded, discarding it!
I see, the question is not regarding the 0x0008 error code as we know its description and how to process it but the question is regarding the "Maximum retries for message exceeded, discarding it!" Best Regards, On Mon, 23 Sep 2019 at 11:58, Rene Kluwen wrote: > No, the smsc returns error code 0x0008. > > Kannel calls it a “system error” but the real meaning depends on your smsc. > > > > == Rene Kluwen > > > > *Van:* Denis Lezgin > *Verzonden:* maandag 23 september 2019 10:56 > *Aan:* Rene Kluwen > *CC:* users@kannel.org > *Onderwerp:* Re: SMSC - Maximum retries for message exceeded, discarding > it! > > > > Hi Rene, > > > > Thanks for quick response. > > > > You mean that the " Maximum retries for message exceeded, discarding it! " > is coming from SMSC? as for me it looks like Kannel response. > > > > Thanks > > > > Best Regards, > > > > > > [image: Afbeelding verwijderd door afzender.] > > > > > > On Mon, 23 Sep 2019 at 11:54, Rene Kluwen wrote: > > Hi Denis, > > > > It can mean different things. It’s best to inquire with your smsc > themselves to ask them what this message means. > > > > Regards, > > > > Rene Kluwen > > > > > > *Van:* users *Namens *Denis Lezgin > *Verzonden:* maandag 23 september 2019 10:51 > *Aan:* users@kannel.org > *Onderwerp:* SMSC - Maximum retries for message exceeded, discarding it! > > > > Hi guys, > > > > I noticed strange behavior of bearerbox (SMSC side of it) that most likely > have been occurring for some long time but I just noticed it. > > > > In smsc log i see following warning message: > > > > "Maximum retries for message exceeded, discarding it!" > > > > and it comes right after submit_sm_resp that has an error from SMSC within > it, for example: > > > > 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU 0x7f209a72a760 dump: > > 2019-09-23 08:29:03 [11913] [86] DEBUG: type_name: submit_sm_resp > > 2019-09-23 08:29:03 [11913] [86] DEBUG: command_id: 2147483652 = > 0x8004 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: command_status: 8 = 0x0008 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: sequence_number: 1840687 = > 0x001c162f > > 2019-09-23 08:29:03 [11913] [86] DEBUG: message_id: > > 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string at 0x7f209a78aba0: > > 2019-09-23 08:29:03 [11913] [86] DEBUG: len: 2 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: size: 3 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: immutable: 0 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: data: 04 > 23 .# > > 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string dump ends. > > 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU dump ends. > > 2019-09-23 08:29:03 [11913] [86] ERROR: SMPP[]: SMSC returned error code > 0x0008 (System Error) in response to submit_sm PDU. > > 2019-09-23 08:29:03 [11913] [86] WARNING: Maximum retries for message > exceeded, discarding it! > > > > SMSC conf: > > > > group = smsc > smsc = smpp > smsc-id = > smsc-admin-id = > allowed-smsc-id = > host = > port = > transceiver-mode = true > throughput = 30 > smsc-username = > smsc-password = > interface-version = 34 > system-type = "ESME" > source-addr-ton = 3 > source-addr-npi = 9 > dest-addr-ton = 1 > dest-addr-npi = 1 > reconnect-delay = 10 > enquire-link-interval = 60 > address-range = "" > log-file = "/opt/kannel/var/log/smsc_.log" > log-level = 0 > msg-id-type = 0x01 > source-addr-autodetect = yes > > > > The "0x0008 (System Error)" is ok, we know what this error means and > how to process it. > > > > I searched a lot about this warning message over the internet but couldn't > find anything. > > > > Is there anyway to overcome this issue maybe? > > > > > > Our system information: > > Kannel bearerbox version `svn-r5180M' > > OS: Ubuntu 14.04.4 LTS > > > > > > Thanks in advance! > > > > Best Regards, > > > > > > [image: Afbeelding verwijderd door afzender.] > >
Re: SMSC - Maximum retries for message exceeded, discarding it!
Hi Rene, Thanks for quick response. You mean that the " Maximum retries for message exceeded, discarding it! " is coming from SMSC? as for me it looks like Kannel response. Thanks Best Regards, On Mon, 23 Sep 2019 at 11:54, Rene Kluwen wrote: > Hi Denis, > > > > It can mean different things. It’s best to inquire with your smsc > themselves to ask them what this message means. > > > > Regards, > > > > Rene Kluwen > > > > > > *Van:* users *Namens *Denis Lezgin > *Verzonden:* maandag 23 september 2019 10:51 > *Aan:* users@kannel.org > *Onderwerp:* SMSC - Maximum retries for message exceeded, discarding it! > > > > Hi guys, > > > > I noticed strange behavior of bearerbox (SMSC side of it) that most likely > have been occurring for some long time but I just noticed it. > > > > In smsc log i see following warning message: > > > > "Maximum retries for message exceeded, discarding it!" > > > > and it comes right after submit_sm_resp that has an error from SMSC within > it, for example: > > > > 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU 0x7f209a72a760 dump: > > 2019-09-23 08:29:03 [11913] [86] DEBUG: type_name: submit_sm_resp > > 2019-09-23 08:29:03 [11913] [86] DEBUG: command_id: 2147483652 = > 0x8004 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: command_status: 8 = 0x0008 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: sequence_number: 1840687 = > 0x001c162f > > 2019-09-23 08:29:03 [11913] [86] DEBUG: message_id: > > 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string at 0x7f209a78aba0: > > 2019-09-23 08:29:03 [11913] [86] DEBUG: len: 2 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: size: 3 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: immutable: 0 > > 2019-09-23 08:29:03 [11913] [86] DEBUG: data: 04 > 23 .# > > 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string dump ends. > > 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU dump ends. > > 2019-09-23 08:29:03 [11913] [86] ERROR: SMPP[]: SMSC returned error code > 0x0008 (System Error) in response to submit_sm PDU. > > 2019-09-23 08:29:03 [11913] [86] WARNING: Maximum retries for message > exceeded, discarding it! > > > > SMSC conf: > > > > group = smsc > smsc = smpp > smsc-id = > smsc-admin-id = > allowed-smsc-id = > host = > port = > transceiver-mode = true > throughput = 30 > smsc-username = > smsc-password = > interface-version = 34 > system-type = "ESME" > source-addr-ton = 3 > source-addr-npi = 9 > dest-addr-ton = 1 > dest-addr-npi = 1 > reconnect-delay = 10 > enquire-link-interval = 60 > address-range = "" > log-file = "/opt/kannel/var/log/smsc_.log" > log-level = 0 > msg-id-type = 0x01 > source-addr-autodetect = yes > > > > The "0x0008 (System Error)" is ok, we know what this error means and > how to process it. > > > > I searched a lot about this warning message over the internet but couldn't > find anything. > > > > Is there anyway to overcome this issue maybe? > > > > > > Our system information: > > Kannel bearerbox version `svn-r5180M' > > OS: Ubuntu 14.04.4 LTS > > > > > > Thanks in advance! > > > > Best Regards, > > > > > >
SMSC - Maximum retries for message exceeded, discarding it!
Hi guys, I noticed strange behavior of bearerbox (SMSC side of it) that most likely have been occurring for some long time but I just noticed it. In smsc log i see following warning message: "Maximum retries for message exceeded, discarding it!" and it comes right after submit_sm_resp that has an error from SMSC within it, for example: 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU 0x7f209a72a760 dump: 2019-09-23 08:29:03 [11913] [86] DEBUG: type_name: submit_sm_resp 2019-09-23 08:29:03 [11913] [86] DEBUG: command_id: 2147483652 = 0x8004 2019-09-23 08:29:03 [11913] [86] DEBUG: command_status: 8 = 0x0008 2019-09-23 08:29:03 [11913] [86] DEBUG: sequence_number: 1840687 = 0x001c162f 2019-09-23 08:29:03 [11913] [86] DEBUG: message_id: 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string at 0x7f209a78aba0: 2019-09-23 08:29:03 [11913] [86] DEBUG: len: 2 2019-09-23 08:29:03 [11913] [86] DEBUG: size: 3 2019-09-23 08:29:03 [11913] [86] DEBUG: immutable: 0 2019-09-23 08:29:03 [11913] [86] DEBUG: data: 04 23 .# 2019-09-23 08:29:03 [11913] [86] DEBUG:Octet string dump ends. 2019-09-23 08:29:03 [11913] [86] DEBUG: SMPP PDU dump ends. 2019-09-23 08:29:03 [11913] [86] ERROR: SMPP[]: SMSC returned error code 0x0008 (System Error) in response to submit_sm PDU. 2019-09-23 08:29:03 [11913] [86] WARNING: Maximum retries for message exceeded, discarding it! SMSC conf: group = smsc smsc = smpp smsc-id = smsc-admin-id = allowed-smsc-id = host = port = transceiver-mode = true throughput = 30 smsc-username = smsc-password = interface-version = 34 system-type = "ESME" source-addr-ton = 3 source-addr-npi = 9 dest-addr-ton = 1 dest-addr-npi = 1 reconnect-delay = 10 enquire-link-interval = 60 address-range = "" log-file = "/opt/kannel/var/log/smsc_.log" log-level = 0 msg-id-type = 0x01 source-addr-autodetect = yes The "0x0008 (System Error)" is ok, we know what this error means and how to process it. I searched a lot about this warning message over the internet but couldn't find anything. Is there anyway to overcome this issue maybe? Our system information: Kannel bearerbox version `svn-r5180M' OS: Ubuntu 14.04.4 LTS Thanks in advance! Best Regards,
Extremely low TPS on SMSC connection
Hello all, We're facing following issue. I noticed that there is some kind of bug with Kannel. We have high throughput with SMSC and that happens with all SMSCs and ESME connections. The TPS is extremely low, around 2 TPS while for example we have 100 sms/s, or no limits if that comes to internal ESMEs. Below are our Kannel configs for internal ESME where this issue is urgent to be fixed (sensitive data was removed or replaced) - we do use commercial version of SMPPbox and bearerbox 1.5: 1) bearerbox.conf: group = core admin-port = 13000 admin-password = "" status-password = "" admin-allow-ip = "*.*.*.*" log-file = "/opt/kannel/var/log/bearerbox.log" log-level = 1 access-log = "/opt/kannel/var/log/access_bearerbox.log" box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" smsbox-port = 13001 dlr-storage = mysql store-type = spool store-location = "/opt/kannel/var/spool/bearerbox" # define mysql receipt storage ## here are db configs ## ... group = smsbox bearerbox-host = localhost bearerbox-port = 13001 sendsms-port = 13013 log-file = "/opt/kannel/var/log/smsbox.log" log-level = 0 access-log = "/opt/kannel/var/log/smsbox_access.log" http-request-retry = 3 http-queue-delay = 15 max-pending-requests = 2048 smsbox-id = smsbox1 2) smsc conf: group = smsc smsc = smpp smsc-id = smsc1 allowed-smsc-id = "smsc1;" host = port = transceiver-mode = true smsc-username = smsc1 smsc-password = interface-version = 34 system-type = "VMA" log-level = 0 log-file = "/opt/kannel/var/log/smsc1.log" max-pending-submits = 348 # do not retry unacknowledged messages wait-ack-expire = 0x02 3) second server - smppbox.conf: group = smppbox admin-port = 14000 admin-password = status-password = coredump-location = "/opt/kannel/var/core" # SET YOUR OWN BEARERBOX HOST and DEFAULT SMSC-ID HERE! # bearerbox-host = "localhost" # # the following is to define inter-box charset encoding # bearerbox-dcs = latin1for bearerbox < 1.4.3 # bearerbox-dcs = utf-8 for bearerbox => 1.4.3 # bearerbox-dcs = utf-8 smppbox-port = system-id = "" log-file = "/opt/kannel/var/log/smppbox.log" log-level = 0 access-log = "/opt/kannel/var/log/smpp_access.log" store-type = spool store-location = "/opt/kannel/var/spool/smppbox" # dlr storage, seperated from message spool dlr-store-type = spool dlr-store-location = "/opt/kannel/var/spool/dlr" # enable transparent MO routing # transparent-mo-routing = yes max-login-attempts = 100 response-mode = immediate 4) esme conf (that we use as smsc on another server): group = esme-user username = smsc1 password = default-smsc = "" max-instances = 15 # activate filtering if any plugin should apply for this user # filtering = yes # activate MO routing routing = yes # logging log-file = "/opt/kannel/var/log/esme_smsc1.log" log-level = 0 # receipting strict-dlr-routing = yes response-mode = immediate We were using 'SMPPBOX_THROUGHPUT' but it has been commented out. And this is how TPs looks like: smsc1[smsc1]SMPP::/::VMA (online 58995s, rcvd: sms 0 (0.00,0.00,0.00) / dlr 17722 *(0.91,0.99,0.29*), sent: sms 48893 ( *1.56,1.14,0.81*) / dlr 0 (0.00,0.00,0.00), failed 1, queued 0 msgs) Now there is no queue but when it's there the TPS isn't growing more than 2 TPS. Our issue is same as posted there an year ago but nobody responded to it - http://kannel.6189.n7.nabble.com/EXtremely-Low-TPS-and-high-SMSC-queue-td32281.html Do you have any idea how to overcome that? Thank you in advance. Best Regards,
Re: SSL via SMPP for SMSC connection
Hi Alex, Yes, I have it in smsc group: group = smsc smsc = smpp ... ssl-client-certkey-file = "/opt/kannel/etc/smsc.d/certs/cert.pem" use-ssl = true .. Thank you. Best Regards, On 20 July 2017 at 23:21, <amal...@kannel.org> wrote: > Hi, > > use-ssl = true in smsc group ? > > Thanks, > Alex > > Am 18.07.2017 um 10:28 schrieb Denis Lezgin <de...@veoo.com>: > > 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 = 7400 > ssl-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, > > > > >
SSL via SMPP for SMSC connection
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 = 7400 ssl-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,
Smppbox is being stuck when hit the amount of opened files
Hi all, In last few months we have been facing an issue with amount of opened files (file descriptors) for smppbox daemon. When the amount of opened files come to specific value (4850 opened files) smppbox is being stuck and only restart of could help. The most of opened files are used by Kannel daemons (bearerbox and smppbox). We use commercial version of smppbox - 1.8.207-meta-r4019 and patched bearerbox version with some custom patches and changing value of MAX_LOGFILES parameter. Ulimits are configured as following (for user Kannel): $ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 120242 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 50 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 120242 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Below is some other system settings related to that: $ cat /proc/sys/fs/file-nr 44480 1529806 $ cat /proc/sys/fs/file-max 1529806 $ ps -u kannel PID TTY TIME CMD 3762 ?02:03:18 smppbox 8522 ?00:00:00 bearerbox 8523 ?00:27:05 bearerbox The error I noticed before smppbox being stuck is: *> Max instances reached or expired, binding denied!* All the solutions I found on the internet didn't help at all. Could you please shed a light on possible solution? Thank you in advance. Best Regards,
