RE: Incoming messages take too long to show up
We send a million sms in a few hours with almost no resources -Original Message- From: users On Behalf Of Davor Spasoski Sent: Monday, December 3, 2018 3:40 PM To: Manuel García Cabrera Cc: users@kannel.org Subject: Re: Incoming messages take too long to show up Well, I don’t see anything special in your config. I’ve never used spool store type and if anything, I would try with single file storage type prior to your next peak and see if that makes a difference. Don't forget the dump and monitor your system’s cpu, i/o for anything unusual that might be happening. You could pre-emtively test your whole chain by using the test smsc and injecting desired number of SMS/sec to your application. Check how your app behaves under such load. Good luck! —Davor > On Dec 3, 2018, at 8:40 PM, Manuel García Cabrera > wrote: > > Here is my config file, with "x" where I don't think there would be > something that could interest you. > > > group = core > admin-port = x > smsbox-port = x > admin-password = x > status-password = x > store-type = spool > store-location = /x/x/x/ > log-file = "x" > log-level = 2 > box-deny-ip = x > box-allow-ip = x > admin-allow-ip = x > sms-resend-retry = 100 > > group = smsc > smsc = smpp > smsc-id = MY-SMSC-ID > denied-smsc-id = x > allowed-smsc-id = MY-SMSC-ID > host = x > port = x > smsc-username = x > smsc-password = x > system-type = SMPP > transceiver-mode = true > source-addr-autodetect = false > source-addr-ton = 5 > source-addr-npi = 1 > dest-addr-ton = 1 > dest-addr-npi = 1 > bind-addr-ton = 1 > bind-addr-npi = 1 > reconnect-delay = 90 > enquire-link-interval = 10 > > group = sendsms-user > username = x > password = x > forced-smsc = MY-SMSC-ID > user-deny-ip = "" > user-allow-ip = "" > concatenation = true > max-messages = 4 > > group = sms-service > accepted-smsc = MY-SMSC-ID > keyword = default > get-url = "http://my.app.url; > concatenation = true > max-messages = 0 > omit-empty = true > accept-x-kannel-headers = true > > > To send messages, I insert them in a SQL Box Database. To receive messages, > my app listenes to the url configured in "get-url". > > > On 3/12/18 16:31, Davor Spasoski wrote: >> Well, is it an smsbox service with http get/post/xml call, a shell execute >> or you are using opensmppbox maybe? >> >> You should include your config file. >> >>> On Dec 3, 2018, at 8:25 PM, Manuel García Cabrera >>> wrote: >>> >>> Store Type is "spool". What do you mean with how do I call the service? >>> >>> Regarding the tcpdump, I'm not having the issue right now because there is >>> no high traffic. I could only get it when the problem occurs, but it would >>> be already too late by then. I will though if it happens again this weekend. >>> >>> On 3/12/18 15:52, Davor Spasoski wrote: >>>> OK, I get it. I think you should disclose your kannel.config for >>>> the community to come up with ideas. (what store methods are you using, >>>> how do you call the service, etc…) Did you try to tcpdump and check the >>>> communication between bearerbox and smsbox? It will look like smpp >>>> protocol with improperly used PDUs, but you would still be able to >>>> recognize sender and short number. Check how it matches with the >>>> deliver_sm time. That way you will isolate the component that introduces >>>> the delay. >>>> >>>> —Davor >>>> >>>>> On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera >>>>> wrote: >>>>> >>>>> Hi Davor, >>>>> >>>>> 1. I say that kannel is logging the incoming SMS and sending it to my app >>>>> minutes after the SMSC sent the message. >>>>> 2. The reply is the submit_sm that my application sends back. The >>>>> deliver_sm "OK" is being sent almost instantly according to the tcpdump. >>>>> The submit_sm that the application sends back is taking minutes because >>>>> of the delay between the deliver_sm "OK" and Kannel sending the message >>>>> to the application. The application takes under a second to reply when it >>>>> gets the message. >>>>> >>>>> Thank you >>>>> >>>>> On 3/12/18 11:57, Davor Spasoski wrote: >>>>>> Hi, >>>>>> >&
Re: Incoming messages take too long to show up
Well, I don’t see anything special in your config. I’ve never used spool store type and if anything, I would try with single file storage type prior to your next peak and see if that makes a difference. Don't forget the dump and monitor your system’s cpu, i/o for anything unusual that might be happening. You could pre-emtively test your whole chain by using the test smsc and injecting desired number of SMS/sec to your application. Check how your app behaves under such load. Good luck! —Davor > On Dec 3, 2018, at 8:40 PM, Manuel García Cabrera > wrote: > > Here is my config file, with "x" where I don't think there would be > something that could interest you. > > > group = core > admin-port = x > smsbox-port = x > admin-password = x > status-password = x > store-type = spool > store-location = /x/x/x/ > log-file = "x" > log-level = 2 > box-deny-ip = x > box-allow-ip = x > admin-allow-ip = x > sms-resend-retry = 100 > > group = smsc > smsc = smpp > smsc-id = MY-SMSC-ID > denied-smsc-id = x > allowed-smsc-id = MY-SMSC-ID > host = x > port = x > smsc-username = x > smsc-password = x > system-type = SMPP > transceiver-mode = true > source-addr-autodetect = false > source-addr-ton = 5 > source-addr-npi = 1 > dest-addr-ton = 1 > dest-addr-npi = 1 > bind-addr-ton = 1 > bind-addr-npi = 1 > reconnect-delay = 90 > enquire-link-interval = 10 > > group = sendsms-user > username = x > password = x > forced-smsc = MY-SMSC-ID > user-deny-ip = "" > user-allow-ip = "" > concatenation = true > max-messages = 4 > > group = sms-service > accepted-smsc = MY-SMSC-ID > keyword = default > get-url = "http://my.app.url; > concatenation = true > max-messages = 0 > omit-empty = true > accept-x-kannel-headers = true > > > To send messages, I insert them in a SQL Box Database. To receive messages, > my app listenes to the url configured in "get-url". > > > On 3/12/18 16:31, Davor Spasoski wrote: >> Well, is it an smsbox service with http get/post/xml call, a shell execute >> or you are using opensmppbox maybe? >> >> You should include your config file. >> >>> On Dec 3, 2018, at 8:25 PM, Manuel García Cabrera >>> wrote: >>> >>> Store Type is "spool". What do you mean with how do I call the service? >>> >>> Regarding the tcpdump, I'm not having the issue right now because there is >>> no high traffic. I could only get it when the problem occurs, but it would >>> be already too late by then. I will though if it happens again this weekend. >>> >>> On 3/12/18 15:52, Davor Spasoski wrote: OK, I get it. I think you should disclose your kannel.config for the community to come up with ideas. (what store methods are you using, how do you call the service, etc…) Did you try to tcpdump and check the communication between bearerbox and smsbox? It will look like smpp protocol with improperly used PDUs, but you would still be able to recognize sender and short number. Check how it matches with the deliver_sm time. That way you will isolate the component that introduces the delay. —Davor > On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera > wrote: > > Hi Davor, > > 1. I say that kannel is logging the incoming SMS and sending it to my app > minutes after the SMSC sent the message. > 2. The reply is the submit_sm that my application sends back. The > deliver_sm "OK" is being sent almost instantly according to the tcpdump. > The submit_sm that the application sends back is taking minutes because > of the delay between the deliver_sm "OK" and Kannel sending the message > to the application. The application takes under a second to reply when it > gets the message. > > Thank you > > On 3/12/18 11:57, Davor Spasoski wrote: >> Hi, >> >> I'm just trying to understand this. >> - You basically say that kannel is logging the incoming and reply sms >> behind of time on smsc, right? >> - What do you consider a "reply", the deliver_sm "OK" or the submit_sm >> that the application sends back? >> >> BR, >> --Davor >> >> -Original Message- >> From: users On Behalf Of Manuel García Cabrera >> Sent: Monday, December 3, 2018 3:09 PM >> To: users@kannel.org >> Subject: Incoming messages take too long to show up >> >> Hi everyone. I'm having problems with incoming messages during high >> traffic. During a campaign the other day I was receving 85 messages per >> second, however, clients were complaining that my reply took over five >> minutes. I checked the logs, and I found out that wasn't the case, I was >> replying only a few seconds after Kannel was logging the message. >> However, my Carrier sent me a tcpdump were they showed that Kannel was >> in fact replying to the incoming message with a Deliver_sm "OK" with >> only a few
Re: Incoming messages take too long to show up
Here is my config file, with "x" where I don't think there would be something that could interest you. group = core admin-port = x smsbox-port = x admin-password = x status-password = x store-type = spool store-location = /x/x/x/ log-file = "x" log-level = 2 box-deny-ip = x box-allow-ip = x admin-allow-ip = x sms-resend-retry = 100 group = smsc smsc = smpp smsc-id = MY-SMSC-ID denied-smsc-id = x allowed-smsc-id = MY-SMSC-ID host = x port = x smsc-username = x smsc-password = x system-type = SMPP transceiver-mode = true source-addr-autodetect = false source-addr-ton = 5 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 bind-addr-ton = 1 bind-addr-npi = 1 reconnect-delay = 90 enquire-link-interval = 10 group = sendsms-user username = x password = x forced-smsc = MY-SMSC-ID user-deny-ip = "" user-allow-ip = "" concatenation = true max-messages = 4 group = sms-service accepted-smsc = MY-SMSC-ID keyword = default get-url = "http://my.app.url; concatenation = true max-messages = 0 omit-empty = true accept-x-kannel-headers = true To send messages, I insert them in a SQL Box Database. To receive messages, my app listenes to the url configured in "get-url". On 3/12/18 16:31, Davor Spasoski wrote: Well, is it an smsbox service with http get/post/xml call, a shell execute or you are using opensmppbox maybe? You should include your config file. On Dec 3, 2018, at 8:25 PM, Manuel García Cabrera wrote: Store Type is "spool". What do you mean with how do I call the service? Regarding the tcpdump, I'm not having the issue right now because there is no high traffic. I could only get it when the problem occurs, but it would be already too late by then. I will though if it happens again this weekend. On 3/12/18 15:52, Davor Spasoski wrote: OK, I get it. I think you should disclose your kannel.config for the community to come up with ideas. (what store methods are you using, how do you call the service, etc…) Did you try to tcpdump and check the communication between bearerbox and smsbox? It will look like smpp protocol with improperly used PDUs, but you would still be able to recognize sender and short number. Check how it matches with the deliver_sm time. That way you will isolate the component that introduces the delay. —Davor On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera wrote: Hi Davor, 1. I say that kannel is logging the incoming SMS and sending it to my app minutes after the SMSC sent the message. 2. The reply is the submit_sm that my application sends back. The deliver_sm "OK" is being sent almost instantly according to the tcpdump. The submit_sm that the application sends back is taking minutes because of the delay between the deliver_sm "OK" and Kannel sending the message to the application. The application takes under a second to reply when it gets the message. Thank you On 3/12/18 11:57, Davor Spasoski wrote: Hi, I'm just trying to understand this. - You basically say that kannel is logging the incoming and reply sms behind of time on smsc, right? - What do you consider a "reply", the deliver_sm "OK" or the submit_sm that the application sends back? BR, --Davor -Original Message- From: users On Behalf Of Manuel García Cabrera Sent: Monday, December 3, 2018 3:09 PM To: users@kannel.org Subject: Incoming messages take too long to show up Hi everyone. I'm having problems with incoming messages during high traffic. During a campaign the other day I was receving 85 messages per second, however, clients were complaining that my reply took over five minutes. I checked the logs, and I found out that wasn't the case, I was replying only a few seconds after Kannel was logging the message. However, my Carrier sent me a tcpdump were they showed that Kannel was in fact replying to the incoming message with a Deliver_sm "OK" with only a few seconds of delay, but that was minutes before the message was logged in Kannel logs. Where does the message go during that time? What can I improve? Disclaimer: one.Vip DOOEL Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДООЕЛ Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е
Re: Incoming messages take too long to show up
Well, is it an smsbox service with http get/post/xml call, a shell execute or you are using opensmppbox maybe? You should include your config file. > On Dec 3, 2018, at 8:25 PM, Manuel García Cabrera > wrote: > > Store Type is "spool". What do you mean with how do I call the service? > > Regarding the tcpdump, I'm not having the issue right now because there is no > high traffic. I could only get it when the problem occurs, but it would be > already too late by then. I will though if it happens again this weekend. > > On 3/12/18 15:52, Davor Spasoski wrote: >> OK, I get it. I think you should disclose your kannel.config for the >> community to come up with ideas. (what store methods are you using, how do >> you call the service, etc…) >> Did you try to tcpdump and check the communication between bearerbox and >> smsbox? It will look like smpp protocol with improperly used PDUs, but you >> would still be able to recognize sender and short number. Check how it >> matches with the deliver_sm time. That way you will isolate the component >> that introduces the delay. >> >> —Davor >> >>> On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera >>> wrote: >>> >>> Hi Davor, >>> >>> 1. I say that kannel is logging the incoming SMS and sending it to my app >>> minutes after the SMSC sent the message. >>> 2. The reply is the submit_sm that my application sends back. The >>> deliver_sm "OK" is being sent almost instantly according to the tcpdump. >>> The submit_sm that the application sends back is taking minutes because of >>> the delay between the deliver_sm "OK" and Kannel sending the message to the >>> application. The application takes under a second to reply when it gets the >>> message. >>> >>> Thank you >>> >>> On 3/12/18 11:57, Davor Spasoski wrote: Hi, I'm just trying to understand this. - You basically say that kannel is logging the incoming and reply sms behind of time on smsc, right? - What do you consider a "reply", the deliver_sm "OK" or the submit_sm that the application sends back? BR, --Davor -Original Message- From: users On Behalf Of Manuel García Cabrera Sent: Monday, December 3, 2018 3:09 PM To: users@kannel.org Subject: Incoming messages take too long to show up Hi everyone. I'm having problems with incoming messages during high traffic. During a campaign the other day I was receving 85 messages per second, however, clients were complaining that my reply took over five minutes. I checked the logs, and I found out that wasn't the case, I was replying only a few seconds after Kannel was logging the message. However, my Carrier sent me a tcpdump were they showed that Kannel was in fact replying to the incoming message with a Deliver_sm "OK" with only a few seconds of delay, but that was minutes before the message was logged in Kannel logs. Where does the message go during that time? What can I improve? Disclaimer: one.Vip DOOEL Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДООЕЛ Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДООЕЛ Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата! >> >> >> >> Disclaimer: one.Vip DOOEL Skopje >> This e-mail (including any
Re: Incoming messages take too long to show up
Store Type is "spool". What do you mean with how do I call the service? Regarding the tcpdump, I'm not having the issue right now because there is no high traffic. I could only get it when the problem occurs, but it would be already too late by then. I will though if it happens again this weekend. On 3/12/18 15:52, Davor Spasoski wrote: OK, I get it. I think you should disclose your kannel.config for the community to come up with ideas. (what store methods are you using, how do you call the service, etc…) Did you try to tcpdump and check the communication between bearerbox and smsbox? It will look like smpp protocol with improperly used PDUs, but you would still be able to recognize sender and short number. Check how it matches with the deliver_sm time. That way you will isolate the component that introduces the delay. —Davor On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera wrote: Hi Davor, 1. I say that kannel is logging the incoming SMS and sending it to my app minutes after the SMSC sent the message. 2. The reply is the submit_sm that my application sends back. The deliver_sm "OK" is being sent almost instantly according to the tcpdump. The submit_sm that the application sends back is taking minutes because of the delay between the deliver_sm "OK" and Kannel sending the message to the application. The application takes under a second to reply when it gets the message. Thank you On 3/12/18 11:57, Davor Spasoski wrote: Hi, I'm just trying to understand this. - You basically say that kannel is logging the incoming and reply sms behind of time on smsc, right? - What do you consider a "reply", the deliver_sm "OK" or the submit_sm that the application sends back? BR, --Davor -Original Message- From: users On Behalf Of Manuel García Cabrera Sent: Monday, December 3, 2018 3:09 PM To: users@kannel.org Subject: Incoming messages take too long to show up Hi everyone. I'm having problems with incoming messages during high traffic. During a campaign the other day I was receving 85 messages per second, however, clients were complaining that my reply took over five minutes. I checked the logs, and I found out that wasn't the case, I was replying only a few seconds after Kannel was logging the message. However, my Carrier sent me a tcpdump were they showed that Kannel was in fact replying to the incoming message with a Deliver_sm "OK" with only a few seconds of delay, but that was minutes before the message was logged in Kannel logs. Where does the message go during that time? What can I improve? Disclaimer: one.Vip DOOEL Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДООЕЛ Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДООЕЛ Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата! Disclaimer: one.Vip DOOEL Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system.
Re: Incoming messages take too long to show up
OK, I get it. I think you should disclose your kannel.config for the community to come up with ideas. (what store methods are you using, how do you call the service, etc…) Did you try to tcpdump and check the communication between bearerbox and smsbox? It will look like smpp protocol with improperly used PDUs, but you would still be able to recognize sender and short number. Check how it matches with the deliver_sm time. That way you will isolate the component that introduces the delay. —Davor > On Dec 3, 2018, at 4:06 PM, Manuel García Cabrera > wrote: > > Hi Davor, > > 1. I say that kannel is logging the incoming SMS and sending it to my app > minutes after the SMSC sent the message. > 2. The reply is the submit_sm that my application sends back. The deliver_sm > "OK" is being sent almost instantly according to the tcpdump. The submit_sm > that the application sends back is taking minutes because of the delay > between the deliver_sm "OK" and Kannel sending the message to the > application. The application takes under a second to reply when it gets the > message. > > Thank you > > On 3/12/18 11:57, Davor Spasoski wrote: >> Hi, >> >> I'm just trying to understand this. >> - You basically say that kannel is logging the incoming and reply sms behind >> of time on smsc, right? >> - What do you consider a "reply", the deliver_sm "OK" or the submit_sm that >> the application sends back? >> >> BR, >> --Davor >> >> -Original Message- >> From: users On Behalf Of Manuel García Cabrera >> Sent: Monday, December 3, 2018 3:09 PM >> To: users@kannel.org >> Subject: Incoming messages take too long to show up >> >> Hi everyone. I'm having problems with incoming messages during high traffic. >> During a campaign the other day I was receving 85 messages per second, >> however, clients were complaining that my reply took over five minutes. I >> checked the logs, and I found out that wasn't the case, I was replying only >> a few seconds after Kannel was logging the message. >> However, my Carrier sent me a tcpdump were they showed that Kannel was in >> fact replying to the incoming message with a Deliver_sm "OK" with only a few >> seconds of delay, but that was minutes before the message was logged in >> Kannel logs. Where does the message go during that time? What can I improve? >> >> >> >> >> Disclaimer: one.Vip DOOEL Skopje >> This e-mail (including any attachments) is confidential and may be protected >> by legal privilege. If you are not the intended recipient, you should not >> copy it, re-transmit it, use it or disclose its contents, but should return >> it to the sender immediately and delete your copy from your system. Any >> unauthorized use or dissemination of this message in whole or in part is >> strictly prohibited. Please note that e-mails are susceptible to change. >> one.Vip DOOEL Skopje shall not be liable for the improper or incomplete >> transmission of the information contained in this communication nor for any >> delay in its receipt or damage to your system. >> Please, do not print this e-mail unless it is necessary! Think about saving >> the environment! >> >> Напомена: оне.Вип ДООЕЛ Скопје >> Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да >> биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е >> наменета пораката, не треба да ја копирате, дистрибуирате или да ја >> откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и >> да ја избришете оригиналната порака и сите нејзини копии од Вашиот >> компјутерски систем. Секое неовластено користење на оваа порака во целост >> или делови од истата е строго забрането. Ве молиме да забележите дека >> електронските пораки се подложни на промени. оне.Вип ДООЕЛ Скопје не презема >> одговорност за несоодветно или нецелосно пренесување на информациите >> содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот >> или оштетувања на вашиот систем. >> Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја >> природата! > Disclaimer: one.Vip DOOEL Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДООЕЛ Скопје Оваа електронска порака
Re: Incoming messages take too long to show up
Hi Davor, 1. I say that kannel is logging the incoming SMS and sending it to my app minutes after the SMSC sent the message. 2. The reply is the submit_sm that my application sends back. The deliver_sm "OK" is being sent almost instantly according to the tcpdump. The submit_sm that the application sends back is taking minutes because of the delay between the deliver_sm "OK" and Kannel sending the message to the application. The application takes under a second to reply when it gets the message. Thank you On 3/12/18 11:57, Davor Spasoski wrote: Hi, I'm just trying to understand this. - You basically say that kannel is logging the incoming and reply sms behind of time on smsc, right? - What do you consider a "reply", the deliver_sm "OK" or the submit_sm that the application sends back? BR, --Davor -Original Message- From: users On Behalf Of Manuel García Cabrera Sent: Monday, December 3, 2018 3:09 PM To: users@kannel.org Subject: Incoming messages take too long to show up Hi everyone. I'm having problems with incoming messages during high traffic. During a campaign the other day I was receving 85 messages per second, however, clients were complaining that my reply took over five minutes. I checked the logs, and I found out that wasn't the case, I was replying only a few seconds after Kannel was logging the message. However, my Carrier sent me a tcpdump were they showed that Kannel was in fact replying to the incoming message with a Deliver_sm "OK" with only a few seconds of delay, but that was minutes before the message was logged in Kannel logs. Where does the message go during that time? What can I improve? Disclaimer: one.Vip DOOEL Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДООЕЛ Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДООЕЛ Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата!
RE: Incoming messages take too long to show up
Hi, I'm just trying to understand this. - You basically say that kannel is logging the incoming and reply sms behind of time on smsc, right? - What do you consider a "reply", the deliver_sm "OK" or the submit_sm that the application sends back? BR, --Davor -Original Message- From: users On Behalf Of Manuel García Cabrera Sent: Monday, December 3, 2018 3:09 PM To: users@kannel.org Subject: Incoming messages take too long to show up Hi everyone. I'm having problems with incoming messages during high traffic. During a campaign the other day I was receving 85 messages per second, however, clients were complaining that my reply took over five minutes. I checked the logs, and I found out that wasn't the case, I was replying only a few seconds after Kannel was logging the message. However, my Carrier sent me a tcpdump were they showed that Kannel was in fact replying to the incoming message with a Deliver_sm "OK" with only a few seconds of delay, but that was minutes before the message was logged in Kannel logs. Where does the message go during that time? What can I improve? Disclaimer: one.Vip DOOEL Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. one.Vip DOOEL Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Please, do not print this e-mail unless it is necessary! Think about saving the environment! Напомена: оне.Вип ДООЕЛ Скопје Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое неовластено користење на оваа порака во целост или делови од истата е строго забрането. Ве молиме да забележите дека електронските пораки се подложни на промени. оне.Вип ДООЕЛ Скопје не презема одговорност за несоодветно или нецелосно пренесување на информациите содржани во оваа комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на вашиот систем. Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја природата!
