Re: Routing DLR to ESME using OpenSMPPBox

[Ruben Melikyan]

Hi,
According to provided log, it seems kannel does not find dlr record to process.
Returning to your configs It will be better to let CORE to handle dlr store and 
update process.
So, i suggest to remove dlr-storage=internal line from opensmppbox config and 
place it to core setup. 
Below is my working configs concerning dlr.

.
* core config
group= core
…….
…….
store-type= file
store-location= “your location here”/STORE
dlr-storage=spool
dlr-spool = “your location here”/DLR
.

Note: you do not need to create STORE and DLR flies in your location. Kannel 
will create them automatically on start.

Best regards,
Ruben Melikyan

> On 9 May 2022, at 05:48, christopher kamutumwa  
> wrote:
> 
> 
> Thank you ruben,
> added that line but still getting below in logs please advise
> 
> 2022-05-09 03:45:12 [20164] [11] INFO: We received an SMS message.
> 2022-05-09 03:45:12 [20164] [11] DEBUG: DLR[mysql]: Looking for DLR 
> smsc=smpp1, ts=a70c7834-3a07-43c0-9749-89cebfeedc85, dst=+260976198318, type=1
> 2022-05-09 03:45:12 [23636] [24] DEBUG: boxc_sender: sent message to 
> <127.0.0.1>
> 2022-05-09 03:45:12 [20164] [11] DEBUG: sql: SELECT `mask`, `service`, `url`, 
> `source`, `destination`, `boxcid` FROM `dlr` WHERE `smsc`=? AND `ts`=?  LIMIT 
> 1
> 2022-05-09 03:45:12 [20164] [11] DEBUG: column=mask buffer_type=253 
> max_length=0 length=4
> 2022-05-09 03:45:12 [20164] [11] DEBUG: column=service buffer_type=253 
> max_length=0 length=16
> 2022-05-09 03:45:12 [20164] [11] DEBUG: column=url buffer_type=253 
> max_length=0 length=2048
> 2022-05-09 03:45:12 [20164] [11] DEBUG: column=source buffer_type=253 
> max_length=0 length=32
> 2022-05-09 03:45:12 [20164] [11] DEBUG: column=destination buffer_type=253 
> max_length=0 length=32
> 2022-05-09 03:45:12 [20164] [11] DEBUG: column=boxcid buffer_type=253 
> max_length=0 length=16
> 2022-05-09 03:45:12 [20164] [11] WARNING: DLR[mysql]: DLR from SMSC 
> for DST<+260976198318> not found.
> 2022-05-09 03:45:12 [20164] [11] WARNING: msg_to_pdu failed, sending negative 
> ack
> 
>   Virus-free. www.avg.com
> 
>> On Sun, May 8, 2022 at 12:03 PM Ruben Melikyan  wrote:
>> Try to set in smsc config the following line:
>> reroute-dlr=true
>> 
>> Best regards,
>> Ruben Melikyan
>> 
>>>> On 8 May 2022, at 10:32, christopher kamutumwa  
>>>> wrote:
>>>> 
>>> 
>>> I have configured my servers to send from ESME to SMSC through OpenSMPPBox,
>>> i have applied the below flow
>>> ESME -->> OpenSMPPBox -->> SQLBox -->>Bearerbox -->> SMSC
>>> I have succeeded in sending the sms from ESME to the SMSC but my problem is
>>> related to the DLR.
>>> The Bearerbox actually received the DLR from the SMSC but it didn't route
>>> it to the ESME.
>>> 
>>> What is the required configurations that could resolve the above issue. i
>>> need to route the DLR to the ESME
>>> 
>>> Your help in this regard is highly appreciated and thanks in advance.i can 
>>> see entries in db when i send msg
>>> 
>>> Below are my config files and log error,
>>> 2022-05-07 14:36:47 [3023] [7] DEBUG: DLR[mysql]: Looking for DLR 
>>> smsc=smpp1, ts=1a11039a-901d-43e3-8f99-1b42fa14aacb, dst=+260976198318, 
>>> type=1
>>> 2022-05-07 14:36:47 [3023] [7] DEBUG: sql: SELECT `mask`, `service`, `url`, 
>>> `source`, `destination`, `boxcid` FROM `dlr` WHERE `smsc`=? AND `ts`=?  
>>> LIMIT 1
>>> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=mask buffer_type=253 
>>> max_length=0 length=4
>>> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=service buffer_type=253 
>>> max_length=0 length=16
>>> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=url buffer_type=253 
>>> max_length=0 length=2048
>>> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=source buffer_type=253 
>>> max_length=0 length=32
>>> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=destination buffer_type=253 
>>> max_length=0 length=32
>>> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=boxcid buffer_type=253 
>>> max_length=0 length=16
>>> 2022-05-07 14:36:47 [3023] [7] WARNING: DLR[mysql]: DLR from SMSC 
>>> for DST<+260976198318> not found.
>>> 2022-05-07 14:36:47 [3023] [7] WARNING: msg_to_pdu failed, sending negative 
>>> ack
>>> *** Kannel.conf 
>>> #-
>>> # core setup
>>> 
>>> group = core
>>> admin-port = 13000
>>> smsbox-port = 13001
>>> wapbox-p

Re: Routing DLR to ESME using OpenSMPPBox

[christopher kamutumwa]

Thank you ruben,
added that line but still getting below in logs please advise

2022-05-09 03:45:12 [20164] [11] INFO: We received an SMS message.
2022-05-09 03:45:12 [20164] [11] DEBUG: DLR[mysql]: Looking for DLR
smsc=smpp1, ts=a70c7834-3a07-43c0-9749-89cebfeedc85, dst=+260976198318,
type=1
2022-05-09 03:45:12 [23636] [24] DEBUG: boxc_sender: sent message to
<127.0.0.1>
2022-05-09 03:45:12 [20164] [11] DEBUG: sql: SELECT `mask`, `service`,
`url`, `source`, `destination`, `boxcid` FROM `dlr` WHERE `smsc`=? AND
`ts`=?  LIMIT 1
2022-05-09 03:45:12 [20164] [11] DEBUG: column=mask buffer_type=253
max_length=0 length=4
2022-05-09 03:45:12 [20164] [11] DEBUG: column=service buffer_type=253
max_length=0 length=16
2022-05-09 03:45:12 [20164] [11] DEBUG: column=url buffer_type=253
max_length=0 length=2048
2022-05-09 03:45:12 [20164] [11] DEBUG: column=source buffer_type=253
max_length=0 length=32
2022-05-09 03:45:12 [20164] [11] DEBUG: column=destination buffer_type=253
max_length=0 length=32
2022-05-09 03:45:12 [20164] [11] DEBUG: column=boxcid buffer_type=253
max_length=0 length=16
2022-05-09 03:45:12 [20164] [11] WARNING: DLR[mysql]: DLR from SMSC
for DST<+260976198318> not found.
2022-05-09 03:45:12 [20164] [11] WARNING: msg_to_pdu failed, sending
negative ack

<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, May 8, 2022 at 12:03 PM Ruben Melikyan  wrote:

> Try to set in smsc config the following line:
> reroute-dlr=true
>
> Best regards,
> Ruben Melikyan
>
> On 8 May 2022, at 10:32, christopher kamutumwa 
> wrote:
>
> 
>
> I have configured my servers to send from ESME to SMSC through OpenSMPPBox,
> i have applied the below flow
> ESME -->> OpenSMPPBox -->> SQLBox -->>Bearerbox -->> SMSC
>
> I have succeeded in sending the sms from ESME to the SMSC but my problem is
> related to the DLR.
> The Bearerbox actually received the DLR from the SMSC but it didn't route
> it to the ESME.
>
> What is the required configurations that could resolve the above issue. i
> need to route the DLR to the ESME
>
> Your help in this regard is highly appreciated and thanks in advance.i can 
> see entries in db when i send msg
>
> Below are my config files and log error,
> 2022-05-07 14:36:47 [3023] [7] DEBUG: DLR[mysql]: Looking for DLR smsc=smpp1, 
> ts=1a11039a-901d-43e3-8f99-1b42fa14aacb, dst=+260976198318, type=1
> 2022-05-07 14:36:47 [3023] [7] DEBUG: sql: SELECT `mask`, `service`, `url`, 
> `source`, `destination`, `boxcid` FROM `dlr` WHERE `smsc`=? AND `ts`=?  LIMIT 
> 1
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=mask buffer_type=253 
> max_length=0 length=4
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=service buffer_type=253 
> max_length=0 length=16
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=url buffer_type=253 max_length=0 
> length=2048
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=source buffer_type=253 
> max_length=0 length=32
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=destination buffer_type=253 
> max_length=0 length=32
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=boxcid buffer_type=253 
> max_length=0 length=16
> 2022-05-07 14:36:47 [3023] [7] WARNING: DLR[mysql]: DLR from SMSC for 
> DST<+260976198318> not found.
> 2022-05-07 14:36:47 [3023] [7] WARNING: msg_to_pdu failed, sending negative 
> ack
>
> *** Kannel.conf 
> #-
> # core setup
>
> group = core
> admin-port = 13000
> smsbox-port = 13001
> wapbox-port = 13002
> admin-password = admin123
> status-password = status123
> wdp-interface-name = "*"
> log-file = "/usr/local/kannel/bearerbox.log"
> log-level = 3
> access-log = "/usr/local/kannel/bearerboxaccess.log"
> store-type = spool
> store-location = "/usr/local/kannel/store"
> store-dump-freq = 60
> #-
> # smsc setup
>
> group = smsc
> smsc = smpp
> smsc-id = VFSMPP1
> host = "x.x.x.x"
> port = 
> smsc-username = egypt321
> smsc-password = egypt321
> system-type = "egypt321"
> address-range = ""
> dest-addr-ton=1
> dest-addr-npi=1
> interface-version = 34
> enquire-link-interval = 25
> reconnect-delay = 15
> transceiver-mode = 1
> #max-pending-submits = 8
> throughput = 6
> #-
> # smsbox setup
>
> group = smsbox
> smsbox-id = smsbox1
> bearer

Re: Routing DLR to ESME using OpenSMPPBox

[Ruben Melikyan]

Try to set in smsc config the following line:
reroute-dlr=true

Best regards,
Ruben Melikyan

> On 8 May 2022, at 10:32, christopher kamutumwa  
> wrote:
> 
> 
> I have configured my servers to send from ESME to SMSC through OpenSMPPBox,
> i have applied the below flow
> ESME -->> OpenSMPPBox -->> SQLBox -->>Bearerbox -->> SMSC
> I have succeeded in sending the sms from ESME to the SMSC but my problem is
> related to the DLR.
> The Bearerbox actually received the DLR from the SMSC but it didn't route
> it to the ESME.
> 
> What is the required configurations that could resolve the above issue. i
> need to route the DLR to the ESME
> 
> Your help in this regard is highly appreciated and thanks in advance.i can 
> see entries in db when i send msg
> 
> Below are my config files and log error,
> 2022-05-07 14:36:47 [3023] [7] DEBUG: DLR[mysql]: Looking for DLR smsc=smpp1, 
> ts=1a11039a-901d-43e3-8f99-1b42fa14aacb, dst=+260976198318, type=1
> 2022-05-07 14:36:47 [3023] [7] DEBUG: sql: SELECT `mask`, `service`, `url`, 
> `source`, `destination`, `boxcid` FROM `dlr` WHERE `smsc`=? AND `ts`=?  LIMIT 
> 1
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=mask buffer_type=253 
> max_length=0 length=4
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=service buffer_type=253 
> max_length=0 length=16
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=url buffer_type=253 max_length=0 
> length=2048
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=source buffer_type=253 
> max_length=0 length=32
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=destination buffer_type=253 
> max_length=0 length=32
> 2022-05-07 14:36:47 [3023] [7] DEBUG: column=boxcid buffer_type=253 
> max_length=0 length=16
> 2022-05-07 14:36:47 [3023] [7] WARNING: DLR[mysql]: DLR from SMSC for 
> DST<+260976198318> not found.
> 2022-05-07 14:36:47 [3023] [7] WARNING: msg_to_pdu failed, sending negative 
> ack
> *** Kannel.conf 
> #-
> # core setup
> 
> group = core
> admin-port = 13000
> smsbox-port = 13001
> wapbox-port = 13002
> admin-password = admin123
> status-password = status123
> wdp-interface-name = "*"
> log-file = "/usr/local/kannel/bearerbox.log"
> log-level = 3
> access-log = "/usr/local/kannel/bearerboxaccess.log"
> store-type = spool
> store-location = "/usr/local/kannel/store"
> store-dump-freq = 60
> #-
> # smsc setup
> 
> group = smsc
> smsc = smpp
> smsc-id = VFSMPP1
> host = "x.x.x.x"
> port = 
> smsc-username = egypt321
> smsc-password = egypt321
> system-type = "egypt321"
> address-range = ""
> dest-addr-ton=1
> dest-addr-npi=1
> interface-version = 34
> enquire-link-interval = 25
> reconnect-delay = 15
> transceiver-mode = 1
> #max-pending-submits = 8
> throughput = 6
> #-
> # smsbox setup
> 
> group = smsbox
> smsbox-id = smsbox1
> bearerbox-host = "127.0.0.1"
> sendsms-port = 13013
> sendsms-chars = "0123456789 +-"
> log-file = "/usr/local/kannel/smsbox.log"
> log-level = 3
> access-log = "/usr/local/kannel/smsboxaccess.log"
> mo-recode = true
> http-request-retry = 1000
> max-pending-requests = 33000
> #-
> # smsbox-route setup
> 
> group = smsbox-route
> smsbox-id = smsc1
> smsc-id = VFSMPP1
> ###
> 
> *** OpenSMPPBox.conf **
> group = core
> dlr-storage = internal
> 
> group = opensmppbox
> bearerbox-host = 127.0.0.1
> bearerbox-port = 13005
> opensmppbox-id = opensmppbox1
> opensmppbox-port = 13003
> log-file = "/usr/local/kannel/smppbox.log"
> #log-level = 3
> our-system-id = Inaccess
> #route-to-smsc = cardboard
> smpp-logins = /usr/local/kannel/smpplogins.txt
> ###
> 
> *** smpplogins.txt***
> test testpw smsc1 *.*.*.*
> ###
> 
> *** SQLBox.conf ***
> group = sqlbox
> id = sqlbox-db
> smsbox-id = sqlbox
> global-sender = ""
> bearerbox-host = 127.0.0.1
> bearerbox-port = 13001
> smsbox-port = 13005
> smsbox-port-ssl = false
> sql-log-table = sent_sms
> sql-insert-table = send_sms
> log-file = "/usr/local/kannel/kannel-sqlbox.log"
> 
> # MYSQL Connection
> group = mysql-connection
> id = sqlbox-db
> host = localhost
> username = root
> password = root
> database = mysqlbox
> ###
> 
> 
> 
> Regards,
> 
>   Virus-free. www.avg.com

Routing DLR to ESME using OpenSMPPBox

[christopher kamutumwa]

I have configured my servers to send from ESME to SMSC through OpenSMPPBox,
i have applied the below flow
ESME -->> OpenSMPPBox -->> SQLBox -->>Bearerbox -->> SMSC

I have succeeded in sending the sms from ESME to the SMSC but my problem is
related to the DLR.
The Bearerbox actually received the DLR from the SMSC but it didn't route
it to the ESME.

What is the required configurations that could resolve the above issue. i
need to route the DLR to the ESME

Your help in this regard is highly appreciated and thanks in advance.i
can see entries in db when i send msg

Below are my config files and log error,
2022-05-07 14:36:47 [3023] [7] DEBUG: DLR[mysql]: Looking for DLR
smsc=smpp1, ts=1a11039a-901d-43e3-8f99-1b42fa14aacb,
dst=+260976198318, type=1
2022-05-07 14:36:47 [3023] [7] DEBUG: sql: SELECT `mask`, `service`,
`url`, `source`, `destination`, `boxcid` FROM `dlr` WHERE `smsc`=? AND
`ts`=?  LIMIT 1
2022-05-07 14:36:47 [3023] [7] DEBUG: column=mask buffer_type=253
max_length=0 length=4
2022-05-07 14:36:47 [3023] [7] DEBUG: column=service buffer_type=253
max_length=0 length=16
2022-05-07 14:36:47 [3023] [7] DEBUG: column=url buffer_type=253
max_length=0 length=2048
2022-05-07 14:36:47 [3023] [7] DEBUG: column=source buffer_type=253
max_length=0 length=32
2022-05-07 14:36:47 [3023] [7] DEBUG: column=destination
buffer_type=253 max_length=0 length=32
2022-05-07 14:36:47 [3023] [7] DEBUG: column=boxcid buffer_type=253
max_length=0 length=16
2022-05-07 14:36:47 [3023] [7] WARNING: DLR[mysql]: DLR from
SMSC for DST<+260976198318> not found.
2022-05-07 14:36:47 [3023] [7] WARNING: msg_to_pdu failed, sending negative ack

*** Kannel.conf 
#-
# core setup

group = core
admin-port = 13000
smsbox-port = 13001
wapbox-port = 13002
admin-password = admin123
status-password = status123
wdp-interface-name = "*"
log-file = "/usr/local/kannel/bearerbox.log"
log-level = 3
access-log = "/usr/local/kannel/bearerboxaccess.log"
store-type = spool
store-location = "/usr/local/kannel/store"
store-dump-freq = 60
#-
# smsc setup

group = smsc
smsc = smpp
smsc-id = VFSMPP1
host = "x.x.x.x"
port = 
smsc-username = egypt321
smsc-password = egypt321
system-type = "egypt321"
address-range = ""
dest-addr-ton=1
dest-addr-npi=1
interface-version = 34
enquire-link-interval = 25
reconnect-delay = 15
transceiver-mode = 1
#max-pending-submits = 8
throughput = 6
#-
# smsbox setup

group = smsbox
smsbox-id = smsbox1
bearerbox-host = "127.0.0.1"
sendsms-port = 13013
sendsms-chars = "0123456789 +-"
log-file = "/usr/local/kannel/smsbox.log"
log-level = 3
access-log = "/usr/local/kannel/smsboxaccess.log"
mo-recode = true
http-request-retry = 1000
max-pending-requests = 33000
#-
# smsbox-route setup

group = smsbox-route
smsbox-id = smsc1
smsc-id = VFSMPP1
#######

*** OpenSMPPBox.conf **
group = core
dlr-storage = internal

group = opensmppbox
bearerbox-host = 127.0.0.1
bearerbox-port = 13005
opensmppbox-id = opensmppbox1
opensmppbox-port = 13003
log-file = "/usr/local/kannel/smppbox.log"
#log-level = 3
our-system-id = Inaccess
#route-to-smsc = cardboard
smpp-logins = /usr/local/kannel/smpplogins.txt
###

*** smpplogins.txt***
test testpw smsc1 *.*.*.*
###

*** SQLBox.conf ***
group = sqlbox
id = sqlbox-db
smsbox-id = sqlbox
global-sender = ""
bearerbox-host = 127.0.0.1
bearerbox-port = 13001
smsbox-port = 13005
smsbox-port-ssl = false
sql-log-table = sent_sms
sql-insert-table = send_sms
log-file = "/usr/local/kannel/kannel-sqlbox.log"

# MYSQL Connection
group = mysql-connection
id = sqlbox-db
host = localhost
username = root
password = root
database = mysqlbox
###



Regards,


<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

RE: OpenSMPPBox won't create DLR

[Rene Kluwen]

Hi Martin,

 

About Github: +1 from me, how about the main developer(s) in charge?

 

The force-dlr option is a good idea, but it’s better to implement it in 
bearerbox, as in your use-case you always want it – not just for messages 
relayed via opensmppbox?

I’m not sure if something like that already exists.

 

True, that -besides that- also it needs to be implemented in opensmppbox to 
keep the dlr store.

 

== Rene

 

Van: Martin Caetano  
Verzonden: vrijdag 30 april 2021 02:18
Aan: Rene Kluwen 
CC: users@kannel.org
Onderwerp: Re: OpenSMPPBox won't create DLR

 

 

Are the submit_sm's sent with registered_delivery set to 1?

 

It wasn’t and that was the issue. Now it is creating the DLR and storing them 
in the db. Thank you!

 

However, for our case this option is inconvenient as we plan to allow customers 
to connect via SMPP and use DLR for tracking billing. If we allow the customers 
to set dlr off we won’t be able to charge them.

 

As a solution I manually edited the opensmppbox.c file and “forced” a dlr-mask 
setting and removed the registered_delivery check: 

 

https://redmine.kannel.org/projects/smppbox/repository/entry/trunk/gw/opensmppbox.c#L1254
 

 

I believe it would be useful to enable this functionality (force-dlr) as an 
option on the smppopenbox settings.

 

I’m happy to send it as a patch if it is considered worth of adding to the 
project.

 

By the way, wouldn’t be better to migrate the kannel to Github and ditch 
subversion? I guess it would encourage more collaboration and make life easier 
for everybody.

 

Martin.





On Apr 29, 2021, at 4:18 PM, Rene Kluwen mailto:rene.klu...@chimit.nl> > wrote:

 

Hi Martin,

Looks like you got opensmppbox setup correctly for dlr.
Adding or omitting sqlbox won't make a difference, like you already saw that
correctly.

Could you list if there is any rows available in the dlr table in your
postgres database?

Are the submit_sm's sent with registered_delivery set to 1?

It could be a msg-id-type issue. I'm not even sure if that's implemented in
opensmppbox.

== Rene


-Oorspronkelijk bericht-
Van: users mailto:users-boun...@kannel.org> > Namens 
Martin Caetano
Verzonden: donderdag 29 april 2021 21:01
Aan: users@kannel.org <mailto:users@kannel.org> 
Onderwerp: OpenSMPPBox won't create DLR

I've spent a significant amount of time around this issue. I've read the
complete Kannel guide, SO, Nabble and any other resource I could find yet I
couldn't find any solution or hint on why the DLR aren't being created. 

I believe what I'm trying to do is very straightforward: 

I'm connected using SMPP to OpenSMPPBox, using PostgreSQL and routing to a
SMPP SMSC like this: 

opensmppbox --> sqlbox ->  bearerbox -> smsc 

I can send SMS with no problem to the other end and I can see the pdu
responses back in the logs. However, the DLRs aren't being created as they
are when I use HTTP with smsbox and dlr-mask/dlr-url params. 

It doesn't matter if I remove the sqlbox and use internal storage, the DLRs
are never being created (or at least never appear as created in the logs)
when connecting via smpp to opensmppbox. 

2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: throughput (0.00,0.00)
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: Got PDU:
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU 0x7eff380010e0 dump:
2021-04-29 05:28:14 [35121] [6] DEBUG:   type_name: deliver_sm
2021-04-29 05:28:14 [35121] [6] DEBUG:   command_id: 5 = 0x0005
2021-04-29 05:28:14 [35121] [6] DEBUG:   command_status: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sequence_number: 31 = 0x001f
2021-04-29 05:28:14 [35121] [6] DEBUG:   service_type: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_ton: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_npi: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr: "xx"
2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_ton: 5 = 0x0005
2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_npi: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   destination_addr: "MySender"
2021-04-29 05:28:14 [35121] [6] DEBUG:   esm_class: 4 = 0x0004
2021-04-29 05:28:14 [35121] [6] DEBUG:   protocol_id: 8 = 0x0008
2021-04-29 05:28:14 [35121] [6] DEBUG:   priority_flag: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   schedule_delivery_time: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   validity_period: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   registered_delivery: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   replace_if_present_flag: 0 =
0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   data_coding: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_default_msg_id: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_length: 105 = 0x0069
2021-04-29 05:28:14 [35121] [6] DEBUG:   short_message:
2021-04-29 05:28:14 [35121] [6] DEBUG:Octet string at 0x7eff38001340:

Re: OpenSMPPBox won't create DLR

[Martin Caetano]

> Are the submit_sm's sent with registered_delivery set to 1?

It wasn’t and that was the issue. Now it is creating the DLR and storing them 
in the db. Thank you!

However, for our case this option is inconvenient as we plan to allow customers 
to connect via SMPP and use DLR for tracking billing. If we allow the customers 
to set dlr off we won’t be able to charge them.

As a solution I manually edited the opensmppbox.c file and “forced” a dlr-mask 
setting and removed the registered_delivery check: 

https://redmine.kannel.org/projects/smppbox/repository/entry/trunk/gw/opensmppbox.c#L1254
 
<https://redmine.kannel.org/projects/smppbox/repository/entry/trunk/gw/opensmppbox.c#L1254>
 

I believe it would be useful to enable this functionality (force-dlr) as an 
option on the smppopenbox settings.

I’m happy to send it as a patch if it is considered worth of adding to the 
project.

By the way, wouldn’t be better to migrate the kannel to Github and ditch 
subversion? I guess it would encourage more collaboration and make life easier 
for everybody.

Martin.

> On Apr 29, 2021, at 4:18 PM, Rene Kluwen  wrote:
> 
> Hi Martin,
> 
> Looks like you got opensmppbox setup correctly for dlr.
> Adding or omitting sqlbox won't make a difference, like you already saw that
> correctly.
> 
> Could you list if there is any rows available in the dlr table in your
> postgres database?
> 
> Are the submit_sm's sent with registered_delivery set to 1?
> 
> It could be a msg-id-type issue. I'm not even sure if that's implemented in
> opensmppbox.
> 
> == Rene
> 
> 
> -Oorspronkelijk bericht-
> Van: users  Namens Martin Caetano
> Verzonden: donderdag 29 april 2021 21:01
> Aan: users@kannel.org
> Onderwerp: OpenSMPPBox won't create DLR
> 
> I've spent a significant amount of time around this issue. I've read the
> complete Kannel guide, SO, Nabble and any other resource I could find yet I
> couldn't find any solution or hint on why the DLR aren't being created. 
> 
> I believe what I'm trying to do is very straightforward: 
> 
> I'm connected using SMPP to OpenSMPPBox, using PostgreSQL and routing to a
> SMPP SMSC like this: 
> 
> opensmppbox --> sqlbox ->  bearerbox -> smsc 
> 
> I can send SMS with no problem to the other end and I can see the pdu
> responses back in the logs. However, the DLRs aren't being created as they
> are when I use HTTP with smsbox and dlr-mask/dlr-url params. 
> 
> It doesn't matter if I remove the sqlbox and use internal storage, the DLRs
> are never being created (or at least never appear as created in the logs)
> when connecting via smpp to opensmppbox. 
> 
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: throughput (0.00,0.00)
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: Got PDU:
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU 0x7eff380010e0 dump:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   type_name: deliver_sm
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   command_id: 5 = 0x0005
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   command_status: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sequence_number: 31 = 0x001f
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   service_type: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_ton: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_npi: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr: "xx"
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_ton: 5 = 0x0005
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_npi: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   destination_addr: "MySender"
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   esm_class: 4 = 0x0004
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   protocol_id: 8 = 0x0008
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   priority_flag: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   schedule_delivery_time: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   validity_period: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   registered_delivery: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   replace_if_present_flag: 0 =
> 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   data_coding: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_default_msg_id: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_length: 105 = 0x0069
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   short_message:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:Octet string at 0x7eff38001340:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  len:  105
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  size: 106
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  immutable: 0
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 69 64 3a 37 32 36 34 37 33
&

Re: OpenSMPPBox won't create DLR

[Web Min]

I was getting the same issue but now I'm getting the below error from the
access-log

2021-04-27 23:testsender08:20 2021-04-27 23:08:20 DISCARDED SMS [SMSC:]
[SVC:] [ACT:] [BINF:] [FID:18][from:testsender] [to:2378945612]
[flags:-1:2:-1:-1:31] [msg:0:] [udh:0:]
2021-04-27 23:08:20 2021-04-27 23:08:20 Receive DLR [SMSC:] [SVC:] [ACT:]
[BINF:] [FID:18][from:testsender] [to:2378945612] [flags:-1:-1:-1:-1:16]
[msg:12:NACK/no SMSC] [udh:0:]
2021-04-27 23:09:21 2021-04-27 23:08:20 DISCARDED SMS [SMSC:smsc1] [SVC:]
[ACT:] [BINF:] [FID:17][from:testsender] [to:2378945612]
[flags:-1:2:-1:-1:31] [msg:0:] [udh:0:]
2021-04-27 23:09:21 2021-04-27 23:09:21 Receive DLR [SMSC:smsc1] [SVC:]
[ACT:] [BINF:] [FID:17][from:testsender] [to:2378945612]
[flags:-1:-1:-1:-1:16] [msg:21:NACK/Retries Exceeded] [udh:0:]

Any idea about the discarded msgs?



On Thu, Apr 29, 2021 at 10:26 PM Rene Kluwen  wrote:

> Hi Martin,
>
> Looks like you got opensmppbox setup correctly for dlr.
> Adding or omitting sqlbox won't make a difference, like you already saw
> that
> correctly.
>
> Could you list if there is any rows available in the dlr table in your
> postgres database?
>
> Are the submit_sm's sent with registered_delivery set to 1?
>
> It could be a msg-id-type issue. I'm not even sure if that's implemented in
> opensmppbox.
>
> == Rene
>
>
> -Oorspronkelijk bericht-
> Van: users  Namens Martin Caetano
> Verzonden: donderdag 29 april 2021 21:01
> Aan: users@kannel.org
> Onderwerp: OpenSMPPBox won't create DLR
>
> I've spent a significant amount of time around this issue. I've read the
> complete Kannel guide, SO, Nabble and any other resource I could find yet I
> couldn't find any solution or hint on why the DLR aren't being created.
>
> I believe what I'm trying to do is very straightforward:
>
> I'm connected using SMPP to OpenSMPPBox, using PostgreSQL and routing to a
> SMPP SMSC like this:
>
> opensmppbox --> sqlbox ->  bearerbox -> smsc
>
> I can send SMS with no problem to the other end and I can see the pdu
> responses back in the logs. However, the DLRs aren't being created as they
> are when I use HTTP with smsbox and dlr-mask/dlr-url params.
>
> It doesn't matter if I remove the sqlbox and use internal storage, the DLRs
> are never being created (or at least never appear as created in the logs)
> when connecting via smpp to opensmppbox.
>
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: throughput (0.00,0.00)
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: Got PDU:
> 2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU 0x7eff380010e0 dump:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   type_name: deliver_sm
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   command_id: 5 = 0x0005
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   command_status: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sequence_number: 31 = 0x001f
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   service_type: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_ton: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_npi: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr: "xx"
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_ton: 5 = 0x0005
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_npi: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   destination_addr: "MySender"
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   esm_class: 4 = 0x0004
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   protocol_id: 8 = 0x0008
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   priority_flag: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   schedule_delivery_time: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   validity_period: NULL
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   registered_delivery: 0 =
> 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   replace_if_present_flag: 0 =
> 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   data_coding: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_default_msg_id: 0 = 0x
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_length: 105 = 0x0069
> 2021-04-29 05:28:14 [35121] [6] DEBUG:   short_message:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:Octet string at 0x7eff38001340:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  len:  105
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  size: 106
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  immutable: 0
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 69 64 3a 37 32 36 34 37
> 33
> 33 37 20 73 75 62 3a   id:72647337 sub:
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 30 20 64 6c 76 72 64 3a
> 32
> 38 20 73 75 62 6d 69   0 dlvrd:28 submi
> 2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 74 20 64 61 74 65 3a 3

RE: OpenSMPPBox won't create DLR

[Rene Kluwen]

Hi Martin,

Looks like you got opensmppbox setup correctly for dlr.
Adding or omitting sqlbox won't make a difference, like you already saw that
correctly.

Could you list if there is any rows available in the dlr table in your
postgres database?

Are the submit_sm's sent with registered_delivery set to 1?

It could be a msg-id-type issue. I'm not even sure if that's implemented in
opensmppbox.

== Rene


-Oorspronkelijk bericht-
Van: users  Namens Martin Caetano
Verzonden: donderdag 29 april 2021 21:01
Aan: users@kannel.org
Onderwerp: OpenSMPPBox won't create DLR

