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 = 19
am <http://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.
**
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-de
el/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 s
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
Dear Akamat,
>From kannel user manual,
*Smsbox routing inside bearerbox*
The communication link between bearerbox and smsbox has been designed for
the purpose of load-balancing via random assignment. Which means, bearerbox
holds all smsc connections and passes inbound message to one of
especially if you set catch-all parameter to true.
>
> Best regards,
> Ruben Melikyan
> --
> *From:* users on behalf of akamat sarat <
> akamat.sa...@gmail.com>
> *Sent:* Wednesday, April 19, 2023 7:32:45 PM
> *To:* Tolga Ulas
> *Cc:* us
behalf of akamat sarat
Sent: Wednesday, April 19, 2023 7:32:45 PM
To: Tolga Ulas
Cc: 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
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
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 scrip
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 wrote:
> Thank for coming back, you mean something like:
>
>
Thank for coming back, you mean something like:
group=smsbox-route
smsbox-id=mysmsbox
smsc-id=SMSC1; SMSC2; SMSC3...
If so, this means that every time a new SMSC is added, I will need to add
it to the smsc-id's list in the above configuration.
After that I will need to restart kannel which I do n
Put a single route to a single smsbox which has a single service and define
all your smscs in the route as origin.
Tolga Ulas
On Wed, Apr 19, 2023 at 5:22 PM akamat sarat wrote:
> To all kannelers,
>
> I am trying to find a way to configure kannel so that all incoming
> messages (MOs) from all
To all kannelers,
I am trying to find a way to configure kannel so that all incoming messages
(MOs) from all SMSCs to go to the same script.
The problem is that i could not find a working solution that does not rely
on smsbox-routes
and it is not possible to add smsbox-routes on the fly.
Any he
Hello Users,
Can i route messages in kannel by sender id per SMSC connection like the
way denied-prefix is? if not is they any best way to achieve this?
Regards
Chris
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 wo
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-
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 -->>
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 DL
This may work out for me currently. But my SMS are already in kannel store,
Even though SMS in kannel store file Is this routing is going to work out.
Also I will try to play with allowed-smsc and preferred-smsc to see how
routing is working. Currently, we are sending smsc parameter always to
...@mobtexting.com> wrote:
>
>
> Hello all,
> I am facing one Issue something like below.
> Sometimes I get more traffic and according to routing logic (simple one
> user to one SMSC)
> all messages are queued at kannel for a particular SMSC let name it
> *SMSC_PROVIDER1
l,
> I am facing one Issue something like below.
> Sometimes I get more traffic and according to routing logic (simple one user
> to one SMSC)
> all messages are queued at kannel for a particular SMSC let name it
> SMSC_PROVIDER1.
> Form admin interface I know that another SMSC let
Hello all,
I am facing one Issue something like below.
Sometimes I get more traffic and according to routing logic (simple one
user to one SMSC)
all messages are queued at kannel for a particular SMSC let name it
*SMSC_PROVIDER1*.
Form admin interface I know that another SMSC let name it
Hi everyone,
Happy New Year to All
can anyone help me to setup kannel as source based routing for MT Traffic
like..
if source Sender id is "ABC" then process this via smsc1 or bind1
if source sender id is "xyz" then process this via smsc2 or bind2
thanks
Deepak
Hi Users,
We have two host running kannel connecting to the same SMSC. The issue is with
Long MO where SMSC tend to split it and send to host 1 and host 2 respectively
and this causing kannel on each host waiting for the MO parts. My question to
this, Is it possible to route inbound MO to kanne
lf Of Davor Spasoski
Sent: Wednesday, July 26, 2017 10:35 PM
To: Gorki Alfaro <gork...@gmail.com>
Cc: users@kannel.org
Subject: Re: Routing to multiple SMSCs OPENSMPP
The smscs do not necessarily have to have same-ids. Same smsc-ids are used when you want to load balance the traffic amo
to have a preferred SMSC for prefix3 instead of
> load sharing, just add preferred-smsc-id = SMSC1 in the SMSC1 configuration.
>
>
>
> Good luck!
>
>
>
> *Davor Spasoski*
>
>
>
> *From:* users [mailto:users-boun...@kannel.org] *On Behalf Of *Davor
> Spa
f load sharing, just
add preferred-smsc-id = SMSC1 in the SMSC1 configuration.
Good luck!
Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Davor Spasoski
Sent: Wednesday, July 26, 2017 10:35 PM
To: Gorki Alfaro
Cc: users@kannel.org
Subject: Re: Routing to multiple SMSC
aso...@onevip.mk>:
Hi,
Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of variables.
Davor Spasoski
From: users [mailto:users-bounces@kannel.org]
On Behalf Of Gorki Alfaro
Sent: Wednesday, July 26, 2017 5:47 AM
To: users@kannel.org
Subject: Routing to multiple SMSCs OPE
...@kannel.org] *On Behalf Of *Gorki
> Alfaro
> *Sent:* Wednesday, July 26, 2017 5:47 AM
> *To:* users@kannel.org
> *Subject:* Routing to multiple SMSCs OPENSMPP
>
>
>
> Hello my friends
>
>
>
> Does anyone solve this situation? I have clients connecting to me
>
Hi,
Try using the allowed-smsc-id and allowed-prefix of the SMSC group set of
variables.
Davor Spasoski
From: users [mailto:users-boun...@kannel.org] On Behalf Of Gorki Alfaro
Sent: Wednesday, July 26, 2017 5:47 AM
To: users@kannel.org
Subject: Routing to multiple SMSCs OPENSMPP
Hello my
Hello my friends
Does anyone solve this situation? I have clients connecting to me through
SMPP connections who needs to send messages to more than one SMSC however
OPENSMPP configuration only allows one SMSC (variable route-to-smsc) .
The question is: How can I redirect messages to different SMS
Check if routing delay is from telecom side (SMSC often sends DLR pretty
late). It should be visible in bearerbox logs. Logically, bbox should not
be delaying DLRs.
On Wed, Oct 21, 2015 at 8:51 AM, Amelye Chatila wrote:
> I experience a delay in DLRs routing. I have couple of smsboxes
I experience a delay in DLRs routing. I have couple of smsboxes and couple
of SMSC connections. What is causing this? What adjustments can I make?
Thanks in advance!
Hello,
I have been experiencing big latency (up to 15 minutes) just after Kannel
receives MOs and does the deliver to de app. server.I'm using a "exec" to a
local perl script that does a userAgent->get to the App.Srvr.
Months ago I was using a "get-url" to a php to the App.Srvr. that apparently
*Hello To All,*
I'm successfully configuring OpenSMPPBox with kannel but I'm having some
issues regarding DLR routing.
SMPP client connects my SMPP on transmitter and receiver mode.
So SMPP client not received all DLR's to their kannel.
So please suggest me how to resolve t
; Freundliche Grüsse
>
> Javier Escalante
>
> 00 41 78 689 85 69
>
> escalant...@gmail.com
>
>
>
> *From:* Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
> *Sent:* 16 June 2015 16:37
> *To:* escalant...@gmail.com
> *Cc:* users
> *Subject:* Re: Routing failed, req
ail.com
From: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
Sent: 16 June 2015 16:37
To: escalant...@gmail.com
Cc: users
Subject: Re: Routing failed, reqeued
Hi
Can you post how are you feeding messages to kannel?
You should define a default route or specify it on your call to sms
2015 16:37
To: escalant...@gmail.com
Cc: users
Subject: Re: Routing failed, reqeued
Hi
Can you post how are you feeding messages to kannel?
You should define a default route or specify it on your call to smsbox.
Regards
Alvaro
15.
BR
Freundliche Grüsse
Javier Escalante
00 41 78 689 85 69
escalant...@gmail.com
From: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
Sent: 16 June 2015 16:37
To: escalant...@gmail.com
Cc: users
Subject: Re: Routing failed, reqeued
Hi
Can you post how are you feeding messages
Hi Alvaro,
In line.
BR
Freundliche Grüsse
Javier Escalante
00 41 78 689 85 69
escalant...@gmail.com
From: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
Sent: 16 June 2015 18:11
To: escalant...@gmail.com
Cc: users
Subject: Re: Routing failed, reqeued
Hi Javier
The
what you want…could you please specify?
>
>
>
> BR
>
>
>
> Freundliche Grüsse
>
> Javier Escalante
>
> 00 41 78 689 85 69
>
> escalant...@gmail.com
>
>
>
> *From:* Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
> *Sent:* 16 June 2015 16:3
Subject: Re: Routing failed, reqeued
Hi
Can you post how are you feeding messages to kannel?
You should define a default route or specify it on your call to smsbox.
Regards
Alvaro
Hi
Can you post how are you feeding messages to kannel?
You should define a default route or specify it on your call to smsbox.
Regards
Alvaro
|-|
Envíe y Reciba Datos y mensajes de
Hello,
My USB modem is working and sending messages with minicom, but its
impossible for me to get rid of the above message and send sms from Kannel.
Caould yoou please give me a clue?
Thanks
BR
Config attached.
Freundliche Grüsse
Javier Escalante
00 41 78 689 85 69
es
Maybe you can post some logs of a submit_sm operation, on both sides
(opensmppbox and SMSC1).
From: users [mailto:users-boun...@kannel.org] On Behalf Of Ammar Ali
Sent: maandag 18 mei 2015 16:03
To: users@kannel.org
Subject: OpenSMPPBox DLR Routing
Hello Everyone,
I'm config
Hello Everyone,
I'm configuring OpenSMPPBox with Kannel and It works fine.
I'm testing this with NOWSMS SMPP simulator. I'm sending sms through this
simulator, I'm getting sms on cell phone. But there is an issue with DLR,
I'm not getting DLR.
*This is my configuration files:*
*Kannel.conf*
g
re routed to the http smsc
Ho i can do different routing for incoming and outgoing messages?
What i'm doing wronk?
Thanks in advance
Apologies if this has already been covered in past: does anyone know of a mod
for Kannel to enable routing function similar to a standard SMSC?
maps to pid 5037.
> 2015-03-18 23:13:26 [5037] [2] DEBUG: HTTP: Including port 13000, fd 10
> for polling in server thread
> 2015-03-18 23:13:26 [5037] [0] DEBUG: Started thread 3
> (gw/bb_http.c:httpadmin_run)
> 2015-03-18 23:13:26 [5037] [3] DEBUG: Thread 3
> (gw/bb_http.c:httpadmin_
-max-pending' not set,
using default (100).
2015-03-18 23:13:26 [5037] [0] DEBUG: Adding smsbox routing to id
for smsc id
2015-03-18 23:13:26 [5037] [0] DEBUG: Started thread 4
(gw/bb_boxc.c:sms_to_smsboxes)
2015-03-18 23:13:26 [5037] [4] DEBUG: Thread 4
(gw/bb_boxc.c:sms_to_smsboxes) maps to
gt; SMSC simulation). Is that possible?
>
>
>
> Thanks & Regards
>
> Nilubon Soonthon
>
> *From:* Tapan Kumar Thapa [mailto:tapan.thapa2...@gmail.com]
> *Sent:* Thursday, March 12, 2015 11:43 AM
> *To:* Nilubon Soonthon
> *Subject:* Re: Routing failed, re-queued a
h 12, 2015 11:43 AM
To: Nilubon Soonthon
Subject: Re: Routing failed, re-queued and 3: Queued for later delivery
Although url seems ok but can you try below and see if its resolves your issue.
http://localhost:13013/cgi-bin/sendsms?username=admin
<http://localhost:13013/cgi-bin/sendsms?usernam
wer: request.>
>
> 2015-03-12 17:12:56 [3907] [3] DEBUG: HTTP: Resetting HTTPClient for
> `127.0.0.1'.
>
>
>
> 2015-03-12 17:13:56 [3907] [1] DEBUG: Timeout for fd:25 appears.
>
> 2015-03-12 17:13:56 [3907] [1] DEBUG: HTTP: Destroying HTTPClient area
> 0x7f
ail.com]
Sent: Wednesday, March 11, 2015 8:56 PM
To: Tapan Kumar Thapa
Cc: Nilubon Soonthon; users@kannel.org
Subject: Re: Routing failed, re-queued and 3: Queued for later delivery
Hi
Can you post relevant parts
, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
y GPRS online
Visitenos en www.perusms.com
On Tue, Mar 10, 2015 at 11:23 PM, Tapan Kumar Thapa <
tapan.thapa2...@gmail.com> wrote:
> Dear Nilubon,
>
> Are you still facing the re-routing issue?
>
> Your
Dear Nilubon,
Are you still facing the re-routing issue?
Your bearerbox is on from 35 min and your SMSC is on from 16s only.
Is there any issue with SMSC? Have you restarted SMSC via kannel admin
interface?
On Wed, Mar 11, 2015 at 9:46 AM, Nilubon Soonthon
wrote:
> Dear Tapan,
>
>
, March 11, 2015 10:58 AM
To: Nilubon Soonthon
Cc: users@kannel.org
Subject: Re: Routing failed, re-queued and 3: Queued for later delivery
Dear Nilubon,
Can you please give us the output of below url?
http://10.11.21.248:13000/status?password=kannel
Regards
Tapan Thapa
On Wed, Mar 11,
roblem?
>
>
>
>
>
> Thanks & regards
>
> Nilubon Soonthon
>
> *From:* Tapan Kumar Thapa [mailto:tapan.thapa2...@gmail.com]
> *Sent:* Monday, March 9, 2015 3:20 PM
> *To:* Nilubon Soonthon
> *Cc:* users@kannel.org
> *Subject:* Re: Routing failed, re-queued and
down .Do you have any idea for me to solve this problem?
Thanks & regards
Nilubon Soonthon
From: Tapan Kumar Thapa [mailto:tapan.thapa2...@gmail.com]
Sent: Monday, March 9, 2015 3:20 PM
To: Nilubon Soonthon
Cc: users@kannel.org
Subject: Re: Routing failed, re-queued and 3: Queued for l
fo/users>]# tail -20
> bearerbox.log
>
> 2014-03-19 19:24:51 [31238] [7] DEBUG: Routing failed, re-queued.
>
> 2014-03-19 19:24:51 [31238] [7] DEBUG: sms_router: handling message
>
> (0x971e120 vs 0x9724248)
>
> 2014-03-19 19:24:51 [31238] [7] DEBUG: Routing failed
sleep 30.00 secs.
[root at hosta <http://www.kannel.org/mailman/listinfo/users> ]# tail -20
bearerbox.log
2014-03-19 19:24:51 [31238] [7] DEBUG: Routing failed, re-queued.
2014-03-19 19:24:51 [31238] [7] DEBUG: sms_router: handling message
(0x971e120 vs 0x9724248)
2014-03-19 19:24:51 [31238] [7]
Greetings to all, I need help you'm riding a server and I need to make a
routing because a server will be the primary and the other will be the
sending server in the main server is installed an kannel + playsms and the
other only the kannel I need to send a sms he take the Dad of the code and
Hi
Kannel is an smpp client, not server. You need opensmpp pluging to make
kannel an smpp server.
With that, you need to set routing accordingly.
Regards
Alvaro
|-|
Envíe y Reciba
Good day
We are using kannel as our SMPP server and using SMSC protocol.
When clients are connected to us via SMPP their MO's only goes to their web
UI account's inbox and does not send the MO's through to them via the SMPP
bind with us.
How do we get the clients that is connected to us via S
ice.
>
> I tried a few different things like having allowed-receiver-prefixes
> of +93729103500 and 93729103500 as well as having two binds, one with
> a forced bind-npi and ton and neither seemed to help. Any ideas on how
> I can get the routing to work appropriately within smsbox?
&g
her seemed to help. Any ideas on how
I can get the routing to work appropriately within smsbox?
Here's a dump of an incoming message that fails:
SMPP PDU 0x7fa9cc000a10 dump:
type_name: deliver_sm
command_id: 5 = 0x0005
command_status: 0 = 0x
sequence_number: 15989026
t; Tracing some info in the log we can see the following behaviour:
>>>>
>>>> kannel.log
>>>>
>>>> 2014-11-06 14:22:13 [20038] [1] DEBUG: HTTP: Destroying HTTPClient for
>>>> `127.0.0.1'.
>>>> 2014-11-06 14:22:19 [20038] [1
DEBUG: send_msg: sending msg to box:
>>> <127.0.0.1>
>>> 2014-11-06 14:22:19 [20038] [14] DEBUG: boxc_sender: sent message to
>>> <127.0.0.1>
>>> 2014-11-06 14:22:19 [20038] [13] DEBUG: boxc_receiver: got ack
>>> 2014-11-06 14:22:19 [2003
t;127.0.0.1>
>> 2014-11-06 14:22:19 [20038] [13] DEBUG: boxc_receiver: got ack
>> 2014-11-06 14:22:19 [20038] [13] DEBUG: boxc_receiver: sms received
>> 2014-11-06 14:22:19 [20038] [13] DEBUG: send_msg: sending msg to box:
>> <127.0.0.1>
>> 2014-11-06 14:22:19 [
DEBUG: send_msg: sending msg to box:
> <127.0.0.1>
> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: handling message
> (0x7f4344001670 vs 0x7f4344001670)
> 2014-11-06 14:22:19 [20038] [12] DEBUG: Routing failed, re-queued.
> 2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router
:19 [20038] [13] DEBUG: boxc_receiver: sms received
2014-11-06 14:22:19 [20038] [13] DEBUG: send_msg: sending msg to box:
<127.0.0.1>
2014-11-06 14:22:19 [20038] [12] DEBUG: sms_router: handling message
(0x7f4344001670 vs 0x7f4344001670)
2014-11-06 14:22:19 [20038] [12] DEBUG: Routing failed, re
Hi
By gateway you mean a kannel instance or an smsc?
If the latter, you can add an id to your call to kannel and use
allowed-smsc and denied-smsc to route sms.
If the first you might need to do at your application level
Regards
Alvaro
|-
Hi All,
I want to route my SMS to different gateways based on prefixes.
For an example, if I have two gateways configured ''gw1" and "gw2"
Number with 99 prefix > gw1
Number with 95 prefix > gw2
So on
so now if I send SMS to any number with 99 prefix then it should be sent
usin
See the smsbox-route configuration option.
From: users [mailto:users-boun...@kannel.org] On Behalf Of David Riches
Sent: maandag 22 september 2014 21:41
To: users@kannel.org
Subject: Routing from Kannel SMPP connection to a connected OpenSMPPbox client
Hi
Ive been strugling with this
company
(client)
I need to be able to route inbound messages from the Carrier -> Client but
cant quite work out where I need to set up the routing. Im not trying to
do anything more advanced than this , just a simple passthrough of all
traffic from the carrier to the client via SMPP.
Can any
Here goes the logs (tested with dlr-mask=3):
http://localhost:13013/cgi-bin/sendsms?username=xxx&password=yyy&to=+595981414913&from=1244&binfo=CMBEG&text=Prueba+de+servicio&smsc=tigo&dlr-mask=3&dlr-url=http%3A%2F%2Flocalhost%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D1212%26type%3D%25d
bearerbox.log
2014-08
Hi
dlr 8 means message has been submitted to smsc (and accepted by it)
dlr 1 means message has been delivered to phone (and stored either in SIM
or phone memory)
Also; some operators does not provide all dlr status; however as stated on
my previous mail. kannel is in fact receiving the dlr with t
Still not working. Tried msg-id-type = 0x01 and still not working. Also
putting dlr-mask before dlr-url on the param sequence.
The thing is that i do receive the dlr when type=8 and type=16 but kannel
does not send me dlr with type=1.
If the message has been delivered to the phone.. should i have
Hi
Re-reading your original question I saw that, in fact, you do receive the
dlr.
2014-08-21 12:33:22 [2202] [7] DEBUG: DLR[internal]: Looking for DLR
smsc=tigo, ts=11e22675ee6, dst=595981414913, type=1
However kannel is unable to track it back to original message:
2014-08-21 12:33:22 [2202] [
Hi
Sorry you are right. Can you test this:
&dlr-mask=31&dlr-url=
http://localhost/sms/api/dlr.php?myId=1212%26type%3D%25d
Basically type should
|-|
Envíe y Reciba Datos y mensaje
2014-08-21 23:03 GMT+04:00 Alejandro Mussi :
> Hi Alvaro,
>
> If i replace, it does not send dlr at all. According to the manual the
> dlr-mask is not an param in the dlr-url.
>
> Best
>
You're correct.
Problem is with your SMSC provider. As long as you see only 8 and 16, first
status means ACK
Hi Alvaro,
If i replace, it does not send dlr at all. According to the manual the
dlr-mask is not an param in the dlr-url.
Best
On Thu, Aug 21, 2014 at 1:37 PM, Alvaro Cornejo
wrote:
> Hi Alejandro
>
> Change %26type%3D%25d&dlr-mask=31 with %26type%3D25%26dlr-mask%3D31
>
> Note that what
Hi Alejandro
Change %26type%3D%25d&dlr-mask=31 with %26type%3D25%26dlr-mask%3D31
Note that what you request as dlr is not necessarily what you will receive.
Carriers define which dlr status will they forward. Some disable
intermediate status, some allow all of them.
Regards
Alvaro
|-
Hi guys,
My kannel is not sending my dlr-url when type=1. I get it when type=16 and
type=8.
Here is what log saids:
2014-08-21 12:33:22 [2202] [7] DEBUG: DLR[internal]: Looking for DLR
smsc=tigo, ts=11e22675ee6, dst=595981414913, type=1
2014-08-21 12:33:22 [2202] [7] WARNING: DLR[internal]: DLR
Thanks, it can be routed using allowed-receiver-prefix-regex
On Mon, Aug 18, 2014 at 5:29 PM, ha...@aeon.pk wrote:
> Read the user manual, especially the REGEX part.
>
>
> On Mon, Aug 18, 2014 at 9:33 PM, Alejandro Mussi
> wrote:
>
>> Hi guys,
>>
>> How is possible to route an incoming sms
Read the user manual, especially the REGEX part.
On Mon, Aug 18, 2014 at 9:33 PM, Alejandro Mussi wrote:
> Hi guys,
>
> How is possible to route an incoming sms to differents sms-service
> depending of the short code number sent.?
>
> I have a client that has his own content management (not kan
Hi guys,
How is possible to route an incoming sms to differents sms-service
depending of the short code number sent.?
I have a client that has his own content management (not kannel) and i want
to send all the sms traffic that have certains short numbers. Anyone can
recommend a better way to do t
password = kannel
> concatenation = true
> max-messages = 3
>
> # SMSC SMPP
> group = smsc
> smsc = smpp
> smsc-id = external
> host = xxx.xxx.xxx.xxx
> port = 1
> receive-port = 1
> smsc-username = password
> smsc-password = password
> system-type =
system-type = VMA
address-range =
log-file = "/var/log/kannel/external.log"
log-level = 0
reroute-smsc-id = messages
# SMS routing rules
group = smsbox-route
smsc-id=external
shortcode=1
smsbox-id=messages
# INCOMING SMS
group = sms-service
keyword = ping
text = "Pong!"
gro
; *Sent:* vrijdag 25 april 2014 17:06
> *To:* users@kannel.org
> *Subject:* OpenSMPPBox: DLR Routing to connected SMPP client
>
>
>
> Hi,
>
> I am stuck in a problem which seems to have a simple solution. Here is my
> system:
>
> SMSC<--->Kannel<--->Sqlbox&
Have the client set registered_delivery to 2.
== Rene
From: users [mailto:users-boun...@kannel.org] On Behalf Of Saurabh Pandey
Sent: vrijdag 25 april 2014 17:06
To: users@kannel.org
Subject: OpenSMPPBox: DLR Routing to connected SMPP client
Hi,
I am stuck in a problem which seems to
originated from content provided
server X.
We have to implement some routing logic mentioned below.
a) All
traffic originated by content provider server X, destined to 123x will route
through
SMSC A.
The is what we are achieving right now
as per the below config :
For authentication
Hi,
I am stuck in a problem which seems to have a simple solution. Here is my
system:
SMSC<--->Kannel<--->Sqlbox<--->OpenSMPPbox<--->SMPP Client
Now when SMPP client submits a message, it only gets the intermediate DLR
i.e. 8 (Submitted to SMSC). It never receives the final DLR. But when I
send
: donderdag 10 april 2014 12:29
To: 'Rene Kluwen'; 'users@kannel.org'
Subject: RE: Routing assistance needed
Thanks for that rene.
I tried it and it worked exactly as you explained it would.
We're trying to do something slighltly different however.
I suspect kannel
dumped into SQL.
Any ideas on that one?
From: Ciaran Scolard
Sent: 28 January 2014 17:31
To: Rene Kluwen; users@kannel.org
Subject: RE: Routing assistance needed
Hi Rene,
In terms of routing does that mean I should specify the bearerbox-port in
opensmppbox.conf as 13009 instead of 13001?
I&#
... was an invalid SIM card.
tyS0
speed = 19200
# pin = 2345
validityperiod = 167
keepalive = 60
sms-center = "0279735986"
sim-buffering = true
max-error-count = "3"
host = "debser10"
port = 13002
smsc-username = kannel
smsc-password = tunnel
I read somewhere that someone else had an issue like this and
Hi spameden,
The smsbox logs at debug level are not showing any errors. I am not using
sqlbox at the moment.
I will monitor smsbox incase it re-occurs.
Thanks,
Duncan
--
View this message in context:
http://kannel.6189.n7.nabble.com/Routing-failed-re-queued-and-3-Queued-for-later-delivery
Hi Alvaro,
you are right. sorry it is 1.5 I will try the SVN.
Thanks,
Duncan
--
View this message in context:
http://kannel.6189.n7.nabble.com/Routing-failed-re-queued-and-3-Queued-for-later-delivery-tp29636p29646.html
Sent from the Kannel - User mailing list archive at Nabble.com.
1 - 100 of 473 matches
Mail list logo
