date:20230424

Re: MO Routing on the fly

2023-04-24 Thread akamat sarat

Ruben,

Thank you so much. I don't know how I managed to fail to notice that smsbox
was not up. so stupid.
You are the man.
Everybody else who was kind enough to reply with helpful suggestions, I
thank you as well your help is appreciated.






On Mon, Apr 24, 2023 at 12:55 PM rm mobbis.am  wrote:

> Hi Akamat,
>
> Your Warning is not related to sms routing.
>
> Please check if your smsbox is up.
>
>
>
> Core config example:
>
>
>
> # -- CORE --core.conf
>
>
>
> group=core
>
> admin-port = 19000
>
> smsbox-port = 19005
>
> admin-password = *
>
> status-password = *
>
> admin-allow-ip = "
>
> admin-deny-ip = "*.*.*.*"
>
> log-file = "/var/log/kanpsms/bearerbox.log"
>
> log-level = 3
>
> access-log = "/var/log/kanpsms/SentReceivedSMS.log"
>
> access-log-clean = true
>
> access-log-format = "%t %l [SMSC:%i] [SVC:%n] [ACT:%A] [BINF:%B] [FID:%F]
> [META:%D] [from:%p] [to:%P] [flags:%m:%c:%M:%C:%d] [msg:%L:%b] [udh:%U:%u]"
>
> box-allow-ip = "127.0.0.1;*.*.*.*"
>
> sms-combine-concatenated-mo=true
>
> # --
>
> store-type = file
>
> store-location = /home/KANNEL_PSMS/STORE
>
> dlr-storage = spool
>
> dlr-spool = /home/KANNEL_PSMS/DLR
>
>
>
>
>
> # -- OUTBOUND-SMS-CENTERS -
>
> include="/home/KANNEL_PSMS/smsc/smsc1.conf"
>
> include = "/home/KANNEL_PSMS/smsc/smsc2.conf"
>
> include = "/home/KANNEL_PSMS/smsc/smsc3.conf"
>
>
>
> #- SMSBOX---
>
> include = "/home/KANNEL_PSMS/configs/smsbox.conf"
>
>
>
> #SENDSMS USERS--
>
> include = "/home/KANNEL_PSMS/users/SendSMSusers.conf"
>
>
>
> # -- SMS-SERVICE --
>
> include = "/home/KANNEL_PSMS/services/services.conf"
>
>
>
>
>
> *Other configs examples you can find in previous email*
>
>
>
> *Steps to RUN KANNEL*
>
>
>
> *Step1: /usr/local/kanpsms/bearerbox --parachute
> /home/KANNEL_PSMS/configs/core.conf &*
>
>
>
> *Step2: usr/local/kanpsms/smsbox --parachute
> /home/KANNEL_PSMS/configs/core.conf *
>
>
>
> *Best regards,*
>
> *Ruben Melikyan*
>
>
>
>
>
> *From:* akamat sarat 
> *Sent:* 24.04.2023 13:31
> *To:* rm mobbis.am 
> *Cc:* Tolga Ulas ; users@kannel.org
> *Subject:* Re: MO Routing on the fly
>
>
>
> Dear All,
>
> Thank you for your advice. I have tried all of your suggestions but
> cant get it to work like you say it should.
> Without an smsbox-route, when ever an MO comes in I still get the
> "WARNING: smsbox_list empty"  warning.
> Below my complete setup is below, what am I doing wrong?
>
> group = core
>
> admin-port = 13000
>
> admin-password = ADMINPW
>
> status-password = STATUSPW
>
> smsbox-port = 13032
>
> log-file = "/var/log/kannel/kannel.log"
>
> log-level = 5
>
> box-allow-ip = "*.*.*.*"
>
> access-log = "/var/log/kannel/access.log"
>
> store-type = spool
>
> store-location = /var/spool/kannel/store
>
> smsbox-max-pending = 100
>
> dlr-storage = "internal"
>
> sms-resend-freq = 1200
>
> sms-resend-retry = 1
>
>
>
>
>
>
>
> group = smsbox
>
> bearerbox-host = localhost
>
> bearerbox-port = 13032
>
> sendsms-port = 13033
>
> log-file = "/var/log/kannel/nosmscidsmsbox.log"
>
> log-level = 3
>
> reply-emptymessage = ""
>
> http-request-retry = 2
>
> http-queue-delay = 15
>
> sms-length = 500
>
> mo-recode=yes
>
>
>
>
>
>
>
> group = sms-service
>
> keyword = default
>
> catch-all=true
>
> omit-empty = true
>
> assume-plain-text = yes
>
> concatenation = true
>
> max-messages = 0
>
> get-url = "my_gt_uri"
>
>
>
>
>
> group = smsc
>
> smsc = smpp
>
> smsc-admin-id = SMSC
>
> smsc-id = SMSC
>
> allowed-smsc-id = SMSC
>
> preferred-smsc-id = SMSC
>
> host = host
>
> port = port
>
> transceiver-mode = 1
>
> smsc-username = USERNAME
>
> smsc-password = PASSWORD
>
> dest-addr-ton = 0
>
> dest-addr-npi = 0
>
> source-addr-ton = 0
>
> source-addr-npi = 0
>
> throughput = 30
>
> enquire-link-interval = 30
>
> log-file = /var/log/kannel/SMSC.log
>
> log-level = 0
>
> system-type = ""
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Mon, Apr 24, 2023 at 10:02 AM rm mobbis.am  wrote:
>
> Hi Akamat. Sorry for late response.
>
>
>
> The point is that you organize routing outside kannel and inside your
> script or your MO sms handler web application side. This gives you
> possibility to implement sms-service with any difficulty.
>
>
>
> *Below are essential configs examples:*
>
>
>
> # -- SMSBOX GROUP --
>
> group = smsbox
>
> bearerbox-host = localhost
>
> bearerbox-port = 19005
>
> sendsms-port = 19555
>
> log-file = "/var/log/kanpsms/smsbox.log"
>
> log-level = 3
>
> access-log = "/var/log/kanpsms/smsbox-sms-access.log"
>
> sendsms-chars = "0123456789 +#._"
>
> reply-couldnotfetch = // If set, replaces the SMS message sent back to
> user when Kannel could not fetch content //
>
> reply-couldnotrepresent = // If set, replaces the SMS message sent back
> when Kannel could not represent the result as a SMS message//
>
> reply-requestfailed = // If set, replaces the SMS message sent back when
> Kannel could not contact http service.//
>
> reply-emptymessage = ""
>
> http-request-retry = 2
>
> h