I've spent a significant amount of time around this issue. I've read the
complete Kannel guide, SO, Nabble and any other resource I could find yet I
couldn't find any solution or hint on why the DLR aren't being created. 

I believe what I'm trying to do is very straightforward: 

I'm connected using SMPP to OpenSMPPBox, using PostgreSQL and routing to a
SMPP SMSC like this: 

opensmppbox --> sqlbox ->  bearerbox -> smsc 

I can send SMS with no problem to the other end and I can see the pdu
responses back in the logs. However, the DLRs aren't being created as they
are when I use HTTP with smsbox and dlr-mask/dlr-url params. 

It doesn't matter if I remove the sqlbox and use internal storage, the DLRs
are never being created (or at least never appear as created in the logs)
when connecting via smpp to opensmppbox. 

2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: throughput (0.00,0.00)
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: Got PDU:
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU 0x7eff380010e0 dump:
2021-04-29 05:28:14 [35121] [6] DEBUG:   type_name: deliver_sm
2021-04-29 05:28:14 [35121] [6] DEBUG:   command_id: 5 = 0x0005
2021-04-29 05:28:14 [35121] [6] DEBUG:   command_status: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sequence_number: 31 = 0x001f
2021-04-29 05:28:14 [35121] [6] DEBUG:   service_type: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_ton: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_npi: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr: "xx"
2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_ton: 5 = 0x0005
2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_npi: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   destination_addr: "MySender"
2021-04-29 05:28:14 [35121] [6] DEBUG:   esm_class: 4 = 0x0004
2021-04-29 05:28:14 [35121] [6] DEBUG:   protocol_id: 8 = 0x0008
2021-04-29 05:28:14 [35121] [6] DEBUG:   priority_flag: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   schedule_delivery_time: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   validity_period: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   registered_delivery: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   replace_if_present_flag: 0 =
0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   data_coding: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_default_msg_id: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_length: 105 = 0x0069
2021-04-29 05:28:14 [35121] [6] DEBUG:   short_message:
2021-04-29 05:28:14 [35121] [6] DEBUG:Octet string at 0x7eff38001340:
2021-04-29 05:28:14 [35121] [6] DEBUG:  len:  105
2021-04-29 05:28:14 [35121] [6] DEBUG:  size: 106
2021-04-29 05:28:14 [35121] [6] DEBUG:  immutable: 0
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 69 64 3a 37 32 36 34 37 33
33 37 20 73 75 62 3a   id:72647337 sub:
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 30 20 64 6c 76 72 64 3a 32
38 20 73 75 62 6d 69   0 dlvrd:28 submi
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 74 20 64 61 74 65 3a 32 31
30 34 32 39 30 32 32   t date:210429022
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 38 20 64 6f 6e 65 20 64 61
74 65 3a 32 31 30 34   8 done date:2104
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 32 39 30 32 32 38 20 73 74
61 74 3a 45 4e 52 4f   290228 stat:ENRO
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 55 54 45 20 65 72 72 3a 30
20 54 65 78 74 3a 48   UTE err:0 Text:H
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 65 6c 6c 6f 20 54 65 78 74
ello Text
2021-04-29 05:28:14 [35121] [6] DEBUG:Octet string dump ends.
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU dump ends.
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1] handle_pdu, got DLR
2021-04-29 05:28:14 [35121] [6] DEBUG: DLR[pgsql]: Looking for DLR
smsc=smsc1, ts=72647337, dst=xx, type=4
2021-04-29 05:28:14 [35121] [6] DEBUG: sql: SELECT "mask", "service", "url",
"source", "destination", "boxc" FROM "dlr" WHERE "smsc"='smsc1' AND
"ts"='72647337'  LIMIT 1;
2021-04-29 05:28:14 [35121] [6] DEBUG: no rows found
2021-04-29 05:28:14 [35121] [6] WARNING: DLR[pgsql]: DLR from SMSC
for DST not found.
2021-04-29 05:28:14 [35121] [6] ERROR: SMPP[smsc1]: got DLR but could not
find messag

OpenSMPPBox won't create DLR

[Martin Caetano]

I've spent a significant amount of time around this issue. I've read the 
complete Kannel guide, SO, Nabble and any other resource I could find yet I 
couldn't find any solution or hint on why the DLR aren't being created. 

I believe what I'm trying to do is very straightforward: 

I'm connected using SMPP to OpenSMPPBox, using PostgreSQL and routing to a SMPP 
SMSC like this: 

opensmppbox --> sqlbox ->  bearerbox -> smsc 

I can send SMS with no problem to the other end and I can see the pdu responses 
back in the logs. However, the DLRs aren't being created as they are when I use 
HTTP with smsbox and dlr-mask/dlr-url params. 

It doesn't matter if I remove the sqlbox and use internal storage, the DLRs are 
never being created (or at least never appear as created in the logs) when 
connecting via smpp to opensmppbox. 

2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: throughput (0.00,0.00)
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: Got PDU:
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU 0x7eff380010e0 dump:
2021-04-29 05:28:14 [35121] [6] DEBUG:   type_name: deliver_sm
2021-04-29 05:28:14 [35121] [6] DEBUG:   command_id: 5 = 0x0005
2021-04-29 05:28:14 [35121] [6] DEBUG:   command_status: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sequence_number: 31 = 0x001f
2021-04-29 05:28:14 [35121] [6] DEBUG:   service_type: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_ton: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr_npi: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   source_addr: "xx"
2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_ton: 5 = 0x0005
2021-04-29 05:28:14 [35121] [6] DEBUG:   dest_addr_npi: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   destination_addr: "MySender"
2021-04-29 05:28:14 [35121] [6] DEBUG:   esm_class: 4 = 0x0004
2021-04-29 05:28:14 [35121] [6] DEBUG:   protocol_id: 8 = 0x0008
2021-04-29 05:28:14 [35121] [6] DEBUG:   priority_flag: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   schedule_delivery_time: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   validity_period: NULL
2021-04-29 05:28:14 [35121] [6] DEBUG:   registered_delivery: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   replace_if_present_flag: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   data_coding: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_default_msg_id: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sm_length: 105 = 0x0069
2021-04-29 05:28:14 [35121] [6] DEBUG:   short_message:
2021-04-29 05:28:14 [35121] [6] DEBUG:Octet string at 0x7eff38001340:
2021-04-29 05:28:14 [35121] [6] DEBUG:  len:  105
2021-04-29 05:28:14 [35121] [6] DEBUG:  size: 106
2021-04-29 05:28:14 [35121] [6] DEBUG:  immutable: 0
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 69 64 3a 37 32 36 34 37 33 33 
37 20 73 75 62 3a   id:72647337 sub:
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 30 20 64 6c 76 72 64 3a 32 38 
20 73 75 62 6d 69   0 dlvrd:28 submi
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 74 20 64 61 74 65 3a 32 31 30 
34 32 39 30 32 32   t date:210429022
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 38 20 64 6f 6e 65 20 64 61 74 
65 3a 32 31 30 34   8 done date:2104
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 32 39 30 32 32 38 20 73 74 61 
74 3a 45 4e 52 4f   290228 stat:ENRO
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 55 54 45 20 65 72 72 3a 30 20 
54 65 78 74 3a 48   UTE err:0 Text:H
2021-04-29 05:28:14 [35121] [6] DEBUG:  data: 65 6c 6c 6f 20 54 65 78 74
ello Text
2021-04-29 05:28:14 [35121] [6] DEBUG:Octet string dump ends.
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU dump ends.
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1] handle_pdu, got DLR
2021-04-29 05:28:14 [35121] [6] DEBUG: DLR[pgsql]: Looking for DLR smsc=smsc1, 
ts=72647337, dst=xx, type=4
2021-04-29 05:28:14 [35121] [6] DEBUG: sql: SELECT "mask", "service", "url", 
"source", "destination", "boxc" FROM "dlr" WHERE "smsc"='smsc1' AND 
"ts"='72647337'  LIMIT 1;
2021-04-29 05:28:14 [35121] [6] DEBUG: no rows found
2021-04-29 05:28:14 [35121] [6] WARNING: DLR[pgsql]: DLR from SMSC for 
DST not found.
2021-04-29 05:28:14 [35121] [6] ERROR: SMPP[smsc1]: got DLR but could not find 
message or was not interested in it id<72647337> dst, type<4>
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP[smsc1]: Sending PDU:
2021-04-29 05:28:14 [35121] [6] DEBUG: SMPP PDU 0x7eff38001ec0 dump:
2021-04-29 05:28:14 [35121] [6] DEBUG:   type_name: deliver_sm_resp
2021-04-29 05:28:14 [35121] [6] DEBUG:   command_id: 2147483653 = 0x8005
2021-04-29 05:28:14 [35121] [6] DEBUG:   command_status: 0 = 0x
2021-04-29 05:28:14 [35121] [6] DEBUG:   sequence_number: 31 = 0x001f
2021-04-29 05:28:14 [35121] [6] DEBUG:   message

Issue/Bug in opensmppbox

[mosbah abdelkader]

Hello all,

We got a ticket from a customer where the sms has not received final
dlr (status still in ACK).

We analyzed our packet trace and we found that our opensmppbox sent
the deliver_sm before sending the submit_sm_resp which leads to
mis-interpretation of the dlr on their side !!.

The deliver_sm was packed with 3 other smpp responses and the same for
the submit_sm_resp but the two were sent in separate packets. And,
deliver_sm was sent before submit_sm_resp.

Any help how we can fix this.

BR.

Re: OPENSMPPBOX code 0x0000000d (Bind Failed) help

[Mesbahuddin Malik]

Hello ,
Use space check opensmpp manual and be sure to add the system_type
parameter  correctly at  client end.
system-id-01 password-01 system-type-0
mesbah mesbah kannel 10.10.10.1
Please check and let me know if you face any problem.
Regards
Mesbah

On Mon, Nov 30, 2020 at 4:33 PM Michael Osakede  wrote:

> Hi,
>
> Its is separated by SPACE or TAB?
> Do you have a functional login configuration?
>
> Michael.
>
> On Mon, 30 Nov 2020, 10:22 am Rene Kluwen,  wrote:
>
>> You could double check your smpplogins.txt.
>>
>>
>>
>> == Rene
>>
>>
>>
>> *Van:* users  *Namens *Michael Osakede
>> *Verzonden:* maandag 30 november 2020 03:06
>> *Aan:* users@kannel.org
>> *Onderwerp:* OPENSMPPBOX code 0x000d (Bind Failed) help
>>
>>
>>
>> Hello,
>>
>>
>>
>> I have this setup
>>
>>
>>
>> KANNEL SMSC <==> OPENSMPPBOX Server
>>
>> below are the opensmppbox and kannel config.
>>
>>
>>
>> OPENSMPPBOX
>>
>> group = core
>> dlr-storage = internal
>>
>> group = opensmppbox
>> opensmppbox-id = orange
>> opensmppbox-port = 1991
>> bearerbox-host = localhost
>> bearerbox-port = 13001
>> our-system-id = orange_vezeti
>> smpp-logins = "/etc/kannel/box/smpplogins.txt"
>> route-to-smsc = MEDIATEL
>> log-level = 0
>> log-file = /tmp/smppbox.log
>>
>> OPENSMPP Users
>>
>> mike mike orange 78.208.228.38
>>
>>
>>
>> CONNECTING Kannel SMSC
>>
>> # SMSC SMPP
>> group = smsc
>> smsc-id = orange
>> smsc = smpp
>> host = 156.0.249.122
>> port = 1991
>> #receive-port = 2346
>> smsc-username = mike
>> smsc-password = mike
>> system-type = orange
>> #interface-version = 52
>> keepalive = 50
>> allowed-smsc-id = orange
>> transceiver-mode = true
>> msg-id-type =  0x00
>> throughput = 10
>> max-pending-submits = 10
>> wait-ack = 600
>>
>>
>>
>> Kannel Log
>>
>> ] DEBUG: Connecting to <156.0.249.122>
>> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP[orange]: Sending PDU:
>> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU 0x7f1154000a10 dump:
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   type_name: bind_transceiver
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   command_id: 9 = 0x0009
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   command_status: 0 = 0x
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   sequence_number: 91 = 0x005b
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   system_id: "mike"
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   password: "mike"
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   system_type: "orange"
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   interface_version: 52 =
>> 0x0034
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   addr_ton: 0 = 0x
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   addr_npi: 0 = 0x
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   address_range: NULL
>> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU dump ends.
>> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP[orange]: Got PDU:
>> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU 0x7f1154000a10 dump:
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   type_name: bind_transceiver_resp
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   command_id: 2147483657 =
>> 0x8009
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   command_status: 13 = 0x000d
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   sequence_number: 91 = 0x005b
>> 2020-11-30 00:51:50 [18114] [6] DEBUG:   system_id: NULL
>> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU dump ends.
>> 2020-11-30 00:51:50 [18114] [6] ERROR: SMPP[orange]: SMSC rejected login
>> to transmit, code 0x000d (Bind Failed).
>> 2020-11-30 00:51:50 [18114] [6] ERROR: SMPP[orange]: Couldn't connect to
>> SMS center (retrying in 10 seconds).
>>
>>
>>
>> OPENSMPP Log
>>
>> 2020-11-30 02:53:26 [19202] [0] DEBUG: Started thread 1
>> (opensmppbox.c:function)
>> 2020-11-30 02:53:26 [19202] [1] DEBUG: Thread 1 (opensmppbox.c:function)
>> maps to pid 19202.
>> 2020-11-30 02:53:26 [19202] [1] INFO: Client connected from
>> <74.208.228.38>
>> 2020-11-30 02:53:26 [19202] [1] DEBUG: Connecting to <127.0.0.1>
>> 2020-11-30 02:53:26 [19202] [1] INFO: Connected to bearerbox at localhost
>> port 13001.
>> 2020-11-30 02:53:26 [19202] [1] DEBUG: Started thread 2
>> (opensmppbox.c:smpp_to_bearerbox)
>> 2020-11-30 02:53:26 [19202] [2] DEBUG:

Re: OPENSMPPBOX code 0x0000000d (Bind Failed) help

[Michael Osakede]

Hi,

Its is separated by SPACE or TAB?
Do you have a functional login configuration?

Michael.

On Mon, 30 Nov 2020, 10:22 am Rene Kluwen,  wrote:

> You could double check your smpplogins.txt.
>
>
>
> == Rene
>
>
>
> *Van:* users  *Namens *Michael Osakede
> *Verzonden:* maandag 30 november 2020 03:06
> *Aan:* users@kannel.org
> *Onderwerp:* OPENSMPPBOX code 0x000d (Bind Failed) help
>
>
>
> Hello,
>
>
>
> I have this setup
>
>
>
> KANNEL SMSC <==> OPENSMPPBOX Server
>
> below are the opensmppbox and kannel config.
>
>
>
> OPENSMPPBOX
>
> group = core
> dlr-storage = internal
>
> group = opensmppbox
> opensmppbox-id = orange
> opensmppbox-port = 1991
> bearerbox-host = localhost
> bearerbox-port = 13001
> our-system-id = orange_vezeti
> smpp-logins = "/etc/kannel/box/smpplogins.txt"
> route-to-smsc = MEDIATEL
> log-level = 0
> log-file = /tmp/smppbox.log
>
> OPENSMPP Users
>
> mike mike orange 78.208.228.38
>
>
>
> CONNECTING Kannel SMSC
>
> # SMSC SMPP
> group = smsc
> smsc-id = orange
> smsc = smpp
> host = 156.0.249.122
> port = 1991
> #receive-port = 2346
> smsc-username = mike
> smsc-password = mike
> system-type = orange
> #interface-version = 52
> keepalive = 50
> allowed-smsc-id = orange
> transceiver-mode = true
> msg-id-type =  0x00
> throughput = 10
> max-pending-submits = 10
> wait-ack = 600
>
>
>
> Kannel Log
>
> ] DEBUG: Connecting to <156.0.249.122>
> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP[orange]: Sending PDU:
> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU 0x7f1154000a10 dump:
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   type_name: bind_transceiver
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   command_id: 9 = 0x0009
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   command_status: 0 = 0x
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   sequence_number: 91 = 0x005b
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   system_id: "mike"
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   password: "mike"
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   system_type: "orange"
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   interface_version: 52 = 0x0034
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   addr_ton: 0 = 0x
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   addr_npi: 0 = 0x
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   address_range: NULL
> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU dump ends.
> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP[orange]: Got PDU:
> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU 0x7f1154000a10 dump:
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   type_name: bind_transceiver_resp
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   command_id: 2147483657 =
> 0x8009
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   command_status: 13 = 0x000d
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   sequence_number: 91 = 0x005b
> 2020-11-30 00:51:50 [18114] [6] DEBUG:   system_id: NULL
> 2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU dump ends.
> 2020-11-30 00:51:50 [18114] [6] ERROR: SMPP[orange]: SMSC rejected login
> to transmit, code 0x000d (Bind Failed).
> 2020-11-30 00:51:50 [18114] [6] ERROR: SMPP[orange]: Couldn't connect to
> SMS center (retrying in 10 seconds).
>
>
>
> OPENSMPP Log
>
> 2020-11-30 02:53:26 [19202] [0] DEBUG: Started thread 1
> (opensmppbox.c:function)
> 2020-11-30 02:53:26 [19202] [1] DEBUG: Thread 1 (opensmppbox.c:function)
> maps to pid 19202.
> 2020-11-30 02:53:26 [19202] [1] INFO: Client connected from <74.208.228.38>
> 2020-11-30 02:53:26 [19202] [1] DEBUG: Connecting to <127.0.0.1>
> 2020-11-30 02:53:26 [19202] [1] INFO: Connected to bearerbox at localhost
> port 13001.
> 2020-11-30 02:53:26 [19202] [1] DEBUG: Started thread 2
> (opensmppbox.c:smpp_to_bearerbox)
> 2020-11-30 02:53:26 [19202] [2] DEBUG: Thread 2
> (opensmppbox.c:smpp_to_bearerbox) maps to pid 19202.
> 2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP[orange]: Got PDU:
> 2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU 0x7fa51c000d50 dump:
> 2020-11-30 02:53:26 [19202] [2] DEBUG:   type_name: bind_transceiver
> 2020-11-30 02:53:26 [19202] [2] DEBUG:   command_id: 9 = 0x0009
> 2020-11-30 02:53:26 [19202] [2] DEBUG:   command_status: 0 = 0x
> 2020-11-30 02:53:26 [19202] [2] DEBUG:   sequence_number: 1 = 0x0001
> 2020-11-30 02:53:26 [19202] [2] DEBUG:   system_id: "mike"
> 2020-11-30 02:53:26 [19202] [2] DEBUG:   password: "mike"
> 2020-11-30 02:53:26 [19202] [2] DEBUG:   system_type: "orange"
> 2020-11-30 02:53:26 [19202] [2] DEBUG:   interface_version: 52 = 0x0034
> 2020-11-30 02:53:26 [19202] [2] DEBU

RE: OPENSMPPBOX code 0x0000000d (Bind Failed) help

[Rene Kluwen]

You could double check your smpplogins.txt.

 

== Rene

 

Van: users  Namens Michael Osakede
Verzonden: maandag 30 november 2020 03:06
Aan: users@kannel.org
Onderwerp: OPENSMPPBOX code 0x000d (Bind Failed) help

 

Hello,

 

I have this setup

 

KANNEL SMSC <==> OPENSMPPBOX Server

below are the opensmppbox and kannel config.

 

OPENSMPPBOX

group = core
dlr-storage = internal

group = opensmppbox
opensmppbox-id = orange
opensmppbox-port = 1991
bearerbox-host = localhost
bearerbox-port = 13001
our-system-id = orange_vezeti
smpp-logins = "/etc/kannel/box/smpplogins.txt"
route-to-smsc = MEDIATEL
log-level = 0
log-file = /tmp/smppbox.log

OPENSMPP Users

mike mike orange 78.208.228.38

 

CONNECTING Kannel SMSC

# SMSC SMPP
group = smsc
smsc-id = orange
smsc = smpp
host = 156.0.249.122
port = 1991
#receive-port = 2346
smsc-username = mike
smsc-password = mike
system-type = orange
#interface-version = 52
keepalive = 50
allowed-smsc-id = orange
transceiver-mode = true
msg-id-type =  0x00
throughput = 10
max-pending-submits = 10
wait-ack = 600

 

Kannel Log

] DEBUG: Connecting to <156.0.249.122>
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP[orange]: Sending PDU:
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU 0x7f1154000a10 dump:
2020-11-30 00:51:50 [18114] [6] DEBUG:   type_name: bind_transceiver
2020-11-30 00:51:50 [18114] [6] DEBUG:   command_id: 9 = 0x0009
2020-11-30 00:51:50 [18114] [6] DEBUG:   command_status: 0 = 0x
2020-11-30 00:51:50 [18114] [6] DEBUG:   sequence_number: 91 = 0x005b
2020-11-30 00:51:50 [18114] [6] DEBUG:   system_id: "mike"
2020-11-30 00:51:50 [18114] [6] DEBUG:   password: "mike"
2020-11-30 00:51:50 [18114] [6] DEBUG:   system_type: "orange"
2020-11-30 00:51:50 [18114] [6] DEBUG:   interface_version: 52 = 0x0034
2020-11-30 00:51:50 [18114] [6] DEBUG:   addr_ton: 0 = 0x
2020-11-30 00:51:50 [18114] [6] DEBUG:   addr_npi: 0 = 0x
2020-11-30 00:51:50 [18114] [6] DEBUG:   address_range: NULL
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU dump ends.
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP[orange]: Got PDU:
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU 0x7f1154000a10 dump:
2020-11-30 00:51:50 [18114] [6] DEBUG:   type_name: bind_transceiver_resp
2020-11-30 00:51:50 [18114] [6] DEBUG:   command_id: 2147483657 = 0x8009
2020-11-30 00:51:50 [18114] [6] DEBUG:   command_status: 13 = 0x000d
2020-11-30 00:51:50 [18114] [6] DEBUG:   sequence_number: 91 = 0x005b
2020-11-30 00:51:50 [18114] [6] DEBUG:   system_id: NULL
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU dump ends.
2020-11-30 00:51:50 [18114] [6] ERROR: SMPP[orange]: SMSC rejected login to 
transmit, code 0x000d (Bind Failed).
2020-11-30 00:51:50 [18114] [6] ERROR: SMPP[orange]: Couldn't connect to SMS 
center (retrying in 10 seconds).

 

OPENSMPP Log

2020-11-30 02:53:26 [19202] [0] DEBUG: Started thread 1 (opensmppbox.c:function)
2020-11-30 02:53:26 [19202] [1] DEBUG: Thread 1 (opensmppbox.c:function) maps 
to pid 19202.
2020-11-30 02:53:26 [19202] [1] INFO: Client connected from <74.208.228.38>
2020-11-30 02:53:26 [19202] [1] DEBUG: Connecting to <127.0.0.1>
2020-11-30 02:53:26 [19202] [1] INFO: Connected to bearerbox at localhost port 
13001.
2020-11-30 02:53:26 [19202] [1] DEBUG: Started thread 2 
(opensmppbox.c:smpp_to_bearerbox)
2020-11-30 02:53:26 [19202] [2] DEBUG: Thread 2 
(opensmppbox.c:smpp_to_bearerbox) maps to pid 19202.
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP[orange]: Got PDU:
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU 0x7fa51c000d50 dump:
2020-11-30 02:53:26 [19202] [2] DEBUG:   type_name: bind_transceiver
2020-11-30 02:53:26 [19202] [2] DEBUG:   command_id: 9 = 0x0009
2020-11-30 02:53:26 [19202] [2] DEBUG:   command_status: 0 = 0x
2020-11-30 02:53:26 [19202] [2] DEBUG:   sequence_number: 1 = 0x0001
2020-11-30 02:53:26 [19202] [2] DEBUG:   system_id: "mike"
2020-11-30 02:53:26 [19202] [2] DEBUG:   password: "mike"
2020-11-30 02:53:26 [19202] [2] DEBUG:   system_type: "orange"
2020-11-30 02:53:26 [19202] [2] DEBUG:   interface_version: 52 = 0x0034
2020-11-30 02:53:26 [19202] [2] DEBUG:   addr_ton: 0 = 0x
2020-11-30 02:53:26 [19202] [2] DEBUG:   addr_npi: 0 = 0x
2020-11-30 02:53:26 [19202] [2] DEBUG:   address_range: NULL
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU dump ends.
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP[orange]: Sending PDU:
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU 0x7fa51c001050 dump:
2020-11-30 02:53:26 [19202] [2] DEBUG:   type_name: bind_transceiver_resp
2020-11-30 02:53:26 [19202] [2] DEBUG:   command_id: 2147483657 = 0x8009
2020-11-30 02:53:26 [19202] [2] DEBUG:   command_status: 13 = 0x000d
2020-11-30 02:53:26 [19202] [2] DEBUG:   sequence_number: 1 = 0x0001
2020-11-30 02:53:26 [19202] [2] DEBUG:   system_id: NULL
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU dump ends.
20

OPENSMPPBOX code 0x0000000d (Bind Failed) help

[Michael Osakede]

Hello,

I have this setup

KANNEL SMSC <==> OPENSMPPBOX Server
below are the opensmppbox and kannel config.

OPENSMPPBOX
group = core
dlr-storage = internal

group = opensmppbox
opensmppbox-id = orange
opensmppbox-port = 1991
bearerbox-host = localhost
bearerbox-port = 13001
our-system-id = orange_vezeti
smpp-logins = "/etc/kannel/box/smpplogins.txt"
route-to-smsc = MEDIATEL
log-level = 0
log-file = /tmp/smppbox.log

OPENSMPP Users
mike mike orange 78.208.228.38

CONNECTING Kannel SMSC
# SMSC SMPP
group = smsc
smsc-id = orange
smsc = smpp
host = 156.0.249.122
port = 1991
#receive-port = 2346
smsc-username = mike
smsc-password = mike
system-type = orange
#interface-version = 52
keepalive = 50
allowed-smsc-id = orange
transceiver-mode = true
msg-id-type =  0x00
throughput = 10
max-pending-submits = 10
wait-ack = 600

Kannel Log
] DEBUG: Connecting to <156.0.249.122>
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP[orange]: Sending PDU:
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU 0x7f1154000a10 dump:
2020-11-30 00:51:50 [18114] [6] DEBUG:   type_name: bind_transceiver
2020-11-30 00:51:50 [18114] [6] DEBUG:   command_id: 9 = 0x0009
2020-11-30 00:51:50 [18114] [6] DEBUG:   command_status: 0 = 0x
2020-11-30 00:51:50 [18114] [6] DEBUG:   sequence_number: 91 = 0x005b
2020-11-30 00:51:50 [18114] [6] DEBUG:   system_id: "mike"
2020-11-30 00:51:50 [18114] [6] DEBUG:   password: "mike"
2020-11-30 00:51:50 [18114] [6] DEBUG:   system_type: "orange"
2020-11-30 00:51:50 [18114] [6] DEBUG:   interface_version: 52 = 0x0034
2020-11-30 00:51:50 [18114] [6] DEBUG:   addr_ton: 0 = 0x
2020-11-30 00:51:50 [18114] [6] DEBUG:   addr_npi: 0 = 0x
2020-11-30 00:51:50 [18114] [6] DEBUG:   address_range: NULL
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU dump ends.
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP[orange]: Got PDU:
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU 0x7f1154000a10 dump:
2020-11-30 00:51:50 [18114] [6] DEBUG:   type_name: bind_transceiver_resp
2020-11-30 00:51:50 [18114] [6] DEBUG:   command_id: 2147483657 = 0x8009
2020-11-30 00:51:50 [18114] [6] DEBUG:   command_status: 13 = 0x000d
2020-11-30 00:51:50 [18114] [6] DEBUG:   sequence_number: 91 = 0x005b
2020-11-30 00:51:50 [18114] [6] DEBUG:   system_id: NULL
2020-11-30 00:51:50 [18114] [6] DEBUG: SMPP PDU dump ends.
2020-11-30 00:51:50 [18114] [6] ERROR: SMPP[orange]: SMSC rejected login to
transmit, code 0x000d (Bind Failed).
2020-11-30 00:51:50 [18114] [6] ERROR: SMPP[orange]: Couldn't connect to
SMS center (retrying in 10 seconds).

OPENSMPP Log
2020-11-30 02:53:26 [19202] [0] DEBUG: Started thread 1
(opensmppbox.c:function)
2020-11-30 02:53:26 [19202] [1] DEBUG: Thread 1 (opensmppbox.c:function)
maps to pid 19202.
2020-11-30 02:53:26 [19202] [1] INFO: Client connected from <74.208.228.38>
2020-11-30 02:53:26 [19202] [1] DEBUG: Connecting to <127.0.0.1>
2020-11-30 02:53:26 [19202] [1] INFO: Connected to bearerbox at localhost
port 13001.
2020-11-30 02:53:26 [19202] [1] DEBUG: Started thread 2
(opensmppbox.c:smpp_to_bearerbox)
2020-11-30 02:53:26 [19202] [2] DEBUG: Thread 2
(opensmppbox.c:smpp_to_bearerbox) maps to pid 19202.
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP[orange]: Got PDU:
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU 0x7fa51c000d50 dump:
2020-11-30 02:53:26 [19202] [2] DEBUG:   type_name: bind_transceiver
2020-11-30 02:53:26 [19202] [2] DEBUG:   command_id: 9 = 0x0009
2020-11-30 02:53:26 [19202] [2] DEBUG:   command_status: 0 = 0x
2020-11-30 02:53:26 [19202] [2] DEBUG:   sequence_number: 1 = 0x0001
2020-11-30 02:53:26 [19202] [2] DEBUG:   system_id: "mike"
2020-11-30 02:53:26 [19202] [2] DEBUG:   password: "mike"
2020-11-30 02:53:26 [19202] [2] DEBUG:   system_type: "orange"
2020-11-30 02:53:26 [19202] [2] DEBUG:   interface_version: 52 = 0x0034
2020-11-30 02:53:26 [19202] [2] DEBUG:   addr_ton: 0 = 0x
2020-11-30 02:53:26 [19202] [2] DEBUG:   addr_npi: 0 = 0x
2020-11-30 02:53:26 [19202] [2] DEBUG:   address_range: NULL
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU dump ends.
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP[orange]: Sending PDU:
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU 0x7fa51c001050 dump:
2020-11-30 02:53:26 [19202] [2] DEBUG:   type_name: bind_transceiver_resp
2020-11-30 02:53:26 [19202] [2] DEBUG:   command_id: 2147483657 = 0x8009
2020-11-30 02:53:26 [19202] [2] DEBUG:   command_status: 13 = 0x000d
2020-11-30 02:53:26 [19202] [2] DEBUG:   sequence_number: 1 = 0x0001
2020-11-30 02:53:26 [19202] [2] DEBUG:   system_id: NULL
2020-11-30 02:53:26 [19202] [2] DEBUG: SMPP PDU dump ends.
2020-11-30 02:53:27 [19202] [2] ERROR: Invalid SMPP PDU received.
2020-11-30 02:53:27 [19202] [2] DEBUG: Thread 2
(opensmppbox.c:smpp_to_bearerbox) terminates.
2020-11-30 02:53:28 [19202] [1] DEBUG: Thread 1 (opensmppbox.c:function)
terminates.

any help is welcome, what am I getting wrong?

Michael

help with handling incoming sms via opensmppbox to sqlbox

[Muteesa Fred]

Hello Users, I have installed kannelOpensmpp à sqlbox -> smscI want to receive an sms via the opensmppbox and route it via smsc using sql box. Please advise on the best way to achieve this. I have installed kannel, sqlbox, opensmppbox successfully.  Regards,Fred Muteesa Sent from Mail for Windows 10 

Re: opensmppbox smsc-route

[Techinnovation]

Thank you !
It works for me.

BR,
Aleksandr

Monday, March 30, 2020, 11:22:33 AM, you wrote:


