Hello again.
This is to share my experience about SMPP v3.3 issue and how could manage to
bypass the bearerbox bug. I found configuration parameters to separate TX and
RX ports on ESME and this make possible to use two independent kannel
instances: one for RX and one for TX. The scheme is as below:
ESME_tx | => | opensmppbox_tx | => | bearerbox_tx | ---->| |
| SMSC |
ESME_rx | <= | opensmppbox_rx | <= | bearerbox_rx | <----| |
I submitted a bug about problem found in order to be known issue and eventually
fixed one day: https://redmine.kannel.org/issues/619
Velin.
----- Rene Kluwen ([email protected]), 06.10.2011 15:16 -----
> Possibly, yes, this is a bug. Because I couldn’t find any mistakes in your
> config.
>
> I will look into the matter.
>
> Queue management and load sharing are completely in bearerbox. You are right
> about that.
>
> To debug deeper, you will have to dive into the sources.
>
>
>
> == Rene
>
>
>
>
>
> From: [email protected] [mailto:[email protected]] On Behalf Of
> [email protected]
> Sent: Thursday, 06 October, 2011 13:44
> To: [email protected]
> Subject: RE: opensmppbox problem with SMPPv3.3 ESME
>
>
>
> Hello Rene, thanks for your answer.
>
> I know it is strange, it took few days for me to find where these messages
> were "lost". I performed a test by reconnecting ESME and then all buffered
> messages are delivered trough receiver thread. Later the symptom comes again
> and messages are getting buffered. This I found on bearerbox web monitoring
> interface where could be seen every opensmppbox instance and buffered
> counter. In log files I can not find any useful information.
>
> The workaround you propose is not possible because the communication layer is
> hardcoded in ESME and can not be changed.
>
> Is it possible this to be a bug? And is there any way to debug more deeply.
> Queue management and load sharing mechanism should be in bearerbox. Am I
> right?
>
> Regards,
>
> Velin
>
>
>
>
>
> ----- Цитат от Rene Kluwen ([email protected]), на 06.10.2011 в 13:54
> -----
> Strange. When receiving an sms on a transmitter lag, opensmppbox should
> automatically relay that message to the receiver leg.
>
> A workaround (if possible) is binding as transceiver. But like this, it
> should work as well.
>
>
>
> == Rene
>
>
> From: [email protected] [mailto:[email protected]] On Behalf Of
> [email protected]
> Sent: Thursday, 06 October, 2011 10:22
> To: [email protected]
> Subject: opensmppbox problem with SMPPv3.3 ESME
>
> Hello kannel community.
>
> I have a configuration of kannel and opensmppbox which acts as SMPP
> adaptation
> layer between SMSC and client ESME. This is because ESME is quite old and
> there
> is SMPP version incompatibility between both sides. ESME is using SMPPv3.3
> communication scheme with two connections: one connection as receiver and one
> as transmitter.
>
> Scheme is as below
>
> | T |------->|
> | ESME | | openSMPPbox || bearerbox || SMSC |
> | R |
>
> As general this is a working solution and messages pass both directions, the
> problem which I observed in a while was some messages received by bearerbox
> but not delivered to ESME.
>
> Each connection to opensmppbox is presented as separate instance to bearerbox
> and we have one receiver and one transmitter instance.
> Two openSMPPbox instances are represented as two smsboxes to bearerbox and
> kannel tries to load-balancing between these two instances (one receiver and
> one transmitter). Because transmitter instance could not deliver messages to
> ESME they stayed buffered in opensmppbox transmitter thread queue.
>
> I am using SVN snapshot version from 27 September.
>
> My first question is about configuration, do I miss something? I tested few
> days and could not find solution.
>
> If there is no problem with configuration is it possible this to be a bug,
> because there is no point to queue messages to a transmitter thread.
>
> Here is my configuration:
>
> kannel.conf
> =============================================================
> group = core
> admin-port = 13000
> admin-password = xxxxx
> log-file = "/var/log/kannel/bearerbox.log"
> log-level = 0
> access-log = "/var/log/kannel/bearerbox_access.log"
> # Smsbox related
> smsbox-port = 13001
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "127.0.0.1"
> sms-resend-retry = 2
>
> # SMSC SMPP
> group = smsc
> smsc = smpp
> smsc-id = coms
> host = xxxxxxxxxx
> port = xxxx
> interface-version=34
> enquire-link-interval = 298
> connect-allow-ip = 127.0.0.1
> transceiver-mode = yes
> smsc-username = xxxxxx
> smsc-password = xxxxx
> system-type = xxx
> source-addr-ton = 2
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi = 1
>
> # SMSBOX SETUP
> group = smsbox
> smsbox-id = "fakesmsc"
> bearerbox-host = localhost
> log-file = "/var/log/kannel/smsbox.log"
> log-level = 1
> access-log = "/var/log/kannel/smsbox_access.log"
>
> # SMS routing setup
> group = smsbox-route
> smsbox-id = sms4chat
> smsc-id = "coms"
> ==============================================================
>
> openSMPPbox.conf
> ==============================================================
> group = core
> dlr-storage = internal
>
> # openSMPP box configuration
> group = opensmppbox
> bearerbox-host = 127.0.0.1
> bearerbox-port = 13001
> timeout = 86400
> our-system-id = VSMSC
> opensmppbox-id = smppbox1
> opensmppbox-port = 13003
> log-file = /var/log/kannel/opensmppbox.log
> log-level = 0
> route-to-smsc = coms
> smpp-logins = /etc/kannel/SMPPclients.conf
> ==============================================================
>
> SMPPclients.conf
> ==============================================================
> xxxxxx xxxxx sms4chat 127.0.0.1
> ==============================================================
>
> Regards,
> Velin.
>
> -------------------------------------
> Mail.bg: Безплатен e-mail адрес. Най-добрите характеристики на българския
> пазар - 10 GB пощенска кутия, 20 MB прикрепен файл, безплатен POP3, мобилна
> версия, SMS известяване и други.
>
>
>
>
>
> -------------------------------------
> Mail.bg: Безплатен e-mail адрес. Най-добрите характеристики на българския
> пазар - 10 GB пощенска кутия, 20 MB прикрепен файл, безплатен POP3, мобилна
> версия, SMS известяване и други.
>
>
-------------------------------------
Mail.bg: Безплатен e-mail адрес. Най-добрите характеристики на българския пазар
- 10 GB пощенска кутия, 20 MB прикрепен файл, безплатен POP3, мобилна версия,
SMS известяване и други.
-------------------------------------
Mail.bg: Безплатен e-mail адрес. Най-добрите характеристики на българския пазар
- 10 GB пощенска кутия, 20 MB прикрепен файл, безплатен POP3, мобилна версия,
SMS известяване и други.
-------------------------------------
Mail.bg: Безплатен e-mail адрес. Най-добрите характеристики на българския пазар
- 10 GB пощенска кутия, 20 MB прикрепен файл, безплатен POP3, мобилна версия,
SMS известяване и други.
-------------------------------------
Mail.bg: Безплатен e-mail адрес. Най-добрите характеристики на българския пазар
- 10 GB пощенска кутия, 20 MB прикрепен файл, безплатен POP3, мобилна версия,
SMS известяване и други.
-------------------------------------
Mail.bg: Безплатен e-mail адрес. Най-добрите характеристики на българския пазар
- 10 GB пощенска кутия, 20 MB прикрепен файл, безплатен POP3, мобилна версия,
SMS известяване и други.