Re: MO Routing on the fly

2023-04-24 Thread Kyriacos/Netsmart


Hi,

I think you are missing the smsbox-route route.

group = smsbox-route
smsbox-id = mySMSBox
smsc-id = smpp [list any other SMSC connections here]


On 24/04/2023 12:31 pm, akamat sarat wrote:

Dear All,

Thank you for your advice. I have tried all of your suggestions but 
cant get it to work like you say it should.
Without an smsbox-route, when ever an MO comes in I still get the 
"WARNING: smsbox_list empty"  warning.

Below my complete setup is below, what am I doing wrong?


group = core
admin-port = 13000
admin-password = ADMINPW
status-password = STATUSPW
smsbox-port = 13032
log-file = "/var/log/kannel/kannel.log"
log-level = 5
box-allow-ip = "*.*.*.*"
access-log = "/var/log/kannel/access.log"
store-type = spool
store-location = /var/spool/kannel/store
smsbox-max-pending = 100
dlr-storage = "internal"
sms-resend-freq = 1200
sms-resend-retry = 1
group = smsbox
bearerbox-host = localhost
bearerbox-port = 13032
sendsms-port = 13033
log-file = "/var/log/kannel/nosmscidsmsbox.log"
log-level = 3
reply-emptymessage = ""
http-request-retry = 2
http-queue-delay = 15
sms-length = 500
mo-recode=yes
group = sms-service
keyword = default
catch-all=true
omit-empty = true
assume-plain-text = yes
concatenation = true
max-messages = 0
get-url = "my_gt_uri"
group = smsc
smsc = smpp
smsc-admin-id = SMSC
smsc-id = SMSC
allowed-smsc-id = SMSC
preferred-smsc-id = SMSC
host = host
port = port
transceiver-mode = 1
smsc-username = USERNAME
smsc-password = PASSWORD
dest-addr-ton = 0
dest-addr-npi = 0
source-addr-ton = 0
source-addr-npi = 0
throughput = 30
enquire-link-interval = 30
log-file = /var/log/kannel/SMSC.log
log-level = 0
system-type = ""