You need a separate opensmppbox.conf for each instance.
Then start opensmppbox three times, each with it’s own config file.
 
Van: Techinnovation  
Verzonden: maandag 30 maart 2020 11:00
Aan: Rene Kluwen 
CC: users@kannel.org
Onderwerp: Re: opensmppbox smsc-route
 
Hello,

Could you please support with configurations where three separate opensmppbox 
instances ?
It will be help with example.

Thank you !


BR,
Alekxandr 

Tuesday, January 28, 2020, 10:38:52 AM, you wrote:

Hello Rene,

Could you please share example of configurations with three separate 
opensmppbox instances ?

BR,
Aleksandr

Monday, January 27, 2020, 2:17:44 PM, you wrote:

Inside of opensmppbox there is no esme-routing.
Apart from that, Kannel itself only has prefix-routing that you could use.
 
A work-around for that will be firing three separate opensmppbox instances, 
each with a different config and port.
That way you could set the route-to-smsc for the esme to the desired smsc.
 
== Rene
 
Van: users  Namens Techinnovation
Verzonden: maandag 27 januari 2020 13:09
Aan: users@kannel.org
Onderwerp: opensmppbox smsc-route
 
Hello,

I have installed kannel with opensmmbox, all work fine.

I have connected 3 different ESME customers on opensmppbox, 
and I need for each ESME have additional sms routing to separate SMSC on kannel 
server. 

With this configuration all sms from all ESME (customer1,customer2, customer3) 
route to smsc1.
But I need to have route like

from customer1 to smsc1
from customer2 to smsc2
from customer3 to smsc3

Please help.

===
smpplogins.txt
customer1 password1 localbox *.*.*.*
customer2 password2 localbox *.*.*.* 
customer3 password3 localbox *.*.*.* 

opensmmpbox.conf
# sample opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = mycompany
opensmppbox-port = 2799
bearerbox-host = localhost
bearerbox-port = 13005
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = mycompany
route-to-smsc = smsc1
smpp-logins = "/etc/kannel/smpplogins.txt"
use-systemid-as-smsboxid = true

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = localhost
username = kannel 
password = kannelpass
database = kannel

group = dlr-db
id = dlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc 


BR,
Alekxandr 






-- 
Best regards,
 Techinnovationmailto:techinnovat...@inbox.lv





-- 
Best regards,
 Techinnovationmailto:techinnovat...@inbox.lv




-- 
Best regards,
 Techinnovationmailto:techinnovat...@inbox.lv

RE: opensmppbox smsc-route

[Rene Kluwen]

You need a separate opensmppbox.conf for each instance.

Then start opensmppbox three times, each with it's own config file.

 

Van: Techinnovation  
Verzonden: maandag 30 maart 2020 11:00
Aan: Rene Kluwen 
CC: users@kannel.org
Onderwerp: Re: opensmppbox smsc-route

 

Hello,

Could you please support with configurations where three separate
opensmppbox instances ?
It will be help with example.

Thank you !


BR,
Alekxandr 

Tuesday, January 28, 2020, 10:38:52 AM, you wrote:


Hello Rene,

Could you please share example of configurations with three separate
opensmppbox instances ?

BR,
Aleksandr

Monday, January 27, 2020, 2:17:44 PM, you wrote:


Inside of opensmppbox there is no esme-routing.
Apart from that, Kannel itself only has prefix-routing that you could use.
 
A work-around for that will be firing three separate opensmppbox instances,
each with a different config and port.
That way you could set the route-to-smsc for the esme to the desired smsc.
 
== Rene
 
Van: users mailto:users-boun...@kannel.org> >
Namens Techinnovation
Verzonden: maandag 27 januari 2020 13:09
Aan: users@kannel.org <mailto:users@kannel.org> 
Onderwerp: opensmppbox smsc-route
 
Hello,

I have installed kannel with opensmmbox, all work fine.

I have connected 3 different ESME customers on opensmppbox, 
and I need for each ESME have additional sms routing to separate SMSC on
kannel server. 

With this configuration all sms from all ESME (customer1,customer2,
customer3) route to smsc1.
But I need to have route like

from customer1 to smsc1
from customer2 to smsc2
from customer3 to smsc3

Please help.

===
smpplogins.txt
customer1 password1 localbox *.*.*.*
customer2 password2 localbox *.*.*.* 
customer3 password3 localbox *.*.*.* 

opensmmpbox.conf
# sample opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = mycompany
opensmppbox-port = 2799
bearerbox-host = localhost
bearerbox-port = 13005
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = mycompany
route-to-smsc = smsc1
smpp-logins = "/etc/kannel/smpplogins.txt"
use-systemid-as-smsboxid = true

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = localhost
username = kannel 
password = kannelpass
database = kannel

group = dlr-db
id = dlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc 


BR,
Alekxandr 






-- 
Best regards,
 Techinnovation <mailto:techinnovat...@inbox.lv>
mailto:techinnovat...@inbox.lv





-- 
Best regards,
 Techinnovation <mailto:techinnovat...@inbox.lv>
mailto:techinnovat...@inbox.lv

Re: opensmppbox smsc-route

[Techinnovation]

Hello,

Could you please support with configurations where three separate opensmppbox 
instances ?
It will be help with example.

Thank you !


BR,
Alekxandr 

Tuesday, January 28, 2020, 10:38:52 AM, you wrote:


Hello Rene,

Could you please share example of configurations with three separate 
opensmppbox instances ?

BR,
Aleksandr

Monday, January 27, 2020, 2:17:44 PM, you wrote:


Inside of opensmppbox there is no esme-routing.
Apart from that, Kannel itself only has prefix-routing that you could use.
 
A work-around for that will be firing three separate opensmppbox instances, 
each with a different config and port.
That way you could set the route-to-smsc for the esme to the desired smsc.
 
== Rene
 
Van: users  Namens Techinnovation
Verzonden: maandag 27 januari 2020 13:09
Aan: users@kannel.org
Onderwerp: opensmppbox smsc-route
 
Hello,

I have installed kannel with opensmmbox, all work fine.

I have connected 3 different ESME customers on opensmppbox, 
and I need for each ESME have additional sms routing to separate SMSC on kannel 
server. 

With this configuration all sms from all ESME (customer1,customer2, customer3) 
route to smsc1.
But I need to have route like

from customer1 to smsc1
from customer2 to smsc2
from customer3 to smsc3

Please help.

===
smpplogins.txt
customer1 password1 localbox *.*.*.*
customer2 password2 localbox *.*.*.* 
customer3 password3 localbox *.*.*.* 

opensmmpbox.conf
# sample opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = mycompany
opensmppbox-port = 2799
bearerbox-host = localhost
bearerbox-port = 13005
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = mycompany
route-to-smsc = smsc1
smpp-logins = "/etc/kannel/smpplogins.txt"
use-systemid-as-smsboxid = true

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = localhost
username = kannel 
password = kannelpass
database = kannel

group = dlr-db
id = dlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc 


BR,
Alekxandr 





-- 
Best regards,
 Techinnovationmailto:techinnovat...@inbox.lv




-- 
Best regards,
 Techinnovationmailto:techinnovat...@inbox.lv

opensmppbox wrong delivery report

[Techinnovation]

Hello,

I found that opensmppbox sent wrong delivery report to ESME: "DELIVRD err:27" 
instead  "EXPIRED err:27"

SMS flow :   ESME(esme-1) -> OPENSMPPBOX -> KANNEL -> SMSC(smsc-1)

Can you please assist me.

From SMSC(smsc-1) kannel received correct status EXPIRED err:27

2020-02-18 14:36:46 [471] [8] DEBUG: SMPP[smsc-1]: Got PDU:
2020-02-18 14:36:46 [471] [8] DEBUG: SMPP PDU 0x7f61b00010b0 dump:
2020-02-18 14:36:46 [471] [8] DEBUG:   type_name: deliver_sm
2020-02-18 14:36:46 [471] [8] DEBUG:   command_id: 5 = 0x0005
2020-02-18 14:36:46 [471] [8] DEBUG:   command_status: 0 = 0x
2020-02-18 14:36:46 [471] [8] DEBUG:   sequence_number:  = 0x0d05
2020-02-18 14:36:46 [471] [8] DEBUG:   service_type: NULL
2020-02-18 14:36:46 [471] [8] DEBUG:   source_addr_ton: 1 = 0x0001
2020-02-18 14:36:46 [471] [8] DEBUG:   source_addr_npi: 1 = 0x0001
2020-02-18 14:36:46 [471] [8] DEBUG:   source_addr: "89542121253"
2020-02-18 14:36:46 [471] [8] DEBUG:   dest_addr_ton: 1 = 0x0001
2020-02-18 14:36:46 [471] [8] DEBUG:   dest_addr_npi: 1 = 0x0001
2020-02-18 14:36:46 [471] [8] DEBUG:   destination_addr: "3809415487"
2020-02-18 14:36:46 [471] [8] DEBUG:   esm_class: 4 = 0x0004
2020-02-18 14:36:46 [471] [8] DEBUG:   protocol_id: 0 = 0x
2020-02-18 14:36:46 [471] [8] DEBUG:   priority_flag: 0 = 0x
2020-02-18 14:36:46 [471] [8] DEBUG:   schedule_delivery_time: NULL
2020-02-18 14:36:46 [471] [8] DEBUG:   validity_period: NULL
2020-02-18 14:36:46 [471] [8] DEBUG:   registered_delivery: 0 = 0x
2020-02-18 14:36:46 [471] [8] DEBUG:   replace_if_present_flag: 0 = 0x
2020-02-18 14:36:46 [471] [8] DEBUG:   data_coding: 0 = 0x
2020-02-18 14:36:46 [471] [8] DEBUG:   sm_default_msg_id: 0 = 0x
2020-02-18 14:36:46 [471] [8] DEBUG:   sm_length: 109 = 0x006d
2020-02-18 14:36:46 [471] [8] DEBUG:   short_message:
2020-02-18 14:36:46 [471] [8] DEBUG:Octet string at 0x7f61b00053b0:
2020-02-18 14:36:46 [471] [8] DEBUG:  len:  109
2020-02-18 14:36:46 [471] [8] DEBUG:  size: 110
2020-02-18 14:36:46 [471] [8] DEBUG:  immutable: 0
2020-02-18 14:36:46 [471] [8] DEBUG:  data: 69 64 3a 30 31 43 41 36 30 42 
36 20 73 75 62 3a   id:01CA60B6 sub:
2020-02-18 14:36:46 [471] [8] DEBUG:  data: 30 30 31 20 64 6c 76 72 64 3a 
30 30 30 20 73 75   001 dlvrd:000 su
2020-02-18 14:36:46 [471] [8] DEBUG:  data: 62 6d 69 74 20 64 61 74 65 3a 
32 30 30 32 31 38   bmit date:200218
2020-02-18 14:36:46 [471] [8] DEBUG:  data: 31 34 33 36 34 36 20 64 6f 6e 
65 20 64 61 74 65   143646 done date
2020-02-18 14:36:46 [471] [8] DEBUG:  data: 3a 32 30 30 32 31 38 31 35 33 
36 34 36 20 73 74   :200218153646 st
2020-02-18 14:36:46 [471] [8] DEBUG:  data: 61 74 3a 45 58 50 49 52 45 44 
20 65 72 72 3a 32   at:EXPIRED err:2
2020-02-18 14:36:46 [471] [8] DEBUG:  data: 37 20 54 65 78 74 3a 72 65 70 
6f 72 747 Text:report
2020-02-18 14:36:46 [471] [8] DEBUG:Octet string dump ends.
2020-02-18 14:36:46 [471] [8] DEBUG:   message_state: 3 = 0x0003
2020-02-18 14:36:46 [471] [8] DEBUG:   receipted_message_id: "01CA60B6"
2020-02-18 14:36:46 [471] [8] DEBUG: SMPP PDU dump ends.
2020-02-18 14:36:46 [471] [8] DEBUG: SMPP[smsc-1] handle_pdu, got DLR
2020-02-18 14:36:46 [471] [8] DEBUG: DLR[mysql]: Looking for DLR smsc=smsc-1, 
ts=01CA60B6, dst=89542121253, type=34
2020-02-18 14:36:46 [471] [8] DEBUG: sql: SELECT `mask`, `service`, `url`, 
`source`, `destination`, `boxc` FROM `dlr` WHERE `smsc`=? AND `ts`=?  LIMIT 1
2020-02-18 14:36:46 [471] [8] DEBUG: column=mask buffer_type=3 max_length=0 
length=10
2020-02-18 14:36:46 [471] [8] DEBUG: column=service buffer_type=253 
max_length=0 length=40
2020-02-18 14:36:46 [471] [8] DEBUG: column=url buffer_type=253 max_length=0 
length=255
2020-02-18 14:36:46 [471] [8] DEBUG: column=source buffer_type=253 max_length=0 
length=40
2020-02-18 14:36:46 [471] [8] DEBUG: column=destination buffer_type=253 
max_length=0 length=40
2020-02-18 14:36:46 [471] [8] DEBUG: column=boxc buffer_type=253 max_length=0 
length=40
2020-02-18 14:36:46 [471] [8] DEBUG: DLR[mysql]: created DLR message for URL 

2020-02-18 14:36:46 [471] [8] DEBUG: removing DLR from database
2020-02-18 14:36:46 [471] [8] DEBUG: sql: DELETE FROM `dlr` WHERE `smsc`=? AND 
`ts`=?  LIMIT 1
2020-02-18 14:36:46 [471] [8] DEBUG: new group created `orig_msg'
2020-02-18 14:36:46 [471] [8] DEBUG: group=`orig_msg' key=`dlr_mask' value=`19'
2020-02-18 14:36:46 [471] [8] DEBUG: new group created `orig_msg'
2020-02-18 14:36:46 [471] [8] DEBUG: group=`orig_msg' key=`dlr_mask' value=`19'
2020-02-18 14:36:46 [471] [8] DEBUG: new group created `smpp'
2020-02-18 14:36:46 [471] [8] DEBUG: group=`smpp' key=`dlr_err' value=`'
2020-02-18 14:36:46 [471] [8] DEBUG: SMPP[smsc-1]: Sending PDU:

But to ESME opensmppbox sent incorrect DELIVRD err:27

2020-02-18 14:36:46 [4691] [3] INFO: We received an SMS message.
2020-0

Re: Issue of DLR - URL with opensmppbox kannel

[Web Min]

Provide your sqlbox.conf please

On Thu, Feb 13, 2020, 4:32 PM Umair Baig  wrote:

> Hello All,
>
> I have configured opensmppbox and I am trying to submit sms using mysql as
> dlr storage.
> When I receive sms it gets delivered but dlr does not get inserted into
> dlr table instead I get an error message in opensmppbox logs saying the
> below.
>
> 2020-02-13 19:21:14 [15724] [2] ERROR: MYSQL: mysql_stmt_execute() failed:
> `Data truncated for column 'url' at row 1'
> 2020-02-13 19:21:14 [15724] [2] ERROR: DLR: MYSQL: Error while adding dlr
> entry for DST<+9177XX>
>
> I am not sure why url data is not coming when sms is being received and
> field dlr-url in the log file is always empty.
>
> my opensmppbox conf
>
> #configuration
> group = core
> dlr-storage = mysql
>
> ###
> group = mysql-connection
> id = dlr-db
> host = 127.0.0.1
> port = 3303
> username = opensmppbox
> password = "X"
> database = new_sms
> max-connections = 20
>
> ###
> group = dlr-db
> id = dlr-db
> table = dlr
> field-smsc = smsc
> field-timestamp = ts
> field-destination = destination
> field-source = source
> field-service = service
> field-url = url
> field-mask = mask
> field-status = status
> field-boxc-id = boxc
> ###
>
> group = opensmppbox
> bearerbox-host = 127.0.0.1
> bearerbox-port = 13001
> opensmppbox-id = smppbox1
> opensmppbox-port = 2775
> log-file = /usr/opensmppbox.log
> log-level = 0
> our-system-id =smpp
> use-systemid-as-smsboxid = true
> route-to-smsc = Test001
> # New accounts
> smpp-logins = /usr/smpplogin.txt
>
> *Thanks & Regards,*
>
>
> *UMAIR BAIG*
> *Sr.Manager*
> *Buzz: +91- 7738857063*
> *On Desk: 022-22007840*
> *SKYPE-ID -umair.baig2893*
>
>   <http://mobilogi.com/>
>
>

Re: Issue of DLR - URL with opensmppbox kannel

[Umair Baig]

Thanks it worked.

*Thanks & Regards,*


*UMAIR BAIG*
*Sr.Manager*
*Buzz: +91- 7738857063*
*On Desk: 022-22007840*
*SKYPE-ID -umair.baig2893*

  



On Thu, Feb 13, 2020 at 8:28 PM Antony Stone <
antony.st...@kannel.open.source.it> wrote:

> On Thursday 13 February 2020 at 15:47:47, Umair Baig wrote:
>
> > Hello Rene,
> >
> > Firstly thanks for your response.
> >
> >  The length of my url field in dlr table is  bigint(20)  so I think this
> is
> > enough.
>
> You can't put a URL into an integer field :)
>
> Try changing it to a varchar, and in my opinion 20 characters if way too
> small
> - the entries in my sms_dlr table are 153 characters long, for example.
>
>
> Antony.
>
> --
> When you find yourself arguing with an idiot,
> you should first of all make sure
> that the other person isn't doing the same thing.
>
>Please reply to the
> list;
>  please *don't* CC
> me.
>
>

Issue of DLR - URL with opensmppbox kannel

[Tolga Ulas]

I think url field should be varchar since it will store a urlencoded
string so that smsbox will summon it by populating with its variables.

