nd
> all parts via the same SMSC and in the right order.
>
> Thanks,
> Alex
>
>
>> Am 19.12.2017 um 14:32 schrieb Grant Saicom <grant.sai...@gmail.com>:
>>
>> Hi Kannel Users
>>
>> I have an issue which I need to address with respect to how ka
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.
That is what I thought. Thank you for confirmation.
> On 21 Nov 2017, at 10:49, amal...@kannel.org wrote:
>
> Hi,
>
> there is submit_sm_resp for each submit_sm for concatenated message as well.
>
> Thanks,
> Alex
>
>
>> Am 21.11.2017 um 08:23 schrieb
Hello Kannel Users
I have a question with regards to the signaling flow of a concatenated SMS.
Simplistically, when we send a single (successful) sms of less than 160 chars
(gsm7) on an established bind, the ESME sends a single submit_sm to the SMSC,
then the SMSC responds to the ESME with a
Hi Dmitry
I have come across something similar with mysql. Check that your table
collation matches to chosen alphabet encoding. This caused me a lot of issues
in the past.
The reason why smsbox works is because of the url encoding handles the more
complex characters and is correctly
submit_sm
SMSC -> kannel: submit_sm : Resp OK
SMSC -> kannel: submit_sm : Resp OK
SMSC -> kannel: submit_sm : Resp OK
SMSC -> kannel: submit_sm : Resp OK
This out of sequence behaviour indicated that there was a delay occurring
somewhere and in our case, it was the updates to the
Hi Everyone
I am looking for an opinion (good natured discussion please) on which
distribution is best to run a lean purpose built kannel system for smpp sms
delivery and replies using sqlbox.
DB is mysql and the DB is running on a separate VM on the same hypervisor with
SSD drives.
We are
ingle file and in RAM, I found this way it's very fast.
>
> Let me know if it helps.
>
> If you want to preserve queue (in case of hard reset or something) you can
> rsync it's contents every 2 minutes or so in some permanent directory.
>
> 2015-12-15 12:56 GMT+03:00 Gran
urce_addr_ton: 2 = 0x0002
2016-01-13 11:00:00 [4771] [7] DEBUG: source_addr_npi: 1 = 0x0001
> On 13 Jan 2016, at 13:34, Grant Saicom <grant.sai...@gmail.com> wrote:
>
> Hi
>
> Thank you for your reply. See my config below. Logs are pretty massive, so
ome bearerbox logs and config so that we can advise on
> the retransmission bit.
>
> @sotandeka
>
> On Wed, Jan 13, 2016 at 2:03 PM, Grant Saicom <grant.sai...@gmail.com
> <mailto:grant.sai...@gmail.com>> wrote:
> Hi Everyone
>
> I am looking for an
provider with mtr output and tcpdump captures there might be unoptimal direct
> or/and reverse network path between you and your SMSC provider.
>
> 2016-01-13 14:07 GMT+03:00 Grant Saicom <grant.sai...@gmail.com
> <mailto:grant.sai...@gmail.com>>:
> I suspect the issue I am
kannel there and see how
it behaves there.
Thank you for the advice.
> On 13 Jan 2016, at 15:09, spameden <spame...@gmail.com> wrote:
>
>
>
> 2016-01-13 15:14 GMT+03:00 Grant Saicom <grant.sai...@gmail.com
> <mailto:grant.sai...@gmail.com>>:
>
We process the sent_sms into another table on they fly. Maximum size the
sent_sms table gets is maybe 40k tops but mostly it averages around 10K. We see
this once 1 week maybe.
I have really made every attempt to remove any bottlenecks in terms unwieldy
database sizes to allow kannel to work
Hi
I don’t see any real improvement in performance.
I am trying some different values.
Just an aside: It almost seems to me that the bottleneck is sqlbox’s submission
to bearerbox and not the quantity sqlbox pops out of send_sms to hand over. I
am going to go over the sqlbox config doc again,
14 matches
Mail list logo