On Mon, Apr 24, 2023 at 10:02 AM rm mobbis.am  
 wrote:


Hi Akamat. Sorry for late response.

The point is that you organize routing outside kannel and inside
your script or your MO sms handler web application side. This
gives you possibility to implement sms-service with any difficulty.

**

*Below are essential configs examples:*

# -- SMSBOX GROUP --

group = smsbox

bearerbox-host = localhost

bearerbox-port = 19005

sendsms-port = 19555

log-file = "/var/log/kanpsms/smsbox.log"

log-level = 3

access-log = "/var/log/kanpsms/smsbox-sms-access.log"

sendsms-chars = "0123456789 +#._"

reply-couldnotfetch = // If set, replaces the SMS message sent
back to user when Kannel could not fetch content //

reply-couldnotrepresent = // If set, replaces the SMS message sent
back when Kannel could not represent the result as a SMS message//

reply-requestfailed = // If set, replaces the SMS message sent
back when Kannel could not contact http service.//

reply-emptymessage = ""

http-request-retry = 2

http-queue-delay = 15

sms-length = 500

mo-recode=yes

# --  SMS SERVICE --

group = sms-service

keyword = default

catch-all=true

omit-empty = true

assume-plain-text = yes

concatenation = true

max-messages = 0

get-url = //Link to your script//

# -- SENDSMS USER GROUPS --

group = sendsms-user

username = SMSC1

password = *

user-deny-ip = "*.*.*.*"

user-allow-ip = "”

concatenation = true

max-messages = 4

forced-smsc = SMSC-ID1

group = sendsms-user

username = SMSC2

password = **

user-deny-ip = "*.*.*.*"

user-allow-ip = "”

concatenation = true

max-messages = 4

forced-smsc = SMSC-ID2

group = sendsms-user

username = SMSC3

password = ***

user-deny-ip = "*.*.*.*"

user-allow-ip =  "”

concatenation = true

max-messages = 4

forced-smsc = SMSC-ID3

*Please note,  that there is no smsbox-route config in my setup.*

*Explanation*

When kannel receives MO message it forwards received message to
your script.

Message handling, processing, saving your message to related DB,
generating answer and also submitting reply/answer message to
related SMSC (using the *KANNEL’S *HTTP interface to send SMS
messages) must be implemented in your script or your MO sms
handler web application side.

**

*Best regards,*

*Ruben Melikyan*



*From:*akamat sarat 
*Sent:* Thursday, April 20, 2023 11:53:17 AM
*To:* rm mobbis.am  
*Cc:* Tolga Ulas ; users@kannel.org

*Subject:* Re: MO Routing on the fly

Do you mean something like the following?
group = sms-service

get-url = "http://get-url.com";
catch-all = yes
This kind of setup does not work without adding smsbox-route. 
smsbox-route is either short code or smsc-id specific.
If you mean something else, can you write an example please?

Than k you

On Wed, Apr 19, 2023 at 9:32 PM rm mobbis.am 
 wro

RE: MO Routing on the fly

2023-04-24 Thread rm mobbis . am

Hi Akamat,
Your Warning is not related to sms routing.
Please check if your smsbox is up.

Core config example:

# -- CORE --core.conf

group=core
admin-port = 19000
smsbox-port = 19005
admin-password = *
status-password = *
admin-allow-ip = "
admin-deny-ip = "*.*.*.*"
log-file = "/var/log/kanpsms/bearerbox.log"
log-level = 3
access-log = "/var/log/kanpsms/SentReceivedSMS.log"
access-log-clean = true
access-log-format = "%t %l [SMSC:%i] [SVC:%n] [ACT:%A] [BINF:%B] [FID:%F] 
[META:%D] [from:%p] [to:%P] [flags:%m:%c:%M:%C:%d] [msg:%L:%b] [udh:%U:%u]"
box-allow-ip = "127.0.0.1;*.*.*.*"
sms-combine-concatenated-mo=true
# --
store-type = file
store-location = /home/KANNEL_PSMS/STORE
dlr-storage = spool
dlr-spool = /home/KANNEL_PSMS/DLR