> Hello Rene, Firstly thanks for your response. The length of my url field in 
> dlr table is bigint(20) so I think this is enough. and the dlr table is empty 
> as it fails to insert message due to the error above I believe. My dlr table 
> structure CREATE TABLE `dlr` ( `id` bigint(20) UNSIGNED NOT NULL, `smsc` 
> varchar(10) NOT NULL, `ts` varchar(40) NOT NULL, `destination` varchar(20) 
> NOT NULL, `source` varchar(20) NOT NULL, `service` varchar(20) NOT NULL, 
> `url` bigint(20) NOT NULL, `mask` int(11) NOT NULL, `status` int(11) NOT 
> NULL, `boxc` varchar(20) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Re: Issue of DLR - URL with opensmppbox kannel

[Antony Stone]

On Thursday 13 February 2020 at 15:47:47, Umair Baig wrote:

> Hello Rene,
> 
> Firstly thanks for your response.
> 
>  The length of my url field in dlr table is  bigint(20)  so I think this is
> enough.

You can't put a URL into an integer field :)

Try changing it to a varchar, and in my opinion 20 characters if way too small 
- the entries in my sms_dlr table are 153 characters long, for example.


Antony.

-- 
When you find yourself arguing with an idiot,
you should first of all make sure
that the other person isn't doing the same thing.

   Please reply to the list;
 please *don't* CC me.

Re: Issue of DLR - URL with opensmppbox kannel

[Umair Baig]

Hello Rene,

Firstly thanks for your response.

 The length of my url field in dlr table is  bigint(20)  so I think this is
enough.
and the dlr table is empty as it fails to insert message due to the error
above I believe.

My dlr table structure

CREATE TABLE `dlr` (
  `id` bigint(20) UNSIGNED NOT NULL,
  `smsc` varchar(10) NOT NULL,
  `ts` varchar(40) NOT NULL,
  `destination` varchar(20) NOT NULL,
  `source` varchar(20) NOT NULL,
  `service` varchar(20) NOT NULL,
  `url` bigint(20) NOT NULL,
  `mask` int(11) NOT NULL,
  `status` int(11) NOT NULL,
  `boxc` varchar(20) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

*Thanks & Regards,*


*UMAIR BAIG*
*Sr.Manager*
*Buzz: +91- 7738857063*
*On Desk: 022-22007840*
*SKYPE-ID -umair.baig2893*

  <http://mobilogi.com/>



On Thu, Feb 13, 2020 at 8:07 PM Rene Kluwen  wrote:

> What’s the output of show create table dlr in your new_sms database?
>
> What I guess here is that the url column is just too short.
>
>
>
> == Rene
>
>
>
> *Van:* users  *Namens *Umair Baig
> *Verzonden:* donderdag 13 februari 2020 15:31
> *Aan:* users@kannel.org
> *Onderwerp:* Issue of DLR - URL with opensmppbox kannel
>
>
>
> Hello All,
>
>
>
> I have configured opensmppbox and I am trying to submit sms using mysql as
> dlr storage.
>
> When I receive sms it gets delivered but dlr does not get inserted into
> dlr table instead I get an error message in opensmppbox logs saying the
> below.
>
>
>
> 2020-02-13 19:21:14 [15724] [2] ERROR: MYSQL: mysql_stmt_execute() failed:
> `Data truncated for column 'url' at row 1'
> 2020-02-13 19:21:14 [15724] [2] ERROR: DLR: MYSQL: Error while adding dlr
> entry for DST<+9177XX>
>
>
>
> I am not sure why url data is not coming when sms is being received and
> field dlr-url in the log file is always empty.
>
>
>
> my opensmppbox conf
>
>
>
> #configuration
> group = core
> dlr-storage = mysql
>
> ###
> group = mysql-connection
> id = dlr-db
> host = 127.0.0.1
> port = 3303
> username = opensmppbox
> password = "X"
> database = new_sms
> max-connections = 20
>
> ###
> group = dlr-db
> id = dlr-db
> table = dlr
> field-smsc = smsc
> field-timestamp = ts
> field-destination = destination
> field-source = source
> field-service = service
> field-url = url
> field-mask = mask
> field-status = status
> field-boxc-id = boxc
> ###
>
> group = opensmppbox
> bearerbox-host = 127.0.0.1
> bearerbox-port = 13001
> opensmppbox-id = smppbox1
> opensmppbox-port = 2775
> log-file = /usr/opensmppbox.log
> log-level = 0
> our-system-id =smpp
> use-systemid-as-smsboxid = true
> route-to-smsc = Test001
> # New accounts
> smpp-logins = /usr/smpplogin.txt
>
>
>
> *Thanks & Regards,*
>
>
>
> *UMAIR BAIG*
>
> *Sr.Manager*
>
> *Buzz: +91- 7738857063*
>
> *On Desk: 022-22007840*
> *SKYPE-ID -umair.baig2893*
>
>
>
>   <http://mobilogi.com/>
>
>
>

RE: Issue of DLR - URL with opensmppbox kannel

[Rene Kluwen]

What’s the output of show create table dlr in your new_sms database?

What I guess here is that the url column is just too short.

 

== Rene

 

Van: users  Namens Umair Baig
Verzonden: donderdag 13 februari 2020 15:31
Aan: users@kannel.org
Onderwerp: Issue of DLR - URL with opensmppbox kannel

 

Hello All,

 

I have configured opensmppbox and I am trying to submit sms using mysql as dlr 
storage. 

When I receive sms it gets delivered but dlr does not get inserted into dlr 
table instead I get an error message in opensmppbox logs saying the below.

 

2020-02-13 19:21:14 [15724] [2] ERROR: MYSQL: mysql_stmt_execute() failed: 
`Data truncated for column 'url' at row 1'
2020-02-13 19:21:14 [15724] [2] ERROR: DLR: MYSQL: Error while adding dlr entry 
for DST<+9177XX>

 

I am not sure why url data is not coming when sms is being received and field 
dlr-url in the log file is always empty.

 

my opensmppbox conf

 

#configuration
group = core
dlr-storage = mysql

###
group = mysql-connection
id = dlr-db
host = 127.0.0.1
port = 3303
username = opensmppbox
password = "X"
database = new_sms
max-connections = 20

###
group = dlr-db
id = dlr-db
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc
###

group = opensmppbox
bearerbox-host = 127.0.0.1
bearerbox-port = 13001
opensmppbox-id = smppbox1
opensmppbox-port = 2775
log-file = /usr/opensmppbox.log
log-level = 0
our-system-id =smpp
use-systemid-as-smsboxid = true
route-to-smsc = Test001
# New accounts
smpp-logins = /usr/smpplogin.txt

 

Thanks & Regards,

 

UMAIR BAIG

Sr.Manager

Buzz: +91- 7738857063

On Desk: 022-22007840
SKYPE-ID -umair.baig2893

 

  <http://mobilogi.com/> 

 

Issue of DLR - URL with opensmppbox kannel

[Umair Baig]

Hello All,

I have configured opensmppbox and I am trying to submit sms using mysql as
dlr storage.
When I receive sms it gets delivered but dlr does not get inserted into dlr
table instead I get an error message in opensmppbox logs saying the below.

2020-02-13 19:21:14 [15724] [2] ERROR: MYSQL: mysql_stmt_execute() failed:
`Data truncated for column 'url' at row 1'
2020-02-13 19:21:14 [15724] [2] ERROR: DLR: MYSQL: Error while adding dlr
entry for DST<+9177XX>

I am not sure why url data is not coming when sms is being received and
field dlr-url in the log file is always empty.

my opensmppbox conf

#configuration
group = core
dlr-storage = mysql

###
group = mysql-connection
id = dlr-db
host = 127.0.0.1
port = 3303
username = opensmppbox
password = "X"
database = new_sms
max-connections = 20

###
group = dlr-db
id = dlr-db
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc
###

group = opensmppbox
bearerbox-host = 127.0.0.1
bearerbox-port = 13001
opensmppbox-id = smppbox1
opensmppbox-port = 2775
log-file = /usr/opensmppbox.log
log-level = 0
our-system-id =smpp
use-systemid-as-smsboxid = true
route-to-smsc = Test001
# New accounts
smpp-logins = /usr/smpplogin.txt

*Thanks & Regards,*


*UMAIR BAIG*
*Sr.Manager*
*Buzz: +91- 7738857063*
*On Desk: 022-22007840*
*SKYPE-ID -umair.baig2893*

  <http://mobilogi.com/>

Re: opensmppbox smsc-route

[Techinnovation]

Hello Rene,

Could you please share example of configurations with three separate 
opensmppbox instances ?

BR,
Aleksandr

Monday, January 27, 2020, 2:17:44 PM, you wrote:


Inside of opensmppbox there is no esme-routing.
Apart from that, Kannel itself only has prefix-routing that you could use.
 
A work-around for that will be firing three separate opensmppbox instances, 
each with a different config and port.
That way you could set the route-to-smsc for the esme to the desired smsc.
 
== Rene
 
Van: users  Namens Techinnovation
Verzonden: maandag 27 januari 2020 13:09
Aan: users@kannel.org
Onderwerp: opensmppbox smsc-route
 
Hello,

I have installed kannel with opensmmbox, all work fine.

I have connected 3 different ESME customers on opensmppbox, 
and I need for each ESME have additional sms routing to separate SMSC on kannel 
server. 

With this configuration all sms from all ESME (customer1,customer2, customer3) 
route to smsc1.
But I need to have route like

from customer1 to smsc1
from customer2 to smsc2
from customer3 to smsc3

Please help.

===
smpplogins.txt
customer1 password1 localbox *.*.*.*
customer2 password2 localbox *.*.*.* 
customer3 password3 localbox *.*.*.* 

opensmmpbox.conf
# sample opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = mycompany
opensmppbox-port = 2799
bearerbox-host = localhost
bearerbox-port = 13005
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = mycompany
route-to-smsc = smsc1
smpp-logins = "/etc/kannel/smpplogins.txt"
use-systemid-as-smsboxid = true

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = localhost
username = kannel 
password = kannelpass
database = kannel

group = dlr-db
id = dlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc 


BR,
Alekxandr 




-- 
Best regards,
 Techinnovationmailto:techinnovat...@inbox.lv

RE: opensmppbox smsc-route

[Davor Spasoski]

You can do that in bearerbox config in the smsc group.
You should use the allow-smsc-id = customerX whee customerX is the esme 
system-id that is propagated as smsc-id due to the directive that you use in 
opensmppbox: use-systemid-as-smsboxid = true

For the reverse direction you should route all smsc-ids towards your mycompany 
opensmppbox. Opensmppbox will know how to route to the proper esme.

BR,

Davor Spasoski


From: users  On Behalf Of Techinnovation
Sent: Monday, January 27, 2020 1:09 PM
To: users@kannel.org
Subject: opensmppbox smsc-route

Hello,

I have installed kannel with opensmmbox, all work fine.

I have connected 3 different ESME customers on opensmppbox,
and I need for each ESME have additional sms routing to separate SMSC on kannel 
server.

With this configuration all sms from all ESME (customer1,customer2, customer3) 
route to smsc1.
But I need to have route like

from customer1 to smsc1
from customer2 to smsc2
from customer3 to smsc3

Please help.

===
smpplogins.txt
customer1 password1 localbox *.*.*.*
customer2 password2 localbox *.*.*.*
customer3 password3 localbox *.*.*.*

opensmmpbox.conf
# sample opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = mycompany
opensmppbox-port = 2799
bearerbox-host = localhost
bearerbox-port = 13005
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = mycompany
route-to-smsc = smsc1
smpp-logins = "/etc/kannel/smpplogins.txt"
use-systemid-as-smsboxid = true

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = localhost
username = kannel
password = kannelpass
database = kannel

group = dlr-db
id = dlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc


BR,
Alekxandr



Disclaimer: A1 Makedonija 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. A1 Makedonija 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!

: ?1 ?? ? ??
 ??? ?? (??? ?? ? ?) ? ? ?  ??  
? ?? ?? ??. ??? ?? ??? ?? ?? ??? ??? ?? ?  
, ?? ? ?? ?? , ? ??? ?? ?? ? ? 
,  ?? ?? ?? ?? ?? ?? ? ?? ?? ? 
 ?? ?  ??? ? ?? ??  ??. ? 
??? ? ??  ?? ?? ?? ??? ?? ?? ?? ? ?? 
?. ?? ?? ?? ??  ? ?? ??  ?? 
???. ?1 ?? ? ?? ?? ??? ??? ?? ??? ??? 
? ??? ??   ??  ,  ??? 
??  ? ??? ?? ??? ??? ?? ?? ?? ??.
?? ?? ?? ??   ?? ? ??? ?? ? ?! ? ?? 
?!

RE: opensmppbox smsc-route

[Rene Kluwen]

Inside of opensmppbox there is no esme-routing.

Apart from that, Kannel itself only has prefix-routing that you could use.

 

A work-around for that will be firing three separate opensmppbox instances,
each with a different config and port.

That way you could set the route-to-smsc for the esme to the desired smsc.

 

== Rene

 

Van: users  Namens Techinnovation
Verzonden: maandag 27 januari 2020 13:09
Aan: users@kannel.org
Onderwerp: opensmppbox smsc-route

 

Hello,

I have installed kannel with opensmmbox, all work fine.

I have connected 3 different ESME customers on opensmppbox, 
and I need for each ESME have additional sms routing to separate SMSC on
kannel server. 

With this configuration all sms from all ESME (customer1,customer2,
customer3) route to smsc1.
But I need to have route like

from customer1 to smsc1
from customer2 to smsc2
from customer3 to smsc3

Please help.

===
smpplogins.txt
customer1 password1 localbox *.*.*.*
customer2 password2 localbox *.*.*.* 
customer3 password3 localbox *.*.*.* 

opensmmpbox.conf
# sample opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = mycompany
opensmppbox-port = 2799
bearerbox-host = localhost
bearerbox-port = 13005
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = mycompany
route-to-smsc = smsc1
smpp-logins = "/etc/kannel/smpplogins.txt"
use-systemid-as-smsboxid = true

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = localhost
username = kannel 
password = kannelpass
database = kannel

group = dlr-db
id = dlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc 


BR,
Alekxandr 

opensmppbox smsc-route

[Techinnovation]

Hello,

I have installed kannel with opensmmbox, all work fine.

I have connected 3 different ESME customers on opensmppbox, 
and I need for each ESME have additional sms routing to separate SMSC on kannel 
server. 

With this configuration all sms from all ESME (customer1,customer2, customer3) 
route to smsc1.
But I need to have route like

from customer1 to smsc1
from customer2 to smsc2
from customer3 to smsc3

Please help.

===
smpplogins.txt
customer1 password1 localbox *.*.*.*
customer2 password2 localbox *.*.*.* 
customer3 password3 localbox *.*.*.* 

opensmmpbox.conf
# sample opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = mycompany
opensmppbox-port = 2799
bearerbox-host = localhost
bearerbox-port = 13005
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = mycompany
route-to-smsc = smsc1
smpp-logins = "/etc/kannel/smpplogins.txt"
use-systemid-as-smsboxid = true

# the following is just standard dlr configuration

group = mysql-connection
id = dlr
host = localhost
username = kannel 
password = kannelpass
database = kannel

group = dlr-db
id = dlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc 


BR,
Alekxandr 

DLR issue to opensmppbox mclient

[Dev Sharma]

Dear All,

i am facing DLR issue to opensmppbox client.

Opensmppbox --> Http Generic SMSC -- >our internal API

SMs is processed as above but confirmation of SMS submission on smppbox
connectiivty . is not returned to opensmppbox client. so SMS is in pending
state at client end.

however , our internal API is given response OK but this response OK is not
returned to opensmppbox client and aslo not being saved in sqlbox DB , i
need it should be returned to opensmppbox client..
Can you pls help me?

Thanks in advance..

My configuration :

kannel.conf

group = core

admin-port = 13000

smsbox-port = 13001

wapbox-port = 13002

admin-password = adminuser

#status-password = adminpass

#admin-deny-ip = ""

admin-allow-ip =
"127.0.0.1;10.0.0.199;192.168.26.5;192.168.26.10;192.168.26.2"

#box-deny-ip = "*.*.*.*"

box-allow-ip = "127.0.0.1;10.0.0.199;10.0.0.165"

#unified-prefix = "+358,00358,0;+,00"

log-level = 7

log-file = "/var/log/kannel.log"

#log-file = "/tmp/kanneldebug.log"

access-log = "/tmp/access.log"

store-file = "/tmp/kannel.store"

#ssl-server-cert-file = "cert.pem"

#ssl-server-key-file = "key.pem"

#ssl-certkey-file = "mycertandprivkeyfile.pem"

sms-combine-concatenated-mo = true

sms-combine-concatenated-mo-timeout = "1800"

dlr-storage = mysql

wdp-interface-name="*"




group = smsbox-route

smsbox-id = "smppbox1"

smsc-id = "KHItest"


group = smsc

smsc = http

system-type = generic

smsc-id="KHItest"

#host=xx.xx.xx.xx

receive-port=43

port = 13017

send-url =" https://xx.xx.xx.xx/DS/php/msg=%a=%p;

status-success-regex = "OK"

status-permfail-regex = "error"

status-tempfail-regex = "retry later"

reroute-dlr = true

transceiver-mode = true

generic-message-sent = "Message sent with ID: %I"

generic-status-sent = 200

generic-status-error = 404

group = smsbox

bearerbox-host = localhost

sendsms-port = 13013

bearerbox-port=13005

mo-recode=true
http-request-retry = 3

http-queue-delay = 3

reply-emptymessage = ""

--
opensmppbox.conf

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = smppbox1
bearerbox-host = localhost
#admin-port = 13000
#smsbox-port = 13005
opensmppbox-port = 2875
#bearerbox-host = 127.0.0.1
bearerbox-port = 13005
#smsbox-id = dlrbox2
log-level = 0
log-file = /var/log/opensmppbox.log
our-system-id = smppbox1
route-to-smsc = "KHItest"
source-addr-ton=5
source-addr-npi=0
#dlr-mask=31
smpp-logins = "/usr/local/sbin/smpplogins1.txt"
use-systemid-as-smsboxid=true

group = mysql-connection
id = mydlr
host = localhost
username = "root"
password = "abc123"
database = sqlbox
# max count of connections that will be opened for dbpool
# default is 1
max-connections = 10
#port=3306

group = dlr-db
id = mydlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc


-
SQLBOX.conf





group = sqlbox
id = sqlbox-db
smsbox-id = dlrbox2
#global-sender = "My Sender"
bearerbox-host = localhost
bearerbox-port = 13001
smsbox-port = 13005
smsbox-port-ssl = false
sql-log-table = sent_sms
sql-insert-table = send_sms
log-file = "/var/log/kannel/kannel-sqlbox.log"
log-level = 0

group = mysql-connection
id = sqlbox-db
host = localhost
port=3306
username = "root"
password = "abc123"
database = sqlbox







Regards
DS <https://xx.xx.xx.xx/DS/php/msg=%a=%p> 



--
Sent from: http://kannel.6189.n7.nabble.com/Kannel-User-f3.html

Re: opensmppbox: change route for unsuccessful sms

[Rahul Mittal]

Yes please suggest.


On Thu, 6 Jun 2019, 00:54 Rene Kluwen,  wrote:

> It’s open source. So if you want to do a thing like that, I suggest you
> start in the code.
>
> Either in bearerbox itself or use pluginbox.
>
>
>
> == Rene
>
>
>
> *Van:* Rahul Mittal 
> *Verzonden:* woensdag 5 juni 2019 15:37
> *Aan:* Rene Kluwen 
> *CC:* users@kannel.org
> *Onderwerp:* Re: opensmppbox: change route for unsuccessful sms
>
>
>
> How can we add?
>
>
>
> On Wed, 5 Jun 2019, 13:02 Rene Kluwen,  wrote:
>
> There’s no such provision in Kannel nor in smppbox server.
>
>
>
> *Van:* Rahul Mittal 
> *Verzonden:* maandag 3 juni 2019 20:43
> *Aan:* Rene Kluwen 
> *CC:* users@kannel.org
> *Onderwerp:* Re: opensmppbox: change route for unsuccessful sms
>
>
>
> Thanks for replying but I want to handle on smpp server instead of smpp
> client.
>
>
>
> On Mon, 3 Jun 2019, 23:24 Rene Kluwen,  wrote:
>
> You will have to catch the failure report on the esme and resend the
> message.
>
>
>
> == Rene
>
>
>
> *Van:* users  *Namens *Rahul Mittal
> *Verzonden:* maandag 3 juni 2019 18:59
> *Aan:* users@kannel.org
> *Onderwerp:* opensmppbox: change route for unsuccessful sms
>
>
>
> Hi Friends,
>
>
>
> In Opensmppbox, I need to change route if the current route is not able to
> send sms due to any reason. Please suggest, How I can change route for the
> same sms.
>
>
>
> Thanks,
>
> Rahul Mittal
>
>

RE: opensmppbox: change route for unsuccessful sms

[Rene Kluwen]

It’s open source. So if you want to do a thing like that, I suggest you start 
in the code.

Either in bearerbox itself or use pluginbox.

 

== Rene

 

Van: Rahul Mittal  
Verzonden: woensdag 5 juni 2019 15:37
Aan: Rene Kluwen 
CC: users@kannel.org
Onderwerp: Re: opensmppbox: change route for unsuccessful sms

 

How can we add?

 

On Wed, 5 Jun 2019, 13:02 Rene Kluwen, mailto:rene.klu...@chimit.nl> > wrote:

There’s no such provision in Kannel nor in smppbox server.

 

Van: Rahul Mittal mailto:rahulmittal.mc...@gmail.com> > 
Verzonden: maandag 3 juni 2019 20:43
Aan: Rene Kluwen mailto:rene.klu...@chimit.nl> >
CC: users@kannel.org <mailto:users@kannel.org> 
Onderwerp: Re: opensmppbox: change route for unsuccessful sms

 

Thanks for replying but I want to handle on smpp server instead of smpp client.

 

On Mon, 3 Jun 2019, 23:24 Rene Kluwen, mailto:rene.klu...@chimit.nl> > wrote:

You will have to catch the failure report on the esme and resend the message.

 

== Rene

 

Van: users mailto:users-boun...@kannel.org> > Namens 
Rahul Mittal
Verzonden: maandag 3 juni 2019 18:59
Aan: users@kannel.org <mailto:users@kannel.org> 
Onderwerp: opensmppbox: change route for unsuccessful sms

 

Hi Friends,

 

In Opensmppbox, I need to change route if the current route is not able to send 
sms due to any reason. Please suggest, How I can change route for the same sms.

 

Thanks,

Rahul Mittal

Re: opensmppbox: change route for unsuccessful sms

[Rahul Mittal]

How can we add?

On Wed, 5 Jun 2019, 13:02 Rene Kluwen,  wrote:

> There’s no such provision in Kannel nor in smppbox server.
>
>
>
> *Van:* Rahul Mittal 
> *Verzonden:* maandag 3 juni 2019 20:43
> *Aan:* Rene Kluwen 
> *CC:* users@kannel.org
> *Onderwerp:* Re: opensmppbox: change route for unsuccessful sms
>
>
>
> Thanks for replying but I want to handle on smpp server instead of smpp
> client.
>
>
>
> On Mon, 3 Jun 2019, 23:24 Rene Kluwen,  wrote:
>
> You will have to catch the failure report on the esme and resend the
> message.
>
>
>
> == Rene
>
>
>
> *Van:* users  *Namens *Rahul Mittal
> *Verzonden:* maandag 3 juni 2019 18:59
> *Aan:* users@kannel.org
> *Onderwerp:* opensmppbox: change route for unsuccessful sms
>
>
>
> Hi Friends,
>
>
>
> In Opensmppbox, I need to change route if the current route is not able to
> send sms due to any reason. Please suggest, How I can change route for the
> same sms.
>
>
>
> Thanks,
>
> Rahul Mittal
>
>

Re: opensmppbox: change route for unsuccessful sms

[Rahul Mittal]

Thanks for replying but I want to handle on smpp server instead of smpp
client.

On Mon, 3 Jun 2019, 23:24 Rene Kluwen,  wrote:

> You will have to catch the failure report on the esme and resend the
> message.
>
>
>
> == Rene
>
>
>
> *Van:* users  *Namens *Rahul Mittal
> *Verzonden:* maandag 3 juni 2019 18:59
> *Aan:* users@kannel.org
> *Onderwerp:* opensmppbox: change route for unsuccessful sms
>
>
>
> Hi Friends,
>
>
>
> In Opensmppbox, I need to change route if the current route is not able to
> send sms due to any reason. Please suggest, How I can change route for the
> same sms.
>
>
>
> Thanks,
>
> Rahul Mittal
>

RE: opensmppbox: change route for unsuccessful sms

[Rene Kluwen]

You will have to catch the failure report on the esme and resend the message.

 

== Rene

 

Van: users  Namens Rahul Mittal
Verzonden: maandag 3 juni 2019 18:59
Aan: users@kannel.org
Onderwerp: opensmppbox: change route for unsuccessful sms

 

Hi Friends,

 

In Opensmppbox, I need to change route if the current route is not able to send 
sms due to any reason. Please suggest, How I can change route for the same sms.

 

Thanks,

Rahul Mittal

opensmppbox: change route for unsuccessful sms

[Rahul Mittal]

Hi Friends,

In Opensmppbox, I need to change route if the current route is not able to
send sms due to any reason. Please suggest, How I can change route for the
same sms.

Thanks,
Rahul Mittal

Re: UDH Support on OpenSMPPBox

[Vangelis Typaldos]

In my eyes it seems like a 7-byte udh header with 2 byte reference number that 
should be a valid smpp PDU.

Note sure that opensmppbox and kannel in general supports -byte reference 
numbers udh header but are quite valid in the smpp protocol - tipically used 
for high traffic environments to avoid duplicated udh headers in SMSC side.

Kind Regards
Vangelis

Sent from my BlackBerry 10 smartphone.
From: garz m
Sent: Δευτέρα, 25 Μαρτίου 2019 - 03:46
To: Davor Spasoski
Cc: users@kannel.org
Subject: Re: UDH Support on OpenSMPPBox


Hi Davor,

Thanks for the response. No, i'm not. I'm seeing ESME's seeing PDU like i'd 
shared more often now. I think their purpose is to notify via SMPP Apple 
devices.

Regards

On Thu, Mar 21, 2019 at 3:27 PM Davor Spasoski 
mailto:davor.spaso...@onevip.mk>> wrote:
Are you trying to reverse engineer iMessage? I don't think it uses MAP for that 
purpose. iMessage is available only on Wi-Fi/Cellular data, it’s something 
proprietary to Apple and I’d even be surprised if it’s related to RCS. Can you 
shed some light if you know the insights?

Cheers

On Mar 21, 2019, at 2:27 AM, garz m 
mailto:garz...@gmail.com>> wrote:

Dear Users,

Greetings!

Just like to consult if our Opensmppbox service supports Apple type Push 
Notification such as imessage and facetime? I have seen the correct UDH on the 
PDU however I found a - maybe an error that I hope you can help check. I'm 
sharing here the PDU captured:
==
DEBUG: SMPP: Got PDU:
DEBUG: SMPP PDU 0x7f1c10001270 dump:
DEBUG:   type_name: submit_sm
DEBUG:   command_id: 4 = 0x0004
DEBUG:   command_status: 0 = 0x
DEBUG:   sequence_number: 128203 = 0x0001f4cb
DEBUG:   service_type: NULL
DEBUG:   source_addr_ton: 1 = 0x0001
DEBUG:   source_addr_npi: 1 = 0x0001
DEBUG:   source_addr: ""
DEBUG:   dest_addr_ton: 1 = 0x0001
DEBUG:   dest_addr_npi: 1 = 0x0001
DEBUG:   destination_addr: ""
DEBUG:   esm_class: 67 = 0x0043
DEBUG:   protocol_id: 0 = 0x
DEBUG:   priority_flag: 0 = 0x
DEBUG:   schedule_delivery_time: NULL
DEBUG:   validity_period: NULL
DEBUG:   registered_delivery: 1 = 0x0001
DEBUG:   replace_if_present_flag: 0 = 0x
DEBUG:   data_coding: 4 = 0x0004
DEBUG:   sm_default_msg_id: 0 = 0x
DEBUG:   sm_length: 90 = 0x005a
DEBUG:   short_message:
DEBUG:Octet string at 0x7f1c100014d0:
DEBUG:  len:  90
DEBUG:  size: 91
DEBUG:  immutable: 0
DEBUG:  data: 06 05 04 15 79 00 00 42 66 78 20 32 34 20 73 75   y..Bfx 
24 su
DEBUG:  data: 20 61 69 64 6c 75 65 2e 20 3f 20 32 50 76 3d 20aidlue. ? 
2Pv=
DEBUG:  data: 35 39 31 20 33 2d 38 20 39 2b 52 53 72 33 45 52   591 3-8 
9+RSr3ER
DEBUG:  data: 20 38 3b 30 35 20 3d 33 6e 20 45 3d 33 20 34 318;05 =3n 
E=3 41
DEBUG:  data: 30 32 20 37 30 3d 20 31 31 33 73 20 36 42 3b 20   02 70= 113s 
6B;
DEBUG:  data: 47 38 34 3b 20 30 35 43 33 2e G84; 05C3.
DEBUG:Octet string dump ends.
DEBUG: SMPP PDU dump ends.
DEBUG: SMPP: UDH length read as 7
DEBUG: Found unknown IEI 5 with length 4
DEBUG: UDH was present, but no reference to multipart SMSs
DEBUG: Msg object at 0x7f1c10001a90:
DEBUG:  type: sms
DEBUG:  sms.sender:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:len:  13
DEBUG:size: 1024
DEBUG:immutable: 0
DEBUG:data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.receiver:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:len:  13
DEBUG:size: 1024
DEBUG:immutable: 0
DEBUG:data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.udhdata:
DEBUG:  Octet string at 0x7f1c100022e0:
DEBUG:len:  7
DEBUG:size: 8
DEBUG:immutable: 0
DEBUG:data: 06 05 04 15 79 00 00  y..
DEBUG:  Octet string dump ends.
DEBUG:  sms.msgdata:
DEBUG:  Octet string at 0x7f1c100014d0:
DEBUG:len:  83
DEBUG:size: 91
DEBUG:immutable: 0
DEBUG:data: 42 66 78 20 32 34 20 73 75 20 61 69 64 6c 75 65   Bfx 24 su 
aidlue
DEBUG:data: 2e 20 3f 20 32 50 76 3d 20 35 39 31 20 33 2d 38   . ? 2Pv= 591 
3-8
DEBUG:data: 20 39 2b 52 53 72 33 45 52 20 38 3b 30 35 20 3d9+RSr3ER 
8;05 =
DEBUG:data: 33 6e 20 45 3d 33 20 34 31 30 32 20 37 30 3d 20   3n E=3 4102 
70=
DEBUG:data: 31 31 33 73 20 36 42 3b 20 47 38 34 3b 20 30 35   113s 6B; G84; 
05
DEBUG:data: 43 33 2e  C3.
DEBUG:  Octet string dump ends.
DEBUG:  sms.time: 1552605905
DEBUG:  sms.smsc_id:
DEBUG:  sms.smsc_number:
DEBUG:  sms.foreign_id:
DEBUG:  sms.service:
DEBUG:  Octet string at 0x7f1c100022b0:
DEBUG:len:  4
DEBUG:size: 5
DEBUG:immutable: 0
DEBUG:data:
DEBUG:  Octet string dump ends.
DEBUG:  sms.account:
DEBUG:  
sms.id<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsms.id%2F=02%7C01%7C%7C12586c3fd562456b6e5708d6b0c3c43c%7C84df9

Re: UDH Support on OpenSMPPBox

[garz m]

Hi Davor,

Thanks for the response. No, i'm not. I'm seeing ESME's seeing PDU like i'd
shared more often now. I think their purpose is to notify via SMPP Apple
devices.

Regards

On Thu, Mar 21, 2019 at 3:27 PM Davor Spasoski 
wrote:

> Are you trying to reverse engineer iMessage? I don't think it uses MAP for
> that purpose. iMessage is available only on Wi-Fi/Cellular data, it’s
> something proprietary to Apple and I’d even be surprised if it’s related to
> RCS. Can you shed some light if you know the insights?
>
> Cheers
>
> On Mar 21, 2019, at 2:27 AM, garz m  wrote:
>
> Dear Users,
>
> Greetings!
>
> Just like to consult if our Opensmppbox service supports Apple type Push
> Notification such as imessage and facetime? I have seen the correct UDH on
> the PDU however I found a - maybe an error that I hope you can help check.
> I'm sharing here the PDU captured:
> ==
> DEBUG: SMPP: Got PDU:
> DEBUG: SMPP PDU 0x7f1c10001270 dump:
> DEBUG:   type_name: submit_sm
> DEBUG:   command_id: 4 = 0x0004
> DEBUG:   command_status: 0 = 0x
> DEBUG:   sequence_number: 128203 = 0x0001f4cb
> DEBUG:   service_type: NULL
> DEBUG:   source_addr_ton: 1 = 0x0001
> DEBUG:   source_addr_npi: 1 = 0x0001
> DEBUG:   source_addr: ""
> DEBUG:   dest_addr_ton: 1 = 0x0001
> DEBUG:   dest_addr_npi: 1 = 0x0001
> DEBUG:   destination_addr: ""
> DEBUG:   esm_class: 67 = 0x0043
> DEBUG:   protocol_id: 0 = 0x
> DEBUG:   priority_flag: 0 = 0x
> DEBUG:   schedule_delivery_time: NULL
> DEBUG:   validity_period: NULL
> DEBUG:   registered_delivery: 1 = 0x0001
> DEBUG:   replace_if_present_flag: 0 = 0x
> DEBUG:   data_coding: 4 = 0x0004
> DEBUG:   sm_default_msg_id: 0 = 0x
> DEBUG:   sm_length: 90 = 0x005a
> DEBUG:   short_message:
> DEBUG:Octet string at 0x7f1c100014d0:
> DEBUG:  len:  90
> DEBUG:  size: 91
> DEBUG:  immutable: 0
> DEBUG:  data: *06 05 04 15 79 00 00* 42 66 78 20 32 34 20 73 75
> y..Bfx 24 su
> DEBUG:  data: 20 61 69 64 6c 75 65 2e 20 3f 20 32 50 76 3d 20
> aidlue. ? 2Pv=
> DEBUG:  data: 35 39 31 20 33 2d 38 20 39 2b 52 53 72 33 45 52   591
> 3-8 9+RSr3ER
> DEBUG:  data: 20 38 3b 30 35 20 3d 33 6e 20 45 3d 33 20 34 318;05
> =3n E=3 41
> DEBUG:  data: 30 32 20 37 30 3d 20 31 31 33 73 20 36 42 3b 20   02 70=
> 113s 6B;
> DEBUG:  data: 47 38 34 3b 20 30 35 43 33 2e G84;
> 05C3.
> DEBUG:Octet string dump ends.
> DEBUG: SMPP PDU dump ends.
> DEBUG: SMPP: UDH length read as 7
> *DEBUG: Found unknown IEI 5 with length 4*
> DEBUG: UDH was present, but no reference to multipart SMSs
> DEBUG: Msg object at 0x7f1c10001a90:
> DEBUG:  type: sms
> DEBUG:  sms.sender:
> DEBUG:  Octet string at 0x7f1c1000:
> DEBUG:len:  13
> DEBUG:size: 1024
> DEBUG:immutable: 0
> DEBUG:data: 2b +
> DEBUG:  Octet string dump ends.
> DEBUG:  sms.receiver:
> DEBUG:  Octet string at 0x7f1c1000:
> DEBUG:len:  13
> DEBUG:size: 1024
> DEBUG:immutable: 0
> DEBUG:data: 2b +
> DEBUG:  Octet string dump ends.
> DEBUG:  sms.udhdata:
> DEBUG:  Octet string at 0x7f1c100022e0:
> DEBUG:len:  7
> DEBUG:size: 8
> DEBUG:immutable: 0
> DEBUG:data: 06 05 04 15 79 00 00  y..
> DEBUG:  Octet string dump ends.
> DEBUG:  sms.msgdata:
> DEBUG:  Octet string at 0x7f1c100014d0:
> DEBUG:len:  83
> DEBUG:size: 91
> DEBUG:immutable: 0
> DEBUG:data: 42 66 78 20 32 34 20 73 75 20 61 69 64 6c 75 65   Bfx 24
> su aidlue
> DEBUG:data: 2e 20 3f 20 32 50 76 3d 20 35 39 31 20 33 2d 38   . ? 2Pv=
> 591 3-8
> DEBUG:data: 20 39 2b 52 53 72 33 45 52 20 38 3b 30 35 20 3d
> 9+RSr3ER 8;05 =
> DEBUG:data: 33 6e 20 45 3d 33 20 34 31 30 32 20 37 30 3d 20   3n E=3
> 4102 70=
> DEBUG:data: 31 31 33 73 20 36 42 3b 20 47 38 34 3b 20 30 35   113s 6B;
> G84; 05
> DEBUG:data: 43 33 2e  C3.
> DEBUG:  Octet string dump ends.
> DEBUG:  sms.time: 1552605905
> DEBUG:  sms.smsc_id:
> DEBUG:  sms.smsc_number:
> DEBUG:  sms.foreign_id:
> DEBUG:  sms.service:
> DEBUG:  Octet string at 0x7f1c100022b0:
> DEBUG:len:  4
> DEBUG:size: 5
> DEBUG:immutable: 0
> DEBUG:data:
> DEBUG:  Octet string dump ends.
> DEBUG:  sms.account:
> DEBUG:  sms.id: e20f497c-cc20-45c2-b989-c9006d828d24
> DEBUG:  sms.sms_type: 2
> DEBUG:  sms.mclass: -1
> DEBUG:  sms.mwi: -1
> DEBUG:  sms.coding: 1
> DEBUG:  sms.compress: 0
> DEBUG:  

Re: UDH Support on OpenSMPPBox

[Davor Spasoski]

Are you trying to reverse engineer iMessage? I don't think it uses MAP for that purpose. iMessage is available only on Wi-Fi/Cellular data, it’s something proprietary to Apple and I’d even be surprised if it’s related to RCS. Can you shed some light if you
 know the insights?


Cheers


On Mar 21, 2019, at 2:27 AM, garz m <garz...@gmail.com> wrote:







Dear Users,


Greetings!


Just like to consult if our Opensmppbox service supports Apple type Push Notification such as imessage and facetime? I have seen the correct UDH on the PDU however I found a - maybe an error that I hope you can help check. I'm sharing here the
 PDU captured:
==
DEBUG: SMPP: Got PDU:
DEBUG: SMPP PDU 0x7f1c10001270 dump:
DEBUG:   type_name: submit_sm
DEBUG:   command_id: 4 = 0x0004
DEBUG:   command_status: 0 = 0x
DEBUG:   sequence_number: 128203 = 0x0001f4cb
DEBUG:   service_type: NULL
DEBUG:   source_addr_ton: 1 = 0x0001
DEBUG:   source_addr_npi: 1 = 0x0001
DEBUG:   source_addr: ""
DEBUG:   dest_addr_ton: 1 = 0x0001
DEBUG:   dest_addr_npi: 1 = 0x0001
DEBUG:   destination_addr: ""
DEBUG:   esm_class: 67 = 0x0043
DEBUG:   protocol_id: 0 = 0x
DEBUG:   priority_flag: 0 = 0x
DEBUG:   schedule_delivery_time: NULL
DEBUG:   validity_period: NULL
DEBUG:   registered_delivery: 1 = 0x0001
DEBUG:   replace_if_present_flag: 0 = 0x
DEBUG:   data_coding: 4 = 0x0004
DEBUG:   sm_default_msg_id: 0 = 0x
DEBUG:   sm_length: 90 = 0x005a
DEBUG:   short_message:
DEBUG:    Octet string at 0x7f1c100014d0:
DEBUG:  len:  90
DEBUG:  size: 91
DEBUG:  immutable: 0
DEBUG:  data: 06 05 04 15 79 00 00 42 66 78 20 32 34 20 73 75   y..Bfx 24 su
DEBUG:  data: 20 61 69 64 6c 75 65 2e 20 3f 20 32 50 76 3d 20    aidlue. ? 2Pv=
DEBUG:  data: 35 39 31 20 33 2d 38 20 39 2b 52 53 72 33 45 52   591 3-8 9+RSr3ER
DEBUG:  data: 20 38 3b 30 35 20 3d 33 6e 20 45 3d 33 20 34 31    8;05 =3n E=3 41
DEBUG:  data: 30 32 20 37 30 3d 20 31 31 33 73 20 36 42 3b 20   02 70= 113s 6B;
DEBUG:  data: 47 38 34 3b 20 30 35 43 33 2e G84; 05C3.
DEBUG:    Octet string dump ends.
DEBUG: SMPP PDU dump ends.
DEBUG: SMPP: UDH length read as 7
DEBUG: Found unknown IEI 5 with length 4
DEBUG: UDH was present, but no reference to multipart SMSs
DEBUG: Msg object at 0x7f1c10001a90:
DEBUG:  type: sms
DEBUG:  sms.sender:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:    len:  13
DEBUG:    size: 1024
DEBUG:    immutable: 0
DEBUG:    data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.receiver:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:    len:  13
DEBUG:    size: 1024
DEBUG:    immutable: 0
DEBUG:    data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.udhdata:
DEBUG:  Octet string at 0x7f1c100022e0:
DEBUG:    len:  7
DEBUG:    size: 8
DEBUG:    immutable: 0
DEBUG:    data: 06 05 04 15 79 00 00  y..
DEBUG:  Octet string dump ends.
DEBUG:  sms.msgdata:
DEBUG:  Octet string at 0x7f1c100014d0:
DEBUG:    len:  83
DEBUG:    size: 91
DEBUG:    immutable: 0
DEBUG:    data: 42 66 78 20 32 34 20 73 75 20 61 69 64 6c 75 65   Bfx 24 su aidlue
DEBUG:    data: 2e 20 3f 20 32 50 76 3d 20 35 39 31 20 33 2d 38   . ? 2Pv= 591 3-8
DEBUG:    data: 20 39 2b 52 53 72 33 45 52 20 38 3b 30 35 20 3d    9+RSr3ER 8;05 =
DEBUG:    data: 33 6e 20 45 3d 33 20 34 31 30 32 20 37 30 3d 20   3n E=3 4102 70=
DEBUG:    data: 31 31 33 73 20 36 42 3b 20 47 38 34 3b 20 30 35   113s 6B; G84; 05
DEBUG:    data: 43 33 2e  C3.
DEBUG:  Octet string dump ends.
DEBUG:  sms.time: 1552605905
DEBUG:  sms.smsc_id:
DEBUG:  sms.smsc_number:
DEBUG:  sms.foreign_id:
DEBUG:  sms.service:
DEBUG:  Octet string at 0x7f1c100022b0:
DEBUG:    len:  4
DEBUG:    size: 5
DEBUG:    immutable: 0
DEBUG:    data:    
DEBUG:  Octet string dump ends.
DEBUG:  sms.account:
DEBUG:  sms.id: e20f497c-cc20-45c2-b989-c9006d828d24
DEBUG:  sms.sms_type: 2
DEBUG:  sms.mclass: -1
DEBUG:  sms.mwi: -1
DEBUG:  sms.coding: 1
DEBUG:  sms.compress: 0
DEBUG:  sms.validity: -1
DEBUG:  sms.deferred: -1
DEBUG:  sms.dlr_mask: 19
DEBUG:  sms.dlr_url:
DEBUG:  sms.pid: 0
DEBUG:  sms.alt_dcs: 0
DEBUG:  sms.rpi: -1
DEBUG:  sms.charset:
DEBUG:  sms.boxc_id:
DEBUG:  Octet string at 0x7f1c10001590:
DEBUG:    len:  4
DEBUG:    size: 5
DEBUG:    immutable: 0
DEBUG:    data:    
DEBUG:  Octet string dump ends.
DEBUG:  sms.binfo:
DEBUG:  sms.msg_left: -1
DEBUG:  sms.split_parts: (nil)
DEBUG:  sms.priority: 0
DEBUG:  sms.resend_try: -1
DEBUG:  sms.resend_time: -1
DEBUG:  sms.meta_data:
DEBUG:  Octet string at 0x7f1c10002310:
DEBUG:    len:  6
D

UDH Support on OpenSMPPBox

[garz m]

Dear Users,

Greetings!

Just like to consult if our Opensmppbox service supports Apple type Push
Notification such as imessage and facetime? I have seen the correct UDH on
the PDU however I found a - maybe an error that I hope you can help check.
I'm sharing here the PDU captured:
==
DEBUG: SMPP: Got PDU:
DEBUG: SMPP PDU 0x7f1c10001270 dump:
DEBUG:   type_name: submit_sm
DEBUG:   command_id: 4 = 0x0004
DEBUG:   command_status: 0 = 0x
DEBUG:   sequence_number: 128203 = 0x0001f4cb
DEBUG:   service_type: NULL
DEBUG:   source_addr_ton: 1 = 0x0001
DEBUG:   source_addr_npi: 1 = 0x0001
DEBUG:   source_addr: ""
DEBUG:   dest_addr_ton: 1 = 0x0001
DEBUG:   dest_addr_npi: 1 = 0x0001
DEBUG:   destination_addr: ""
DEBUG:   esm_class: 67 = 0x0043
DEBUG:   protocol_id: 0 = 0x
DEBUG:   priority_flag: 0 = 0x
DEBUG:   schedule_delivery_time: NULL
DEBUG:   validity_period: NULL
DEBUG:   registered_delivery: 1 = 0x0001
DEBUG:   replace_if_present_flag: 0 = 0x
DEBUG:   data_coding: 4 = 0x0004
DEBUG:   sm_default_msg_id: 0 = 0x
DEBUG:   sm_length: 90 = 0x005a
DEBUG:   short_message:
DEBUG:Octet string at 0x7f1c100014d0:
DEBUG:  len:  90
DEBUG:  size: 91
DEBUG:  immutable: 0
DEBUG:  data: *06 05 04 15 79 00 00* 42 66 78 20 32 34 20 73 75
y..Bfx 24 su
DEBUG:  data: 20 61 69 64 6c 75 65 2e 20 3f 20 32 50 76 3d 20
aidlue. ? 2Pv=
DEBUG:  data: 35 39 31 20 33 2d 38 20 39 2b 52 53 72 33 45 52   591 3-8
9+RSr3ER
DEBUG:  data: 20 38 3b 30 35 20 3d 33 6e 20 45 3d 33 20 34 318;05
=3n E=3 41
DEBUG:  data: 30 32 20 37 30 3d 20 31 31 33 73 20 36 42 3b 20   02 70=
113s 6B;
DEBUG:  data: 47 38 34 3b 20 30 35 43 33 2e G84;
05C3.
DEBUG:Octet string dump ends.
DEBUG: SMPP PDU dump ends.
DEBUG: SMPP: UDH length read as 7
*DEBUG: Found unknown IEI 5 with length 4*
DEBUG: UDH was present, but no reference to multipart SMSs
DEBUG: Msg object at 0x7f1c10001a90:
DEBUG:  type: sms
DEBUG:  sms.sender:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:len:  13
DEBUG:size: 1024
DEBUG:immutable: 0
DEBUG:data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.receiver:
DEBUG:  Octet string at 0x7f1c1000:
DEBUG:len:  13
DEBUG:size: 1024
DEBUG:immutable: 0
DEBUG:data: 2b +
DEBUG:  Octet string dump ends.
DEBUG:  sms.udhdata:
DEBUG:  Octet string at 0x7f1c100022e0:
DEBUG:len:  7
DEBUG:size: 8
DEBUG:immutable: 0
DEBUG:data: 06 05 04 15 79 00 00  y..
DEBUG:  Octet string dump ends.
DEBUG:  sms.msgdata:
DEBUG:  Octet string at 0x7f1c100014d0:
DEBUG:len:  83
DEBUG:size: 91
DEBUG:immutable: 0
DEBUG:data: 42 66 78 20 32 34 20 73 75 20 61 69 64 6c 75 65   Bfx 24 su
aidlue
DEBUG:data: 2e 20 3f 20 32 50 76 3d 20 35 39 31 20 33 2d 38   . ? 2Pv=
591 3-8
DEBUG:data: 20 39 2b 52 53 72 33 45 52 20 38 3b 30 35 20 3d9+RSr3ER
8;05 =
DEBUG:data: 33 6e 20 45 3d 33 20 34 31 30 32 20 37 30 3d 20   3n E=3
4102 70=
DEBUG:data: 31 31 33 73 20 36 42 3b 20 47 38 34 3b 20 30 35   113s 6B;
G84; 05
DEBUG:data: 43 33 2e  C3.
DEBUG:  Octet string dump ends.
DEBUG:  sms.time: 1552605905
DEBUG:  sms.smsc_id:
DEBUG:  sms.smsc_number:
DEBUG:  sms.foreign_id:
DEBUG:  sms.service:
DEBUG:  Octet string at 0x7f1c100022b0:
DEBUG:len:  4
DEBUG:size: 5
DEBUG:immutable: 0
DEBUG:data:
DEBUG:  Octet string dump ends.
DEBUG:  sms.account:
DEBUG:  sms.id: e20f497c-cc20-45c2-b989-c9006d828d24
DEBUG:  sms.sms_type: 2
DEBUG:  sms.mclass: -1
DEBUG:  sms.mwi: -1
DEBUG:  sms.coding: 1
DEBUG:  sms.compress: 0
DEBUG:  sms.validity: -1
DEBUG:  sms.deferred: -1
DEBUG:  sms.dlr_mask: 19
DEBUG:  sms.dlr_url:
DEBUG:  sms.pid: 0
DEBUG:  sms.alt_dcs: 0
DEBUG:  sms.rpi: -1
DEBUG:  sms.charset:
DEBUG:  sms.boxc_id:
DEBUG:  Octet string at 0x7f1c10001590:
DEBUG:len:  4
DEBUG:size: 5
DEBUG:immutable: 0
DEBUG:data:
DEBUG:  Octet string dump ends.
DEBUG:  sms.binfo:
DEBUG:  sms.msg_left: -1
DEBUG:  sms.split_parts: (nil)
DEBUG:  sms.priority: 0
DEBUG:  sms.resend_try: -1
DEBUG:  sms.resend_time: -1
DEBUG:  sms.meta_data:
DEBUG:  Octet string at 0x7f1c10002310:
DEBUG:len:  6
DEBUG:size: 1024
DEBUG:immutable: 0
DEBUG:data: 3f 73 6d 70 70 3f ?smpp?
DEBUG:  Octet string dump ends.
=
Setup Info:
Kannel bearerbox version `1.4.5'
Libxml version 2.9.3
Opensmppbox svn Revision: 86
OS : Ubuntu 16.04
==

Hoping someone can take a look if indeed the "unknown IEI" is an error or
not.

Thanks in advance.

Regards,

Garz

Re[4]: route from opensmppbox to internal API

[Хиль Эдуард]

Hey, Ruben! Thank you for your attention on my problem!

My last problem was, cuz i haven't defined any SMSC in my config. For example, 
this config works without error:

#
# opensmppbox config
#
group = core
dlr-storage = internal
store-file = "/var/log/kannel/smpp_store_sms"
group = opensmppbox
opensmppbox-id = test12
opensmppbox-port = 13005
bearerbox-host = 127.0.0.1
bearerbox-port = 13001
log-level = 0
log-file = "/var/log/kannel/opensmppbox.log"
our-system-id = test12
use-systemid-as-smsboxid = true
smpp-logins = "/etc/kannel/users.conf"

#
# kannel config
#
group = core
admin-port = 13000
admin-password = "1234556"
status-password = "1234556"
admin-deny-ip = "*.*.*.*"
admin-allow-ip = "192.168.*.*"
log-file = "/var/log/kannel/bearerbox.log"
log-level = 0
access-log = "/var/log/kannel/access_kannel.log"
store-file = "/var/log/kannel/store_sms"
smsbox-port = 13001
dlr-storage = internal
sms-resend-retry = 1
group = smsc
smsc = fake
port = 1
group = smsc
smsc = loopback
smsc-id = loop1
reroute-dlr = true
allowed-smsc-id = loop1
group = smsbox-route
smsbox-id = test12
smsc-id = loop1
group = smsbox
bearerbox-host = localhost
sendsms-port = 13003
log-file = /var/log/kannel/smsbox.log
log-level = 0
access-log = /var/log/kannel/access_smsbox.log
group = sendsms-user
username = "user"
password = "1234556"
concatenation = true
max-messages = 20
group = sms-service
keyword = default
catch-all = yes
omit-empty = true
assume-plain-text = yes
#post-url = 
"http://127.0.0.1/sendsms.php?d=%d=%R=%F=%I=%c=%C=%O=%u=%n=%p=%P=%b;
post-url = 
"http://127.0.0.1/sendsms.php?src=%p=%P=%t=%c=%i=%C;
concatenation = true
max-messages = 0
BUT! This wrong logic. All SMS from client behind opensmpp, kannel simple 
resend to FAKESMSC. I don't need that kannel resend this SMS, cuz this SMS for 
me, i want kannel to "store" all SMS from opensmppbox to API with defined 
sms-service.

>Понедельник,  4 марта 2019, 1:47 +05:00 от Ruben Melikyan :
>
>Hi Eduard, 
>I think you have messed something in your configurations. Can you please check 
> if your configs are correct? In my example 1234 was the opensmppbox-id, which 
>receives incoming message. Otherwise you can share your configs which lead to 
>error. 
> In this case maybe I can tell you why you are receiving mentioned errors.
>
>Best regards,
>Ruben Melikyan
>
>On Mar 2, 2019, at 17:31, Хиль Эдуард < i.am.t...@mail.ru > wrote:
>
>>Hey, Ruben! Thank you for your advice and configs example!
>>
>>I have tried that configuration, and i got an errors:
>>
>>WARNING: Cannot find SMSCConn for message to < +99887766 >, rejected.
>>WARNING: Message rejected by bearerbox, no router!
>>
>>But if i remove " allowed-smsc-id = loop1 " on loopback settings, i sees 
>>another error
>>
>>WARNING: Could not route message to smsbox id <1234>, smsbox is gone!
>>
>>I have stuck on this error for this time... so i have tried another way: i 
>>have removed " smsbox-route " complitely, and on opensmppbox settings added 
>>"route-to-smsc = loop1" and it works, i see how kannel POST my sms:
>>
>>POST 
>>/sendsms.php?src=%2B1122334455=%2B99887766=2019-03-02+12:55:02=0=loop1=UTF-8
>> HTTP/1.1
>>
>>but and in this case all not so fine... as you can see, there is 
>>"=loop1" thats mean, kannel will put loop1 in all cases, and if on my 
>>opensmppbox connects many clients - all of them will be "loop1" and i can't 
>>distinguish between them. In this case the only right decision is somehow 
>>chagne my API logic? And all this solution with opensmppbox "route-to-smsc" 
>>option is correct? Maybe i must somehow solve "Could not route message to 
>>smsbox id" error and then doing how said Ruben?
>>
>>>Суббота,  2 марта 2019, 16:04 +05:00 от Ruben Melikyan < r...@mobbis.am >:
>>>
>>>Hi Eduard,
>>> 
>>>You should config loopback smsc which will handle your incoming message from 
>>>opensmppbox to your service.
>>> 
>>>Config example:
>>>#-OPENSMPPBOX-
>>>group = opensmppbox
>>>opensmppbox-id =  1234
>>>opensmppbox-port = …
>>>bearerbox-host = …
>>>bearerbox-port = …
>>>log-level = …
>>>log-file = ….
>>>our-system-id = ….
>>>smpp-logins = …..
>>>use-systemid-as-smsboxid=true
>>>source-addr-ton = …
>>>source-addr-npi = …
>>>dest-addr-ton = ….
>>>dest-addr-npi = ….
>>> 
>>>#-SMSC smpp LOOP1-----
>>>group = smsc
>>>smsc = loopba

Re[2]: route from opensmppbox to internal API

[Хиль Эдуард]

Hey, Ruben! Thank you for your advice and configs example!

I have tried that configuration, and i got an errors:

WARNING: Cannot find SMSCConn for message to <+99887766>, rejected.
WARNING: Message rejected by bearerbox, no router!

But if i remove " allowed-smsc-id = loop1 " on loopback settings, i sees 
another error

WARNING: Could not route message to smsbox id <1234>, smsbox is gone!

I have stuck on this error for this time... so i have tried another way: i have 
removed " smsbox-route " complitely, and on opensmppbox settings added 
"route-to-smsc = loop1" and it works, i see how kannel POST my sms:

POST 
/sendsms.php?src=%2B1122334455=%2B99887766=2019-03-02+12:55:02=0=loop1=UTF-8
 HTTP/1.1

but and in this case all not so fine... as you can see, there is "=loop1" 
thats mean, kannel will put loop1 in all cases, and if on my opensmppbox 
connects many clients - all of them will be "loop1" and i can't distinguish 
between them. In this case the only right decision is somehow chagne my API 
logic? And all this solution with opensmppbox "route-to-smsc" option is 
correct? Maybe i must somehow solve "Could not route message to smsbox id" 
error and then doing how said Ruben?

>Суббота,  2 марта 2019, 16:04 +05:00 от Ruben Melikyan :
>
>Hi Eduard,
> 
>You should config loopback smsc which will handle your incoming message from 
>opensmppbox to your service.
> 
>Config example:
>#-OPENSMPPBOX-
>group = opensmppbox
>opensmppbox-id =  1234
>opensmppbox-port = …
>bearerbox-host = …
>bearerbox-port = …
>log-level = …
>log-file = ….
>our-system-id = ….
>smpp-logins = …..
>use-systemid-as-smsboxid=true
>source-addr-ton = …
>source-addr-npi = …
>dest-addr-ton = ….
>dest-addr-npi = ….
> 
>#-SMSC smpp LOOP1-
>group = smsc
>smsc = loopback
>smsc-id = loop1
>reroute-dlr=true
>allowed-smsc-id = loop1
> 
> 
># --  SMS SERVICE --
>group = sms-service
>keyword = default
>catch-all=yes
>max-messages = 4
>omit-empty = true
>assume-plain-text = yes
>concatenation = true
>max-messages = 4
>post-url =….
> 
># --  SMS ROUTING --
> 
>group = smsbox-route
>smsbox-id = 1234
>smsc-id = loop1
> 
> 
> 
> 
>Best regards
>Ruben Melikyan
> 
> 
>From: users [mailto:users-boun...@kannel.org]  On Behalf Of  Хиль Эдуард
>Sent: Saturday, 2 March, 2019 13:08
>To: users@kannel.org
>Subject: route from opensmppbox to internal API
> 
>Hi there!
>Let's imagine, that i have on my kannel one smsc and one sms-service with 
>config:
>group = sms-service
>keyword = default
>post-url = " 
>http://127.0.0.1/sendsms.php?src=%P=%p=%t=%c=%n=%C
> "
>concatenation = true
>max-messages = 0
>
>In this case, when kannel calls this API, he used POST method and on this API 
>(on PHP page) i have some code "file_get_contents('php://input')" where i can 
>get text of SMS from html-body. All works correct and i'm satisfied.
>But now, i have opensmppbox and i must somehow route sms from opensmppbox to 
>this API. I have find 2 methods: with "smsc http" and "smsc http with 
>system-type generic", but in this both cases kannel uses GET method, and i 
>must use %b variable that put text in http link (for example: 
>...=%n=%C%text=%b), but i can't, cuz there are length and charset 
>troubles - i can't put on my link sms message with over 900 symbols with 
>strange codepage :'( 
>So, maybe there are some other methods to route SMS from opensmppbox to kannel 
>sms-service? Or maybe kannel can use POST method not only on sms-service group?
>-- 
>Best regards,
>Me.

-- 
Best regards,
Me.

RE: route from opensmppbox to internal API

[Ruben Melikyan]

Hi Eduard,

 

You should config loopback smsc which will handle your incoming message from 
opensmppbox to your service.

 

Config example:

#-OPENSMPPBOX-

group = opensmppbox

opensmppbox-id = 1234

opensmppbox-port = …

bearerbox-host = …

bearerbox-port = …

log-level = …

log-file = ….

our-system-id = ….

smpp-logins = …..

use-systemid-as-smsboxid=true

source-addr-ton = …

source-addr-npi = …

dest-addr-ton = ….

dest-addr-npi = ….

 

#-SMSC smpp LOOP1-

group = smsc

smsc = loopback

smsc-id = loop1

reroute-dlr=true

allowed-smsc-id = loop1

 

 

# --  SMS SERVICE --

group = sms-service

keyword = default

catch-all=yes

max-messages = 4

omit-empty = true

assume-plain-text = yes

concatenation = true

max-messages = 4

post-url =….

 

# --  SMS ROUTING --

 

group = smsbox-route

smsbox-id = 1234

smsc-id = loop1

 

 

 

 

Best regards

Ruben Melikyan

 

 

From: users [mailto:users-boun...@kannel.org] On Behalf Of Хиль Эдуард
Sent: Saturday, 2 March, 2019 13:08
To: users@kannel.org
Subject: route from opensmppbox to internal API

 

Hi there!
Let's imagine, that i have on my kannel one smsc and one sms-service with 
config:

group = sms-service
keyword = default
post-url = "http://127.0.0.1/sendsms.php?src=%P 
<http://127.0.0.1/sendsms.php?src=%25P=%25p=%25t=%25c=%25n=%25C>
 =%p=%t=%c=%n=%C"
concatenation = true
max-messages = 0

In this case, when kannel calls this API, he used POST method and on this API 
(on PHP page) i have some code "file_get_contents('php://input')" where i can 
get text of SMS from html-body. All works correct and i'm satisfied.
But now, i have opensmppbox and i must somehow route sms from opensmppbox to 
this API. I have find 2 methods: with "smsc http" and "smsc http with 
system-type generic", but in this both cases kannel uses GET method, and i must 
use %b variable that put text in http link (for example: 
...=%n=%C%text=%b), but i can't, cuz there are length and charset 
troubles - i can't put on my link sms message with over 900 symbols with 
strange codepage :'( 
So, maybe there are some other methods to route SMS from opensmppbox to kannel 
sms-service? Or maybe kannel can use POST method not only on sms-service group?

-- 
Best regards,
Me.

Re: OPENSMPPBox issue.

[Stipe Tolj]

Am 19.02.19 08:08, schrieb Gert Tamm:

2019-02-19 08:07:13 [13238] [0] INFO: Debug_lvl = 0, log_file = ,
log_lvl = 0
2019-02-19 08:07:13 [13238] [0] DEBUG: Loading include file
`/etc/kannel/opensmppbox.conf' (on line 39 of file /etc/kannel/kannel.conf).
2019-02-19 08:07:13 [13238] [0] ERROR: Group 'opensmppbox' is no valid
group identifier.
2019-02-19 08:07:13 [13238] [0] ERROR: Error found on line 5 of file
`/etc/kannel/kannel.conf'.
2019-02-19 08:07:13 [13238] [0] PANIC: Couldn't read configuration from
`/etc/kannel/kannel.conf'.
2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(gw_panic+0x16b) [0x48068b]
2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(main+0xe3a) [0x40d69a]
2019-02-19 08:07:13 [13238] [0] PANIC:
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f9fe54d0830]
2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(_start+0x29) [0x40d759]


2019-02-19 08:07:15 [13239] [0] INFO: Debug_lvl = 0, log_file = ,
log_lvl = 0
2019-02-19 08:07:15 [13239] [0] DEBUG: Loading include file
`/etc/kannel/opensmppbox.conf' (on line 39 of file /etc/kannel/kannel.conf).
2019-02-19 08:07:15 [13239] [0] ERROR: Group 'opensmppbox' is no valid
group identifier.
2019-02-19 08:07:15 [13239] [0] ERROR: Error found on line 5 of file
`/etc/kannel/kannel.conf'.
2019-02-19 08:07:15 [13239] [0] PANIC: Couldn't read configuration from
`/etc/kannel/kannel.conf'.
2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(gw_panic+0x16b) [0x439adb]
2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(main+0x12b9) [0x40d7d9]
2019-02-19 08:07:15 [13239] [0] PANIC:
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fbc458d8830]
2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(_start+0x29) [0x40da69]

2/19/2019 09:05 Web Min kirjutas:

try the following instead

bearerbox -v 0 /etc/kannel/kannel.conf

smsbox -v 0 /etc/kannel/kannel.conf


that's actually correct, since the opensmppbox is an add-on component 
that registers it's own config group identifiers, and therefore they can 
ONLY be used in the configuration scope of the opensmppbox runtime.


In other words, if you add a 'group = opensmppbox' context to your 
kannel.conf that is used for bearebox and smsbox, they will NOT KNOW 
about that config group, and hence complain.


The best idea is that you separate the configuration structure, so that 
opensmppbox uses only it's own parts and bearerbox/smsbox vice versa.


--
Best Regards,
Stipe Tolj

---
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/

st...@kannel.org  s...@tolj.org
---

Re: OPENSMPPBox issue.

[Web Min]

it seems you have a problem with your configuration as showing below

2019-02-19 08:07:13 [13238] [0] ERROR: Group 'opensmppbox' is no valid
group identifier.
2019-02-19 08:07:13 [13238] [0] ERROR: Error found on line 5 of file
`/etc/kannel/kannel.conf'.



On Tue, Feb 19, 2019 at 10:08 AM Gert Tamm  wrote:

> 2019-02-19 08:07:13 [13238] [0] INFO: Debug_lvl = 0, log_file = ,
> log_lvl = 0
> 2019-02-19 08:07:13 [13238] [0] DEBUG: Loading include file
> `/etc/kannel/opensmppbox.conf' (on line 39 of file /etc/kannel/kannel.conf).
> 2019-02-19 08:07:13 [13238] [0] ERROR: Group 'opensmppbox' is no valid
> group identifier.
> 2019-02-19 08:07:13 [13238] [0] ERROR: Error found on line 5 of file
> `/etc/kannel/kannel.conf'.
> 2019-02-19 08:07:13 [13238] [0] PANIC: Couldn't read configuration from
> `/etc/kannel/kannel.conf'.
> 2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(gw_panic+0x16b) [0x48068b]
> 2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(main+0xe3a) [0x40d69a]
> 2019-02-19 08:07:13 [13238] [0] PANIC:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f9fe54d0830]
> 2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(_start+0x29) [0x40d759]
>
>
> 2019-02-19 08:07:15 [13239] [0] INFO: Debug_lvl = 0, log_file = ,
> log_lvl = 0
> 2019-02-19 08:07:15 [13239] [0] DEBUG: Loading include file
> `/etc/kannel/opensmppbox.conf' (on line 39 of file /etc/kannel/kannel.conf).
> 2019-02-19 08:07:15 [13239] [0] ERROR: Group 'opensmppbox' is no valid
> group identifier.
> 2019-02-19 08:07:15 [13239] [0] ERROR: Error found on line 5 of file
> `/etc/kannel/kannel.conf'.
> 2019-02-19 08:07:15 [13239] [0] PANIC: Couldn't read configuration from
> `/etc/kannel/kannel.conf'.
> 2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(gw_panic+0x16b) [0x439adb]
> 2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(main+0x12b9) [0x40d7d9]
> 2019-02-19 08:07:15 [13239] [0] PANIC:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fbc458d8830]
> 2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(_start+0x29) [0x40da69]
>
> 2/19/2019 09:05 Web Min kirjutas:
>
> try the following instead
>
> bearerbox -v 0 /etc/kannel/kannel.conf
>
> smsbox -v 0 /etc/kannel/kannel.conf
>
> and share the output
>
>
> On Tue, Feb 19, 2019 at 10:03 AM Gert Tamm  wrote:
>
>> I start all the parts of kannel like this :
>>
>> sudo /usr/local/sbin/run_kannel_box --pidfile
>> /var/run/kannel/kannel_bearerbox.pid --no-extra-args
>> /usr/local/sbin/bearerbox -v 0 -- /etc/kannel/kannel.conf
>> sudo /usr/local/sbin/run_kannel_box --pidfile
>> /var/run/kannel/kannel_smsbox.pid --no-extra-args /usr/local/sbin/smsbox -v
>> 0 -- /etc/kannel/kannel.conf
>> sudo /usr/local/sbin/run_kannel_box --pidfile
>> /var/run/kannel/kannel_smppbox.pid --no-extra-args
>> /usr/local/sbin/opensmppbox -v 0 -- /etc/kannel/kannel.conf
>> 2/18/2019 11:54 Web Min kirjutas:
>>
>> How you are running both bearerbox and smsbox?
>>
>> make sure to pico /etc/default/kannel
>> and then add
>>
>> START_WAPBOX=1
>> START_SMSBOX=1
>>
>> then restart the kannel service, after that check the status via your
>> brower
>>
>>
>> On Mon, Feb 18, 2019 at 12:49 PM Gert Tamm  wrote:
>>
>>> Hello,
>>>
>>> When I start my bearerbox and smsbox with any configuration of
>>> OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't start. And
>>> I'm not getting any errors to log files.
>>> What I might have done wrong?
>>>
>>> --
>>> Tervitades/Best Wishes,
>>> Gert Tamm
>>> Süsteemiadministraator/System administrator
>>> E-mail: g...@messenger.ee
>>> Direct Messenger OÜ
>>>
>>>
>>> --
>> Tervitades/Best Wishes,
>> Gert Tamm
>> Süsteemiadministraator/System administrator
>> E-mail: g...@messenger.ee
>> Direct Messenger OÜ
>>
>> --
> Tervitades/Best Wishes,
> Gert Tamm
> Süsteemiadministraator/System administrator
> E-mail: g...@messenger.ee
> Direct Messenger OÜ
>
>

Re: OPENSMPPBox issue.

[Gert Tamm]

2019-02-19 08:07:13 [13238] [0] INFO: Debug_lvl = 0, log_file = , 
log_lvl = 0
2019-02-19 08:07:13 [13238] [0] DEBUG: Loading include file 
`/etc/kannel/opensmppbox.conf' (on line 39 of file /etc/kannel/kannel.conf).
2019-02-19 08:07:13 [13238] [0] ERROR: Group 'opensmppbox' is no valid 
group identifier.
2019-02-19 08:07:13 [13238] [0] ERROR: Error found on line 5 of file 
`/etc/kannel/kannel.conf'.
2019-02-19 08:07:13 [13238] [0] PANIC: Couldn't read configuration from 
`/etc/kannel/kannel.conf'.