# -- OUTBOUND-SMS-CENTERS -
include="/home/KANNEL_PSMS/smsc/smsc1.conf"
include = "/home/KANNEL_PSMS/smsc/smsc2.conf"
include = "/home/KANNEL_PSMS/smsc/smsc3.conf"

#- SMSBOX---
include = "/home/KANNEL_PSMS/configs/smsbox.conf"

#SENDSMS USERS--
include = "/home/KANNEL_PSMS/users/SendSMSusers.conf"

# -- SMS-SERVICE --
include = "/home/KANNEL_PSMS/services/services.conf"


Other configs examples you can find in previous email

Steps to RUN KANNEL

Step1: /usr/local/kanpsms/bearerbox --parachute 
/home/KANNEL_PSMS/configs/core.conf &

Step2: usr/local/kanpsms/smsbox --parachute /home/KANNEL_PSMS/configs/core.conf

Best regards,
Ruben Melikyan


From: akamat sarat 
Sent: 24.04.2023 13:31
To: rm mobbis.am 
Cc: Tolga Ulas ; users@kannel.org
Subject: Re: MO Routing on the fly

Dear All,

Thank you for your advice. I have tried all of your suggestions but cant get it 
to work like you say it should.
Without an smsbox-route, when ever an MO comes in I still get the "WARNING: 
smsbox_list empty"  warning.
Below my complete setup is below, what am I doing wrong?

group = core
admin-port = 13000
admin-password = ADMINPW
status-password = STATUSPW
smsbox-port = 13032
log-file = "/var/log/kannel/kannel.log"
log-level = 5
box-allow-ip = "*.*.*.*"
access-log = "/var/log/kannel/access.log"
store-type = spool
store-location = /var/spool/kannel/store
smsbox-max-pending = 100
dlr-storage = "internal"
sms-resend-freq = 1200
sms-resend-retry = 1



group = smsbox
bearerbox-host = localhost
bearerbox-port = 13032
sendsms-port = 13033
log-file = "/var/log/kannel/nosmscidsmsbox.log"
log-level = 3
reply-emptymessage = ""
http-request-retry = 2
http-queue-delay = 15
sms-length = 500
mo-recode=yes



group = sms-service
keyword = default
catch-all=true
omit-empty = true
assume-plain-text = yes
concatenation = true
max-messages = 0
get-url = "my_gt_uri"


group = smsc
smsc = smpp
smsc-admin-id = SMSC
smsc-id = SMSC
allowed-smsc-id = SMSC
preferred-smsc-id = SMSC
host = host
port = port
transceiver-mode = 1
smsc-username = USERNAME
smsc-password = PASSWORD
dest-addr-ton = 0
dest-addr-npi = 0
source-addr-ton = 0
source-addr-npi = 0
throughput = 30
enquire-link-interval = 30
log-file = /var/log/kannel/SMSC.log
log-level = 0
system-type = ""









On Mon, Apr 24, 2023 at 10:02 AM rm mobbis.am 
mailto:r...@mobbis.am>> wrote:
Hi Akamat. Sorry for late response.

The point is that you organize routing outside kannel and inside your script or 
your MO sms handler web application side. This gives you possibility to 
implement sms-service with any difficulty.

Below are essential configs examples:

# -- SMSBOX GROUP --
group = smsbox
bearerbox-host = localhost
bearerbox-port = 19005
sendsms-port = 19555
log-file = "/var/log/kanpsms/smsbox.log"
log-level = 3
access-log = "/var/log/kanpsms/smsbox-sms-access.log"
sendsms-chars = "0123456789 +#._"
reply-couldnotfetch = // If set, replaces the SMS message sent back to user 
when Kannel could not fetch content //
reply-couldnotrepresent = // If set, replaces the SMS message sent back when 
Kannel could not represent the result as a SMS message//
reply-requestfailed = // If set, replaces the SMS message sent back when Kannel 
could not contact http service.//
reply-emptymessage = ""
http-request-retry = 2
http-queue-delay = 15
sms-length = 500
mo-recode=yes