2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(gw_panic+0x16b) [0x48068b]
2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(main+0xe3a) [0x40d69a]
2019-02-19 08:07:13 [13238] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f9fe54d0830]

2019-02-19 08:07:13 [13238] [0] PANIC: bearerbox(_start+0x29) [0x40d759]


2019-02-19 08:07:15 [13239] [0] INFO: Debug_lvl = 0, log_file = , 
log_lvl = 0
2019-02-19 08:07:15 [13239] [0] DEBUG: Loading include file 
`/etc/kannel/opensmppbox.conf' (on line 39 of file /etc/kannel/kannel.conf).
2019-02-19 08:07:15 [13239] [0] ERROR: Group 'opensmppbox' is no valid 
group identifier.
2019-02-19 08:07:15 [13239] [0] ERROR: Error found on line 5 of file 
`/etc/kannel/kannel.conf'.
2019-02-19 08:07:15 [13239] [0] PANIC: Couldn't read configuration from 
`/etc/kannel/kannel.conf'.

2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(gw_panic+0x16b) [0x439adb]
2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(main+0x12b9) [0x40d7d9]
2019-02-19 08:07:15 [13239] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fbc458d8830]

2019-02-19 08:07:15 [13239] [0] PANIC: smsbox(_start+0x29) [0x40da69]

2/19/2019 09:05 Web Min kirjutas:

try the following instead

bearerbox -v 0 /etc/kannel/kannel.conf

smsbox -v 0 /etc/kannel/kannel.conf


and share the output


On Tue, Feb 19, 2019 at 10:03 AM Gert Tamm <mailto:g...@messenger.ee>> wrote:


I start all the parts of kannel like this :

sudo /usr/local/sbin/run_kannel_box --pidfile
/var/run/kannel/kannel_bearerbox.pid --no-extra-args
/usr/local/sbin/bearerbox -v 0 -- /etc/kannel/kannel.conf
sudo /usr/local/sbin/run_kannel_box --pidfile
/var/run/kannel/kannel_smsbox.pid --no-extra-args
/usr/local/sbin/smsbox -v 0 -- /etc/kannel/kannel.conf
sudo /usr/local/sbin/run_kannel_box --pidfile
/var/run/kannel/kannel_smppbox.pid --no-extra-args
/usr/local/sbin/opensmppbox -v 0 -- /etc/kannel/kannel.conf

2/18/2019 11:54 Web Min kirjutas:

How you are running both bearerbox and smsbox?

make sure to pico /etc/default/kannel
and then add

START_WAPBOX=1
START_SMSBOX=1

then restart the kannel service, after that check the status via
your brower


On Mon, Feb 18, 2019 at 12:49 PM Gert Tamm mailto:g...@messenger.ee>> wrote:

Hello,

When I start my bearerbox and smsbox with any configuration of
OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't
start. And
I'm not getting any errors to log files.
What I might have done wrong?

-- 
Tervitades/Best Wishes,

Gert Tamm
Süsteemiadministraator/System administrator
E-mail: g...@messenger.ee <mailto:g...@messenger.ee>
Direct Messenger OÜ


-- 
Tervitades/Best Wishes,

Gert Tamm
Süsteemiadministraator/System administrator
E-mail:g...@messenger.ee  <mailto:g...@messenger.ee>
Direct Messenger OÜ


--
Tervitades/Best Wishes,
Gert Tamm
Süsteemiadministraator/System administrator
E-mail: g...@messenger.ee
Direct Messenger OÜ

Re: OPENSMPPBox issue.

[Web Min]

try the following instead

bearerbox -v 0 /etc/kannel/kannel.conf

smsbox -v 0 /etc/kannel/kannel.conf

and share the output


On Tue, Feb 19, 2019 at 10:03 AM Gert Tamm  wrote:

> I start all the parts of kannel like this :
>
> sudo /usr/local/sbin/run_kannel_box --pidfile
> /var/run/kannel/kannel_bearerbox.pid --no-extra-args
> /usr/local/sbin/bearerbox -v 0 -- /etc/kannel/kannel.conf
> sudo /usr/local/sbin/run_kannel_box --pidfile
> /var/run/kannel/kannel_smsbox.pid --no-extra-args /usr/local/sbin/smsbox -v
> 0 -- /etc/kannel/kannel.conf
> sudo /usr/local/sbin/run_kannel_box --pidfile
> /var/run/kannel/kannel_smppbox.pid --no-extra-args
> /usr/local/sbin/opensmppbox -v 0 -- /etc/kannel/kannel.conf
> 2/18/2019 11:54 Web Min kirjutas:
>
> How you are running both bearerbox and smsbox?
>
> make sure to pico /etc/default/kannel
> and then add
>
> START_WAPBOX=1
> START_SMSBOX=1
>
> then restart the kannel service, after that check the status via your
> brower
>
>
> On Mon, Feb 18, 2019 at 12:49 PM Gert Tamm  wrote:
>
>> Hello,
>>
>> When I start my bearerbox and smsbox with any configuration of
>> OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't start. And
>> I'm not getting any errors to log files.
>> What I might have done wrong?
>>
>> --
>> Tervitades/Best Wishes,
>> Gert Tamm
>> Süsteemiadministraator/System administrator
>> E-mail: g...@messenger.ee
>> Direct Messenger OÜ
>>
>>
>> --
> Tervitades/Best Wishes,
> Gert Tamm
> Süsteemiadministraator/System administrator
> E-mail: g...@messenger.ee
> Direct Messenger OÜ
>
>

Re: OPENSMPPBox issue.

[Gert Tamm]

I start all the parts of kannel like this :

sudo /usr/local/sbin/run_kannel_box --pidfile 
/var/run/kannel/kannel_bearerbox.pid --no-extra-args 
/usr/local/sbin/bearerbox -v 0 -- /etc/kannel/kannel.conf
sudo /usr/local/sbin/run_kannel_box --pidfile 
/var/run/kannel/kannel_smsbox.pid --no-extra-args /usr/local/sbin/smsbox 
-v 0 -- /etc/kannel/kannel.conf
sudo /usr/local/sbin/run_kannel_box --pidfile 
/var/run/kannel/kannel_smppbox.pid --no-extra-args 
/usr/local/sbin/opensmppbox -v 0 -- /etc/kannel/kannel.conf


2/18/2019 11:54 Web Min kirjutas:

How you are running both bearerbox and smsbox?

make sure to pico /etc/default/kannel
and then add

START_WAPBOX=1
START_SMSBOX=1

then restart the kannel service, after that check the status via your 
brower



On Mon, Feb 18, 2019 at 12:49 PM Gert Tamm <mailto:g...@messenger.ee>> wrote:


Hello,

When I start my bearerbox and smsbox with any configuration of
OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't
start. And
I'm not getting any errors to log files.
What I might have done wrong?

-- 
Tervitades/Best Wishes,

Gert Tamm
Süsteemiadministraator/System administrator
E-mail: g...@messenger.ee <mailto:g...@messenger.ee>
Direct Messenger OÜ



--
Tervitades/Best Wishes,
Gert Tamm
Süsteemiadministraator/System administrator
E-mail: g...@messenger.ee
Direct Messenger OÜ

Re: OPENSMPPBox issue.

[Web Min]

How you are running both bearerbox and smsbox?

make sure to pico /etc/default/kannel
and then add

START_WAPBOX=1
START_SMSBOX=1

then restart the kannel service, after that check the status via your brower


On Mon, Feb 18, 2019 at 12:49 PM Gert Tamm  wrote:

> Hello,
>
> When I start my bearerbox and smsbox with any configuration of
> OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't start. And
> I'm not getting any errors to log files.
> What I might have done wrong?
>
> --
> Tervitades/Best Wishes,
> Gert Tamm
> Süsteemiadministraator/System administrator
> E-mail: g...@messenger.ee
> Direct Messenger OÜ
>
>
>

OPENSMPPBox issue.

[Gert Tamm]

Hello,

When I start my bearerbox and smsbox with any configuration of 
OpenSMPPBox, only SMPPBox starts, bearerbox and smsbox won't start. And 
I'm not getting any errors to log files.

What I might have done wrong?

--
Tervitades/Best Wishes,
Gert Tamm
Süsteemiadministraator/System administrator
E-mail: g...@messenger.ee
Direct Messenger OÜ

[Help with Kannel Configuration for incoming and outgoing (Receive and Send ) SMS using OPENSMPPBOX, SQLBOX]

[sekabira yasin]

Hello there,

I kindly need some help/pointers on how i can configure Kannel to receive
and send sms with Opensmppbox and SQLBox addons..

I'm new to kannel, i have set up my kannel with a fakesmsc, its up and
running.. though i need to configure it with OPENSMPPBOX and SQLBOX, this
is because i wish to have the incoming messages to be stored in a database,
and the OPENSMPPBOX to provide me a smsc settings such that i can receive
messages from other SMPP Providers / ESMEs, for outgoing/sending messages,
these should also be stored in the databases, plus the dlrs..

here is my kannel.conf

# Main kannel config file
#-
# BEARERBOX CONFIGURATIONS
# CORE
group = core
dlr-storage = internal
admin-port = 13000
admin-password = bar
#status-password = 
admin-allow-ip = '*.*.*.*'
smsbox-port = 13001
log-level = 0
log-file = "/etc/kannel/logs/kannel.log"
box-allow-ip = '*.*.*.*'

#-
# This is a fake smsc connection, _only_ used to test the
# system and services. It really cannot relay messages to
# actual handsets!
group = smsc
smsc = fake
smsc-id = FAKE
port = 1
log-level = 0
connect-allow-ip = 127.0.0.1

#-
# SMSBOX SETUP
group = smsbox
smsbox-id  = mysmsbox
bearerbox-host = A.B.C.D # This is a public IP
sendsms-port = 13013
global-sender = 13013
sendsms-chars = "0123456789 +-"
log-file = "/etc/kannel/logs/smsbox.log"
log-level = 0
access-log = "/etc/kannel/logs/access.log"

#-
# SEND-SMS USERS
group = sendsms-user
username = tester
password = foobar

group = smsbox-route
smsbox-id = mysmsbox
smsc-id = FAKE

#-
# SERVICES
group = sms-service
keyword = nop
text = "You asked nothing and i did it!"

# Default
group = sms-service
keyword = default
text = "No service specified"


---
Here is my bearer box status, i have installed Kannel version 1.4.4, my
server is in the Cloud at Linode.

$curl 'http://A.B.C.D:13000/status?password=bar'
Kannel bearerbox version `1.4.4'.
Build `Mar 27 2018 06:58:08', compiler `4.8.5 20150623 (Red Hat 4.8.5-16)'.
System Linux, release 4.15.8-x86_64-linode103, version #1 SMP Fri Mar 9
21:02:39 UTC 2018, machine x86_64.
Hostname li1509-36.members.linode.com, IP A.B.C.D.
Libxml version 2.9.1.
Compiled with MySQL 5.6.39, using MySQL 5.6.39.
Using native malloc.


Status: running, uptime 0d 2h 26m 49s

WDP: received 0 (0 queued), sent 0 (0 queued)

SMS: received 0 (0 queued), sent 0 (0 queued), store size -1
SMS: inbound (0.00,0.00,0.00) 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:mysmsbox, IP A.B.C.D (0 queued), (on-line 0d 2h 25m 49s)


SMSC connections:
FAKE[FAKE]FAKE:1 (connecting, rcvd: sms 0 (0.00,0.00,0.00) /
dlr 0 (0.00,0.00,0.00), sent: sms 0 (0.00,0.00,0.00) / dlr 0
(0.00,0.00,0.00), failed 0, queued 0 msgs)

--

Any Help is highly appreciated...

-- 
Regards
---
*Sekabira Yasin*
sekayasin.me
@sekayasin9 <https://twitter.com/sekayasin9>
-

*Chief Technical Ninja *@katwecolab <https://twitter.com/katwecolab>* | *@
patchedUG <https://twitter.com/patchedUG>* | Mamawalu Foundation | Kompyuta
Giants*
---
#Topooowa

RE: opensmppbox and mysql

[info.ubichip]

Hello,

 

I'm not sure to well understand your need, but please take a look on sqlbox 
which be the solution.

 

BR

 

De : users [mailto:users-boun...@kannel.org] De la part de uves
Envoyé : mercredi 31 janvier 2018 11:04
À : users@kannel.org
Objet : opensmppbox and mysql

 

Hello

 

We use opensmppbox to send sms, directing traffic via route-to-smsc to the call

for the smsc = http channel and receiving for url.

 

Is it possible for the opensmppbox traffic to be saved to the mysql database 
without passing to url?

opensmppbox and mysql

[uves]

Hello   We use opensmppbox to send sms, directing traffic via route-to-smsc to 
the call  for the smsc = http channel and receiving for url.   Is it possible 
for the opensmppbox traffic to be saved to the mysql database without passing 
to url?

Re[8]: OpenSMPPBox Panic

[Педченко Владимир]

Hi Rene / Users! Can U please make a daily snapshot. Last snapshot was made Wed Jan 18 06:04:23 CET 2017.Thank U! 

RE: OPENSMPPBOX Panic

[Wan Md Arif Noor Bin. Wan Nizam]

Hi Again,

I'm getting the PANIC more and more each day and I still can't find what 
causing it. I can just revert to the old version, however the old version has 
another issue with "Garbage PDU" which I like to avoid as it keeps 
disconnecting user, but PANIC issue is more troubling as it crashed and 
disconnecting all user instead of one.

Below are the latest 2 crashes log :

2017-05-22 23:03:34 [3366] [83] PANIC: gwlib/octstr.c:2569: seems_valid_real: 
Assertion `ostr->data[ostr->len] == '\0'' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2017-05-22 23:03:34 [3366] [83] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(gw_backtrace+0xae) [0x45db6e]
2017-05-22 23:03:34 [3366] [83] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(gw_panic+0x159) [0x45dcd9]
2017-05-22 23:03:34 [3366] [83] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45f95b]
2017-05-22 23:03:34 [3366] [83] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_destroy+0x1d) [0x461c8d]
2017-05-22 23:03:34 [3366] [83] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x40e7bd]
2017-05-22 23:03:34 [3366] [83] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41105f]
2017-05-22 23:03:34 [3366] [83] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-22 23:03:34 [3366] [83] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7fa32a0eaaa1]
2017-05-22 23:03:34 [3366] [83] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7fa3297e693d]

addr2line -e /usr/local/kannel2/sbin/opensmppbox 0x45db6e 0x45dcd9 0x45f95b 
0x461c8d 0x40e7bd 0x41105f 0x4546a9

/home/trunk/gwlib/log.c:572
/home/trunk/gwlib/log.c:608
/home/trunk/gwlib/octstr.c:2571
/home/trunk/gwlib/octstr.c:326
/home/opensmppbox/trunk/gw/opensmppbox.c:1788
/home/opensmppbox/trunk/gw/opensmppbox.c:2150
/home/trunk/gwlib/gwthread-pthread.c:391


2017-05-22 23:21:28 [31827] [79] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x46b3fc]
2017-05-22 23:21:28 [31827] [79] PANIC: /lib64/libpthread.so.0(+0xf7e0) 
[0x7fd664b747e0]
2017-05-22 23:21:28 [31827] [79] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45f992]
2017-05-22 23:21:28 [31827] [79] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_destroy+0x1d) [0x461c8d]
2017-05-22 23:21:28 [31827] [79] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x40e787]
2017-05-22 23:21:28 [31827] [79] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41105f]
2017-05-22 23:21:28 [31827] [79] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-22 23:21:28 [31827] [79] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7fd664b6caa1]
2017-05-22 23:21:28 [31827] [79] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7fd66426893d]

addr2line -e /usr/local/kannel2/sbin/opensmppbox 0x46b3fc 0x45f992 0x461c8d 
0x40e787 0x41105f 0x4546a9

/home/trunk/gwlib/utils.c:168
/home/trunk/gwlib/octstr.c:2568
/home/trunk/gwlib/octstr.c:326
/home/opensmppbox/trunk/gw/opensmppbox.c:1779
/home/opensmppbox/trunk/gw/opensmppbox.c:2150
/home/trunk/gwlib/gwthread-pthread.c:391

Kindly need your assistance on this, do let me know if you need more 
information.

Thanks!
Arif Noor

From: users [mailto:users-boun...@kannel.org] On Behalf Of Wan Md Arif Noor 
Bin. Wan Nizam
Sent: Tuesday, May 16, 2017 10:42 AM
To: users@kannel.org
Subject: RE: OPENSMPPBOX Panic

Hi Users,

Anyone having this same issue?  Need assist urgently.


Thank you and Regards,
Arif Noor

From: users [mailto:users-boun...@kannel.org] On Behalf Of Wan Md Arif Noor 
Bin. Wan Nizam
Sent: Thursday, May 11, 2017 9:49 AM
To: users@kannel.org<mailto:users@kannel.org>
Subject: OPENSMPPBOX Panic


This sender failed our fraud detection checks and may not be who they appear to 
be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>

Feedback<http://aka.ms/SafetyTipsFeedback>

Hi Kannel Users,

I'm having issues with Opensmppbox which will go into PANIC with below error 
every day after upgrading to new SVN 'svn-r5186M'

09th May

2017-05-09 05:52:42 [29877] [97] PANIC: gwlib/octstr.c:2564: seems_valid_real: 
Assertion `ostr->data != NULL' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(gw_backtrace+0xae) [0x45db6e]
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(gw_panic+0x159) [0x45dcd9]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45fb60]
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_destroy+0x1d) [0x461c8d]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x40e787]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41105f]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-09 05:52:42 [29877] [97] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7fde85adeaa1]
2017-05-09 05:52:42 [29877] [97] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7fde851da93d]

2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin

RE: OPENSMPPBOX Panic

[Wan Md Arif Noor Bin. Wan Nizam]

Hi Users,

Anyone having this same issue?  Need assist urgently.


Thank you and Regards,
Arif Noor

From: users [mailto:users-boun...@kannel.org] On Behalf Of Wan Md Arif Noor 
Bin. Wan Nizam
Sent: Thursday, May 11, 2017 9:49 AM
To: users@kannel.org
Subject: OPENSMPPBOX Panic


This sender failed our fraud detection checks and may not be who they appear to 
be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>

Feedback<http://aka.ms/SafetyTipsFeedback>

Hi Kannel Users,

I'm having issues with Opensmppbox which will go into PANIC with below error 
every day after upgrading to new SVN 'svn-r5186M'

09th May

2017-05-09 05:52:42 [29877] [97] PANIC: gwlib/octstr.c:2564: seems_valid_real: 
Assertion `ostr->data != NULL' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(gw_backtrace+0xae) [0x45db6e]
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(gw_panic+0x159) [0x45dcd9]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45fb60]
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_destroy+0x1d) [0x461c8d]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x40e787]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41105f]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-09 05:52:42 [29877] [97] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7fde85adeaa1]
2017-05-09 05:52:42 [29877] [97] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7fde851da93d]

2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x46b3fc]
2017-05-09 12:53:12 [6023] [88] PANIC: /lib64/libpthread.so.0(+0xf7e0) 
[0x7f27f82977e0]
2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45f8fb]
2017-05-09 12:53:12 [6023] [88] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_get_cstr_real+0x13) [0x45fb83]
2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41051a]
2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-09 12:53:12 [6023] [88] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7f27f828faa1]
2017-05-09 12:53:12 [6023] [88] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7f27f798b93d]

10th May

2017-05-10 16:00:40 [27593] [72] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x46b3fc]
2017-05-10 16:00:40 [27593] [72] PANIC: /lib64/libpthread.so.0(+0xf7e0) 
[0x7f1b36cd17e0]
2017-05-10 16:00:40 [27593] [72] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45f8fb]
2017-05-10 16:00:40 [27593] [72] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_get_cstr_real+0x13) [0x45fb83]
2017-05-10 16:00:40 [27593] [72] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41051a]
2017-05-10 16:00:40 [27593] [72] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-10 16:00:40 [27593] [72] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7f1b36cc9aa1]
2017-05-10 16:00:40 [27593] [72] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7f1b363c593d]

Opensmppbox Configuration

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = FSMPP
opensmppbox-port = 3476
bearerbox-host = localhost
bearerbox-port = 14002
log-level = 0
log-file = "/var/log/kannel/smppbox/debug.log"
our-system-id = fSystem
use-systemid-as-smsboxid = 1
smpp-logins = "/opt/kannel/smpplogins.txt"

group = mysql-connection
id = mydlr
host = localhost
username = *
password = *
database = kannel
max-connections = 6

group = dlr-db
id = mydlr
table = dlr_smpp
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxcid

Kindly assist

Regards and thanks,
Arif Noor

OPENSMPPBOX Panic

[Wan Md Arif Noor Bin. Wan Nizam]

Hi Kannel Users,

I'm having issues with Opensmppbox which will go into PANIC with below error 
every day after upgrading to new SVN 'svn-r5186M'

09th May

2017-05-09 05:52:42 [29877] [97] PANIC: gwlib/octstr.c:2564: seems_valid_real: 
Assertion `ostr->data != NULL' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(gw_backtrace+0xae) [0x45db6e]
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(gw_panic+0x159) [0x45dcd9]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45fb60]
2017-05-09 05:52:42 [29877] [97] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_destroy+0x1d) [0x461c8d]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x40e787]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41105f]
2017-05-09 05:52:42 [29877] [97] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-09 05:52:42 [29877] [97] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7fde85adeaa1]
2017-05-09 05:52:42 [29877] [97] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7fde851da93d]

2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x46b3fc]
2017-05-09 12:53:12 [6023] [88] PANIC: /lib64/libpthread.so.0(+0xf7e0) 
[0x7f27f82977e0]
2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45f8fb]
2017-05-09 12:53:12 [6023] [88] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_get_cstr_real+0x13) [0x45fb83]
2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41051a]
2017-05-09 12:53:12 [6023] [88] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-09 12:53:12 [6023] [88] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7f27f828faa1]
2017-05-09 12:53:12 [6023] [88] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7f27f798b93d]

10th May

2017-05-10 16:00:40 [27593] [72] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x46b3fc]
2017-05-10 16:00:40 [27593] [72] PANIC: /lib64/libpthread.so.0(+0xf7e0) 
[0x7f1b36cd17e0]
2017-05-10 16:00:40 [27593] [72] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x45f8fb]
2017-05-10 16:00:40 [27593] [72] PANIC: 
/usr/local/kannel2/sbin/opensmppbox(octstr_get_cstr_real+0x13) [0x45fb83]
2017-05-10 16:00:40 [27593] [72] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x41051a]
2017-05-10 16:00:40 [27593] [72] PANIC: /usr/local/kannel2/sbin/opensmppbox() 
[0x4546a9]
2017-05-10 16:00:40 [27593] [72] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7f1b36cc9aa1]
2017-05-10 16:00:40 [27593] [72] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7f1b363c593d]

Opensmppbox Configuration

group = core
dlr-storage = mysql

group = opensmppbox
opensmppbox-id = FSMPP
opensmppbox-port = 3476
bearerbox-host = localhost
bearerbox-port = 14002
log-level = 0
log-file = "/var/log/kannel/smppbox/debug.log"
our-system-id = fSystem
use-systemid-as-smsboxid = 1
smpp-logins = "/opt/kannel/smpplogins.txt"

group = mysql-connection
id = mydlr
host = localhost
username = *
password = *
database = kannel
max-connections = 6

group = dlr-db
id = mydlr
table = dlr_smpp
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxcid

Kindly assist

Regards and thanks,
Arif Noor

Re: OpenSMPPBox

[Stipe Tolj]

Am 18.04.2017 22:33, schrieb Omar Khaled:

Dears,

I would like to know what is the parameter *“our-system-id”* refer to as
I found the below description, but I still not understand what is
referring to:

*“Corresponds to SMSC identification transmitted to connected ESMEs”*


if refers to the system-id that is returned to the ESME in the 
corresponding bind resp PDU.


--
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
---

OpenSMPPBox

[Omar Khaled]

Dears,

 

I would like to know what is the parameter "our-system-id" refer to as I
found the below description, but I still not understand what is referring
to:

 

"Corresponds to SMSC identification transmitted to connected ESMEs"

 

Thanks in advance for your for your time.

 

Best Regards,

 




 

Omar Khaled Nazeem

Support Team Leader

 

27 Magdy Salama Street, 

Off Autostrad, Maadi, Cairo, Egypt.

M + 20 (114) 200-9315

T +202 2516 0004

F +202 2516 0060

  www.victorylink.com

.

 



*

The content of this document is classified as Victory Link Confidential and
Proprietary Information. The recipient hereby is committed to hold in strict
confidence the contents of this (e-mail, document, and information) and not
to disclose to any third party without the prior written consent of Victory
Link. Recipient will be held liable for any unauthorized disclosure.

If you have received this message in error, please notify the sender by
return e-mail and delete the message in its entirety, including any
attachments.

 

 

Re: Opensmppbox Issue

[Stipe Tolj]

Am 06.04.17 13:32, schrieb Wan Md Arif Noor Bin. Wan Nizam:

I think he replied to the wrong case maybe?


especially as I didn't mean this Rene, I ment of course Rene Kluwen, the 
Kannel group member that is in charge of the opensmppbox.


Stipe

--
Best Regards,
Stipe Tolj

---
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/

st...@kannel.org  s...@tolj.org
---

RE: Opensmppbox Issue

[Wan Md Arif Noor Bin. Wan Nizam]

I think he replied to the wrong case maybe?

Regards,
Arif Noor.


From: users [mailto:users-boun...@kannel.org] On Behalf Of Vangelis Typaldos
Sent: Thursday, April 06, 2017 4:51 PM
To: René Kapayo; Stipe Tolj
Cc: users@kannel.org
Subject: Re: Opensmppbox Issue

Rene which was the issue? I have the same issue and these garbage generate nack 
pdu to the client and disconnections.

BR


Από: René Kapayo<mailto:yagb...@gmail.com>
Αποστολή: Πέμπτη, 6 Απριλίου 2017 11:18
Προς: Stipe Tolj<mailto:st...@kannel.org>
Κοιν.: users@kannel.org<mailto:users@kannel.org>
Θέμα: Re: Opensmppbox Issue

Hi Stipe,
Sorry for delay.
The issue was resolved.
Thanks

2017-04-05 15:48 GMT+01:00 Stipe Tolj 
<st...@kannel.org<mailto:st...@kannel.org>>:
Am 05.04.17 03:25, schrieb Wan Md Arif Noor Bin. Wan Nizam:
Hi Rene,

I don’t quite understand what you mean by something different from smpp,
is there any way for me to trace which transaction / sequence was
causing this error, I already done a tcpdump but can’t really find
anything peculiar.

if you can share the tcpdump capture file to Rene and me, we can have a chance 
to look into it.

--
Best Regards,
Stipe Tolj

---
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org<http://tolj.org> system architecture
http://www.kannel.org/http://www.tolj.org/

st...@kannel.org<mailto:st...@kannel.org>  
s...@tolj.org<mailto:s...@tolj.org>
---



--
Rene KAPAYO
Ingenieur Informaticien
Certifié Prince 2 Fundation
Tél.(portable) : +236 75 20 25 79
Domicile (portable) : +236 77 06 40 43
B.P. 2533 Bangui
Republique Centrafricaine

Re: Opensmppbox Issue

[Vangelis Typaldos]

Rene which was the issue? I have the same issue and these garbage generate nack 
pdu to the client and disconnections.

BR


Από: René Kapayo<mailto:yagb...@gmail.com>
Αποστολή: Πέμπτη, 6 Απριλίου 2017 11:18
Προς: Stipe Tolj<mailto:st...@kannel.org>
Κοιν.: users@kannel.org<mailto:users@kannel.org>
Θέμα: Re: Opensmppbox Issue

Hi Stipe,
Sorry for delay.
The issue was resolved.
Thanks

2017-04-05 15:48 GMT+01:00 Stipe Tolj 
<st...@kannel.org<mailto:st...@kannel.org>>:
Am 05.04.17 03:25, schrieb Wan Md Arif Noor Bin. Wan Nizam:
Hi Rene,

I don’t quite understand what you mean by something different from smpp,
is there any way for me to trace which transaction / sequence was
causing this error, I already done a tcpdump but can’t really find
anything peculiar.

if you can share the tcpdump capture file to Rene and me, we can have a chance 
to look into it.

--
Best Regards,
Stipe Tolj

---
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org<http://tolj.org> system architecture
http://www.kannel.org/http://www.tolj.org/

st...@kannel.org<mailto:st...@kannel.org>  
s...@tolj.org<mailto:s...@tolj.org>
---




--
Rene KAPAYO
Ingenieur Informaticien
Certifié Prince 2 Fundation
Tél.(portable) : +236 75 20 25 79
Domicile (portable) : +236 77 06 40 43
B.P. 2533 Bangui
Republique Centrafricaine

Re: Opensmppbox Issue

[René Kapayo]

Hi Stipe,
Sorry for delay.
The issue was resolved.
Thanks

2017-04-05 15:48 GMT+01:00 Stipe Tolj :

> Am 05.04.17 03:25, schrieb Wan Md Arif Noor Bin. Wan Nizam:
>
>> Hi Rene,
>>
>> I don’t quite understand what you mean by something different from smpp,
>> is there any way for me to trace which transaction / sequence was
>> causing this error, I already done a tcpdump but can’t really find
>> anything peculiar.
>>
>
> if you can share the tcpdump capture file to Rene and me, we can have a
> chance to look into it.
>
> --
> Best Regards,
> Stipe Tolj
>
> ---
> Düsseldorf, NRW, Germany
>
> Kannel Foundation tolj.org system architecture
> http://www.kannel.org/http://www.tolj.org/
>
> st...@kannel.org  s...@tolj.org
> ---
>
>


-- 
Rene KAPAYO
Ingenieur Informaticien
Certifié Prince 2 Fundation
Tél.(portable) : +236 75 20 25 79
Domicile (portable) : +236 77 06 40 43
B.P. 2533 Bangui
Republique Centrafricaine

Re: Opensmppbox Issue

[Stipe Tolj]

Am 05.04.17 03:25, schrieb Wan Md Arif Noor Bin. Wan Nizam:

Hi Rene,

I don’t quite understand what you mean by something different from smpp,
is there any way for me to trace which transaction / sequence was
causing this error, I already done a tcpdump but can’t really find
anything peculiar.


if you can share the tcpdump capture file to Rene and me, we can have a 
chance to look into it.


--
Best Regards,
Stipe Tolj

---
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/

st...@kannel.org  s...@tolj.org
---

Re: Opensmppbox Slow Response (submit_sm_resp)

[garz m]

Hi Rene,

Thanks for the response. I have the same understanding - access logs are
processed transactions of the bearerbox. In this case, the submission from
the opensmppbox to sqlbox to bearerbox is right on time. But then again the
response back of opensmppbox is delayed. Isn't that opensmppbox should send
right away the submit_sm_resp once it gets the submit_sm? Is there on the
codes I can adjust to achieve this behaviour?

BR,
Garzie

On Mon, Apr 3, 2017 at 9:29 PM, Rene Kluwen <rene.klu...@chimit.nl> wrote:

> Once the message is in the access log it has passed opensmppbox already.
> So if throughput is slow, maybe it's your downstream smsc connection.
>
>
> -- Origineel bericht --
> Van: "garz m" <garz...@gmail.com>
> Aan: users@kannel.org
> Verzonden: 30-3-2017 10:24:54
> Onderwerp: Opensmppbox Slow Response (submit_sm_resp)
>
> Dear Rene / Users:
>
> Good day!
>
> I'd like to consult to you our experience using Kannel Opensmppbox.When an
> ESME sends large TPS traffic, we noticed slow response from the Opensmppbox
> app, thus creating a queue at the ESME's end. I have here sample PDUs:
>
> *Submit_SM PDU*
> *==*
> 2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP[]: Got PDU:
> 2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP PDU 0x7fe24d4a77c0 dump:
> *2017-03-27 14:59:13 [1641] [30] DEBUG:   type_name: submit_sm*
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   command_id: 4 = 0x0004
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   command_status: 0 = 0x
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   sequence_number: 4488803 =
> 0x00447e63
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   service_type: NULL
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr_ton: 5 = 0x0005
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr_npi: 0 = 0x
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr: ""
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   dest_addr_ton: 1 = 0x0001
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   dest_addr_npi: 1 = 0x0001
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   destination_addr: ""
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   esm_class: 0 = 0x
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   protocol_id: 0 = 0x
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   priority_flag: 0 = 0x
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   schedule_delivery_time: NULL
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   validity_period:
> "170329065905000+"
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   registered_delivery: 1 =
> 0x0001
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   replace_if_present_flag: 0 =
> 0x
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   data_coding: 0 = 0x
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   sm_default_msg_id: 0 = 0x
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   sm_length: 103 = 0x0067
> 2017-03-27 14:59:13 [1641] [30] DEBUG:   short_message:
> 2017-03-27 14:59:13 [1641] [30] DEBUG:Octet string at 0x7fe24d342720:
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  len:  103
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  size: 104
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  immutable: 0
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
> xx xx xx xx xx xx xx xx   
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
> xx xx xx xx xx xx xx xx   
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
> xx xx xx xx xx xx xx xx   
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
> xx xx xx xx xx xx xx xx   
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
> xx xx xx xx xx xx xx xx   
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
> xx xx xx xx xx xx xx xx   
> 2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx
>  xxx
> 2017-03-27 14:59:13 [1641] [30] DEBUG:Octet string dump ends.
> 2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP PDU dump ends.
>
> *Submit_SM_Resp PDU:*
> *==*
> 2017-03-27 14:59:39 [1641] [29] DEBUG: SMPP[]: Sending PDU:
> 2017-03-27 14:59:39 [1641] [29] DEBUG: SMPP PDU 0x7fe24d34a6d0 dump:
> *2017-03-27 14:59:39 [1641] [29] DEBUG:   type_name: submit_sm_resp*
> 2017-03-27 14:59:39 [1641] [29] DEBUG:   command_id: 2147483652
> <(214)%20748-3652> = 0x8004
> 2017-03-27 14:59:39 [1641] [29] DEBUG:   command_status: 0 = 0x
> 2017-03-27 14:59:39 [1641] [29] DEBUG:   sequence_number: 4488803 =
> 0x00447e63
> 2017-03-27 14:59:39 [1641] [29] DEBUG:   message_id:
> 2017-03-27 14:59:39 [1641] [

RE: Opensmppbox Issue

[Wan Md Arif Noor Bin. Wan Nizam]

Hi Rene,

I don’t quite understand what you mean by something different from smpp, is 
there any way for me to trace which transaction / sequence was causing this 
error, I already done a tcpdump but can’t really find anything peculiar.

Thanks again,
Arif Noor


From: Rene Kluwen [mailto:rene.klu...@chimit.nl]
Sent: Monday, April 03, 2017 9:26 PM
To: Wan Md Arif Noor Bin. Wan Nizam; users@kannel.org
Subject: Re: Opensmppbox Issue

Most probable cause is that they connect with something different from smpp.

-- Origineel bericht --
Van: "Wan Md Arif Noor Bin. Wan Nizam" 
<md.a...@forest-interactive.com<mailto:md.a...@forest-interactive.com>>
Aan: "users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
Verzonden: 29-3-2017 4:22:28
Onderwerp: Opensmppbox Issue

Hi Kannel Users,

I have an issue where recently user is constatly reconnecting to the 
opensmppbox. Digging into the logs found below information.

1008761:2017-03-29 09:50:23 [17929] [3595] ERROR: SMPP: PDU length was too 
small (4, minimum is 16).
1008762:2017-03-29 09:50:23 [17929] [3595] ERROR: opensmppbox[Zen]: Server sent 
garbage, ignored.
1008763:2017-03-29 09:50:23 [17929] [3595] ERROR: Invalid SMPP PDU received.
1008764:2017-03-29 09:50:23 [17929] [3595] DEBUG: Thread 3595 
(opensmppbox.c:smpp_to_bearerbox) terminates.

This only occur recently since few days ago for that particular user. Can’t 
find anything weird or what sequence caused that in the logs aside from above. 
Kindly advise.

Kannel Version :

Kannel bearerbox version `svn-r5154M'.
Opensmppbox version 1.5.0

Thanks,
Arif Noor

Re: Opensmppbox Slow Response (submit_sm_resp)

[Rene Kluwen]

Once the message is in the access log it has passed opensmppbox already.
So if throughput is slow, maybe it's your downstream smsc connection.


-- Origineel bericht --
Van: "garz m" <garz...@gmail.com>
Aan: users@kannel.org
Verzonden: 30-3-2017 10:24:54
Onderwerp: Opensmppbox Slow Response (submit_sm_resp)


Dear Rene / Users:

Good day!

I'd like to consult to you our experience using Kannel Opensmppbox.When 
an ESME sends large TPS traffic, we noticed slow response from the 
Opensmppbox app, thus creating a queue at the ESME's end. I have here 
sample PDUs:


Submit_SM PDU
==
2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP[]: Got PDU:
2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP PDU 0x7fe24d4a77c0 dump:
2017-03-27 14:59:13 [1641] [30] DEBUG:   type_name: submit_sm
2017-03-27 14:59:13 [1641] [30] DEBUG:   command_id: 4 = 0x0004
2017-03-27 14:59:13 [1641] [30] DEBUG:   command_status: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   sequence_number: 4488803 = 
0x00447e63

2017-03-27 14:59:13 [1641] [30] DEBUG:   service_type: NULL
2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr_ton: 5 = 
0x0005
2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr_npi: 0 = 
0x

2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr: ""
2017-03-27 14:59:13 [1641] [30] DEBUG:   dest_addr_ton: 1 = 0x0001
2017-03-27 14:59:13 [1641] [30] DEBUG:   dest_addr_npi: 1 = 0x0001
2017-03-27 14:59:13 [1641] [30] DEBUG:   destination_addr: 
""

2017-03-27 14:59:13 [1641] [30] DEBUG:   esm_class: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   protocol_id: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   priority_flag: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   schedule_delivery_time: NULL
2017-03-27 14:59:13 [1641] [30] DEBUG:   validity_period: 
"170329065905000+"
2017-03-27 14:59:13 [1641] [30] DEBUG:   registered_delivery: 1 = 
0x0001
2017-03-27 14:59:13 [1641] [30] DEBUG:   replace_if_present_flag: 0 = 
0x

2017-03-27 14:59:13 [1641] [30] DEBUG:   data_coding: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   sm_default_msg_id: 0 = 
0x

2017-03-27 14:59:13 [1641] [30] DEBUG:   sm_length: 103 = 0x0067
2017-03-27 14:59:13 [1641] [30] DEBUG:   short_message:
2017-03-27 14:59:13 [1641] [30] DEBUG:Octet string at 
0x7fe24d342720:

2017-03-27 14:59:13 [1641] [30] DEBUG:  len:  103
2017-03-27 14:59:13 [1641] [30] DEBUG:  size: 104
2017-03-27 14:59:13 [1641] [30] DEBUG:  immutable: 0
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx 
xx xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx 
xx xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx 
xx xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx 
xx xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx 
xx xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx 
xx xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx  
xxx

2017-03-27 14:59:13 [1641] [30] DEBUG:Octet string dump ends.
2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP PDU dump ends.

Submit_SM_Resp PDU:
==
2017-03-27 14:59:39 [1641] [29] DEBUG: SMPP[]: Sending PDU:
2017-03-27 14:59:39 [1641] [29] DEBUG: SMPP PDU 0x7fe24d34a6d0 dump:
2017-03-27 14:59:39 [1641] [29] DEBUG:   type_name: submit_sm_resp
2017-03-27 14:59:39 [1641] [29] DEBUG:   command_id: 2147483652 
<tel:(214)%20748-3652> = 0x8004

2017-03-27 14:59:39 [1641] [29] DEBUG:   command_status: 0 = 0x
2017-03-27 14:59:39 [1641] [29] DEBUG:   sequence_number: 4488803 = 
0x00447e63

2017-03-27 14:59:39 [1641] [29] DEBUG:   message_id:
2017-03-27 14:59:39 [1641] [29] DEBUG:Octet string at 
0x7fe24d341f30:

2017-03-27 14:59:39 [1641] [29] DEBUG:  len:  36
2017-03-27 14:59:39 [1641] [29] DEBUG:  size: 37
2017-03-27 14:59:39 [1641] [29] DEBUG:  immutable: 0
2017-03-27 14:59:39 [1641] [29] DEBUG:  data: 32 32 39 64 62 39 32 
63 2d 35 37 61 63 2d 34 33   229db92c-57ac-43
2017-03-27 14:59:39 [1641] [29] DEBUG:  data: 34 35 2d 61 64 34 66 
2d 36 61 35 65 65 39 66 31   45-ad4f-6a5ee9f1
2017-03-27 14:59:39 [1641] [29] DEBUG:  data: 66 62 39 30   
fb90

2017-03-27 14:59:39 [1641] [29] DEBUG:Octet string dump ends.
2017-03-27 14:59:39 [1641] [29] DEBUG: SMPP PDU dump ends.

Looking at the Bearerbox Access logs, i found that this sample was 
processed right on time:


Access Logs (CDRs)
2017-03-27 14:59:14 Sent SMS [SMSC:HTTP.SMSC] [SVC:xx] [ACT:] 
[BINF:] [FID:229db92c-57ac-4345

Re: Opensmppbox Issue

[Rene Kluwen]

Most probable cause is that they connect with something different from 
smpp.


-- Origineel bericht --
Van: "Wan Md Arif Noor Bin. Wan Nizam" <md.a...@forest-interactive.com>
Aan: "users@kannel.org" <users@kannel.org>
Verzonden: 29-3-2017 4:22:28
Onderwerp: Opensmppbox Issue


Hi Kannel Users,



I have an issue where recently user is constatly reconnecting to the 
opensmppbox. Digging into the logs found below information.




1008761:2017-03-29 09:50:23 [17929] [3595] ERROR: SMPP: PDU length was 
too small (4, minimum is 16).


1008762:2017-03-29 09:50:23 [17929] [3595] ERROR: opensmppbox[Zen]: 
Server sent garbage, ignored.


1008763:2017-03-29 09:50:23 [17929] [3595] ERROR: Invalid SMPP PDU 
received.


1008764:2017-03-29 09:50:23 [17929] [3595] DEBUG: Thread 3595 
(opensmppbox.c:smpp_to_bearerbox) terminates.




This only occur recently since few days ago for that particular user. 
Can’t find anything weird or what sequence caused that in the logs 
aside from above. Kindly advise.




Kannel Version :



Kannel bearerbox version `svn-r5154M'.

Opensmppbox version 1.5.0



Thanks,

Arif Noor

Opensmppbox Slow Response (submit_sm_resp)

[garz m]

Dear Rene / Users:

Good day!

I'd like to consult to you our experience using Kannel Opensmppbox.When an
ESME sends large TPS traffic, we noticed slow response from the Opensmppbox
app, thus creating a queue at the ESME's end. I have here sample PDUs:

*Submit_SM PDU*
*==*
2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP[]: Got PDU:
2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP PDU 0x7fe24d4a77c0 dump:
*2017-03-27 14:59:13 [1641] [30] DEBUG:   type_name: submit_sm*
2017-03-27 14:59:13 [1641] [30] DEBUG:   command_id: 4 = 0x0004
2017-03-27 14:59:13 [1641] [30] DEBUG:   command_status: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   sequence_number: 4488803 =
0x00447e63
2017-03-27 14:59:13 [1641] [30] DEBUG:   service_type: NULL
2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr_ton: 5 = 0x0005
2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr_npi: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   source_addr: ""
2017-03-27 14:59:13 [1641] [30] DEBUG:   dest_addr_ton: 1 = 0x0001
2017-03-27 14:59:13 [1641] [30] DEBUG:   dest_addr_npi: 1 = 0x0001
2017-03-27 14:59:13 [1641] [30] DEBUG:   destination_addr: ""
2017-03-27 14:59:13 [1641] [30] DEBUG:   esm_class: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   protocol_id: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   priority_flag: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   schedule_delivery_time: NULL
2017-03-27 14:59:13 [1641] [30] DEBUG:   validity_period: "170329065905000+"
2017-03-27 14:59:13 [1641] [30] DEBUG:   registered_delivery: 1 = 0x0001
2017-03-27 14:59:13 [1641] [30] DEBUG:   replace_if_present_flag: 0 =
0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   data_coding: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   sm_default_msg_id: 0 = 0x
2017-03-27 14:59:13 [1641] [30] DEBUG:   sm_length: 103 = 0x0067
2017-03-27 14:59:13 [1641] [30] DEBUG:   short_message:
2017-03-27 14:59:13 [1641] [30] DEBUG:Octet string at 0x7fe24d342720:
2017-03-27 14:59:13 [1641] [30] DEBUG:  len:  103
2017-03-27 14:59:13 [1641] [30] DEBUG:  size: 104
2017-03-27 14:59:13 [1641] [30] DEBUG:  immutable: 0
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx xx
xx xx xx xx xx xx xx xx   
2017-03-27 14:59:13 [1641] [30] DEBUG:  data: xx xx xx xx xx xx xx
 xxx
2017-03-27 14:59:13 [1641] [30] DEBUG:Octet string dump ends.
2017-03-27 14:59:13 [1641] [30] DEBUG: SMPP PDU dump ends.

*Submit_SM_Resp PDU:*
*==*
2017-03-27 14:59:39 [1641] [29] DEBUG: SMPP[]: Sending PDU:
2017-03-27 14:59:39 [1641] [29] DEBUG: SMPP PDU 0x7fe24d34a6d0 dump:
*2017-03-27 14:59:39 [1641] [29] DEBUG:   type_name: submit_sm_resp*
2017-03-27 14:59:39 [1641] [29] DEBUG:   command_id: 2147483652
<(214)%20748-3652> = 0x8004
2017-03-27 14:59:39 [1641] [29] DEBUG:   command_status: 0 = 0x
2017-03-27 14:59:39 [1641] [29] DEBUG:   sequence_number: 4488803 =
0x00447e63
2017-03-27 14:59:39 [1641] [29] DEBUG:   message_id:
2017-03-27 14:59:39 [1641] [29] DEBUG:Octet string at 0x7fe24d341f30:
2017-03-27 14:59:39 [1641] [29] DEBUG:  len:  36
2017-03-27 14:59:39 [1641] [29] DEBUG:  size: 37
2017-03-27 14:59:39 [1641] [29] DEBUG:  immutable: 0
2017-03-27 14:59:39 [1641] [29] DEBUG:  data: 32 32 39 64 62 39 32 63
2d 35 37 61 63 2d 34 33   229db92c-57ac-43
2017-03-27 14:59:39 [1641] [29] DEBUG:  data: 34 35 2d 61 64 34 66 2d
36 61 35 65 65 39 66 31   45-ad4f-6a5ee9f1
2017-03-27 14:59:39 [1641] [29] DEBUG:  data: 66 62 39 30
fb90
2017-03-27 14:59:39 [1641] [29] DEBUG:Octet string dump ends.
2017-03-27 14:59:39 [1641] [29] DEBUG: SMPP PDU dump ends.

Looking at the Bearerbox Access logs, i found that this sample was
processed right on time:

*Access Logs (CDRs)*
*2017-03-27 14:59:14 Sent SMS* [SMSC:HTTP.SMSC] [SVC:xx] [ACT:] [BINF:]
[FID:229db92c-57ac-4345-ad4f-6a5ee9f1fb90] [META:?smpp?] [from:xxx]
[to:+xxx] [flags:-1:0:-1:0:19] [msg:103:]
2017-03-27 14:59:19 Receive DLR [SMSC:HTTP.SMSC] [SVC:xx] [ACT:]
[BINF:] [FID:229db92c-57ac-4345-ad4f-6a5ee9f1fb90]
[META:?orig_msg?dlr_mask=19&] [from:x] [to:+]
[flags:-1:-1:-1:-1:1] [msg:0:] [udh:0:]

Also, DB table check confirmed that indeed the

Opensmppbox Issue

[Wan Md Arif Noor Bin. Wan Nizam]

Hi Kannel Users,

I have an issue where recently user is constatly reconnecting to the 
opensmppbox. Digging into the logs found below information.

1008761:2017-03-29 09:50:23 [17929] [3595] ERROR: SMPP: PDU length was too 
small (4, minimum is 16).
1008762:2017-03-29 09:50:23 [17929] [3595] ERROR: opensmppbox[Zen]: Server sent 
garbage, ignored.
1008763:2017-03-29 09:50:23 [17929] [3595] ERROR: Invalid SMPP PDU received.
1008764:2017-03-29 09:50:23 [17929] [3595] DEBUG: Thread 3595 
(opensmppbox.c:smpp_to_bearerbox) terminates.

This only occur recently since few days ago for that particular user. Can't 
find anything weird or what sequence caused that in the logs aside from above. 
Kindly advise.

Kannel Version :

Kannel bearerbox version `svn-r5154M'.
Opensmppbox version 1.5.0

Thanks,
Arif Noor

Re[2]: issue with dlr lost with opensmppbox

[Rene Kluwen]

Could you share your current config?

-- Origineel bericht --
Van: "info.ubichip" <info.ubic...@free.fr>
Aan: users@kannel.org
Verzonden: 21-3-2017 9:54:59
Onderwerp: RE: issue with dlr lost with opensmppbox


Hello,

Do someone have any idea ?

regards


-Message d'origine-
De : users [mailto:users-boun...@kannel.org] De la part de info.ubichip
Envoyé : vendredi 10 mars 2017 15:45
À : users@kannel.org
Objet : issue with dlr lost with opensmppbox

Hello,

I assume probably this issue has been raise years ago (I read something 
in 2011), but I couldn't find any answer. Here is the issue :
I'm using opensmppbox, bearerbox sqlbox and smsbox. Different accounts 
(toto1 to toto9) has been setup in opensmppbox,


Sometime the whole box process are restarted, and then the SMPP account 
DLR before customer can connect (totoX), so the DLR looks to be lost 
because of lack of path to send.
Do you think there is a way to hold on these DLR until customers 
connect correctly ?


Any help will be appreciate


smsbox log :
2017-03-10 07:00:05 [29215] [9] ERROR: Couldn't send request to 
<319addf3>
2017-03-10 07:00:05 [29215] [9] ERROR: URL <4944ff5a> doesn't start 
with `http:/ /' nor `https://'


Kannel.log :

2017-03-10 07:00:04 [29179] [9] DEBUG: boxc_receiver: got boxc_id 
 from <127.0.0.1>
2017-03-10 07:00:04 [29179] [4] WARNING: Could not route message to 
smsbox id , smsbox is gone!

2017-03-10 07:00:04 [29179] [4] WARNING: smsbox_list empty!
2017-03-10 07:00:04 [29179] [4] WARNING: Could not route message to 
smsbox id , smsbox is gone!

RE: issue with dlr lost with opensmppbox

[info.ubichip]

Hello,

Do someone have any idea ?

regards


-Message d'origine-
De : users [mailto:users-boun...@kannel.org] De la part de info.ubichip
Envoyé : vendredi 10 mars 2017 15:45
À : users@kannel.org
Objet : issue with dlr lost with opensmppbox

Hello,

I assume probably this issue has been raise years ago (I read something in 
2011), but I couldn't find any answer. Here is the issue :
I'm using opensmppbox, bearerbox sqlbox and smsbox. Different accounts (toto1 
to toto9) has been setup in opensmppbox, 

Sometime the whole box process are restarted, and then the SMPP account DLR 
before customer can connect (totoX), so the DLR looks to be lost because of 
lack of path to send. 
Do you think there is a way to hold on these DLR until customers connect 
correctly ?

Any help will be appreciate


smsbox log :
2017-03-10 07:00:05 [29215] [9] ERROR: Couldn't send request to <319addf3>
2017-03-10 07:00:05 [29215] [9] ERROR: URL <4944ff5a> doesn't start with 
`http:/ /' nor `https://'

Kannel.log :

2017-03-10 07:00:04 [29179] [9] DEBUG: boxc_receiver: got boxc_id  from 
<127.0.0.1>
2017-03-10 07:00:04 [29179] [4] WARNING: Could not route message to smsbox id 
, smsbox is gone!
2017-03-10 07:00:04 [29179] [4] WARNING: smsbox_list empty!
2017-03-10 07:00:04 [29179] [4] WARNING: Could not route message to smsbox id 
, smsbox is gone!

issue with dlr lost with opensmppbox

[info.ubichip]

Hello,

I assume probably this issue has been raise years ago (I read something in 
2011), but I couldn't find any answer. Here is the issue :
I'm using opensmppbox, bearerbox sqlbox and smsbox. Different accounts (toto1 
to toto9) has been setup in opensmppbox, 

Sometime the whole box process are restarted, and then the SMPP account DLR 
before customer can connect (totoX), so the DLR looks to be lost because of 
lack of path to send. 
Do you think there is a way to hold on these DLR until customers connect 
correctly ?

Any help will be appreciate


smsbox log :
2017-03-10 07:00:05 [29215] [9] ERROR: Couldn't send request to <319addf3>
2017-03-10 07:00:05 [29215] [9] ERROR: URL <4944ff5a> doesn't start with `http:/
/' nor `https://'

Kannel.log :

2017-03-10 07:00:04 [29179] [9] DEBUG: boxc_receiver: got boxc_id  from
<127.0.0.1>
2017-03-10 07:00:04 [29179] [4] WARNING: Could not route message to smsbox id 
, smsbox is gone!
2017-03-10 07:00:04 [29179] [4] WARNING: smsbox_list empty!
2017-03-10 07:00:04 [29179] [4] WARNING: Could not route message to smsbox id 
, smsbox is gone!

RE: Re[6]: OpenSMPPBox Panic

[Davor Spasoski]

Checked and now opensmppbox does not cause panic on startup, nor on sending 
concatenated SMS.

Thanks

Davor Spasoski
VAS Cloud & ICT Development Team Leader / Online and VAS Development

M: +38975400608
e-mail: davor.spaso...@onevip.mk

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia
From: Rene Kluwen [mailto:rene.klu...@chimit.nl]
Sent: 09 February 2017 00:47
To: Davor Spasoski <davor.spaso...@onevip.mk>; Davor Spasoski 
<davor.spaso...@onevip.mk>; spameden <spame...@gmail.com>
Cc: users@kannel.org
Subject: Re[6]: OpenSMPPBox Panic

Please be so kind to check out latest svn again.
Probably store-type was not given in your config, but this is not needed with 
internal/mysql storage.

I need to get an better fix for this. But I am curious to know if it works for 
you now.
Apologies for the inconvenience.

== Rene


-- Origineel bericht --
Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Aan: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>; "spameden" 
<spame...@gmail.com<mailto:spame...@gmail.com>>
Cc: "users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
Verzonden: 8-2-2017 14:38:05
Onderwerp: RE: Re[4]: OpenSMPPBox Panic

This is what I get when called with internal or with mysql storage. Can someone 
check please

vas@smpp-proxy:~/sources/gateway-1.5-svn-06-02-2017/addons/opensmppbox/gw$<mailto:vas@smpp-proxy:~/sources/gateway-1.5-svn-06-02-2017/addons/opensmppbox/gw$>
 /vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox_simple.conf
2017-02-08 14:36:14 [1332] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-08 14:36:14 [1332] [0] INFO: DLR using storage type: internal
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f662ca5a3d0]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f662c397830]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]

2017-02-08 14:34:35 [1330] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-08 14:34:35 [1330] [0] INFO: DLR using storage type: mysql
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f525dbc83d0]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f525d505830]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]

Davor Spasoski
From: users [mailto:users-boun...@kannel.org<mailto:users-boun...@kannel.org>] 
On Behalf Of Davor Spasoski
Sent: 08 February 2017 13:32
To: spameden <spame...@gmail.com<mailto:spame...@gmail.com>>
Cc: users@kannel.org<mailto:users@kannel.org>
Subject: RE: Re[4]: OpenSMPPBox Panic

This shouldn’t be the case. I tried internal as DLR and it panics, too.

Davor Spasoski
From: spameden [mailto:spame...@gmail.com]
Sent: 06 February 2017 13:46
To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: Garry Macasieb <garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>; 
Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>; 
users@kannel.org<mailto:users@kannel.org>
Subject: Re: Re[4]: OpenSMPPBox Panic

Can only guess it's something to do with store format. Maybe in the new version 
it's different that's why OpenSMPPBox panics.

Try deleting store file / spool and restarting opensmppbox.

2017-02-06 13:53 GMT+03:00 Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>:
Hi,

I compiled the latest opensmppbox this morning with the hope for the PANIC 
after concatenated SMS.

Now I can’t even start it. I receive panic on startup. Same config file as ever.

/vas/bin/opensmppbox -v 1 /

Re[8]: OpenSMPPBox Panic

[Rene Kluwen]

Ideally the versions of kannel & opensmppbox should be the same.


-- Origineel bericht --
Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
Aan: "Rene Kluwen" <rene.klu...@chimit.nl>
Verzonden: 13-2-2017 10:43:26
Onderwerp: Re: Re[6]: OpenSMPPBox Panic


Which version of kannel should I compile against? Stabel 1.4.4 or svn?
On Feb 9, 2017, at 12:46 AM, Rene Kluwen wrote:


Please be so kind to check out latest svn again.
Probably store-type was not given in your config, but this is not 
needed with internal/mysql storage.


I need to get an better fix for this. But I am curious to know if it 
works for you now.

Apologies for the inconvenience.

== Rene


-- Origineel bericht --
Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
Aan: "Davor Spasoski" <davor.spaso...@onevip.mk>; "spameden" 
<spame...@gmail.com>

Cc: "users@kannel.org" <users@kannel.org>
Verzonden: 8-2-2017 14:38:05
Onderwerp: RE: Re[4]: OpenSMPPBox Panic

This is what I get when called with internal or with mysql storage. 
Can someone check please


vas@smpp-proxy:~/sources/gateway-1.5-svn-06-02-2017/addons/opensmppbox/gw$ 
/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox_simple.conf
2017-02-08 14:36:14 [1332] [0] INFO: Debug_lvl = 1, log_file = 
, log_lvl = 0

2017-02-08 14:36:14 [1332] [0] INFO: DLR using storage type: internal
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() 
[0x442788]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f662ca5a3d0]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() 
[0x4530ba]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/vas/bin/opensmppbox(store_init+0x2a) [0x41412a]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/vas/bin/opensmppbox(main+0x263) [0x40a443]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) 
[0x7f662c397830]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/vas/bin/opensmppbox(_start+0x29) [0x40b349]


2017-02-08 14:34:35 [1330] [0] INFO: Debug_lvl = 1, log_file = 
, log_lvl = 0
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: Connected to server at 
localhost.
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.

2017-02-08 14:34:35 [1330] [0] INFO: DLR using storage type: mysql
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() 
[0x442788]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f525dbc83d0]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() 
[0x4530ba]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/vas/bin/opensmppbox(store_init+0x2a) [0x41412a]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/vas/bin/opensmppbox(main+0x263) [0x40a443]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) 
[0x7f525d505830]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/vas/bin/opensmppbox(_start+0x29) [0x40b349]


Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor 
Spasoski

Sent: 08 February 2017 13:32
To: spameden <spame...@gmail.com>
Cc: users@kannel.org
Subject: RE: Re[4]: OpenSMPPBox Panic

This shouldn’t be the case. I tried internal as DLR and it panics, 
too.


Davor Spasoski
From: spameden [mailto:spame...@gmail.com]
Sent: 06 February 2017 13:46
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: Garry Macasieb <garry.macas...@gmail.com>; Rene Kluwen 
<rene.klu...@chimit.nl>; users@kannel.org

Subject: Re: Re[4]: OpenSMPPBox Panic

Can only guess it's something to do with store format. Maybe in the 
new version it's different that's why OpenSMPPBox panics.


Try deleting store file / spool and restarting opensmppbox.

2017-02-06 13:53 GMT+03:00 Davor Spasoski <davor.spaso...@onevip.mk>:

Hi,

I compiled the latest opensmppbox this morning with the hope for the 
PANIC after concatenated SMS.


Now I can’t even start it. I receive panic on startup. Same config 
file as ever.


/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox.conf
2017-02-06 11:35:38 [17516] [0] INFO: Debug_lvl = 1, log_file = 
, log_lvl = 0
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: Connected to server at 
localhost.
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.

2017-02-06 11:35:38 [17516] [0] INFO: DLR using storage type: mysql
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() 
[0x442788]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f7a4312e3d0]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() 
[0x4530ba]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a

RE: Re[4]: OpenSMPPBox Panic

[Davor Spasoski]

This is what I get when called with internal or with mysql storage. Can someone 
check please

vas@smpp-proxy:~/sources/gateway-1.5-svn-06-02-2017/addons/opensmppbox/gw$ 
/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox_simple.conf
2017-02-08 14:36:14 [1332] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-08 14:36:14 [1332] [0] INFO: DLR using storage type: internal
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f662ca5a3d0]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-08 14:36:14 [1332] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f662c397830]
2017-02-08 14:36:14 [1332] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]

2017-02-08 14:34:35 [1330] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-08 14:34:35 [1330] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-08 14:34:35 [1330] [0] INFO: DLR using storage type: mysql
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f525dbc83d0]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-08 14:34:35 [1330] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f525d505830]
2017-02-08 14:34:35 [1330] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]

Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski
Sent: 08 February 2017 13:32
To: spameden <spame...@gmail.com>
Cc: users@kannel.org
Subject: RE: Re[4]: OpenSMPPBox Panic

This shouldn’t be the case. I tried internal as DLR and it panics, too.

Davor Spasoski
From: spameden [mailto:spame...@gmail.com]
Sent: 06 February 2017 13:46
To: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Cc: Garry Macasieb <garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>; 
Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>; 
users@kannel.org<mailto:users@kannel.org>
Subject: Re: Re[4]: OpenSMPPBox Panic

Can only guess it's something to do with store format. Maybe in the new version 
it's different that's why OpenSMPPBox panics.

Try deleting store file / spool and restarting opensmppbox.

2017-02-06 13:53 GMT+03:00 Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>:
Hi,

I compiled the latest opensmppbox this morning with the hope for the PANIC 
after concatenated SMS.

Now I can’t even start it. I receive panic on startup. Same config file as ever.

/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox.conf
2017-02-06 11:35:38 [17516] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-06 11:35:38 [17516] [0] INFO: DLR using storage type: mysql
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f7a4312e3d0]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f7a42a6b830]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]
Segmentation fault (core dumped)

Davor Spasoski
VAS Cloud & ICT Development Team Leader / Online and VAS Development

M: +38975400608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia
From: Garry Macasieb 
[mailto:garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>]
Sent: 01 February 2017 05:47
To: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>

RE: Re[4]: OpenSMPPBox Panic

[Davor Spasoski]

This shouldn’t be the case. I tried internal as DLR and it panics, too.

Davor Spasoski
From: spameden [mailto:spame...@gmail.com]
Sent: 06 February 2017 13:46
To: Davor Spasoski <davor.spaso...@onevip.mk>
Cc: Garry Macasieb <garry.macas...@gmail.com>; Rene Kluwen 
<rene.klu...@chimit.nl>; users@kannel.org
Subject: Re: Re[4]: OpenSMPPBox Panic

Can only guess it's something to do with store format. Maybe in the new version 
it's different that's why OpenSMPPBox panics.

Try deleting store file / spool and restarting opensmppbox.

2017-02-06 13:53 GMT+03:00 Davor Spasoski 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>:
Hi,

I compiled the latest opensmppbox this morning with the hope for the PANIC 
after concatenated SMS.

Now I can’t even start it. I receive panic on startup. Same config file as ever.

/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox.conf
2017-02-06 11:35:38 [17516] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-06 11:35:38 [17516] [0] INFO: DLR using storage type: mysql
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f7a4312e3d0]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f7a42a6b830]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]
Segmentation fault (core dumped)

Davor Spasoski
VAS Cloud & ICT Development Team Leader / Online and VAS Development

M: +38975400608
e-mail: davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia
From: Garry Macasieb 
[mailto:garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>]
Sent: 01 February 2017 05:47
To: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: Davor Spasoski <davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>; 
users@kannel.org<mailto:users@kannel.org>
Subject: Re: Re[4]: OpenSMPPBox Panic

Hi Rene,

BIG THANKS. As tested, issue has been fixed.

Kind regards,

Garry

2017-01-31 19:57 GMT+08:00 Rene Kluwen 
<rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>:
I invite you to try again with a fresh svn update.
It should be fixed now.

== Rene

-- Origineel bericht --
Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Aan: "Rene Kluwen" <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: "Garry Macasieb" 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>; 
"users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
Verzonden: 28-1-2017 20:03:48
Onderwerp: Re: Re[2]: OpenSMPPBox Panic

Hi,

Just start opensmppbox normally. Connect a client that takes care how to split 
the SMS in two using UDH. I used kannel and let it split the message that I 
entered on smsbox's http interface.

BR,
Davor
On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:
 I promise to look into this one of these days and provide a patch.
 Meanwhile, could somebody send me steps to reproduce?

 == Rene

 -- Origineel bericht --
 Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
 Aan: "Garry Macasieb" 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>
 Cc: "rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>" 
<rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>; 
"users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
 Verzonden: 27-1-2017 17:16:39
 Onderwerp: Re: OpenSMPPBox Panic
 I second this. The panic happens on receiving the second part. I used kannel 
as a client and the concatenation mechanism used is udh based.
 On Jan 27, 2017, at 2:13 PM, Garry Macasieb 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>> wrote:

 Hi Rene / Users,

 Greetings!

 Wish to consult you about the PANIC i'm getting from Opensmppbox module 
whenever sending concatenated message:

 PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <= 
ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.

Re: Re[4]: OpenSMPPBox Panic

[spameden]

Can only guess it's something to do with store format. Maybe in the new
version it's different that's why OpenSMPPBox panics.

Try deleting store file / spool and restarting opensmppbox.

2017-02-06 13:53 GMT+03:00 Davor Spasoski <davor.spaso...@onevip.mk>:

> Hi,
>
>
>
> I compiled the latest opensmppbox this morning with the hope for the PANIC
> after concatenated SMS.
>
>
>
> Now I can’t even start it. I receive panic on startup. Same config file as
> ever.
>
>
>
> /vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox.conf
>
> 2017-02-06 11:35:38 [17516] [0] INFO: Debug_lvl = 1, log_file = ,
> log_lvl = 0
>
> 2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: Connected to server at
> localhost.
>
> 2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: server version
> 5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
>
> 2017-02-06 11:35:38 [17516] [0] INFO: DLR using storage type: mysql
>
> 2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
>
> 2017-02-06 11:35:38 [17516] [0] PANIC: 
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0)
> [0x7f7a4312e3d0]
>
> 2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
>
> 2017-02-06 11:35:38 [17516] [0] PANIC: 
> /vas/bin/opensmppbox(octstr_str_compare+0x20)
> [0x454a40]
>
> 2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a)
> [0x41412a]
>
> 2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(main+0x263)
> [0x40a443]
>
> 2017-02-06 11:35:38 [17516] [0] PANIC: 
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)
> [0x7f7a42a6b830]
>
> 2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(_start+0x29)
> [0x40b349]
>
> Segmentation fault (core dumped)
>
>
>
> *Davor Spasoski*
>
> VAS Cloud & ICT Development Team Leader / Online and VAS Development
>
>
>
> M: +38975400608
>
> e-mail: davor.spaso...@onevip.mk
>
>
>
> one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000
> Skopje | Macedonia
>
> *From:* Garry Macasieb [mailto:garry.macas...@gmail.com]
> *Sent:* 01 February 2017 05:47
> *To:* Rene Kluwen <rene.klu...@chimit.nl>
> *Cc:* Davor Spasoski <davor.spaso...@onevip.mk>; users@kannel.org
> *Subject:* Re: Re[4]: OpenSMPPBox Panic
>
>
>
> Hi Rene,
>
>
>
> BIG THANKS. As tested, issue has been fixed.
>
>
>
> Kind regards,
>
>
>
> Garry
>
>
>
> 2017-01-31 19:57 GMT+08:00 Rene Kluwen <rene.klu...@chimit.nl>:
>
> I invite you to try again with a fresh svn update.
> It should be fixed now.
>
> == Rene
>
> -- Origineel bericht --
> Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
> Aan: "Rene Kluwen" <rene.klu...@chimit.nl>
> Cc: "Garry Macasieb" <garry.macas...@gmail.com>; "users@kannel.org" <
> users@kannel.org>
> Verzonden: 28-1-2017 20:03:48
> Onderwerp: Re: Re[2]: OpenSMPPBox Panic
>
>
>
> Hi,
>
> Just start opensmppbox normally. Connect a client that takes care how to
> split the SMS in two using UDH. I used kannel and let it split the message
> that I entered on smsbox's http interface.
>
> BR,
> Davor
> On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:
>
>  I promise to look into this one of these days and provide a patch.
>  Meanwhile, could somebody send me steps to reproduce?
>
>  == Rene
>
>  -- Origineel bericht --
>  Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
>  Aan: "Garry Macasieb" <garry.macas...@gmail.com>
>  Cc: "rene.klu...@chimit.nl" <rene.klu...@chimit.nl>; "users@kannel.org" <
> users@kannel.org>
>  Verzonden: 27-1-2017 17:16:39
>  Onderwerp: Re: OpenSMPPBox Panic
>
>  I second this. The panic happens on receiving the second part. I used
> kannel as a client and the concatenation mechanism used is udh based.
>
>  On Jan 27, 2017, at 2:13 PM, Garry Macasieb <garry.macas...@gmail.com>
> wrote:
>
>  Hi Rene / Users,
>
>  Greetings!
>
>  Wish to consult you about the PANIC i'm getting from Opensmppbox module
> whenever sending concatenated message:
>
>  PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <=
> ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)
>
>  Do you have a work around for this or a working patch?
>
>  Thanks and looking forward to your response.
>
>  --
>  Garry
>
>  ===
> ===
>
>
>  
>
>  Disclaimer: one.Vip 

RE: Re[4]: OpenSMPPBox Panic

[Davor Spasoski]

Hi,

I compiled the latest opensmppbox this morning with the hope for the PANIC 
after concatenated SMS.

Now I can’t even start it. I receive panic on startup. Same config file as ever.

/vas/bin/opensmppbox -v 1 /vas/config/kannel/opensmppbox.conf
2017-02-06 11:35:38 [17516] [0] INFO: Debug_lvl = 1, log_file = , log_lvl 
= 0
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: Connected to server at localhost.
2017-02-06 11:35:38 [17516] [0] INFO: MYSQL: server version 
5.7.13-0ubuntu0.16.04.2, client version 5.7.17.
2017-02-06 11:35:38 [17516] [0] INFO: DLR using storage type: mysql
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x442788]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7f7a4312e3d0]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox() [0x4530ba]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/vas/bin/opensmppbox(octstr_str_compare+0x20) [0x454a40]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(store_init+0x2a) 
[0x41412a]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(main+0x263) 
[0x40a443]
2017-02-06 11:35:38 [17516] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f7a42a6b830]
2017-02-06 11:35:38 [17516] [0] PANIC: /vas/bin/opensmppbox(_start+0x29) 
[0x40b349]
Segmentation fault (core dumped)