# --  SMS SERVICE --
group = sms-service
keyword = default
catch-all=true
omit-empty = true
assume-plain-text = yes
concatenation = true
max-messages = 0
get-url = //Link to your script//

# -- SENDSMS USER GROUPS --
group = sendsms-user
username = SMSC1
password = *
user-deny-ip = "*.*.*.*"
user-allow-ip = "”
concatenation = true
max-messages = 4
forced-smsc = SMSC-ID1

group = sendsms-user
username = SMSC2
password = **
user-deny-ip = "*.*.*.*"
user-allow-ip = "”
concatenation = true
max-messages = 4
forced-smsc = SMSC-ID2

group = sendsms-user
username = SMSC3
password = ***
user-deny-ip = "*.*.*.*"
user-allow-ip =  "”
concatenation = true
max-messages = 4
forced-smsc = SMSC-ID3


Please note,  that there is no smsbox-route config in my setup.

Exp

Re: MO Routing on the fly

2023-04-24 Thread akamat sarat

Dear All,

Thank you for your advice. I have tried all of your suggestions but
cant get it to work like you say it should.
Without an smsbox-route, when ever an MO comes in I still get the "WARNING:
smsbox_list empty"  warning.
Below my complete setup is below, what am I doing wrong?


group = core
admin-port = 13000
admin-password = ADMINPW
status-password = STATUSPW
smsbox-port = 13032
log-file = "/var/log/kannel/kannel.log"
log-level = 5
box-allow-ip = "*.*.*.*"
access-log = "/var/log/kannel/access.log"
store-type = spool
store-location = /var/spool/kannel/store
smsbox-max-pending = 100
dlr-storage = "internal"
sms-resend-freq = 1200
sms-resend-retry = 1

group = smsbox
bearerbox-host = localhost
bearerbox-port = 13032
sendsms-port = 13033
log-file = "/var/log/kannel/nosmscidsmsbox.log"
log-level = 3
reply-emptymessage = ""
http-request-retry = 2
http-queue-delay = 15
sms-length = 500
mo-recode=yes
group = sms-service
keyword = default
catch-all=true
omit-empty = true
assume-plain-text = yes
concatenation = true
max-messages = 0
get-url = "my_gt_uri"

group = smsc
smsc = smpp
smsc-admin-id = SMSC
smsc-id = SMSC
allowed-smsc-id = SMSC
preferred-smsc-id = SMSC
host = host
port = port
transceiver-mode = 1
smsc-username = USERNAME
smsc-password = PASSWORD
dest-addr-ton = 0
dest-addr-npi = 0
source-addr-ton = 0
source-addr-npi = 0
throughput = 30
enquire-link-interval = 30
log-file = /var/log/kannel/SMSC.log
log-level = 0
system-type = ""


On Mon, Apr 24, 2023 at 10:02 AM rm mobbis.am  wrote:

> Hi Akamat. Sorry for late response.
>
>
>
> The point is that you organize routing outside kannel and inside your
> script or your MO sms handler web application side. This gives you
> possibility to implement sms-service with any difficulty.
>
>
>
> *Below are essential configs examples:*
>
>
>
> # -- SMSBOX GROUP --
>
> group = smsbox
>
> bearerbox-host = localhost
>
> bearerbox-port = 19005
>
> sendsms-port = 19555
>
> log-file = "/var/log/kanpsms/smsbox.log"
>
> log-level = 3
>
> access-log = "/var/log/kanpsms/smsbox-sms-access.log"
>
> sendsms-chars = "0123456789 +#._"
>
> reply-couldnotfetch = // If set, replaces the SMS message sent back to
> user when Kannel could not fetch content //
>
> reply-couldnotrepresent = // If set, replaces the SMS message sent back
> when Kannel could not represent the result as a SMS message//
>
> reply-requestfailed = // If set, replaces the SMS message sent back when
> Kannel could not contact http service.//
>
> reply-emptymessage = ""
>
> http-request-retry = 2
>
> http-queue-delay = 15
>
> sms-length = 500
>
> mo-recode=yes
>
>
>
> # --  SMS SERVICE --
>
> group = sms-service
>
> keyword = default
>
> catch-all=true
>
> omit-empty = true
>
> assume-plain-text = yes
>
> concatenation = true
>
> max-messages = 0
>
> get-url = //Link to your script//
>
>
>
> # -- SENDSMS USER GROUPS --
>
> group = sendsms-user
>
> username = SMSC1
>
> password = *
>
> user-deny-ip = "*.*.*.*"
>
> user-allow-ip = "”
>
> concatenation = true
>
> max-messages = 4
>
> forced-smsc = SMSC-ID1
>
>
>
> group = sendsms-user
>
> username = SMSC2
>
> password = **
>
> user-deny-ip = "*.*.*.*"
>
> user-allow-ip = "”
>
> concatenation = true
>
> max-messages = 4
>
> forced-smsc = SMSC-ID2
>
>
>
> group = sendsms-user
>
> username = SMSC3
>
> password = ***
>
> user-deny-ip = "*.*.*.*"
>
> user-allow-ip =  "”
>
> concatenation = true
>
> max-messages = 4
>
> forced-smsc = SMSC-ID3
>
>
>
>
>
> *Please note,  that there is no smsbox-route config in my setup.*
>
>
>
> *Explanation*
>
> When kannel receives MO message it forwards received message to your
> script.
>
> Message handling, processing, saving your message to related DB,
> generating answer and also submitting reply/answer message to related SMSC
> (using the *KANNEL’S *HTTP interface to send SMS messages) must be
> implemented in your script or your MO sms handler web application side.
>
>
>
> *Best regards,*
>
> *Ruben Melikyan*
> --
>
> *From:* akamat sarat 
> *Sent:* Thursday, April 20, 2023 11:53:17 AM
> *To:* rm mobbis.am 
> *Cc:* Tolga Ulas ; users@kannel.org <
> users@kannel.org>
> *Subject:* Re: MO Routing on the fly
>
>
>
> Do you mean something like the following?
> group = sms-service
>
> get-url = "http://get-url.com";
> catch-all = yes
> This kind of setup does not work without adding smsbox-route.
> smsbox-route is either short code or smsc-id specific.
> If you mean something else, can you write an example please?
>
> Than k you
>
>
>
> On Wed, Apr 19, 2023 at 9:32 PM rm mobbis.am  wrote:
>
> Hi Akamat,
>
>
>
> Honestly, I suspect that I do not fully understand your situation (
> because if I usnderstand you in right way, it has very obvious solution).
>
> Thus if I understand your request correctly, you just need to:
>
>1. configure sms-service
>2. set your script on  apache or iis
>3. use get-url or post-url and other sms-s

Re: MO Routing on the fly

2023-04-24 Thread rm mobbis . am

Hi Akamat. Sorry for late response.

The point is that you organize routing outside kannel and inside your script or 
your MO sms handler web application side. This gives you possibility to 
implement sms-service with any difficulty.

Below are essential configs examples:

# -- SMSBOX GROUP --
group = smsbox
bearerbox-host = localhost
bearerbox-port = 19005
sendsms-port = 19555
log-file = "/var/log/kanpsms/smsbox.log"
log-level = 3
access-log = "/var/log/kanpsms/smsbox-sms-access.log"
sendsms-chars = "0123456789 +#._"
reply-couldnotfetch = // If set, replaces the SMS message sent back to user 
when Kannel could not fetch content //
reply-couldnotrepresent = // If set, replaces the SMS message sent back when 
Kannel could not represent the result as a SMS message//
reply-requestfailed = // If set, replaces the SMS message sent back when Kannel 
could not contact http service.//
reply-emptymessage = ""
http-request-retry = 2
http-queue-delay = 15
sms-length = 500
mo-recode=yes

# --  SMS SERVICE --
group = sms-service
keyword = default
catch-all=true
omit-empty = true
assume-plain-text = yes
concatenation = true
max-messages = 0
get-url = //Link to your script//

# -- SENDSMS USER GROUPS --
group = sendsms-user
username = SMSC1
password = *
user-deny-ip = "*.*.*.*"
user-allow-ip = "”
concatenation = true
max-messages = 4
forced-smsc = SMSC-ID1

group = sendsms-user
username = SMSC2
password = **
user-deny-ip = "*.*.*.*"
user-allow-ip = "”
concatenation = true
max-messages = 4
forced-smsc = SMSC-ID2

group = sendsms-user
username = SMSC3
password = ***
user-deny-ip = "*.*.*.*"
user-allow-ip =  "”
concatenation = true
max-messages = 4
forced-smsc = SMSC-ID3


Please note,  that there is no smsbox-route config in my setup.

Explanation
When kannel receives MO message it forwards received message to your script.
Message handling, processing, saving your message to related DB, generating 
answer and also submitting reply/answer message to related SMSC (using the 
KANNEL’S HTTP interface to send SMS messages) must be implemented in your 
script or your MO sms handler web application side.

Best regards,
Ruben Melikyan

From: akamat sarat 
Sent: Thursday, April 20, 2023 11:53:17 AM
To: rm mobbis.am 
Cc: Tolga Ulas ; users@kannel.org 
Subject: Re: MO Routing on the fly

Do you mean something like the following?
group = sms-service
get-url = "http://get-url.com";
catch-all = yes
This kind of setup does not work without adding smsbox-route.  smsbox-route is 
either short code or smsc-id specific.
If you mean something else, can you write an example please?

Than k you

On Wed, Apr 19, 2023 at 9:32 PM rm mobbis.am 
mailto:r...@mobbis.am>> wrote:
Hi Akamat,

Honestly, I suspect that I do not fully understand your situation ( because if 
I usnderstand you in right way, it has very obvious solution).
Thus if I understand your request correctly, you just need to:

  1.  configure sms-service
  2.  set your script on  apache or iis
  3.  use get-url or post-url and other sms-service related parameters 
according your needs
Thus you will have smsc independet script which will handle all your MO 
requests especially if you set catch-all parameter to true.

Best regards,
Ruben Melikyan

From: users mailto:users-boun...@kannel.org>> on 
behalf of akamat sarat mailto:akamat.sa...@gmail.com>>
Sent: Wednesday, April 19, 2023 7:32:45 PM
To: Tolga Ulas mailto:tolga.u...@tolgaulas.com>>
Cc: users@kannel.org 
mailto:users@kannel.org>>
Subject: Re: MO Routing on the fly

Even though I could not figure it out, the smsc-id parameter is not mandatory 
for the smsbox-route group.
Does this imply it can be SMSC independent if some other configuration is 
properly applied? possibly. I've tested smsbox-route group without specifying 
any smsc-ids and this did not work.
But I'm probably missing something.

On Wed, Apr 19, 2023 at 7:28 PM akamat sarat 
mailto:akamat.sa...@gmail.com>> wrote:
I figured out a way to set it up the way I need it to work.
So like I said, I wanted to route all MOs originating from all SMSCs to a 
single script to handle all of them.
In my SMSc configuration I am using reroute-smsc-id to re-route all incoming 
MOs to a single HTTP SMSc that will invoke my script.
The thing that kept me back is the preferred-smsc-id setting, because if it is 
used in conjunction with reroute-smsc-id then reroute-smsc-id is completely 
ignored without any mention of it in kannel logs.


On Wed, Apr 19, 2023 at 7:12 PM Tolga Ulas 
mailto:tolga.u...@tolgaulas.com>> wrote:
Not sure on top of my head whether it can be smsc independent, check with the 
documentation in the related section of thart smsc-id part and smsbox-route 
functioning in general.
Tolga Ulas



On Wed, Apr 19, 2023 at 5:51 PM akamat sarat 
mailto:akamat.sa...@gmail.com>> wrote:
Thank for coming b

Re: MO Routing on the fly

Re: MO Routing on the fly

RE: MO Routing on the fly

Re: MO Routing on the fly

Re: MO Routing on the fly

5 matches

Site Navigation

Mail list logo

Footer information