Davor Spasoski
VAS Cloud & ICT Development Team Leader / Online and VAS Development

M: +38975400608
e-mail: davor.spaso...@onevip.mk

one.Vip DOO Skopje | Filip Vtori Makedonski 3, DC Soravia 8th floor | 1000 
Skopje | Macedonia
From: Garry Macasieb [mailto:garry.macas...@gmail.com]
Sent: 01 February 2017 05:47
To: Rene Kluwen <rene.klu...@chimit.nl>
Cc: Davor Spasoski <davor.spaso...@onevip.mk>; users@kannel.org
Subject: Re: Re[4]: OpenSMPPBox Panic

Hi Rene,

BIG THANKS. As tested, issue has been fixed.

Kind regards,

Garry

2017-01-31 19:57 GMT+08:00 Rene Kluwen 
<rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>:
I invite you to try again with a fresh svn update.
It should be fixed now.

== Rene

-- Origineel bericht --
Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
Aan: "Rene Kluwen" <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: "Garry Macasieb" 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>; 
"users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
Verzonden: 28-1-2017 20:03:48
Onderwerp: Re: Re[2]: OpenSMPPBox Panic

Hi,

Just start opensmppbox normally. Connect a client that takes care how to split 
the SMS in two using UDH. I used kannel and let it split the message that I 
entered on smsbox's http interface.

BR,
Davor
On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:
 I promise to look into this one of these days and provide a patch.
 Meanwhile, could somebody send me steps to reproduce?

 == Rene

 -- Origineel bericht --
 Van: "Davor Spasoski" 
<davor.spaso...@onevip.mk<mailto:davor.spaso...@onevip.mk>>
 Aan: "Garry Macasieb" 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>>
 Cc: "rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>" 
<rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>; 
"users@kannel.org<mailto:users@kannel.org>" 
<users@kannel.org<mailto:users@kannel.org>>
 Verzonden: 27-1-2017 17:16:39
 Onderwerp: Re: OpenSMPPBox Panic
 I second this. The panic happens on receiving the second part. I used kannel 
as a client and the concatenation mechanism used is udh based.
 On Jan 27, 2017, at 2:13 PM, Garry Macasieb 
<garry.macas...@gmail.com<mailto:garry.macas...@gmail.com>> wrote:

 Hi Rene / Users,

 Greetings!

 Wish to consult you about the PANIC i'm getting from Opensmppbox module 
whenever sending concatenated message:

 PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <= 
ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)

 Do you have a work around for this or a working patch?

 Thanks and looking forward to your response.

 --
 Garry

 
==


 

 Disclaimer: one.Vip DOO 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 DOO 
Skopje shall not be liable for the improper or incomplete transmission of the 
information contained in this communicatio

Re: Re[4]: OpenSMPPBox Panic

[Garry Macasieb]

Hi Rene,

BIG THANKS. As tested, issue has been fixed.

Kind regards,

Garry

2017-01-31 19:57 GMT+08:00 Rene Kluwen <rene.klu...@chimit.nl>:

> I invite you to try again with a fresh svn update.
> It should be fixed now.
>
> == Rene
>
> -- Origineel bericht --
> Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
> Aan: "Rene Kluwen" <rene.klu...@chimit.nl>
> Cc: "Garry Macasieb" <garry.macas...@gmail.com>; "users@kannel.org" <
> users@kannel.org>
> Verzonden: 28-1-2017 20:03:48
> Onderwerp: Re: Re[2]: OpenSMPPBox Panic
>
>
> Hi,
>>
>> Just start opensmppbox normally. Connect a client that takes care how to
>> split the SMS in two using UDH. I used kannel and let it split the message
>> that I entered on smsbox's http interface.
>>
>> BR,
>> Davor
>> On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:
>>
>>  I promise to look into this one of these days and provide a patch.
>>>  Meanwhile, could somebody send me steps to reproduce?
>>>
>>>  == Rene
>>>
>>>  -- Origineel bericht --
>>>  Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
>>>  Aan: "Garry Macasieb" <garry.macas...@gmail.com>
>>>  Cc: "rene.klu...@chimit.nl" <rene.klu...@chimit.nl>; "users@kannel.org"
>>> <users@kannel.org>
>>>  Verzonden: 27-1-2017 17:16:39
>>>  Onderwerp: Re: OpenSMPPBox Panic
>>>
>>>  I second this. The panic happens on receiving the second part. I used
>>>> kannel as a client and the concatenation mechanism used is udh based.
>>>>
>>>>  On Jan 27, 2017, at 2:13 PM, Garry Macasieb <garry.macas...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>  Hi Rene / Users,
>>>>>
>>>>>  Greetings!
>>>>>
>>>>>  Wish to consult you about the PANIC i'm getting from Opensmppbox
>>>>> module whenever sending concatenated message:
>>>>>
>>>>>  PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len +
>>>>> 1 <= ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_dest
>>>>> roy.)
>>>>>
>>>>>  Do you have a work around for this or a working patch?
>>>>>
>>>>>  Thanks and looking forward to your response.
>>>>>
>>>>>  --
>>>>>  Garry
>>>>>
>>>>>  ===
>>>>> ===
>>>>>
>>>>>
>>>>>
>>>>  
>>>>
>>>>  Disclaimer: one.Vip DOO 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 DOO 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[4]: OpenSMPPBox Panic

[Rene Kluwen]

I invite you to try again with a fresh svn update.
It should be fixed now.

== Rene

-- Origineel bericht --
Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
Aan: "Rene Kluwen" <rene.klu...@chimit.nl>
Cc: "Garry Macasieb" <garry.macas...@gmail.com>; "users@kannel.org" 
<users@kannel.org>

Verzonden: 28-1-2017 20:03:48
Onderwerp: Re: Re[2]: OpenSMPPBox Panic


Hi,

Just start opensmppbox normally. Connect a client that takes care how 
to split the SMS in two using UDH. I used kannel and let it split the 
message that I entered on smsbox's http interface.


BR,
Davor
On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:


 I promise to look into this one of these days and provide a patch.
 Meanwhile, could somebody send me steps to reproduce?

 == Rene

 -- Origineel bericht --
 Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
 Aan: "Garry Macasieb" <garry.macas...@gmail.com>
 Cc: "rene.klu...@chimit.nl" <rene.klu...@chimit.nl>; 
"users@kannel.org" <users@kannel.org>

 Verzonden: 27-1-2017 17:16:39
 Onderwerp: Re: OpenSMPPBox Panic

 I second this. The panic happens on receiving the second part. I 
used kannel as a client and the concatenation mechanism used is udh 
based.


 On Jan 27, 2017, at 2:13 PM, Garry Macasieb 
<garry.macas...@gmail.com> wrote:


 Hi Rene / Users,

 Greetings!

 Wish to consult you about the PANIC i'm getting from Opensmppbox 
module whenever sending concatenated message:


 PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len 
+ 1 <= ostr->size' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)


 Do you have a work around for this or a working patch?

 Thanks and looking forward to your response.

 --
 Garry

 
==





 

 Disclaimer: one.Vip DOO 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 DOO 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 DOO 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 DOO 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: Re[2]: OpenSMPPBox Panic

[Davor Spasoski]

Hi,

Just start opensmppbox normally. Connect a client that takes care how to split 
the SMS in two using UDH. I used kannel and let it split the message that I 
entered on smsbox's http interface.

BR,
Davor
On Jan 28, 2017, at 1:15 PM, Rene Kluwen wrote:

> I promise to look into this one of these days and provide a patch.
> Meanwhile, could somebody send me steps to reproduce?
>
> == Rene
>
> -- Origineel bericht --
> Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
> Aan: "Garry Macasieb" <garry.macas...@gmail.com>
> Cc: "rene.klu...@chimit.nl" <rene.klu...@chimit.nl>; "users@kannel.org" 
> <users@kannel.org>
> Verzonden: 27-1-2017 17:16:39
> Onderwerp: Re: OpenSMPPBox Panic
>
>> I second this. The panic happens on receiving the second part. I used kannel 
>> as a client and the concatenation mechanism used is udh based.
>>
>>> On Jan 27, 2017, at 2:13 PM, Garry Macasieb <garry.macas...@gmail.com> 
>>> wrote:
>>>
>>> Hi Rene / Users,
>>>
>>> Greetings!
>>>
>>> Wish to consult you about the PANIC i'm getting from Opensmppbox module 
>>> whenever sending concatenated message:
>>>
>>> PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <= 
>>> ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)
>>>
>>> Do you have a work around for this or a working patch?
>>>
>>> Thanks and looking forward to your response.
>>>
>>> --
>>> Garry
>>>
>>> ==
>>>
>>>
>>
>> 
>>
>> Disclaimer: one.Vip DOO 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 DOO 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 DOO 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 DOO 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[2]: OpenSMPPBox Panic

[Rene Kluwen]

I promise to look into this one of these days and provide a patch.
Meanwhile, could somebody send me steps to reproduce?

== Rene

-- Origineel bericht --
Van: "Davor Spasoski" <davor.spaso...@onevip.mk>
Aan: "Garry Macasieb" <garry.macas...@gmail.com>
Cc: "rene.klu...@chimit.nl" <rene.klu...@chimit.nl>; "users@kannel.org" 
<users@kannel.org>

Verzonden: 27-1-2017 17:16:39
Onderwerp: Re: OpenSMPPBox Panic

I second this. The panic happens on receiving the second part. I used 
kannel as a client and the concatenation mechanism used is udh based.


 On Jan 27, 2017, at 2:13 PM, Garry Macasieb 
<garry.macas...@gmail.com> wrote:


 Hi Rene / Users,

 Greetings!

 Wish to consult you about the PANIC i'm getting from Opensmppbox 
module whenever sending concatenated message:


 PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 
1 <= ostr->size' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)


 Do you have a work around for this or a working patch?

 Thanks and looking forward to your response.

 --
 Garry

 
==







Disclaimer: one.Vip DOO 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 DOO 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: OpenSMPPBox Panic

[Davor Spasoski]

I second this. The panic happens on receiving the second part. I used kannel as 
a client and the concatenation mechanism used is udh based.

> On Jan 27, 2017, at 2:13 PM, Garry Macasieb <garry.macas...@gmail.com> wrote:
>
> Hi Rene / Users,
>
> Greetings!
>
> Wish to consult you about the PANIC i'm getting from Opensmppbox module 
> whenever sending concatenated message:
>
> PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <= 
> ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)
>
> Do you have a work around for this or a working patch?
>
> Thanks and looking forward to your response.
>
> --
> Garry
>
> ==
>
>



Disclaimer: one.Vip DOO 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 DOO 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!

Напомена: оне.Вип ДОО Скопје
Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да биде 
заштитена со правни привилегии. Доколку не сте лицето на кое таа му е наменета 
пораката, не треба да ја копирате, дистрибуирате или да ја откривате нејзината 
содржина, туку веднаш да ја препратите до испраќачот и да ја избришете 
оригиналната порака и сите нејзини копии од Вашиот компјутерски систем. Секое 
неовластено користење на оваа порака во целост или делови од истата е строго 
забрането. Ве молиме да забележите дека електронските пораки се подложни на 
промени. оне.Вип ДОО Скопје не презема одговорност за несоодветно или нецелосно 
пренесување на информациите содржани во оваа комуникација, ниту пак за било 
какво задоцнување на приемот или оштетувања на вашиот систем.
Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
природата!

OpenSMPPBox Panic

[Garry Macasieb]

Hi Rene / Users,

Greetings!

Wish to consult you about the PANIC i'm getting from Opensmppbox module
whenever sending concatenated message:

PANIC: gwlib/octstr.c:2562: seems_valid_real: Assertion `ostr->len + 1 <=
ostr->size' failed. (Called from gwlib/octstr.c:325:octstr_destroy.)

Do you have a work around for this or a working patch?

Thanks and looking forward to your response.

-- 
Garry

==

Re: Opensmppbox and long SMS

[Rene Kluwen]

Yes, it is.

== Rene

-- Origineel bericht --
Van: "info.ubichip" <info.ubic...@free.fr>
Aan: "'users'" <users@kannel.org>
Verzonden: 12-12-2016 15:34:52
Onderwerp: Opensmppbox and long SMS


Hello,

Does anyone know if opensmppbox is able to send/receive long sms ?

Thanks in advance for your help

Opensmppbox and long SMS

[info.ubichip]

Hello,

Does anyone know if opensmppbox is able to send/receive long sms ?

Thanks in advance for your help

Re: Re[2]: Opensmppbox booting fail on Debian jessie

[Lam Nguyen Tuong]

Thanks Rene but it is still not work.


If add: shortcode = "123" i got this error:


2016-12-11 22:09:12 [11449] [0] WARNING: DLR: using default 'internal' for 
storage type.
2016-12-11 22:09:12 [11449] [0] INFO: DLR using storage type: internal
2016-12-11 22:09:12 [11449] [0] INFO: Starting to log to file 
/var/log/kannel/smppbox.log level 0
2016-12-11 22:09:12 [11449] [0] INFO: Added logfile 
`/var/log/kannel/smppbox.log' with level `0'.
2016-12-11 22:09:12 [11449] [0] DEBUG: Adding smsc routing to id  for 
sender no <123> and smsbox id 
*** Error in `opensmppbox': munmap_chunk(): invalid pointer: 0x02005180 
***

If add: shortcode = "123;456" i got another output:

2016-12-11 22:08:56 [11445] [0] WARNING: DLR: using default 'internal' for 
storage type.
2016-12-11 22:08:56 [11445] [0] INFO: DLR using storage type: internal
2016-12-11 22:08:56 [11445] [0] INFO: Starting to log to file 
/var/log/kannel/smppbox.log level 0
2016-12-11 22:08:56 [11445] [0] INFO: Added logfile 
`/var/log/kannel/smppbox.log' with level `0'.
2016-12-11 22:08:56 [11445] [0] DEBUG: Adding smsc routing to id  for 
sender no <123> and smsbox id 
2016-12-11 22:08:56 [11445] [0] DEBUG: Adding smsc routing to id  for 
sender no <456> and smsbox id 
*** Error in `opensmppbox': double free or corruption (out): 0x01a071d0 
***

Lamnt.



From: Rene Kluwen <rene.klu...@chimit.nl>
Sent: Sunday, December 11, 2016 9:59:08 PM
To: Lam Nguyen Tuong
Cc: users
Subject: Re[2]: Opensmppbox booting fail on Debian jessie

You are missing the "shortcode" configuration parameter in your group = 
smsc-route.
I will try to come up with a patch, one of these days. Because indeed 
opensmppbox shouldn't crash on this.

== Rene

-- Origineel bericht --
Van: "Lam Nguyen Tuong" <lam...@outlook.com<mailto:lam...@outlook.com>>
Aan: "Rene Kluwen" <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Cc: "users" <users@kannel.org<mailto:users@kannel.org>>
Verzonden: 9-12-2016 3:24:39
Onderwerp: Re: Opensmppbox booting fail on Debian jessie


Hi Rene,

It was running configuration.



group = core

group = opensmppbox
opensmppbox-id = smppbox1
opensmppbox-port = 50217
bearerbox-host = 127.0.0.1
bearerbox-port = 13005
our-system-id = testsmpp
smpp-logins = /etc/kannel/smpplogins.txt
use-systemid-as-smsboxid = 1
log-file = /var/log/kannel/smppbox.log
log-level = 0

group = smsc-route
smsc-id = smsc_tb
smsbox-id = myboxID


Lamnt.





From: Rene Kluwen <rene.klu...@chimit.nl<mailto:rene.klu...@chimit.nl>>
Sent: Thursday, December 8, 2016 8:11:21 PM
To: Lam Nguyen Tuong
Cc: users
Subject: Re: Opensmppbox booting fail on Debian jessie

What's your config?

-- Origineel bericht --
Van: "Lam Nguyen Tuong" <lam...@outlook.com<mailto:lam...@outlook.com>>
Aan:
Cc: "users" <users@kannel.org<mailto:users@kannel.org>>
Verzonden: 8-12-2016 5:22:13
Onderwerp: Opensmppbox booting fail on Debian jessie


Hello,

I has complied latest kannel snapshot on Jessie 8.4 with opensmppbox but unable 
to boot it up and get this PANIC log. Appreciate if anyone can help to solve. 
Thank you.


2016-12-08 02:07:21 [14333] [0] PANIC: gwlib/octstr.c:2570: seems_valid_real: 
Assertion `ostr->data[ostr->len] == '\0'' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_backtrace+0xae) [0x45262e]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_panic+0x15f) [0x45279f]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() [0x459e48]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(octstr_destroy+0x1d) [0x45a50d]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox(main+0x7ec) 
[0x40c19c]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fa91a5f2b45]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() [0x40c9cd]


Lamnt.

Re[2]: Opensmppbox booting fail on Debian jessie

[Rene Kluwen]

You are missing the "shortcode" configuration parameter in your group = 
smsc-route.
I will try to come up with a patch, one of these days. Because indeed 
opensmppbox shouldn't crash on this.


== Rene

-- Origineel bericht --
Van: "Lam Nguyen Tuong" <lam...@outlook.com>
Aan: "Rene Kluwen" <rene.klu...@chimit.nl>
Cc: "users" <users@kannel.org>
Verzonden: 9-12-2016 3:24:39
Onderwerp: Re: Opensmppbox booting fail on Debian jessie


Hi Rene,

It was running configuration.






group = core

group = opensmppbox
opensmppbox-id = smppbox1
opensmppbox-port = 50217
bearerbox-host = 127.0.0.1
bearerbox-port = 13005
our-system-id = testsmpp
smpp-logins = /etc/kannel/smpplogins.txt
use-systemid-as-smsboxid = 1
log-file = /var/log/kannel/smppbox.log
log-level = 0

group = smsc-route
smsc-id = smsc_tb
smsbox-id = myboxID


Lamnt.





From: Rene Kluwen <rene.klu...@chimit.nl>
Sent: Thursday, December 8, 2016 8:11:21 PM
To: Lam Nguyen Tuong
Cc: users
Subject: Re: Opensmppbox booting fail on Debian jessie

What's your config?

-- Origineel bericht --
Van: "Lam Nguyen Tuong" <lam...@outlook.com>
Aan:
Cc: "users" <users@kannel.org>
Verzonden: 8-12-2016 5:22:13
Onderwerp: Opensmppbox booting fail on Debian jessie


Hello,

I has complied latest kannel snapshot on Jessie 8.4 with opensmppbox 
but unable to boot it up and get this PANIC log. Appreciate if anyone 
can help to solve. Thank you.





2016-12-08 02:07:21 [14333] [0] PANIC: gwlib/octstr.c:2570: 
seems_valid_real: Assertion `ostr->data[ostr->len] == '\0'' failed. 
(Called from gwlib/octstr.c:325:octstr_destroy.)
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_backtrace+0xae) [0x45262e]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_panic+0x15f) [0x45279f]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() 
[0x459e48]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(octstr_destroy+0x1d) [0x45a50d]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(main+0x7ec) [0x40c19c]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) 
[0x7fa91a5f2b45]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() 
[0x40c9cd]




Lamnt.

Re: Opensmppbox booting fail on Debian jessie

[Lam Nguyen Tuong]

Hi Rene,

It was running configuration.



group = core

group = opensmppbox
opensmppbox-id = smppbox1
opensmppbox-port = 50217
bearerbox-host = 127.0.0.1
bearerbox-port = 13005
our-system-id = testsmpp
smpp-logins = /etc/kannel/smpplogins.txt
use-systemid-as-smsboxid = 1
log-file = /var/log/kannel/smppbox.log
log-level = 0

group = smsc-route
smsc-id = smsc_tb
smsbox-id = myboxID


Lamnt.





From: Rene Kluwen <rene.klu...@chimit.nl>
Sent: Thursday, December 8, 2016 8:11:21 PM
To: Lam Nguyen Tuong
Cc: users
Subject: Re: Opensmppbox booting fail on Debian jessie

What's your config?

-- Origineel bericht --
Van: "Lam Nguyen Tuong" <lam...@outlook.com<mailto:lam...@outlook.com>>
Aan:
Cc: "users" <users@kannel.org<mailto:users@kannel.org>>
Verzonden: 8-12-2016 5:22:13
Onderwerp: Opensmppbox booting fail on Debian jessie


Hello,

I has complied latest kannel snapshot on Jessie 8.4 with opensmppbox but unable 
to boot it up and get this PANIC log. Appreciate if anyone can help to solve. 
Thank you.


2016-12-08 02:07:21 [14333] [0] PANIC: gwlib/octstr.c:2570: seems_valid_real: 
Assertion `ostr->data[ostr->len] == '\0'' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_backtrace+0xae) [0x45262e]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_panic+0x15f) [0x45279f]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() [0x459e48]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(octstr_destroy+0x1d) [0x45a50d]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox(main+0x7ec) 
[0x40c19c]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fa91a5f2b45]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() [0x40c9cd]


Lamnt.

Re: Opensmppbox booting fail on Debian jessie

[Rene Kluwen]

What's your config?

-- Origineel bericht --
Van: "Lam Nguyen Tuong" <lam...@outlook.com>
Aan:
Cc: "users" <users@kannel.org>
Verzonden: 8-12-2016 5:22:13
Onderwerp: Opensmppbox booting fail on Debian jessie


Hello,

I has complied latest kannel snapshot on Jessie 8.4 with opensmppbox 
but unable to boot it up and get this PANIC log. Appreciate if anyone 
can help to solve. Thank you.





2016-12-08 02:07:21 [14333] [0] PANIC: gwlib/octstr.c:2570: 
seems_valid_real: Assertion `ostr->data[ostr->len] == '\0'' failed. 
(Called from gwlib/octstr.c:325:octstr_destroy.)
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_backtrace+0xae) [0x45262e]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_panic+0x15f) [0x45279f]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() 
[0x459e48]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(octstr_destroy+0x1d) [0x45a50d]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(main+0x7ec) [0x40c19c]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) 
[0x7fa91a5f2b45]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() 
[0x40c9cd]




Lamnt.

Opensmppbox booting fail on Debian jessie

[Lam Nguyen Tuong]

Hello,

I has complied latest kannel snapshot on Jessie 8.4 with opensmppbox but unable 
to boot it up and get this PANIC log. Appreciate if anyone can help to solve. 
Thank you.


2016-12-08 02:07:21 [14333] [0] PANIC: gwlib/octstr.c:2570: seems_valid_real: 
Assertion `ostr->data[ostr->len] == '\0'' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_backtrace+0xae) [0x45262e]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(gw_panic+0x15f) [0x45279f]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() [0x459e48]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/usr/local/sbin/opensmppbox(octstr_destroy+0x1d) [0x45a50d]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox(main+0x7ec) 
[0x40c19c]
2016-12-08 02:07:21 [14333] [0] PANIC: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fa91a5f2b45]
2016-12-08 02:07:21 [14333] [0] PANIC: /usr/local/sbin/opensmppbox() [0x40c9cd]


Lamnt.

Re: SMS via Opensmppbox to connected client

[Amritesh Rachelwar]

Yes its possible, google helped me..:-)

Amritesh

On Thu, Dec 1, 2016 at 3:37 AM, Amritesh Rachelwar <amriteshs...@gmail.com>
wrote:

> Hi
>
> Is it possible to send SMS via OpenSMPPbox to Connected SMPP client
>
> Like
>
> Bearerbox->SMSbox->OpenSMPPbox-> SMPP Client
>
> Or by using any other combination.
>
> Please help.
>
> Amritesh
>

SMS via Opensmppbox to connected client

[Amritesh Rachelwar]

Hi

Is it possible to send SMS via OpenSMPPbox to Connected SMPP client

Like

Bearerbox->SMSbox->OpenSMPPbox-> SMPP Client

Or by using any other combination.

Please help.

Amritesh

Opensmppbox Concatenation issue

[Salih Al-Hassan]

Hi guys,

I have an issue with sending MT concatenated message on opensmppbox.
Opensmppbox crashes whenever i send a concatenated message.

Please help.

Salih

OpenSMPPBOX Panic

[Arif Noor]

Sorry, wrong subject for the previous email.

From: users [mailto:users-boun...@kannel.org] On Behalf Of Arif Noor
Sent: Saturday, February 27, 2016 3:23 AM
To: users@kannel.org
Subject: FW: Kannel support only GSM Commands?

Greetings,

I’m having issues with opensmppbox where sending concatenated MT will cause it 
to crash, giving error as below. Is this a bug? And how can I mend this.


2016-02-27 01:32:24 [6013] [16] PANIC: gwlib/octstr.c:2565: seems_valid_real: 
Assertion `ostr->data != NULL' failed. (Called from 
gwlib/octstr.c:325:octstr_destroy.)
2016-02-27 01:32:24 [6013] [16] PANIC: 
/usr/local/kannel/sbin/opensmppbox(gw_backtrace+0xae) [0x45c67e]
2016-02-27 01:32:24 [6013] [16] PANIC: 
/usr/local/kannel/sbin/opensmppbox(gw_panic+0x159) [0x45c7e9]
2016-02-27 01:32:24 [6013] [16] PANIC: /usr/local/kannel/sbin/opensmppbox() 
[0x45e670]
2016-02-27 01:32:24 [6013] [16] PANIC: 
/usr/local/kannel/sbin/opensmppbox(octstr_destroy+0x1d) [0x46079d]
2016-02-27 01:32:24 [6013] [16] PANIC: 
/usr/local/kannel/sbin/opensmppbox(msg_destroy+0x26) [0x416a26]
2016-02-27 01:32:24 [6013] [16] PANIC: 
/usr/local/kannel/sbin/opensmppbox(gwlist_destroy+0x42) [0x45b7c2]
2016-02-27 01:32:24 [6013] [16] PANIC: /usr/local/kannel/sbin/opensmppbox() 
[0x40ff58]
2016-02-27 01:32:24 [6013] [16] PANIC: /usr/local/kannel/sbin/opensmppbox() 
[0x4531e9]
2016-02-27 01:32:24 [6013] [16] PANIC: /lib64/libpthread.so.0(+0x7aa1) 
[0x7f85a9b03aa1]
2016-02-27 01:32:24 [6013] [16] PANIC: /lib64/libc.so.6(clone+0x6d) 
[0x7f85a920193d]


Using opensmppbox below :

2016-02-27 01:22:39 [6013] [0] DEBUG: Kannel opensmppbox version svn-r84 gwlib 
version `svn-r5154M'.
Build `Feb  8 2016 12:04:24', compiler `4.4.7 20120313 (Red Hat 4.4.7-16)'.
System Linux, release 2.6.32-573.18.1.el6.x86_64, version #1 SMP Tue Feb 9 
22:46:17 UTC 2016, machine x86_64.
Hostname localhost, IP 127.0.0.1.
Libxml version 2.6.27.
Using OpenSSL 1.0.1e-fips 11 Feb 2013.
Compiled with MySQL 5.1.73, using MySQL 5.1.73.
Using native malloc.

Thanks in advance.

Re: an opensmppbox question

[Alexander Grechishkin]

hello, thanx for quick reply.

I'm almost done, my opensmppbox receives SMPP-connections from remote
clients and successfully sends these messages via generic http gate smsc.
But I've still got problem with sending DLRs back to opensmppbox.
I accept (got "Sent" in response) HTTP-request from http smsc like
http://127.0.0.1:13033/dlr?username=login=secret=SMS-INFO=N_mask=0=12aee578-ba3e-4b7b-9748-ac1f3c5ce5b4=.
..

but finally have these errors in kannel.log
2016-01-17 21:13:11 [6274] [7] DEBUG: HTTP[generichttpsmsc]: Received an
HTTP request
2016-01-17 21:13:11 [6274] [7] DEBUG: HTTP[generichttpsmsc]: Constructing
new SMS
2016-01-17 21:13:11 [6274] [7] WARNING: Could not route message to smsbox
id , smsbox is gone!

and sometimes this error
2016-01-17 20:13:11 [6274] [7] WARNING: smsbox_list empty

could you help me to understand what is wrong in my kannel configuration?


- kannel.conf
group = core
admin-port = 13000
admin-password = bazbar
status-password = foo
log-level = 0
log-file = "/tmp/kannel/kannel.log"
access-log = "/tmp/kannel/kannel_access.log"
store-file = "/tmp/kannel/kannel_store.log"
admin-allow-ip = "*.*.*.*"
box-allow-ip = "*.*.*.*"
smsbox-port = 13003
dlr-storage = internal

group = smsbox
smsbox-id = mainsmsbox
bearerbox-host = 127.0.0.1
bearerbox-port = 13003
global-sender = SMS-INFO
log-level = 0
log-file = "/tmp/kannel/smsbox.log"
access-log = "/tmp/kannel/smsbox_access.log"

group = smsbox-route
smsbox-id = smppbx
smsc-id = generichttpsmsc

group = smsc
smsc-id = generichttpsmsc
smsc = http
system-type=generic
port = 13033
smsc-username = "login"
smsc-password = "secret"
connect-allow-ip = "*.*.*.*"
send-url = "
http://httpsmsc/sendsms.php?d=%d=%R=%F=%I=%c=%C=%O=%u=%n=%p=%P=%b
"
status-success-regex = "ok"
generic-status-sent = 200
generic-status-error = 404


- opensmppbox.conf
group = core
dlr-storage = internal

group = opensmppbox
bearerbox-host = 127.0.0.1
bearerbox-port = 13003
opensmppbox-id = smppbx
opensmppbox-port = 2775
log-file = /tmp/kannel/opensmppbox.log
log-level = 0
our-system-id = smscToken
route-to-smsc = generichttpsmsc
smpp-logins = /home/user/kannel/opensmppbox.logins




On Wed, Jan 13, 2016 at 4:32 PM, Lee Vidor <l...@nozara.com> wrote:

> For this you could set up your own HTTP SMSC API that you would send the
> SMS to.
> You would configure the port value on your http smsc gateway in
> kannel.conf and send delivery reports from your HTTP SMSC to that port when
> updates are received from your operator.
>
> For example you would send the following URL:
>
> http://*opensmppboxIP*:*portnumber*?dlr-mid=*messageid*=1=
> *destina**tion*
> <http://opensmppboxip:portnumber?dlr-mid=messageid=1=destination>
>
> dlr-mask value would vary depending on status.
>
>
>
> Regards,
>
> Lee
>
> On 13 Jan 2016, at 13:09, Alexander Grechishkin <
> alex.grechish...@gmail.com> wrote:
>
> Hello,
>
>
> I have a small question about opensmppbox configuration and I will
> appreciate any help.
>
> I want to use opensmppbox as a gateway for my customers, so they connect
> to me via SMPP protocol.
> But I want to use http as an smsc (customers's smppclient -> opensmppbox
> -> kannel -> smsc=http -> operator HTTP-gateway)
>
> How can I make a delivery reporting in this case?
> Is there any way opensmppbox can send DELIVER_SM back to client on any
> http request?
> Or what would be the best way to inform opensmppbox about new delivery
> reports so it can send them back to a client?
>
>
> sincerely, alexander
>
>
>


-- 

​sincerely alexander

an opensmppbox question

[Alexander Grechishkin]

Hello,


I have a small question about opensmppbox configuration and I will
appreciate any help.

I want to use opensmppbox as a gateway for my customers, so they connect to
me via SMPP protocol.
But I want to use http as an smsc (customers's smppclient -> opensmppbox ->
kannel -> smsc=http -> operator HTTP-gateway)

How can I make a delivery reporting in this case?
Is there any way opensmppbox can send DELIVER_SM back to client on any http
request?
Or what would be the best way to inform opensmppbox about new delivery
reports so it can send them back to a client?


sincerely, alexander

Regarding; OpenSMPPBox

[Ammar Ali]

*Hello All,*


I have created a OpenSMPPBox for my clients, but I am facing a serious
issue.

When my clients send Flash SMS with some special characters like @, $ etc,
then that type of message shown in cell phone very well. But they send same
message content in normal sms then blank shown in cell phones.


Please give me some suggestions for this.




*Thanks,*

*Ammar Ali *
*Pune (M.H.)*