[ANNOUNCE] GSMA MWC 2024 Meeting opportunity
Dear all, as every year, we are attending the GSMA Mobile World Congress in Barcelona, Spain from 26 Feb to 29 Feb 2024. If you are a mobile network operator, a messaging aggregator, a system integrator for mobile networks and/or services, or an enterprise representative in the mobile business, and would like to meet us on the venue for discussion about - commercial support/consulting for Kannel deployments, development and/or integration - our commercial add-on products - Kannel SMPP v5.0 server (smppbox) - Kannel SMPP v5.0 proxy filter (smppproxy) - Kannel AMQP v0.9.1 messaging broker (amqpbox-rabbitmq) - Kannel AMQP v1.0 messaging broker (amqpbox) - Kannel S@T gateway (gateway-stk) - Kannel OTA gateway (gateway-ota) - Kannel vSMSC (virtual SMSC) solutions - Kannel SMS inter-working/hubbing (iwsmsc) - Kannel-CG (carrier-grade) Mobile Internet Gateway (kannel-cg) - Kannel-CG (carrier-grade) MMSC (kannel-mmsc) - our commercial Support Level Agreements (SLA) for business critical Kannel installations - future technology integrations - RCS Inter-working, ... - to discuss any other topic... please feel free to set-up an appointment with us at the MWC via our main web site URL http://www.kannel.org/, or via the direct interface to the scheduling planer via URL https://kannel.appointlet.com/ We're looking forward to see you at MWC in Barcelona. -- 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: octstr_url_decode: corrupted end-of-string <%>
Am 22.06.22, 09:13, schrieb christopher kamutumwa: Hello team, I get this when % sign is put in message . Advise how to resolve. the function octstr_url_decode() assumes that the input is a URL-encoded string. By definition a % is a special character in the URL-encoded string format, which follows a 2 character value representing the byte code, i.e. %30 for the ASCII character '0'. A sole '%' in the string, i.e. at the end would be an illegal input, by definition. If you need to "decode" a '%' sign itself, that would be the URL-encoded value %25. -- 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: Missing delivery reports from SMSC dropping delivery reports
Am 14.02.22, 18:01, schrieb akamat sarat: Dear Users, We are unable to debug an issue with SMSC having to do with delivery reports missing from SMSC over smpp bind. The connection to SMSC is working properly according to kannel logs. No obvious errors are visible in the logs. But we are missing delivery reports that SMSC is saying were delivered and ACKd by kannel. Specifically they are saying that they have 'CDRs state "Delivered Direct"' and that kannel ACKd the delivery report. We however cannot see it in kannel access logs or SMSC logs or in any logs. Having run tcpdumps we cannot locate it either. Any way to debug this issue that we are missing? Thanks, Akamat Hi Akamat, what COULD be the case here is that Kannel bearerbox does ACK the deliver_sm PDUs from the SMSC with a corresponding deliver_sm_resp PDU, (so from the SMSCs perspective they are acknowledged), but your DLR message ID setup (or smsc-id patch setup) is configured wrong in Kannel, and the DLR is formally not resolved in bearerbox to the temporary data that is store in the DLR storage. Hence the DLR is "not found", and then not logged to the access-log (in older releases). Suggesting you run the bearerbox.log (log-file) in DEBUG level (log-level = 0), and then check that you DO see the deliver_sm PDUs from the SMSC. Additional things to check: - Make sure you are AWARE of the message ID notation. Some SMSCs use hex in submit_sm_resp PDU, but decimal in the deliver_sm payload (see msg-id-type directive) - If you splitted the SMPP binds in receiver and transmitter, make sure they have the same 'smsc-id' identifier, otherwise you would receive a DLR on the receive bind that would not resolve correctly from the DLR storage, since the transmitter side used a difference smsc-id tag. -- 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 ---
*** MERRY CHRISTMAS and a HAPPY NEW YEAR! *** from the Kannel Group!
Dear developers, Dear users, while we know this past year had additional challenges for everyone of us, in the name of the whole Kannel Group we wish you: *** Merry Christmas, Happy Holidays and a Happy New Year! *** Enjoy the holiday season and make yourself a great time, either with family, friends or both. Stay responsible, stay safe. 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: SMSBOX not starting with PANIC
Am 15.12.21, 20:07, schrieb Norbert Kwizera:
Hey All,
We run a kannel instances with multiple connections and to increase the
throughput for each we found that we can set multiple instances for each
connection
We have no issue when we set the instances to 5 however
we have an issue when we set that to 10, starting kannel service fails
with the error below
2021-12-14 10:39:14 [4089406] [0] ERROR: connect to <127.0.0.1> failed
2021-12-14 10:39:14 [4089406] [0] ERROR: System error 111: Connection
refused
2021-12-14 10:39:14 [4089406] [0] ERROR: error connecting to server
`localhost' at port `13001'
2021-12-14 10:39:14 [4089406] [0] PANIC: Couldn't connect to the bearerbox.
2021-12-14 10:39:14 [4089406] [0] PANIC:
/usr/local/sbin/smsbox(gw_backtrace+0xf0) [0x5557e89e6fc0]
2021-12-14 10:39:14 [4089406] [0] PANIC:
/usr/local/sbin/smsbox(gw_panic+0x167) [0x5557e89e7137]
2021-12-14 10:39:14 [4089406] [0] PANIC:
/usr/local/sbin/smsbox(main+0xead) [0x5557e89b4b8d]
2021-12-14 10:39:14 [4089406] [0] PANIC:
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7ffb41e3e0b3]
2021-12-14 10:39:14 [4089406] [0] PANIC:
/usr/local/sbin/smsbox(_start+0x2e) [0x5557e89b560e]
Hi,
the error of smsbox is unrelated to the fact that you use 'instances =
x' in the corresponding 'group = smsc'.
In fact it even doesn't have any configuration relation, since smsbox
daemon never looks into the config of 'group = smsc' values, these are
only relevant for bearerbox.
At the time you are trying to start smsbox, bearerbox's smsbox-port is
not available, and this is why smsbox PANICs.
--
Best Regards,
Stipe
---
Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: license file invalid - kannel
Am 14.07.21, 20:01, schrieb Antony Stone: On Wednesday 14 July 2021 at 18:25:16, Francisco wrote: We've been using a version of Kannel that one of the core kannel developers / supports spun up for us. We'd like to set up a test server (test changes / updates), but, get the following license panic which prevents smppbox from loading. 2021-07-14 11:45:22.693 [13212] [0] PANIC: *** Local license information in '/opt/kannel/etc/license.d/smppbox.licenseV1' is invalid! Please check 'username' and 'password' values in group license! *** I have never come across the concept of a kannel licence, in terms of being allowed to use it. The software is Open Source under the BSD licence. I suggest you get back to whomever supplied this version of the software to you and ask what this means, because it doesn't fit with my understanding of the BSD licence which kannel is published under. for clarification: the license file Francisco is talking about is from our commercial add-on components (Kannel SMPP v5.0 server smppbox), which isn't part of the open source distribution. 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 ---
[RIP] Remembering René Kluwen
Dear all, With deep regret and sorrow we let you know that René Kluwen, one of Kannel core developers has passed away this week. René has been a wonderful character and person, a father and a long year active supporter of the Kannel project. His work contributed to the main gateway module, the sqlbox and opensmppbox sub-modules, along with most valued discussions in our mailing list groups. Some of us have been friends with René and we’re heavily shaken by the news. We will miss him, and we would like to express our sincerely condolences to his family. Like in the hearts and minds of his family, his persona will keep on living in his work he contributed with passion to our project. Honoring his contributions is our privilege and determination. Rest in peace René Kluwen (* 10-05-1970, ✝ 06-06-2021) https://kannel.org/images/rouwkaart_rene.png -- 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: registered_delivery could be a bug in 1.5.0
Am 29.05.21, 21:44, schrieb Web Min: Hello, I'm using 1.5.0, I have reported a problem to my gateway to check from their side why I'm not receiving the DLR Report, I surprised when replied that they are receiving the registered_delivery = 0 although it is showing from the SMSC transmitter log. 2021-05-29 15:09:49 [10316] [6] DEBUG: SMPP PDU 0x7ff53800e060 dump: 2021-05-29 15:09:49 [10316] [6] DEBUG: type_name: submit_sm 2021-05-29 15:09:49 [10316] [6] DEBUG: command_id: 4 = 0x0004 2021-05-29 15:09:49 [10316] [6] DEBUG: command_status: 0 = 0x 2021-05-29 15:09:49 [10316] [6] DEBUG: sequence_number: 58 = 0x003a 2021-05-29 15:09:49 [10316] [6] DEBUG: service_type: NULL 2021-05-29 15:09:49 [10316] [6] DEBUG: source_addr_ton: 5 = 0x0005 2021-05-29 15:09:49 [10316] [6] DEBUG: source_addr_npi: 0 = 0x 2021-05-29 15:09:49 [10316] [6] DEBUG: source_addr: "SenderID" 2021-05-29 15:09:49 [10316] [6] DEBUG: dest_addr_ton: 0 = 0x 2021-05-29 15:09:49 [10316] [6] DEBUG: dest_addr_npi: 0 = 0x 2021-05-29 15:09:49 [10316] [6] DEBUG: destination_addr: "123456789" 2021-05-29 15:09:49 [10316] [6] DEBUG: esm_class: 3 = 0x0003 2021-05-29 15:09:49 [10316] [6] DEBUG: protocol_id: 0 = 0x 2021-05-29 15:09:49 [10316] [6] DEBUG: priority_flag: 3 = 0x0003 2021-05-29 15:09:49 [10316] [6] DEBUG: schedule_delivery_time: NULL 2021-05-29 15:09:49 [10316] [6] DEBUG: validity_period: NULL 2021-05-29 15:09:49 [10316] [6] DEBUG: *registered_delivery: 1 = 0x0001* if this is the SMPP PDU dump from the bearebox, then this is what we ARE SENDING. If they object, they may provide a tcpdump trace of the traffic, including the submit_sm_resp PDU showing the message_id, then you can simply compare what you have on the wire. OR, you do the tcpdump scan on your own, so you know what is on the wire when the TCP packets are going towards the SMSC. Assuming that there is no IP router that will do SMPP deep-packet-inspection and modification, this is what they SHOULD receive too then. 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: DISCARDED SMS / NACK/Retries Exceeded
Am 25.05.21, 09:54, schrieb Web Min:
It is already in the SMSC before the host
allowed-prefix = 1
when your users inject as destination addr 1xxx that is fine, but if
they use a international prefixed addr +1xxx that would not be able to
pass via the configured SMSC then.
this would then yield the following code block in
gw/bb_smsconn.c:smsc2_rout():
} else {
gw_rwlock_unlock(_list_lock);
if (bb_status == BB_SHUTDOWN) {
msg_destroy(msg);
return SMSCCONN_QUEUED;
}
warning(0, "Cannot find SMSCConn for message to <%s>, rejected.",
octstr_get_cstr(msg->sms.receiver));
bb_smscconn_send_failed(NULL, msg_duplicate(msg),
SMSCCONN_FAILED_DISCARDED, octstr_create("no SMSC"));
return SMSCCONN_FAILED_DISCARDED;
}
check if you can see this WARNING entry in the log, to double check.
--
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: Slow sms outbox to smsc smpp
Am 25.05.21, 22:52, schrieb Jose N Figueroa: Hello everybody, I'm using kannel latest revision "Kannel bearerbox version svn-r5307M" with the following scenario: Smsbox -> Bearerbox -> SMPP SMSC· I'm using redis as store, but for some strange reason I'm only getting out about 5 sms/s and even I have 2 or 3 binds (load balancing) to the same SMPP SMSC, I tried one smsc and the 3 smsc as load balancing already, same result. This is the config, I'm not sure what I'm doing wrong: the config itself looks ok, there is no major issue that you explain the 5 TPS ratio. My assumption here is that the SMSC side simply regulates your account (same username/system-id on the binds) to have a max ratio of 5 TPS. Are you getting corresponding throttling errors back from the SMSC side? and what is the service response time (SRT) value, so the time difference between submit_sm and corresponding submit_sm_resp PDUs? 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: 1800tps
Am 13.10.20, 06:54, schrieb Arun: Hi friends, I achieved 1800tps on 2gb 2core ec2 machine after months this sounds you did some "changes" or specifically addoptions to reach the TPS ratio. Can you please be more specific how this evolved? I'm sure there are more people around that are interested. Thanks, 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: Upgrading kannel1.4.3 to 1.4.4
Am 18.11.20, 11:38, schrieb mahesh Lavanam: I'm using kannel 1.4.3 on CentOS6. Looking to upgrade to kannel 1.4.4, can you please provide the info how to upgrade. Hi Makesh, the upgrade should be fairly straight forward, as there are no dependencies that would break here moving from 1.4.3 to 1.4.4. The internal Kannel msg structure is kept very stable. I would rather go with 1.4.5 through. -- 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: Long Message Issue
Am 14.10.20, 04:24, schrieb Wan Md Arif Noor Bin. Wan Nizam: Hi Kannel Users, Based on the logs below it seems like Kannel is exceeding 160 characters when sending concatenated long SMS which in result rejected by the operator, is this a bug? Hi Arif, let us try to look into this. Can you please provide the corresponding sendsms HTTP API call that you used to generate the message? In addition the .data_coding = 0x00 is set, so per SMPP protocol the default SMSC alphabet, which is "mostly" GSM 03.38 throughout the world. But your payload looks more like UTF-8 encoded, at least the byte codes are larger the 0x7F which is the max limit of the 7bit GSM encoding. -- 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: ASCI (ANSI X 3.4) IA5 SMPP data coding
Am 24.06.20, 13:04, schrieb ahmed qadeer: Dear Team, Please let me know if we can send use ASCI (ANSI X 3.4) IA5 SMPP data coding in kannel 1.5 Operator has asked to use this data coding instead of 8 bit octet stream Kannel will use GSM 03.38 (aka GSM 7bit) for submit_sm.data_coding = 0x00 (aka SMSC default alphabet). Now, there are 2 options: a) they want you to send ASCII encoding with data_coding = 0x00, because their default alphabet is ASACII, then you can set group = smsc smsc = smpp ... alt-charset = ASCII b) they want you to send ASCII encoding with data_coding = 0x01, then you need to indicate to Kannel via the corresponding meta-data part of the sendsms HTTP API that you want to trigger that, which is then send as http:///..?to=xx=yy=zzz=URLENCODE(?smpp?data_coding=1) 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: ASCI (ANSI X 3.4) IA5 SMPP data coding
Am 24.06.20, 13:11, schrieb Antony Stone: On Wednesday 24 June 2020 at 13:04:43, ahmed qadeer wrote: Dear Team, Please let me know if we can send use ASCI (ANSI X 3.4) IA5 SMPP data coding in kannel 1.5 I don't know the answer to your question, but I would suggest that you reconsider the use of Kannel 1.5 at all, as the code is considerably older (don't ask me why, I think it's silly) than Kannel 1.4.4 or 1.4.5 the point here are the sub-release version convention that we have. We follow Linux historical approach here where: - major.minor (i.e. 1.4) is STABLE release class if minor is even - major.minor (i.e. 1.5) is DEVEL release class if minor if uneven So, due to that 1.5.x can be older then 1.4.x. -- 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: query related to binfo
Am 26.05.20, 17:44, schrieb ritesh rao:
I just wish to know if we set the binfo will that affect the smpp at
smsc side , in other words is binfo is part of smpp protocol ? or
binfo is used for kannel level only?
the 'binfo' field is an abstracted billing identifier/info field, which
is handled differently on each of the the lower SMSC protocol layers.
I.e. for SMPP what you get his this:
/* Set the service type of the outgoing message. We'll use the config
* directive as default and 'binfo' as specific parameter. */
if (octstr_len(msg->sms.binfo)) {
/* SMPP v5.0 has an own TLV for billing information */
if (smpp->version == 0x50) {
pdu->u.submit_sm.billing_identification =
octstr_duplicate(msg->sms.binfo);
} else {
pdu->u.submit_sm.service_type =
octstr_duplicate(msg->sms.binfo);
}
} else {
pdu->u.submit_sm.service_type = octstr_duplicate(smpp->service_type);
}
so in a typical SMPP v3.3 or v3.4 session the value in 'binfo' is passed
as submit_sm.service_type value.
--
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: Sending DLR messages from smsbox
Am 05.05.20, 15:02, schrieb Robert Robinson:
Hello;
We currently use Kannel 1.4.5 as a middleware box which sits between our
network and our partner network. We call into smsbox, using the HTTP API
to submit outbound messages to bearerbox, and using the sms-service to
make HTTP calls into our network when bearerbox submits messages to
smsbox. We interface with our partner using the smpp SMSC module. This
works very well.
Today, we can receive DLR reports for the outbound messages that we send
to our partner by adding the dlr-mask and dlr-url parameters to the HTTP
call we make to smbox.
I would like to know how I can configure smsbox to allow for delivery
reports to be crafted for messages that sms-service delivers over HTTP.
Specifically, I am looking for a way to be able to signal back to our
partner specific SMPP deliver error codes when a message that is
received cannot be delivered. Is this possible with smsbox today? If so,
what would need to be included in the HTTP response returned on the call
made by sms-service?
Thank you for any insight you can provide.
~Robert
The sms-service config we use (callback host changed for sake of example):
group = sms-service
keyword-regex = .*
catch-all = yes
max-messages = 7
omit-empty = true
alt-charset = "UTF-8"
get-url =
http://sms.example.com/sms?to=%P=%p=%a=%u_message=%b
concatenation = true
accept-x-kannel-headers = true
Hi Robert,
does this means you want to:
a) send a corresponding deliver_sm_resp.command_status (error code)
value when the MO is received on bearerbox side, and then being unable
to forward to the sms-service defined URL by smsbox?, or
b) you want to send an ESME outbound DLR to the SMSC side via
submit_sm/data_sm?
So, the question is, DO you want to send a delivery notification towards
the SMSC that the ESME side has "accepted" the MO message? In SMPP this
CAN be done by definition of the protocol, but rarely the SMSCs support
this.
If you run a SMS hubbing configuration, which is presumably the
intention when you interface via IP to the actual user agent on the
device, then typically the communication parties maintain a 2 way
connection by implementing both communication roles.
Example: Let's assume you have a number range that is "your network",
and that number range is delivered to you via a signal link provider and
it's SMSC. Then you would have the following:
operator(SMSC) <-MT- bearerbox <- smsbox <-HTTP- msg(to:yyy,from:xxx) APPL
operator(SMSC) -DLR-> bearerbox -> smsbox -HTTP-> DLR-URL
operator(ESME) msg(to:xxx,from:yyy) -MT-> smppbox ->
bearerbox(smsc_http) -HTTP-> APPL
operator(ESME) <-DLR- smppbox <- bearerbox(smsc_http)
So, the DLR is send to the opreator being in the ESME (SMPP client role)
from your SMPP server (Kannel smppbox) when bearerbox indicates that the
message (MT) has been acknowledged by the HTTP APPL layer.
--
Best Regards,
Stipe
---
Koelner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: SMPP
Am 01.10.19, 12:32, schrieb Robin C: Hi , Anybody providing SMPP software on a commercial basis? Hi Robin, we do provide commercial add-on components for the open source Kannel core, i.e. the commercial Kannel SMPP v5.0 server (smppbox) vSMSC solution, including corresponding consulting and dedicated support levels. Please let me know what usage scenarios you are having and we can provide further details. -- 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: disabling incoming SMS
Am 24.02.19 21:50, schrieb rene.klu...@chimit.nl: I think disabling MO in the AT module is possible if you set sim buffering to false and specify the proper CNMI string for your modem that disables MO indications. thanks Rene for the idea path. Never tried this actually. Maybe you can jump here in and assist? 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: Need help for opensmpp and SQLBox
1* *# DLR table structure* *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* what you have here is basically this: opensmppbox <- smsbox <--|-> bearerbox sqlbox <-- the port 13001 of bearerbox is the "smsbox application" port, and your opensmppbox and sqlbox (along with smsbox) conntect to it. Kannel sqlbox needs to places in the middle, so you get: opensmppbox <- |-> sqlbox <-> bearerbox smsbox <-- so you need to define group = sqlbox bearerbox-host = localhost bearerbox-port = 13001 smsbox-port = 13002 ... and then connect smsbox and opensmppbox to port 13002. -- 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: disabling incoming SMS
Am 19.02.19 17:46, schrieb Stuart Kendrick: I’m seeing a lot of this in my logs: 2019-02-18T19:28:26.526495-08:00 vishnu smsbox[21580]: 2019-02-18 19:28:26 [21580] [5] INFO: Starting to service <#001#006'application/vnd.wap.mms-message> from <301000> to <1234> 2019-02-18T19:28:44.167763-08:00 vishnu smsbox[21580]: 2019-02-18 19:28:44 [21580] [5] INFO: Starting to service <1301000 Error Invalid Number. Please re-send using a valid 10 digit mobile number or valid short code. No service specified> from <+1121611611> to <1234> […] 2019-02-19T08:38:24.918834-08:00 vishnu smsbox[21580]: 2019-02-19 08:38:24 [21580] [5] INFO: Starting to service <11121611611 Error Invalid Number. Please re-send using a valid 10 digit mobile number or valid short code. No service specified> from <+1121611611> to <1234> 2019-02-19T08:38:37.474384-08:00 vishnu smsbox[21580]: 2019-02-19 08:38:37 [21580] [5] INFO: Starting to service <11121611611 Error Invalid Number. Please re-send using a valid 10 digit mobile number or valid short code. No service specified> from <+1121611611> to <1234> I speculate: someone has found my cellular modem number and is sending me spam. For this application, I transmit SMS over the cellular modem; I don’t want to receive anything. * My carrier (AT) tells me that they cannot block in-bound SMS – they can enable bi-directional SMS or disable it: all or nothing. * I disabled auto-answer on the modem … but this setting appears to govern POTS, not SMS * Is there a Kannel way (bearerbox or smsbox) to disable incoming reception of SMS? * Alternatively, is there a way to instruct Kannel to send requests for Invalid Numbers (e.g. ‘1234’) to /dev/null? * Other ideas for dumping these messages? I’m mostly annoyed by the repetitive logging At the moment, I have a cronjob job which stops bearerox & smsbox, sleeps for several minutes (not clear to me why this is necessary), and then restarts them. This of course creates a dead zone, in terms of service, which is suboptimal. Hi Stuart, what you can do is to ensure that the "visible" impact is minimal. The SMSC AT module has no way to "refuse" MOs directly. It will send any MO to your connected smsbox instance. If you have no application driven MOs that you want to receive, then you can drop the MOs to nirvana and ensure that there is no response bounced back to the originator, i.e. via config context group = sms-service keyword = default text = "No action specified" max-messages = 0 You WILL still see the MOs in the bearerbox access-log and the smsbox access-log though. It MAY BE an option to think about a config directive for the SMSC AT module to "turn off" MO interpretation and simply drop anything we get on the modem. @devel: Anyone from the SMSC AT developer folks that wants to pick this up? -- 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.
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 ---
[REMINDER] GSMA MWC 2019 Meeting opportunity
Dear all, as every year, we are attending the GSMA Mobile World Congress in Barcelona, Spain from 25 Feb to 28 Feb 2019. If you are a mobile network operator, a messaging aggregator, a system integrator for mobile networks and/or services, or an enterprise representative in the mobile business, and would like to meet us on the venue for discussion about - commercial support/consulting for Kannel deployments, development and/or integration - our commercial add-on products - Kannel SMPP v5.0 server (smppbox) - Kannel SMPP v5.0 proxy filter (smppproxy) - Kannel AMQP v0.9.1 messaging broker (amqpbox-rabbitmq) - Kannel AMQP v1.0 messaging broker (amqpbox) - Kannel S@T gateway (gateway-stk) - Kannel OTA gateway (gateway-ota) - Kannel vSMSC (virtual SMSC) solutions - Kannel SMS inter-working/hubbing (iwsmsc) - Kannel-CG (carrier-grade) Mobile Internet Gateway (kannel-cg) - Kannel-CG (carrier-grade) MMSC (kannel-mmsc) - our commercial Support Level Agreements (SLA) for business critical Kannel installations - future technology integrations - RCS Interworking, ... - to discuss any other topic... please feel free to set-up an appointment with us at the MWC via our main web site URL http://www.kannel.org/, or via the direct interface to the scheduling planer via URL https://kannel.appointlet.com/ We're looking forward to see you at MWC in Barcelona. -- 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 ---
[ANNOUNCE] GSMA MWC 2019 Meeting opportunity
Dear all, as every year, we are attending the GSMA Mobile World Congress in Barcelona, Spain from 25 Feb to 28 Feb 2019. If you are a mobile network operator, a messaging aggregator, a system integrator for mobile networks and/or services, or an enterprise representative in the mobile business, and would like to meet us on the venue for discussion about - commercial support/consulting for Kannel deployments, development and/or integration - our commercial add-on products - Kannel SMPP v5.0 server (smppbox) - Kannel SMPP v5.0 proxy filter (smppproxy) - Kannel AMQP v0.9.1 messaging broker (amqpbox-rabbitmq) - Kannel AMQP v1.0 messaging broker (amqpbox) - Kannel S@T gateway (gateway-stk) - Kannel OTA gateway (gateway-ota) - Kannel vSMSC (virtual SMSC) solutions - Kannel SMS inter-working/hubbing (iwsmsc) - Kannel-CG (carrier-grade) Mobile Internet Gateway (kannel-cg) - Kannel-CG (carrier-grade) MMSC (kannel-mmsc) - our commercial Support Level Agreements (SLA) for business critical Kannel installations - future technology integrations - RCS Interworking, ... - to discuss any other topic... please feel free to set-up an appointment with us at the MWC via our main web site URL http://www.kannel.org/, or via the direct interface to the scheduling planer via URL https://kannel.appointlet.com/ We're looking forward to see you at MWC in Barcelona. -- 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: Commercial pricing of Kannel-smppbox
Am 30.06.18 13:03, schrieb Web Services: hi, can anyone suggest pricing for Commercial Kannel SMPP v3.4 server (smppbox) as i seen its paid kannel add-on Hi, thanks a lot for your interest in the commercial add-on Kannel SMPP v5.0 server (smppbox) vSMSC solution. We're happy to provide additional information. Kindly, please forward your request via a business email address to me. -- 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 ---
[ANNOUNCE] Kannel 1.4.5 stable release available
The Kannel Group is pleased to announce the availability of Kannel 1.4.5 stable release via our web site at URL http://www.kannel.org/download.shtml Please find attached the NEWS file section for the 1.4.5 stable release. -- 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 --- NEWS about Kannel: Open Source WAP and SMS Gateway version 1.4.5 This is a STABLE version. It should be usable for production systems. Please do report problems to the Kannel bug tracking system available at https://redmine.kannel.org/issues or send a mail to (the development mailing list, see https://www.kannel.org/lists.shtml). Changes since version 1.4.4 stable: [*** Beware that the version move from 1.4.4 stable to 1.4.5 stable contains numerous change sets, with major bug fixes and improvements. Following is a summary of the main issues. For a complete and detailed set of changes please refer to the specific ChangeLog in the doc/ directory of the distribution. ***] Compatibility breakers: New features: * Added graceful-restarting of bearerbox via the SIGHUP signal, which can be used to softly restart bearerbox on config changes allowing existing SMSC connections to keep on running. * Added redis support as message store and DLR storage. * Added Apache Cassandra 2.1, 2.2 and 3.0 support as DLR storage. * Added OpenSSL 1.1.x support. * Added support for chained certificate files. * Added support to define which SSL/TLS chipher suites to use. * Added UCS-2 (Unicode) support for FAKE SMSC MOs. * Allow override of specific SMPP values via meta-data forwarding, i.e. for TON/NPI, DCS. * Splitting white/black-list into per direction (sender/receiver) allowing a more fine grained control. * Added 'instances' directive for 'group = smsc' contexts to duplicate the configuration group into any number of instances, so there is no need to duplicate the configuration in the config files, reducing the potential for errors and redundancy. * Added per line PDU dump function for SMPP. * Added support for constant SMPP TLVs. Bugfixes: * Fixed various SMPP module issues. * Better handling of MySQL DBPool temporary error codes. * Various fixes in the routing abstraction layer. * Fixed segfault in logging module for permission errors. * Fixed smsbox's XML MT and XML POST processing. * Fixed HTTP SMSC queue counter. * Fixed waiting time when in bearerbox shutdown phase. * Fixed missing character set processing in HTTP SMSC (type kannel). * Fixed MO concatenation handling for re-routing cases. * Fixed various memory leaks. * Fixing asymmetric load distribution for this HTTP SMSC type. * Fixing HTTP Keep-Alive indication as HTTP server. * Fixed HTTP UCS-2 payload forwarding. * Fixed HTTP admin command /reload-lists. Changes since version 1.4.3: [*** Beware that the version move from 1.4.3 to 1.5.0 contains numerous change sets, with major bug fixes and improvements. Following is a summary of the main issues. For a complete and detailed set of changes please refer to the specific ChangeLog in the doc/ directory of the distribution. ***] Compatibility breakers: * Internal message structure has changed, so older smsbox connection daemons won't be able to communicate with this bearerbox. Please ensure that you use boxes from releases greater or equal 1.5.0 for correct communication. * DLR storage via MySQL requires now MySQL 4.1 or higher, due that we use now prepared statements in the SQL calls. New features: * Added 'meta-data' support, which provides a mechanism to pass SMSC protocol specific optional data to the lower SMSC module layer. Ie. optional TLVs for SMPP. * Added better serial speed support for the AT modem on MacOS systems. * Added cleaner iconv() support for character re-encoding. * Added SMPP v3.4 DLR support via optional TLV values. * Added DLR support for the MT batch processing program. * Added Microsoft SQL server support as DLR storage backend. * Extended the HTTP admin interface. * Added SMPP v3.4 intermediate notification support. * Added MT module handling of +CME ERROR cases. * Added better result parsing generic HTTP SMSC module. * Added better throughput handling in SMPP module. * Added SMSC module 'loopback' as the MT counterpart of the 're-route' directive in the 'group = smsc' for MO messages. MT messages are bounced back as MOs into the incoming queue. * Added separate DLR message counters on the HTTP admin status. * Added 'http
Re: Compile Error: No rule to make target 'am--refresh'
Am 06.03.2018 11:18, schrieb Alexander Malysh: Hi, we have to delete configure and stuff because it should not be there only in the release tar archive. ok, agree. Let's add this to an BUILD file so people know how to deal with it when they do svn trunk checkouts. Shall I proceed and also roll for a new devel release? I guess we want to go for the 1.6.0 branch rather then staying in 1.5.x. Any objections? Cheers, Stipe -- 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 ---
Re: Compile Error: No rule to make target 'am--refresh'
Am 05.03.2018 13:22, schrieb amal...@kannel.org: Hi, please call: ./bootstrap.sh before configure. Alex, shouldn't we commit one output instance of the bootstrap.sh output files to svn trunk so people can build without running into this? -- 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 ---
[REMINDER] GSMA MWC 2018 Meeting opportunity
Dear all, a kind reminder: As every year, we are attending the GSMA Mobile World Congress in Barcelona, Spain from 26 Feb to 1 Mar 2018. If you are a mobile network operator, a messaging aggregator, a system integrator for mobile networks and/or services, or an enterprise representative in the mobile business, and would like to meet us on the venue for discussion about - commercial support/consulting for Kannel deployments, development and/or integration - our commercial add-on products - Kannel SMPP v5.0 server (smppbox) - Kannel SMPP v5.0 proxy filter (smppproxy) - Kannel AMQP v1.0 messaging broker (amqpbox) - Kannel vSMSC (virtual SMSC) solutions - Kannel SMS inter-working/hubbing (iwsmsc) - Kannel-CG (carrier-grade) Mobile Internet Gateway (kannel-cg) - Kannel-CG (carrier-grade) MMSC (kannel-mmsc) - our commercial Support Level Agreements (SLA) for business critical Kannel installations - future technology integrations - RCS Interworking, ... - to discuss any other topic... please feel free to set-up an appointment with us at the MWC via our main web site URL http://www.kannel.org/, or via the direct interface to the scheduling planer via URL https://kannel.appointlet.com/ We're looking forward to see you at MWC in Barcelona. -- 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 ---
Re: [ANNOUNCE] GSMA MWC 2018 Meeting opportunity
Am 16.01.2018 19:16, schrieb Stipe Tolj: Dear all, as every year, we are attending the GSMA Mobile World Congress in Barcelona, Spain from 26 Feb to 1 Mar 2017. of course this should have been: from 26 Feb to 1 Mar 2018. We're looking forward to hear from you via our scheduling planer and see you in Barcelona. -- 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 ---
[ANNOUNCE] GSMA MWC 2018 Meeting opportunity
Dear all, as every year, we are attending the GSMA Mobile World Congress in Barcelona, Spain from 26 Feb to 1 Mar 2017. If you are a mobile network operator, a messaging aggregator, a system integrator for mobile networks and/or services, or an enterprise representative in the mobile business, and would like to meet us on the venue for discussion about - commercial support/consulting for Kannel deployments, development and/or integration - our commercial add-on products - Kannel SMPP v5.0 server (smppbox) - Kannel SMPP v5.0 proxy filter (smppproxy) - Kannel AMQP v1.0 messaging broker (amqpbox) - Kannel vSMSC (virtual SMSC) solutions - Kannel SMS inter-working/hubbing (iwsmsc) - Kannel-CG (carrier-grade) Mobile Internet Gateway (kannel-cg) - Kannel-CG (carrier-grade) MMSC (kannel-mmsc) - our commercial Support Level Agreements (SLA) for business critical Kannel installations - future technology integrations - RCS Interworking, ... - to discuss any other topic... please feel free to set-up an appointment with us at the MWC via our main web site URL http://www.kannel.org/, or via the direct interface to the scheduling planer via URL https://kannel.appointlet.com/ We're looking forward to see you at MWC in Barcelona. -- 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 ---
Re: Problem with GET HTTP
Am 19.10.2017 15:56, schrieb Stipe Tolj: Am 24.08.2017 18:24, schrieb Giulio Giovannini: Hello Stipe. Thanks for the interest. I can not confirm 100% that but I can see the smsbox.log flowing without interruption. So I assume that the lines below are written as a DLR is picked up by the smsbox and if a new line gets printed the previous DLR has been processed. 2017-08-24 18:18:27 [27072] [5] INFO: Starting delivery report from 2017-08-24 18:18:27 [27072] [5] INFO: Starting delivery report from 2017-08-24 18:18:27 [27072] [5] INFO: Starting delivery report from Nonethless, while that log flows fluid, a tcpdump on the machine shows that HTTP GET are delayed, like accumulated in batches. That is confirmed on the other end where the HTTP GETs are received in batches. When traffic is low, there are no losses. When traffic gets intense I noticed losses in the DLRs on the HTTP receiving end. Hi Giulio, now, the only reason I see at the moment for something that "looks" like a batched HTTP call processing, is the limit that Kannel's HTTP client sets for how many concurrent calls are allowed to be in a "open state". Which is controlled via: group = smsbox ... max-pending-requests = x BTW, default is 512 if not configured. BTW, this was introduced as "protection" towards the HTTP servers, as we had various cases in the real-world where Kannel was loading the HTTP server side so heavily,that it was basically becoming a DOS attack. -- 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 ---
Re: Problem with GET HTTP
Am 24.08.2017 18:24, schrieb Giulio Giovannini: Hello Stipe. Thanks for the interest. I can not confirm 100% that but I can see the smsbox.log flowing without interruption. So I assume that the lines below are written as a DLR is picked up by the smsbox and if a new line gets printed the previous DLR has been processed. 2017-08-24 18:18:27 [27072] [5] INFO: Starting delivery report from 2017-08-24 18:18:27 [27072] [5] INFO: Starting delivery report from 2017-08-24 18:18:27 [27072] [5] INFO: Starting delivery report from Nonethless, while that log flows fluid, a tcpdump on the machine shows that HTTP GET are delayed, like accumulated in batches. That is confirmed on the other end where the HTTP GETs are received in batches. When traffic is low, there are no losses. When traffic gets intense I noticed losses in the DLRs on the HTTP receiving end. Hi Giulio, now, the only reason I see at the moment for something that "looks" like a batched HTTP call processing, is the limit that Kannel's HTTP client sets for how many concurrent calls are allowed to be in a "open state". Which is controlled via: group = smsbox ... max-pending-requests = x BTW, default is 512 if not configured. So, what COULD happen is that we load the HTTP server in a high load situation, the HTTP server may take a bit longer to respond per request, yielding this "open response" count to 512, and while this is the case the HTTP client side layer would "block" the further calling towards the HTTP server. Then HTTP server flushes out a bunch of responses, the counter drops again for some figure (i.e. 50) and then Kannel's HTTP client writes again 50, to block again since 512 are again "open". As long as the input flow is high, this could result in such an effect you see. But it doesn't explain the differences in the revisions you have been using. Any chance you can create a test scenario with can be reproduced deterministically on our side, so we see the differences for both revisions? Reviewing the changesets from r5180 to r5186 I see only ONE thing touching gwlib/http.c, which is the HTTP/1.1 keep-alive correction I added, but this doesn't touch any of the HTTP client side code, as this is what we do as HTTP server. So we simply can't qualify any change to be the cause and rather assume my above scenario to be the case. -- 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 ---
Re: Problem with GET HTTP
Am 10.08.2017 12:38, schrieb Giulio Giovannini: Hi, nobody has anything to say about this issue? More details: I am seeing a difference of up to 8 seconds between the logging of DLR on smsbox log and the actual sending of the HTTP GET on the network interface. The server the application is running on does not seem to have any problem with the networking. can you confirm that the DLRs are passed from bearerbox to smsbox in a reasonable time, and that the "delaying" is from smsbox's HTTP call perspective? BTW, no, there was no "caching" added, as we always keep the premises to transport ASAP and as fast as possible. -- 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 ---
Re: Fwd: Could not open bearerbox
Am 19.06.2017 12:10, schrieb Robin C: Have you checked it? Any updates>?? Hi Robin, just had a moment to look into this. The corresponding source code locations don't correspond IMO to the backtrace of the PANIC, especially I don't see any reference for octstr_ncompare() at gw/smsc/smsc_smpp.c:854. Is this a vanilla 1.4.4 source build, or do you have patches here that have been applied? If yes, then I will need the gw/smsc/smsc_smpp.c file from you to review. -- 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 ---
Re: Could not open bearerbox
Am 07.06.2017 09:59, schrieb Robin C: Hi, I couldn't start the bearerbox. Please check the logs below: 2017-06-07 13:13:38 [18942] [9] DEBUG: SMPP PDU 0x7f467a10 dump: 2017-06-07 13:13:38 [18942] [9] DEBUG: type_name: bind_transceiver 2017-06-07 13:13:38 [18942] [9] DEBUG: command_id: 9 = 0x0009 2017-06-07 13:13:38 [18942] [9] DEBUG: command_status: 0 = 0x 2017-06-07 13:13:38 [18942] [9] DEBUG: sequence_number: 1 = 0x0001 2017-06-07 13:13:38 [18942] [9] DEBUG: system_id: "usera" 2017-06-07 13:13:38 [18942] [9] DEBUG: password: "pwd" 2017-06-07 13:13:38 [18942] [9] DEBUG: system_type: "smpp11" 2017-06-07 13:13:38 [18942] [9] DEBUG: interface_version: 52 = 0x0034 2017-06-07 13:13:38 [18942] [9] DEBUG: addr_ton: 0 = 0x 2017-06-07 13:13:38 [18942] [9] DEBUG: addr_npi: 0 = 0x 2017-06-07 13:13:38 [18942] [9] DEBUG: address_range: NULL 2017-06-07 13:13:38 [18942] [9] DEBUG: SMPP PDU dump ends. 2017-06-07 13:13:38 [18942] [8] DEBUG: SMPP[MTNL_S1]: Got PDU: 2017-06-07 13:13:38 [18942] [8] DEBUG: SMPP PDU 0x7f467c000a10 dump: 2017-06-07 13:13:38 [18942] [8] DEBUG: type_name: bind_transceiver_resp 2017-06-07 13:13:38 [18942] [8] DEBUG: command_id: 2147483657 = 0x8009 2017-06-07 13:13:38 [18942] [8] DEBUG: command_status: 0 = 0x 2017-06-07 13:13:38 [18942] [8] DEBUG: sequence_number: 1 = 0x0001 2017-06-07 13:13:38 [18942] [8] DEBUG: system_id: NULL 2017-06-07 13:13:38 [18942] [8] DEBUG: SMPP PDU dump ends. 2017-06-07 13:13:38 [18942] [8] DEBUG: SMPP[MTNL_S1]: throughput (0.00,0.00) 2017-06-07 13:13:38 [18942] [10] DEBUG: sms_router: gwlist_len = 4 2017-06-07 13:13:38 [18942] [10] DEBUG: sms_router: handling message (0x13c6150 vs 0x13c6150) 2017-06-07 13:13:38 [18942] [10] DEBUG: Message routed successfully. 2017-06-07 13:13:38 [18942] [8] DEBUG: SMPP[MTNL_S1]: throughput (0.00,0.00) 2017-06-07 13:13:38 [18942] [10] DEBUG: sms_router: handling message (0x13c9fb0 vs 0x13c9fb0) *2017-06-07 13:13:38 [18942] [8] PANIC: gwlib/octstr.c:2549: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:956:octstr_ncompare.)* 2017-06-07 13:13:38 [18942] [10] DEBUG: Message routed successfully. 2017-06-07 13:13:38 [18942] [10] DEBUG: sms_router: handling message (0x13c9ba0 vs 0x13c9ba0) 2017-06-07 13:13:38 [18942] [10] DEBUG: Message routed successfully. 2017-06-07 13:13:38 [18942] [10] DEBUG: sms_router: handling message (0x13c4e80 vs 0x13c4e80) 2017-06-07 13:13:38 [18942] [10] DEBUG: Message routed successfully. 2017-06-07 13:13:38 [18942] [8] PANIC: ./bearerbox(gw_backtrace+0xae) [0x4986fe] 2017-06-07 13:13:38 [18942] [8] PANIC: ./bearerbox(gw_panic+0x159) [0x498869] 2017-06-07 13:13:38 [18942] [8] PANIC: ./bearerbox() [0x499aa2] 2017-06-07 13:13:38 [18942] [8] PANIC: ./bearerbox(octstr_ncompare+0x47) [0x49e5a7] 2017-06-07 13:13:38 [18942] [8] PANIC: ./bearerbox() [0x4640a0] 2017-06-07 13:13:38 [18942] [8] PANIC: ./bearerbox() [0x467375] 2017-06-07 13:13:38 [18942] [8] PANIC: ./bearerbox() [0x48f269] 2017-06-07 13:13:38 [18942] [8] PANIC: /lib64/libpthread.so.0(+0x7aa1) [0x7f4698acbaa1] 2017-06-07 13:13:38 [18942] [8] PANIC: /lib64/libc.so.6(clone+0x6d) [0x7f4697c94aad] Hi, please provide the function location backtrace via output of: $ addr2line -e bearerbox 0x49e5a7 0x4640a0 0x467375 0x48f269 this will show us at what code locations the callstack is traversed. -- 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 ---
Re: OpenSMPPBox
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 ---
Re: Opensmppbox Issue
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
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: HTTP SMSC splitting long SMS
Am 05.04.17 15:16, schrieb ha...@aeon.pk: Hi, I am using HTTP SMSC to send MT SMS to a PHP script. I just discovered that the HTTP SMSC is passing long (concatenated) SMS to the PHP script in 2 parts, which makes them 2 individual SMS for the handset, instead of one long SMS. How can I prevent kannel from doing this? by default the abstraction layer segments all MTs towards an upstream SMSC to 140 octets, the GSM SMS PDU size limit. For an HTTP SMSC upstream this may be unwanted, you can define how long a PDU size can be via: group = smsc ... max-sms-octets = x simply define a larger size here for the HTTP SMSC, in order NOT to segment the message. See also the documentation at section: http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN1447 for details on the config directive. -- 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: web server information disclosure vulnerability
Am 16.03.2017 15:39, schrieb Jeff Thorn: We always proxy kannel with Apache or Nginx. That should resolve your issue. even while Kannel has a strong HTTP library, we're of course under no way as penetrated in terms of external HTTP traffic as the major HTTP server in the market (Apache, nginx). So, Jeff is right here. For external access you always want to do a reverse HTTP proxy configuration in front of Kannel's daemon. Stipe -- 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 ---
[REMINDER] GSMA MWC 2017 Meeting opportunity
Dear all, the GSMA Mobile World Congress in Barcelona, Spain from 27 Feb to 2 Mar 2017 is closing in fast. It's less then two weeks to the event. If you are a mobile network operator, a messaging aggregator, a system integrator for mobile networks and/or services, or an enterprise representative in the mobile business, and would like to meet us on the venue for discussion about - commercial support/consulting for Kannel deployments, development and/or integration - our commercial add-on products - Kannel SMPP v5.0 server (smppbox) - Kannel SMPP v5.0 proxy filter (smppproxy) - Kannel AMQP v1.0 messaging broker (amqpbox) - Kannel vSMSC (virtual SMSC) solutions - Kannel SMS inter-working/hubbing (iwsmsc) - Kannel-CG (carrier-grade) Mobile Internet Gateway (kannel-cg) - Kannel-CG (carrier-grade) MMSC (kannel-mmsc) - our commercial Support Level Agreements (SLA) for business critical Kannel installations - future technology integrations - RCS Interworking, ... - to discuss any other topic... please make an appointment with us at the MWC via our main web site URL http://www.kannel.org/, or via the direct interface to our online planers at: for meetings with Stipe Tolj please use https://kannel.appointlet.com/ for meetings with Alexander Malysh please use https://amalysh.youcanbook.me/ We're looking forward to see you at MWC in Barcelona. -- 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 ---
[ANNOUNCE] GSMA MWC 2017 Meeting opportunity
Dear all, as every year, we are attending the GSMA Mobile World Congress in Barcelona, Spain from 27 Feb to 2 Mar 2017. If you are a mobile network operator, a messaging aggregator, a system integrator for mobile networks and/or services, or an enterprise representative in the mobile business, and would like to meet us on the venue for discussion about - commercial support/consulting for Kannel deployments, development and/or integration - our commercial add-on products - Kannel SMPP v5.0 server (smppbox) - Kannel SMPP v5.0 proxy filter (smppproxy) - Kannel AMQP v1.0 messaging broker (amqpbox) - Kannel vSMSC (virtual SMSC) solutions - Kannel SMS inter-working/hubbing (iwsmsc) - Kannel-CG (carrier-grade) Mobile Internet Gateway (kannel-cg) - Kannel-CG (carrier-grade) MMSC (kannel-mmsc) - our commercial Support Level Agreements (SLA) for business critical Kannel installations - future technology integrations - RCS Interworking, ... - to discuss any other topic... please feel free to set-up an appointment with us at the MWC via our main web site URL http://www.kannel.org/, or via the direct interface to the scheduling planer via URL https://kannel.appointlet.com/ We're looking forward to see you at MWC in Barcelona. -- 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 ---
Re:
Am 20.12.2016 07:44, schrieb sapna singh: Dear Team, Any body hv idea USSD Coonecitivy using CUAP protocol. you means CoAP over USSD transport? Can you please explain what the purpose is and the usage case? -- 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 ---
Re: SMS route based on content
Am 06.12.2016 18:32, schrieb Alvaro Cornejo: Hi As far as I know, it is no possible with kannel/smppbox. You should handle that at your application level or modify kannel/smppbox according to your needs. it is possible with the commercial Kannel SMPP v5.0 server (smppbox) via it's global routing layer. Please let me know if you need more information here. Stipe -- 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 ---
Re: Opensmpp shuts down after panic twice a day
Am 14.11.2016 14:43, schrieb Rene Kluwen: What's the output of: addr2line -e /path/to/opensmppbox 0x40ed03 0x413f3e 0x44e7d9 since I need to mange a lot of these addr2line calls manually from time to time, SHOULD we add a facility in the backtrace calling of Kannel itself to check if addr2line is in $PATH, and if yes, simply use it to get the line information of the addresses? Stipe -- 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 ---
Re: Sender Prefix in SMPP
Am 11.11.2016 14:49, schrieb vinayak mv: In india we need to set a default sender id and prefix for promotional route so sender address is like MT-109887 we have a patchset available for this TRAI requirement case. I will email you in private with details. Stipe -- 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 ---
Re: How to make Kannel to get no notification from SMSC
Am 14.11.2016 07:57, schrieb Gert Tamm: No, I'm notinjecting dlr-mask or dlr-ulr to the. ok, can we see the full PDU exchange from the baerebox.log please? So we can see what exactly Kannel is sending and what the SMSC side is returning. Stipe -- 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 ---
Re: Sender Prefix in SMPP
Am 21.10.2016 19:16, schrieb vinayak mv: Hi, is there any option to set sender prefix and default sender in group smsc and smsc=smpp please make some examples of what you want to do, so we get a better understanding of the requirement here. Stipe -- 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 ---
Re: SMS REJECTED due to throttling
Hi, can we see the EMI/UCP PDU exchange from bearerbox.log in DEBUG level, so we can have a look into the code to see if there was any change? Stipe -- 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 ---
Re: How to make Kannel to get no notification from SMSC
Am 11.11.2016 07:57, schrieb Gert Tamm: A SMSC of mine says that they don't allow getting notifications from them. How could I turn off the Notifications? notifications == DLRs (delivery reports). Are you setting any 'dlr-mask' and 'dlr-url' when injecting the MTs via the smsbox's sendsms HTTP interface? If yes, simply ommit that part for that specific SMSC. Stipe -- 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 ---
Re: Multiple connections same port, different our-port
Am 10.11.2016 14:45, schrieb Davide Bellettini: Hello everybody, I'm wondering if it's possible to establish 8 connections for each of these two configuration block, by using different our-port (10844,10845,10846... and 10836, 10837...) values without copy-pasting the whole configuration 8 times. group = smsc smsc-id = smscname allowed-smsc-id = smscname port = 12248 our-port = 10844 smsc-username = username smsc-password = password smsc = emi host = hostname1 keepalive = 90 throughput = 10 connect-allow-ip = "10.0.0.183;127.0.0.1;10.10.11.34" flow-control = 1 group = smsc smsc-id = smscname allowed-smsc-id = smscname port = 12248 our-port = 10836 smsc-username = username smsc-password = password smsc = emi host = hostname2 keepalive = 90 throughput = 10 connect-allow-ip = "10.0.0.183;127.0.0.1;10.10.11.34" flow-control = 1 the 'our-port' in the EMI/UCP type is optional. If you DO NOT need a specific client-side TCP port to bind for you can use the 'instances = X' in the 'group = smsc' context to "multiply" the connections with a SINGLE group in the config. If you DO meed specific 'our-port' values, then NO, you need to have multiple config groups then. Stipe -- 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 ---
Re: USSD SMPP integration
Am 01.11.2016 07:40, schrieb kabin mool: Hi, I am trying to use kannel for integrating with USSD GW using SMPP. My bind to USSD GW is ok. MO is ok and MT has some problem, msg is receiving in handset but if I send or cancel msg, it is is re-sending the same msg to my handset repetitively. I am using following parameters in kannel.conf without smpp-tlv group. # SMS SERVICE group = sms-service keyword = default omit-empty = true max-messages = 10 get-url = "http://X.X.X.X/abc.php?mob=%p=TRIAL=%3Fsmpp%3Fussd%5Fservice%5Fop%3D17%26its%5Fsession%5Finfo%3D0; name="*2210#" Do I need to define smpp-tlv group in my configuration? As per my wireshark trace, delivery_sm has optional parameters: ussd_service_op and its_session_info (attached) but submit_sm does not have optional parameters set. Do I need to set this parameter, if yes how to send these parameters in submit_sm? correct, you will need to define the corresponding 'group = smpp-tlv' in the config, which make Kannel aware of the tag/name relation. Then use the meta-data HTTP header in the HTTP response to inject the 2 values in the MT message, which is then send as optional TLVs in the submit_sm 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 ---
Re: Route message to backup kannel box on SMS service failure
Am 27.09.16 19:19, schrieb Jim Page: Hi Stipe Sorry if I am being dim, but the incoming message is MT, isn't it, and the outgoing message is MO? Or have I misunderstood something fundamental? If not, and in your statement below MO and MT are round the wrong way, then you are correct - on an sms service REST failure: convert MT message to MO in the smsbox context and pass it back to bearerbox to be forwarded to another SMSC. FYI - these two SMSCs both belong to us, but operate in different divisions of our service. Hi Jim, now, let's first make sure the "definition part" is clear. MT = mobile terminate message, defines a message from the application layer TOWARDS the mobile subscriber. MO = mobile originated message, defines a message from the mobile subscriber towards the application layer (may be SMSC, where it then converts to an MT again, it send to another person). So, what I understood is that an MO is send from a mobile, coming in from the SMSC towards Kannel, and then forwarded to an REST API. IF that API fails, the message convert to an MT and is send to bearerbox for transportation to another SMSC. Is this scenario summary correct? -- 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: Route message to backup kannel box on SMS service failure
Am 07.09.2016 19:38, schrieb Jim Page: Hi There Can anyone tell me if there is a cunning way to configure kannel to do this: - SMS arrives from foreign SMSC - SMS is submitted to REST API via SMS service - If response is '404 not found', forward SMS to a different SMSC, otherwise: done means, converting from an MO message to an MT message inside smsbox scope and passing to bearerbox for upstream SMSC traffic? -- 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 ---
Re: Source code for fake SMSC.
Am 12.09.2016 09:26, schrieb info.ubichip: Hello, There is at least two solutions for you : - use the fake smsc feature in kannel (please read the manual and well documented example) - use the new great opensource Ksmpp which include a 'simulate' smsc (AFAIK) or use a test-drive installation of the commercial Kannel SMPP v5.0 server (smppbox) vSMSC product, which can act as true SMSC end-point. Please let us know if you are interested and we can provide more information. -- 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 ---
Re: Error with global trusted ca file, while compiling latest SVN Kannel.
Am 14.09.2016 13:28, schrieb tammer: Hello, I'm trying to install latest Kannel from SVN. While I'm compiling it I get this error : test/test_http.o: In function `main': /usr/local/src/kannel/gateway/test/test_http.c:456: undefined reference to `conn_use_global_trusted_ca_file' collect2: error: ld returned 1 exit status make: *** [test/test_http] Error 1 What might be the cause of this error? The configure line looks like : ./configure --prefix=/usr/local/kannel --with-mysql --with-mysql-dir=/usr/lib/mysql/ --enable-debug --enable-assertions --with-defaults=speed --disable-localtime --enable-start-stop-daemon --enable-pam --disable-ssl-thread-test --disable-ssl Changed my error. yep, you disabled the SSL (openssl library) support while configuring, and it seems the test_http.c isn't aware of that. Please check your configure.log when configuring normally WITH SSL support, to see why it is not found. You may be lacking the libssl-dev (debian package notation) on your system, depending on what distro it is. -- 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 ---
Re: got DLR but could not find message or was not interested in it
Am 31.07.2015 12:03, schrieb Achyut Raj: Hi Kannel Users, I am having issue with the DLR receiving. I have attached the log and config file below. the SMSC provides the msg ID as HEX notation in the submit_sm.message_id, AND then does provide it as DECIMAL notation in the DLR payload of the deliver_sm PDU. So you need to set: group = smsc ... msg-id-type = 0x01 Please see the corresponding documentation part at: http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN1936 -- 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 ---
Re: USSD with Kannel
ends. 2016-04-13 10:38:58 [12246] [5] DEBUG: Msg object ends. Bearerbox log 7292:2016-04-13 10:38:58 [12229] [6] DEBUG: SMPP[smppUSSD]: Got PDU: 7293:2016-04-13 10:38:58 [12229] [6] DEBUG: SMPP PDU 0x7feef000b390 dump: 7294:2016-04-13 10:38:58 [12229] [6] DEBUG: type_name: deliver_sm 7295:2016-04-13 10:38:58 [12229] [6] DEBUG: command_id: 5 = 0x0005 7296:2016-04-13 10:38:58 [12229] [6] DEBUG: command_status: 0 = 0x 7297:2016-04-13 10:38:58 [12229] [6] DEBUG: sequence_number: 505 = 0x01f9 7298:2016-04-13 10:38:58 [12229] [6] DEBUG: service_type: "USSD" 7299:2016-04-13 10:38:58 [12229] [6] DEBUG: source_addr_ton: 1 = 0x0001 7300:2016-04-13 10:38:58 [12229] [6] DEBUG: source_addr_npi: 1 = 0x0001 7301:2016-04-13 10:38:58 [12229] [6] DEBUG: source_addr: "601030648xx" 7302:2016-04-13 10:38:58 [12229] [6] DEBUG: dest_addr_ton: 0 = 0x 7303:2016-04-13 10:38:58 [12229] [6] DEBUG: dest_addr_npi: 0 = 0x 7304:2016-04-13 10:38:58 [12229] [6] DEBUG: destination_addr: NULL 7305:2016-04-13 10:38:58 [12229] [6] DEBUG: esm_class: 0 = 0x 7306:2016-04-13 10:38:58 [12229] [6] DEBUG: protocol_id: 0 = 0x 7307:2016-04-13 10:38:58 [12229] [6] DEBUG: priority_flag: 0 = 0x 7308:2016-04-13 10:38:58 [12229] [6] DEBUG: schedule_delivery_time: NULL 7309:2016-04-13 10:38:58 [12229] [6] DEBUG: validity_period: NULL 7310:2016-04-13 10:38:58 [12229] [6] DEBUG: registered_delivery: 0 = 0x 7311:2016-04-13 10:38:58 [12229] [6] DEBUG: replace_if_present_flag: 0 = 0x 7312:2016-04-13 10:38:58 [12229] [6] DEBUG: data_coding: 15 = 0x000f 7313:2016-04-13 10:38:58 [12229] [6] DEBUG: sm_default_msg_id: 0 = 0x 7314:2016-04-13 10:38:58 [12229] [6] DEBUG: sm_length: 1 = 0x0001 7315:2016-04-13 10:38:58 [12229] [6] DEBUG: short_message: "1" 7316:2016-04-13 10:38:58 [12229] [6] DEBUG: ussd_service_op: 7317:2016-04-13 10:38:58 [12229] [6] DEBUG:Octet string at 0x7feef0006220: 7318:2016-04-13 10:38:58 [12229] [6] DEBUG: len: 1 7319:2016-04-13 10:38:58 [12229] [6] DEBUG: size: 2 7320:2016-04-13 10:38:58 [12229] [6] DEBUG: immutable: 0 7321:2016-04-13 10:38:58 [12229] [6] DEBUG: data: 12 . 7322:2016-04-13 10:38:58 [12229] [6] DEBUG:Octet string dump ends. 7323:2016-04-13 10:38:58 [12229] [6] DEBUG: ussd_hlr: "60" 7324:2016-04-13 10:38:58 [12229] [6] DEBUG: ussd_optional: "00100434570DB0FF" 7325:2016-04-13 10:38:58 [12229] [6] DEBUG: ussd_srv_op: 7326:2016-04-13 10:38:58 [12229] [6] DEBUG:Octet string at 0x7feef0001150: 7327:2016-04-13 10:38:58 [12229] [6] DEBUG: len: 1 7328:2016-04-13 10:38:58 [12229] [6] DEBUG: size: 2 7329:2016-04-13 10:38:58 [12229] [6] DEBUG: immutable: 0 7330:2016-04-13 10:38:58 [12229] [6] DEBUG: data: 12 . 7331:2016-04-13 10:38:58 [12229] [6] DEBUG:Octet string dump ends. 7332:2016-04-13 10:38:58 [12229] [6] DEBUG: SMPP PDU dump ends. Seems like NULL destination are processed but smsbox won't proceed. Anything else than can I do from my side to get this working Hi Arif, sorry for the long delay in response. Please let me know in case this is still an ongoing issue, and we will try to assist. -- 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 ---
Re: Load balancing MT with preferred SMSC
Am 21.09.2016 08:25, schrieb Davor Spasoski: Hi, I realized yesterday that the reason the allowed/preferred trickery doesn’t work is because opensmppbox doesn’t pass smsc-id dynamically. It’s either a static value using the route-to-smsc directive or it’s blank if this is omitted. The whole point of my usecase was to have different ESMEs routed to different smscs and all that by using a single opensmpp instance (IP/port) due to specific circumstances of the case I need to solve. AFAICS, for this to work it needs development. Hi Davor, correct, the opensmppbox isn't able to handle such routing internally. For the purposes you intend to it's more suitable to use the commercial Kannel SMPP v5.0 server (smppbox), which is a true virtual SMSC solution allowing the same connection scheme, but with a major benefit in configuration ability and flexibility. Please let me know if you would like to hear more details and we can arrange for a test-drive on your own system to get going. -- 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 ---
Re: USSD with Kannel
Am 11.04.2016 17:19, schrieb Stipe Tolj:
I'll prepare a simple patch that let's you resolve the issue.
please try to apply the following patch to the source tree and re-compile.
--
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
---
Index: gw/bb_http.c
===
--- gw/bb_http.c(revision 5150)
+++ gw/bb_http.c(working copy)
@@ -347,24 +347,19 @@
return octstr_create("Black/white lists re-loaded");
}
-static Octstr *httpd_remove_message(List *cgivars, int status_type)
+static Octstr *httpd_dequeue_messages(List *cgivars, int status_type)
{
Octstr *reply;
-Octstr *message_id;
+Octstr *smsc;
if ((reply = httpd_check_authorization(cgivars, 0))!= NULL) return reply;
if ((reply = httpd_check_status())!= NULL) return reply;
/* check if the smsc id is given */
-message_id = http_cgi_variable(cgivars, "id");
-if (message_id) {
-if (octstr_len(message_id) != UUID_STR_LEN)
-return octstr_format("Message id should be %d characters long",
UUID_STR_LEN);
-if (bb_remove_message(message_id) == -1)
-return octstr_format("Could not remove message id `%s'",
octstr_get_cstr(message_id));
-else
-return octstr_format("Message id `%s' removed",
octstr_get_cstr(message_id));
-} else
-return octstr_create("Message id not given");
+smsc = http_cgi_variable(cgivars, "smsc");
+if (smsc) {
+} else {
+
+}
}
/* Known httpd commands and their functions */
@@ -387,7 +382,7 @@
{ "add-smsc", httpd_add_smsc },
{ "remove-smsc", httpd_remove_smsc },
{ "reload-lists", httpd_reload_lists },
-{ "remove-message", httpd_remove_message },
+{ "dequeue", httpd_dequeue_messages },
{ NULL , NULL } /* terminate list */
};
Index: gw/smsc/smsc_smpp.c
===
--- gw/smsc/smsc_smpp.c (revision 5150)
+++ gw/smsc/smsc_smpp.c (working copy)
@@ -609,8 +609,10 @@
/*
* Follows SMPP spec. v3.4. issue 1.2
* it's not allowed to have destination_addr NULL
+ * USSD service type MAY have a NULL value, so allow this.
*/
-if (pdu->u.deliver_sm.destination_addr == NULL) {
+if (pdu->u.deliver_sm.destination_addr == NULL &&
+octstr_case_compare(pdu->u.deliver_sm.service_type,
octstr_imm("USSD")) != 0) {
error(0, "SMPP[%s]: Malformed destination_addr `%s', may not be empty.
"
"Discarding MO message.", octstr_get_cstr(smpp->conn->id),
octstr_get_cstr(pdu->u.deliver_sm.destination_addr));
Re: USSD with Kannel
ot normally familiar with the notion of a source address for a short message, e.g., paging systems, voice mail system. But this doesn't imply that a destination_addr MAY NOT be NULL. I'll prepare a simple patch that let's you resolve the issue. Can you please share the specification documents for the USSD gateway (how the TLVs are defined, etc) in a private email to me. We'll go ahead and make sure we can handle the vendor cleanly. Stipe -- 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 ---
[ANNOUNCE-REMINDER] GSMA MWC 2016 Meeting opportunity
Dear Kannel users,
a couple of more days to go reminder:
We are happy to announce that several Kannel group team members will be
attending this years GSMA Mobile World Congress in Barcelona, Spain from
22-24 Feb 2016.
If you are a mobile network operator, a messaging aggregator, a system
integrator for mobile networks and/or services, or an enterprise
representative in the mobile business, and would like to meet us on the
MWC event for discussion about
- commercial support/consulting for Kannel deployments, development
and/or integration
- our commercial Support Level Agreements (SLA) for business critical
Kannel installations
- our commercial add-on products
- Kannel SMPP v5.0 server (smppbox)
- Kannel SMPP v5.0 proxy filter (smppproxy)
- Kannel vSMSC (virtual SMSC) solutions
- Kannel SMS hubbing (iwsmsc)
- Kannel-CG (carrier-grade) WAP/Mobile Internet Gateway (kannel-cg)
- Kannel-CG (carrier-grade) Data Control PCRF (kannel-pcrf)
- Kannel-CG (carrier-grade) MMSC (kannel-mmsc)
- future technology integrations
- RCS Interworking, ...
- to discuss any other topic...
please feel free to set-up an appointment with us at the MWC via our
main web site URL http://www.kannel.org/, or via the direct interface to
the scheduling planer via URL https://kannel.appointlet.com/.
We're looking forward to see you at MWC in Barcelona.
--
Best Regards,
Stipe
---
Koelner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
[ANNOUNCE] GSMA MWC 2016 Meeting opportunity
Dear Kannel users, we are happy to announce that several Kannel group team members will be attending this years GSMA Mobile World Congress in Barcelona, Spain from 22-24 Feb 2016. If you are a mobile network operator, a messaging aggregator, a system integrator for mobile networks and/or services, or an enterprise representative in the mobile business, and would like to meet us on the MWC event for discussion about - commercial support/consulting for Kannel deployments, development and/or integration - our commercial Support Level Agreements (SLA) for business critical Kannel installations - our commercial add-on products - Kannel SMPP v5.0 server (smppbox) - Kannel SMPP v5.0 proxy filter (smppproxy) - Kannel vSMSC (virtual SMSC) solutions - Kannel SMS hubbing (iwsmsc) - Kannel-CG (carrier-grade) WAP/Mobile Internet Gateway (kannel-cg) - Kannel-CG (carrier-grade) Data Control PCRF (kannel-pcrf) - Kannel-CG (carrier-grade) MMSC (kannel-mmsc) - future technology integrations - RCS Interworking, ... - to discuss any other topic... please feel free to set-up an appointment with us at the MWC via our main web site URL http://www.kannel.org/, or via the direct interface to the scheduling planer via URL https://kannel.appointlet.com/. We're looking forward to see you at MWC in Barcelona. -- 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 ---
Re: Multiple SMPP objects overlapping
Am 14.07.2015 22:11, schrieb Bobby Richardson:
Hello:
My organization uses Kannel logs everyday and is experiencing a
technical challenge recently.
For this issue, I searched through kannel.org and unfortunately could
not find any helpful solution.
From attached, you may see 2 SMPP objects (first one is a complete one;
lines between 1 and 16 and the second one is just a partial) with 2
different connection names (ie. SMPP[SMSC1_ATT_RSS] and
SMPP[SMSC2_ATT_RSS]) .
Before the second SMPP object starts, I expected “SMPP PDU dump ends.”
first and then “SMPP[SMSC2_ATT_RSS]: Got PDU:”. “SMPP[SMSC2_ATT_RSS]:
Got PDU:” was placed in line 14 before the first SMPP object ends.
Is this normal sequence? In many cases, I have seen “SMPP PDU dump
ends.” as an indication of end of a SMPP. And then after this, another
SMPP may start with “SMPP[SMSC2_ATT_RSS]: Got PDU:”.
Do you have any suggestion for how to let Kannel log records one SMPP
object at a time without getting mixed?
Is there any specific parameter in the Configuration file to control
this case?
Hello Bobby,
the log parts show that the mixing happens due to thread concurrency.
Since every SMPP SMSC connection runs in it's own thread, there is no
guaranteed order of thread execution and therefore also no grantee
in that a particular SMPP PDU dump is in-line complete before any
other vectorized in.
So, is this mixing a feature or a bug? It's a feature actually, since we
COULD use mutex locking to perform the SMPP PDU dump completely and then
release the lock, but this would generate a high concurrency delay on
the log file writing, and therefore also in the PDU processing itself.
Alvaro suggested a way to avoid this, by using individual smsc group
specific log-files.
We DO have code branches in our internal trees that allow mutex locking,
though we never used this in high IO scenarios.
If you need any further assistance, please feel free to email me.
--
Best Regards,
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/
mailto:stolj_{at}_kannel.org mailto:st_{at}_tolj.org
---
Re: Kannel SMS gateway with Oracle Enterprise Linux 6 US 64 bit
Am 03.06.2015 19:44, schrieb Charbel DAOUD:
Dear Kannel Users,
I'm Charbel Daoud
We have found online the Kannel SMS Gateway Product, and we started
testing it on our machines that run Oracle Enterprise Linux 6 US 64 bit
as Operating System .
When we tried to install libxml2 library, it didn't work and it seems
that the library is not compatible with this OS.
We would like to know if Kannel works under Oracle Enterprise Linux
System and if we can find an alternative to libxml2 ( the other
required libraries ) on this operating system specifically.
Hello Charbel,
AFAIK, Oracle Enterprise Linux is compatible with RHEL (aka CentOS), so
this SHOULD NOT be a any problem.
Please provide any specific details about the issue if you couldn't
resolve yet.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/
mailto:stolj_{at}_kannel.org mailto:st_{at}_tolj.org
---
Re: Opensmppbox throughput
Am 02.07.2015 10:37, schrieb ahmed qadeer:
Hello Everyone
Is it possible to configure a throughput for each smppbox login created?
Or can there be a limit on each login created?
Hello Ahmed
the Kannel opensmppbox can not handle any throughput in terms of TPS
(transactions per second) control.
For this feature, along with a full set of additional features, please
consider using the commercial Kannel SMPP v5.0 server (smppbox).
Please let me know if you are interested in it, and I can forward you
further information on the product.
--
Best Regards,
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/
mailto:stolj_{at}_kannel.org mailto:st_{at}_tolj.org
---
Re: One SMSC Goes Dead periodically
Am 20.06.15 15:44, schrieb Alvaro Cornejo:
Hi
Can you also attach some logs of your failing smsc?
bearerbox event log (aka beaerbox.log) in DEBUG level would be the most
interesting to see why the SMSC goes dead.
Most likely you are missing to fit the enquire_link PDU interval
requirements that the SMSC may have. And this causes the SMSC to
disconnect you and maybe put you on a grey-list for a period of time not
allowing you to re-connect.
But this is all speculation, we need some logs to verify what goes on
directly.
--
Best Regards,
Stipe
---
Koelner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
[ANNOUNCE] GSMA MWC 2015 Meeting opportunity
Dear users,
we are happy to announce that several Kannel group team members will be
attending this years GSMA Mobile World Congress in Barcelona, Spain from
2-5 March 2015.
If you are a mobile network operator, a messaging aggregator, a system
integrator for mobile networks and/or services, or an enterprise
representative in the mobile business, and would like to meet us on the
venue for discussion about
- commercial support/consulting for Kannel deployments, development
and/or integration
- our commercial add-on products
- Kannel SMPP v5.0 server (smppbox)
- Kannel SMPP v5.0 proxy filter (smppproxy)
- Kannel vSMSC (virtual SMSC) solutions
- Kannel SMS hubbing (iwsmsc)
- Kannel-CG (carrier-grade) Mobile Internet Gateway (kannel-cg)
- Kannel-CG (carrier-grade) MMSC (kannel-mmsc)
- our commercial Support Level Agreements (SLA) for business critical
Kannel installations
- future technology integrations
- RCS Interworking, ...
- to discuss any other topic...
please feel free to set-up an appointment with us at the MWC via our
main web site URL http://www.kannel.org/, or via the direct interface to
the scheduling planer via URL https://kannel.appointlet.com/.
We're looking forward to see you at MWC in Barcelona.
Best Regards,
Stipe Tolj
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Same Sequence Number for many PDUs
Am 26.11.2014 20:51, schrieb Amir Mahmoud:
Hello Guys,
I'm facing abnormal behavior with my kannel (1.4.4) installed on CentOS 7,
I have found that when i submit SMS to my number and after receiving it
on my handset that kannel still keeps the sms on the store trying to
re-submit it again and again to the SMSC and with each attempt i receive
it again on my handset and finally after finishing the retrials kannel
log it with status DISCARD
I have set the bearerbox in debug mode and found that kannel already
sent submit_sm successfully PDU but it didn't receive submit_sm_resp
and i think this is the reason behind keeping it in the store and
discard it.
So, i have taken tcp dump and found that both submit_sm PDU and
submit_sm_resp already sent but i can't understand why kannel didn't
handle it Also i have found unusual thing while checking the dump, i
found that many PDUs are having the sequence number (Enquire_Link
Submit_SM)
Is that normal and why kannel is doing so ?
please provide corresponding log file and tcpdump (pcap) parts of this
so we can look into it.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Kannel 1.5 on a 64-bit OS
Am 10.11.2014 19:30, schrieb Lamasuta Franck:
Hi all,
We are running Kannel 1.5 on a server with RHEL4 (32 bits) and we are
using the SMPP, CIMD2 and HTTP interfaces.
We would like to upgrade the server to RHEL 6.4 (64 bits).
Is Kannel fully compatible with a 64-bit OS?
Kannel itself and the commercial Kannel SMPP v5.0 server (smppbox) are
in production use on numerous x86_64-centos-6 (RHEL 6) sites around the
globe without any issue based on 64bit.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Kannel Redis Dlr
Am 11.11.2014 05:19, schrieb Tapan Kumar Thapa:
Hi,
I have not heard anything from anyone on this (Good or Bad). Does this
means that no-one is using Redis as DLR storage?
I have compiled latest kannel (svn-r5110) from svn with Redis DLR support.
Everything is working fine as i have tested 5-10 messages and DLRs are
getting stored under Redis and getting removed too in case we received dlr.
Just wondering if i can put the same under production?
Is anyone using the same combination under production with 1-2 million
messages per day.
Is anyone facing any issues with kannel DLR with Redis?
we have been regression testing the DLR redis support quite a bit before
committing the code to the mainline Kannel.
And it IS included in the Kannel 1.4.4 stable release, so you SHOULD
consider it stable for production.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: [ANNOUNCE] Kannel 1.4.4 stable release available
Am 27.08.2014 17:39, schrieb DHC Admin:
i have fixed the same problem by installing all the needed packages,
deleting the gateway-1.4.4 and starting the whole thing from scratch, re
running ./configure is not enough, so it looks.
At first I was lacking byacc and bison
Regards
thanks a lot for reporting. We assumed it's simply the missing 'bison'
and the way the pre-installed yacc does the compilation that messes up
the build.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/
mailto:stolj_{at}_kannel.org mailto:st_{at}_tolj.org
---
Re: [ANNOUNCE] Kannel 1.4.4 stable release available
Am 08.08.2014 11:30, schrieb Hanh Le Bich:
Hello,
I have got error when do make, please help.
app@application:/usr/src/gateway-1.4.4$ sudo make -j 24
...
gcc -std=gnu99 -D_REENTRANT=1 -I. -Igw -g -O2 -D_XOPEN_SOURCE=600
-D_BSD_SOURCE -D_LARGE_FILES= -I/usr/include/libxml2
-I/usr/local/lib/include -I/usr/include/mysql -o gw/bearerbox.o -c
gw/bearerbox.c
gcc -std=gnu99 -D_REENTRANT=1 -I. -Igw -g -O2 -D_XOPEN_SOURCE=600
-D_BSD_SOURCE -D_LARGE_FILES= -I/usr/include/libxml2
-I/usr/local/lib/include -I/usr/include/mysql -o gw/smsbox.o -c gw/smsbox.c
y.tab.c:348:5: error: conflicting types for ‘ws_yy_parse’
In file included from wmlscript/wsgram.y:15:0:
./wmlscript/wsint.h:296:5: note: previous declaration of
‘ws_yy_parse’ was here
int ws_yy_parse(void *context);
^
wmlscript/wsgram.c:63:25: error: conflicting types for ‘ws_yy_parse’
#define yyparse ws_yy_parse
^
y.tab.c:1508:1: note: in expansion of macro ‘yyparse’
In file included from wmlscript/wsgram.y:15:0:
./wmlscript/wsint.h:296:5: note: previous declaration of
‘ws_yy_parse’ was here
int ws_yy_parse(void *context);
^
wmlscript/wsgram.y: In function ‘ws_yy_parse’:
wmlscript/wsgram.y:122:23: error: ‘pctx’ undeclared (first use in
this function)
{ ws_error_syntax(pctx, @1.first_line); }
^
wmlscript/wsgram.y:122:23: note: each undeclared identifier is reported
only once for each function it appears in
In file included from wmlscript/wslexer.c:72:0:
y.tab.h:262:5: error: conflicting types for ‘ws_yy_parse’
In file included from wmlscript/wslexer.c:70:0:
wmlscript/wsint.h:296:5: note: previous declaration of ‘ws_yy_parse’
was here
int ws_yy_parse(void *context);
^
In file included from wmlscript/wsstree.c:72:0:
y.tab.h:262:5: error: conflicting types for ‘ws_yy_parse’
In file included from wmlscript/wsstree.c:71:0:
wmlscript/wsint.h:296:5: note: previous declaration of ‘ws_yy_parse’
was here
int ws_yy_parse(void *context);
^
Makefile:231: recipe for target 'wmlscript/wsgram.o' failed
make: *** [wmlscript/wsgram.o] Error 1
make: *** Waiting for unfinished jobs
Makefile:231: recipe for target 'wmlscript/wslexer.o' failed
make: *** [wmlscript/wslexer.o] Error 1
Makefile:231: recipe for target 'wmlscript/wsstree.o' failed
make: *** [wmlscript/wsstree.o] Error 1
app@application:/usr/src/gateway-1.4.4$
most likely there is an issue with the yacc parser on your system. Do
you have the 'bison' package installed?
The files that are referenced here are generated during the initial
make run. Please try to re-create the files from the package itself and
then re-compile.
If that does not help, please indicate the issue via our bug tracking
system (see website) and report with architecture and Linux distro you
are using.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
Kannel Foundation tolj.org system architecture
http://www.kannel.org/http://www.tolj.org/
mailto:stolj_{at}_kannel.org mailto:st_{at}_tolj.org
---
[ANNOUNCE] Kannel 1.4.4 stable release available
The Kannel Group is pleased to announce the availability of Kannel 1.4.4
stable release via our web site at URL
http://www.kannel.org/download.shtml
Please find attached the NEWS file section for the 1.4.4 stable release.
Best Regards,
Stipe Tolj
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
NEWS about Kannel: Open Source WAP and SMS Gateway version 1.4.4
This is a STABLE version. It should be usable for production systems.
Please do report problems to the Kannel bug tracking system available at
http://bugs.kannel.org/ or send a mail to de...@kannel.org (the development
mailing list).
Changes since version 1.5.0 devel:
[*** Beware that the version move from 1.5.0 devel to 1.4.4 stable contains
numerous change sets, with major bug fixes and improvements. Following is a
summary of the main issues. For a complete and detailed set of changes please
refer to the specific ChangeLog in the doc/ directory of the distribution. ***]
Compatibility breakers:
* SMPP config directives can have ONLY ONE session, either config directive
'port' or 'receive-port' can be set to identify if this is a bind as
transmitter or receiver. Configurations with both config directives will
PANIC at startup time.
New features:
* Added DLR support for redis.
* Added DLR support for spool directories.
* Added DLR support for SQLite3.
* Added SMSC support for GSMA OneAPI/Ericsson ParlayX via gSOAP.
* Added SMSC SMPP support for optional TLVs of response PDUs via meta-data.
* Added 'dead-start' feature for SMSC groups.
* Added SMSC HTTP generic support for meta-data.
* Added smsbox support to listen to specific interfaces.
Bugfixes:
* Fixed smsbox HTTP call starvation while retrying.
* Fixed various minor memory leaks for smsbox reported by valgrind.
* Converted various PANIC conditions to WARNING/ERROR conditions to keep
the operations running.
* Fixed various issues with DLR handling.
* Fixed various segmentation fault possibilities.
* Fixed various internal character transcoding issues.
* Fixed issues for smsbox shutdown.
* Fixed bearerbox MO routing logic.
See ChangeLog for detailed information.
Re: SMPP Port Error
Am 10.06.2014 20:43, schrieb Faizan Mirza:
Hello,
I was using kannel 1.4.3 it was working fine, now when i updated from
svn it is working fine but giving me error regarding ports of SMPP..
Error: Configuration file can only have port or receive-port. Usage of
both in one group is deprecated!
how do i add both port and receive-port to receive delivery report..
correct, we have DEPRECATED the support of both 'bind_transmitter' and
'bind_receiver' session in ONE logical Kannel 'group = smsc' context.
Reasons are of technical nature, since the abstracted SMSCConn struct
context and it's logic isn't able to cleanly abstract BOTH states of the
sessions, that's why we migrate from the approach of having both
sessions configurable in one group to seperate groups.
Hence, you go from:
# bind_transmitter AND bind_receiver
group = smsc
smsc = smpp
...
port =
receive-port = XXX
...
to:
# bind_transmitter
group = smsc
smsc = smpp
...
port =
...
# bind_receiver
group = smsc
smsc = smpp
...
receive-port = XXX
...
Which means formally: The configuration of 1.5.0 (and before) will
BREAK for 1.5.1, which we're about to release ASAP. This will be also
noted in the NEWS section as compatibility breaker.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Redis delivery report DLR backend
Am 06.03.2014 12:37, schrieb Lorenzo Bagni:
Hi all,
I'm facing a blocking problem on redis backend for delivery report.
I'm sendig correctly (and receive on my MT) but the bearerbox hangs when
try to write on redis:
smsc log:
2014-03-06 11:44:54 [25724] [7] DEBUG: SMPP[mobytusaprod]: Got PDU:
2014-03-06 11:44:54 [25724] [7] DEBUG: SMPP PDU 0x7f6c08000a10 dump:
2014-03-06 11:44:54 [25724] [7] DEBUG: type_name: submit_sm_resp
2014-03-06 11:44:54 [25724] [7] DEBUG: command_id: 2147483652
tel:2147483652 = 0x8004
2014-03-06 11:44:54 [25724] [7] DEBUG: command_status: 0 = 0x
2014-03-06 11:44:54 [25724] [7] DEBUG: sequence_number: 2 = 0x0002
2014-03-06 11:44:54 [25724] [7] DEBUG: message_id:
2014-03-06 11:44:54 [25724] [7] DEBUG:Octet string at 0x7f6c080011a0:
2014-03-06 11:44:54 [25724] [7] DEBUG: len: 36
2014-03-06 11:44:54 [25724] [7] DEBUG: size: 37
2014-03-06 11:44:54 [25724] [7] DEBUG: immutable: 0
2014-03-06 11:44:54 [25724] [7] DEBUG: data: 37 35 33 31 62 34 32
61 2d 66 34 34 66 2d 34 33 7531b42a-f44f-43
2014-03-06 11:44:54 [25724] [7] DEBUG: data: 38 31 2d 39 63 35 61
2d 36 31 37 65 32 32 33 31 81-9c5a-617e2231
2014-03-06 11:44:54 [25724] [7] DEBUG: data: 36 30 35 63
605c
2014-03-06 11:44:54 [25724] [7] DEBUG:Octet string dump ends.
2014-03-06 11:44:54 [25724] [7] DEBUG: SMPP PDU dump ends.
2014-03-06 11:44:54 [25724] [7] DEBUG: new group created `smpp'
2014-03-06 11:44:54 [25724] [7] DEBUG: group=`smpp'
key=`mobyt_campaignid' value=`1245'
2014-03-06 11:44:54 [25724] [7] DEBUG: DLR[redis]: Adding DLR
smsc=mobytusaprod, ts=7531b42a-f44f-4381-9c5a-617e2231605c, src=51303,
dst=393284677782, mask=31, boxc=
2014-03-06 11:44:54 [25724] [7] DEBUG: Adding DLR into keystore
bearerbox log:
2014-03-06 11:44:33 [25724] [9] DEBUG: Started thread 10
(gw/bb_boxc.c:boxc_sender)
2014-03-06 11:44:33 [25724] [10] DEBUG: Thread 10
(gw/bb_boxc.c:boxc_sender) maps to pid 25724.
2014-03-06 11:44:54 [25724] [9] DEBUG: boxc_receiver: sms received
2014-03-06 11:44:54 [25724] [9] DEBUG: send_msg: sending msg to box:
127.0.0.1
2014-03-06 11:44:54 [25724] [7] PANIC: /usr/sbin/bearerbox() [0x4a7f7c]
2014-03-06 11:44:54 [25724] [7] PANIC: /lib64/libpthread.so.0(+0xf710)
[0x7f6c21df5710]
2014-03-06 11:44:54 [25724] [7] PANIC: /usr/sbin/bearerbox() [0x48d407]
2014-03-06 11:44:54 [25724] [7] PANIC: /usr/sbin/bearerbox() [0x41fa63]
2014-03-06 11:44:54 [25724] [7] PANIC:
/usr/sbin/bearerbox(dlr_add_real+0x3a3) [0x41cf63]
2014-03-06 11:44:54 [25724] [7] PANIC: /usr/sbin/bearerbox() [0x4682c2]
2014-03-06 11:44:54 [25724] [7] PANIC: /usr/sbin/bearerbox() [0x469395]
2014-03-06 11:44:54 [25724] [7] PANIC: /usr/sbin/bearerbox() [0x491c19]
2014-03-06 11:44:54 [25724] [7] PANIC: /lib64/libpthread.so.0(+0x79d1)
[0x7f6c21ded9d1]
2014-03-06 11:44:54 [25724] [7] PANIC: /lib64/libc.so.6(clone+0x6d)
[0x7f6c20b85b6d]
I've compiled kannel 1.5.0 trunk version 5081:
Kannel bearerbox version `svn-runknown'. Build `Mar 5 2014 14:57:57',
compiler `4.4.7 20120313 (Red Hat 4.4.7-4)'. System Linux, release
2.6.32-431.el6.x86_64, version #1 SMP Fri Nov 22 03:15:09 UTC 2013,
machine x86_64. Hostname xxx.xxx.xxx, IP xxx.xxx.xxx.xxx. Libxml version
2.7.6. Using OpenSSL 1.0.1e-fips 11 Feb 2013. Compiled with MySQL
5.1.71, using MySQL 5.1.71. Using hiredis API 0.10.1 Using native malloc.
The same flow works perfectly if I use the MySql backend, so I guess a
misconfiguration, here's the redis related config:
dlr-storage = redis
group = redis-connection
id = redisdlr
host = 127.0.0.1
port = 6379
#password = foo
database = 0
max-connections = 1
group = dlr-db
id = redisdlr
table = dlr
ttl = 604800
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
Redis works on the same box of kannel, accepts bindigs on all
intefraces, and I've try to perform a CRUD operation from redis-cli
without problems.
Hi Lorenzo,
first of all, thanks a lot for reporting the bug, along with the
comprehensive filing into the redmine bug tracking system.
I have addressed this today and corresponding fixes have been committed
to the SVN trunk.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
[ANNOUNCE] GSMA MWC 2014 Meeting opportunity
Dear users,
as you may have noticed from our main web page, we are attending the
GSMA Mobile World Congress 2014 in Barcelona, Spain.
If you are a SMS aggregator, a GSM/CMDA network operator, a system
integrator for mobile networks or an enterprise representative in the
mobile business, and would like to meet us on the venue in order
- to discuss commercial support for Kannel development and integration
- to discuss commercial add-on components we are providing
- Kannel SMPP v5.0 server (smppbox)
- Kannel SMPP v5.0 proxy filter (smppproxy)
- Kannel CG (carrier-grade) WAP 1.2.1/2.0 gateway (kannel-cg)
- Kannel MMSC (kannel-mmsc)
- ...
- to discuss about commercial support supper level agreements (SLAs) for
commercial grade Kannel deployments
- to discuss any other topics...
please feel free to set-up an appointment with us at the MWC via our
main web site URL http://www.kannel.org/, or via the direct interface to
the scheduling planer via URL https://kannel.appointlet.com/.
We're looking forward to see you.
Best Regards,
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: SMPP TLVs on bind_transceiver_resp and submit_sm_resp
Am 20.01.2014 23:25, schrieb Paulo Correia:
Hi!
I'm trying to find out if there is a way to retrieve TLV data sent from
a SMSC on the PDUs:
* bind_transceiver_resp
* submit_sm_resp
I already defined the TLVs on the configuration and the log indicates
kannel does receive the data, but how can I retrieve it to an external
application?
Here is an example from the log:
2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x0210)
2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 1
2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x1401)
2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 7
2014-01-20 18:26:42 [39688] [6] DEBUG: Found configured optional
parameter `XXX_credit'
2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU:
2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU 0x7f893c001570 dump:
2014-01-20 18:26:42 [39688] [6] DEBUG: type_name: bind_transceiver_resp
2014-01-20 18:26:42 [39688] [6] DEBUG: command_id: 2147483657 = 0x8009
2014-01-20 18:26:42 [39688] [6] DEBUG: command_status: 0 = 0x
2014-01-20 18:26:42 [39688] [6] DEBUG: sequence_number: 1 = 0x0001
2014-01-20 18:26:42 [39688] [6] DEBUG: system_id: lnstsmpp
2014-01-20 18:26:42 [39688] [6] DEBUG: sc_interface_version: 52 = 0x0034
2014-01-20 18:26:42 [39688] [6] DEBUG: XXX_credit: 000
2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU dump ends.
...
2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter tag (0x1401)
2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter length read as 7
2014-01-20 18:30:19 [39688] [6] DEBUG: Found configured optional
parameter `XXX_credit'
2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU:
2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU 0x7f893c0014f0 dump:
2014-01-20 18:30:19 [39688] [6] DEBUG: type_name: submit_sm_resp
2014-01-20 18:30:19 [39688] [6] DEBUG: command_id: 2147483652 = 0x8004
2014-01-20 18:30:19 [39688] [6] DEBUG: command_status: 0 = 0x
2014-01-20 18:30:19 [39688] [6] DEBUG: sequence_number: 2 = 0x0002
2014-01-20 18:30:19 [39688] [6] DEBUG: message_id: 227b7cfd
2014-01-20 18:30:19 [39688] [6] DEBUG: XXX_credit: 10238900
2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU dump ends.
When the message that resulted on the submit_sm_resp was sent to kannel,
I used a dlr-mask=31 and dlr-url with a parameter meta=%D but the first
call to the URL, created by the submit_sm_resp (comes with the %A value
as ACK/), came up with an empty meta value.
I'm using kannel 1.5.0, svn r5065 on these tests and couldn't find any
way that TLVs are processed on the given PDUs on the source code...
this is NOT supported at the moment. The intermediate DLR SMSC SUCCESS
does not handle any optional TVLs coming inside a submit_sm_resp PDU.
I have submitted a patchset to the devel@ mailing list that supports
this, at least for submit_sm_resp. I don't see a practical way to do it
for the bind resp PDUs at the moment.
See [Msg-Id: 52dec1f8.3090...@kannel.org]
Please test the patchset and confirm in the mail thread on the devel@
mailing list. Moving the discussion to there, since it's development
related.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
[FYI] ** Happy New Year and new release cycles **
Dear lists,
on behalf of the core Kannel developers we wish you all a HAPPY and
BLESSED NEW YEAR 2014!
I'd like to take the opportunity to push forward some of the patchsets
that have been posted to the devel mailing list, but haven't made it yet
into the SVN trunk tree.
Going into the mainline SVN trunk tree should go:
- graceful restarting patchset
- redis support for DLR storage
- smsbox non-blocking HTTP retries
both patches are available and will be committed to the SVN trunk. When
done, I would like to go for another Kannel 1.5.1 devel release.
Bringing all the latest changes to a release level.
Then having a phase of problem resolution in for the reports that come
in, followed by a Kannel 1.6.0 stable release with all the above sets
included.
In addition there are several more patchsets that need to go into the
mainline tree, which are prepared so far:
- abstracted message storage; at the moment the message store-file and
spool are pretty bound to the bearerbox incarnation, which we have
abstracted the way the DLR storage is abstract, so anyone can more
easily implement an own message store here, i.e. using a fast
distributed in-memory keystore (redis).
- auto-retry via a list smsc-id patchset; means we can denominate a list
of smsc-id's in the msg-sms.smsc_id and in case we get a not acecpted
by a first smsc-id we automatically retry with the next in the list, etc.
- matchset patchset; the data structure that allows may finer matching
definitions for any cases where we use regex values, including support
for TRE library which allows fuzzy logic matching inside regex notations.
Comments and thoughts as always welcome.
Cheers,
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Segmentation fault in SVN r5063
Am 27.11.2013 16:11, schrieb ha...@aeon.pk:
Hi,
I am having severe error of bearerbox showing segmentation fault in
SVN-r5063 whenever bulk SMS are sent. If someone needs a
diagnose/symptoms, please let me know which files/trace to send to you.
Regards,
please provide a corresponding gdb backtrace of the core file, so we can
see exactly where the segfault is happening.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: WAP Gateway
Am 18.09.2013 12:34, schrieb Stuart Eoghan:
We are looking to deploy a new WAP Gateway in our network, to replace
the existing one which is falling over regularly.
Hi Stuart,
please let me answer you questions inlined below:
I have a few questions:
Is the WAP Kannel gateway in use commercially in many networks?
the normal Kannel WAP gateway, means the WAP 1.2.1 parts are
officially not running in any live MNO networks. We have informations
that some Latin American and Asian networks have it as a kind of
fallback for their main commercial vendors.
Beside the normal Kannel, there are a numerous set of Kannel-CG
installation at MNOs and MVNOs. The commercial Kanenl-CG (carier-grade)
WAP gateway that we provide is a full featured WAP 1.2.1 and WAP 2.0
gateway, including a full featured RADIUS server and on-the-fly byte
accounting server.
We are proud that Kannel-CG has been substituting several major
commercial vendor installations, including deployments from Huawei,
Ericsson, Openwave and Acision - by outperforming all of these vendors
in terms of maximum concurrency performance.
Does it support all of or most of the last WAP protocol?
The open source Kannel does support WAP 1.2.1. Though, there are some
flaws in the WAP 1.2.1 stack, especially when used under high
concurrency load. This was the main reason we have re-written the WAP
1.2.1 stack with more effective data structures and releasing this in
combination with WAP 2.0 (HTTP proxy capability) support into the
commercial Kannel-CG product.
Would it be capable of approximately 70 Transactions per second WAP Pulls?
Should, that's not a huge amount of concurrent traffic. I don't have any
hard figures for the open source Kannel WAP part, the Kannel-CG
installations handle from 800 to 2400 TPS concurrently, depending on
hardware and architecture layout.
What Hardware would be recommended to support that level of throughput?
The 70 TPS should be working out-of-the-box for any normal production
class machine of today. Having a nice amount of RAM is always welcome,
but not necessary.
Thanks for any help that can be given.
you're absolutely welcome. Please let me know if I can assist you any
further, either with the open source Kannel parts for the WAP 1.2.1 or
even with the commercial Kannel-CG WAP Gateway.
Best Regards,
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Kannel + OpenSMPP box
Am 23.05.2013 19:21, schrieb spameden:
Unfortunately there is no solution.
You can modify yourself source code to achieve it.
Or you can look at the commercial SMPPBox, msg st...@tolj.org
mailto:st...@tolj.org for details.
I'll be pleased to provide more information about the commercial add-on
Kannel SMPP v5.0 server (smppbox). Please send me a note to
'st...@kannel.org' or 's...@tolj.org' for further information.
Best Regards,
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: SMSC moving away from SMPP
Am 11.03.2013 12:46, schrieb Milan P. Stanic:
On Mon, 2013-03-11 at 14:21, Ombongi Moraa Fe wrote:
My SMSC is moving CPs away from SMPP and introducing an SDP Platform. There
are a set of endpoints to allow me to receive messages from the SDP gateway
that I need to implement on my end. However, from documentation shared, the
implementation of message forwarding and sending has to be SOAP based.
There is a trend to move from SMPP to SOAP. ;)
which is not good at all.
Question:
1) Is it still possible to use Kannel for this? Since the connection will
no longer be smpp but http, and also since the messages need to forwarded
as soap requests, how can I make the connection between Kannel and the SDP?
Stipe posted patch for Kannel which adds Parlay XML (SOAP)
http://www.kannel.org/pipermail/devel/2011-February/004339.html
New patch can be downloaded from:
http://www.kannel.org/~tolj/patchsets/gSOAP/gateway-gsoap.v7.diff
the patchsets have been committed to SVN trunk, so the whole SOAP
infrastructure is already inside the Kannel code base. Depending on
the SOAP SDP dialect they use, you will need to implement your own
module incarnation for it through.
We support Ericsson's ParlayX and GMSA OneAPI at the moment. What do
they use?
2) Any additional information to help me implement this will be greatly
appreciated.
You can try this with the patch (maybe you will have to adapt it to your
telco) and see if it works.
When I had to change to that (stupid, IMO) SOAP and HTTP, I wrote HTTP
server and SOAP parser/decoder from the scratch because that was easier
for me.
It's a mess that people think exposing SOAP to the VASP side makes the
SMS messaging easier.
In fact what we want to have in Kannel is the GSMA OneAPI SOAP server
side implementation in smsbox, so we can abstract as:
SMSC -SMPP/UCP/CIMD2/..- bearerbox - smsbox -OneAPI SOAP- VASPs
anyone interested in tackling this? The code base is already inside SVN
trunk, you would simply need to make the gSOAP part for the server side.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
[FYI] GSMA MWC 2013 - Kannel group attending
Dear users,
we're attending the GSMA Mobile World Congress 2013 in Barcelona, Spain
again.
Please feel free for any attendees that are available on the venue and
would like to meet Alexander Malysh or Stipe Tolj to make an networking
appointment with us via the appointment organizer on the home page of
kannel.org.
Thanks,
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: wap client with SAR
Am 03.01.2013 22:01, schrieb Piotr Galecki:
I ended up enhancing fakewap utility with SAR function.
Let me know if you are interested in a patch.
Hi Piotr,
thanks a lot for contributing to the Kannel WAP 1 stack and the SAR
part. We're definitely interested.
Kindly please provide a patchset in 'diff -u' against current SVN trunk
to review and commit.
It would be great if we can move the discussion to the devel@ list,
which is more suited for this. Kindly subscribe and send the patchset to
the devel@ list.
Thanks a lot.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
*** MERRY CHRISTMAS and a HAPPY NEW YEAR! *** from the Kannel Group!
Dear developers,
Dear users,
in the name of the whole Kannel Group, and to all the great individual
supporters and contributor that have shown again tremendous
participation and encouragement in this year we wish you:
*** Merry Christmas, Happy Holidays and a Happy New Year! ***
Enjoy the holiday season and make yourself a great time, either with
family, friends or both. :)
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Internal Message ID
Am 31.10.2012 09:16, schrieb Willy Mularto:
In situation where multiple Kannel daemon run on the same server does
Kannel's internal Message ID really unique? Thanks.
yes, we use UUIDs, please see for reference:
http://en.wikipedia.org/wiki/Universally_unique_identifier
NOTE: the yes means, with a confidence that is 99.(some repetition)9%
accurate in terms of uniqueness.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
[RFC] Support for GSMA's OneAPI v2.0 REST support for SMS
Hi lists,
I'm intentionally cross-posting here, sorry for the noise of those
getting it on both channels.
I have been finalizing the GSMA OneAPI v1.0 SOAP/XML protocol support
for Kannel for SMS send/receive. In fact in the meantime, as all seem to
jump on the SOAP/XML is sooo complicated, let's so all the RESTful
approach, so did the GSMA.
In OneAPI v2.0 SMS they go rather with a RESTful approach exchanging
JSON objects via HTTP.
Is there general interest to support this as client side protocol in
Kannel? If yes, please argue why, and if there are real world production
environments already out with Telcos using the OneAPI v2.0 interface,
and we can go for an reference implementation.
Looking forward to comments.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: SMPPBOX Download Link
Am 11.09.2012 21:17, schrieb Shahid Bashir Ahmad:
Dear All,
Thanks for your support. We successfully installed OpenSMPPBox and
SQLBox. Please guide me if there is any open source or paid billing
available for this.
Hi Shahid,
the Kannel opensmppbox doesn't provide any billing handling internally.
For this purposes you MAY want to go with the commercial Kannel SMPP
v3.4 server (smppbox) which support various billing/accounting models on
the SMS flows created by the ESMEs.
Please let me know if you need any further details.
Best Regards,
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Need to download some CVS versions
Am 30.08.2012 10:03, schrieb Willy Mularto:
I need to download some CVS versions of Kannel. Does anybody has the
link to access the CVS?
there is no CVS server anymore running, we migrated all to SVN a long
time ago.
Please see if you can checkout by date via the SVN trunk repository.
I would also doubt why an old CVS version is of any interest?
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Commercial pricing of Kannel
Am 24.11.2011 08:41, schrieb ha...@aeon.pk:
Can someone guide me about the pricing for the commercial usage of Kannel SMS
gateway? Thanks!
as Rene pointed out, Kannel is open source software, under our Kannel Software
License Version 1.0, which is available at:
https://svn.kannel.org/gateway/trunk/LICENSE
though, there are several commercial add-on components, like the Kannel SMPP
v3.4 server (smppbox) and other carrier-grade components. Those are subject to
commercial licensing.
Please let me know if you need additional information.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
smime.p7s
Description: S/MIME Cryptographic Signature
Re: SOAP Request
Am 24.11.2011 05:34, schrieb Milan P. Stanic:
On Thu, 2011-11-24 at 15:59, Willy Mularto wrote:
Hi,
We just received new API from our telco. And it said all MO, MT, DLR will use
HTTP SOAP.
Is that a trend with telco's now? I received the same few months ago.
yes, sort of a un-efficient idea that is spreading.
Since basically SOAP is an XML request. Is it possible if we treat it as
standard HTTP POST and only need to parse the XML structure? Thanks.
Yes, of course. I do that for some SOAP services (not related to
Kannel).
I usually strip namespace and other useless tags (envelope, and what
not) and I have simple XML, which can be then processed with XML tools
(library functions).
Also, I create SOAP requests with simple printf (or alike) functions and
send it as HTTP POST.
rant
I don't understand why so many service providers uses SOAP which is
bloated.
While SOAP itself seems, for the moment, to be patent unencumbered,
WSDL, UDDI, various security add-ons, and possibly alternate transport
mechanisms are all looking questionable.
...
/rant
If you need the SOAP/XML API of your MNO to be implemented very robust into
Kannel, I have past a patch (that is yet to be committed to SVN trunk mainline)
that supports GSMA's OneAPI, as a framework for other SOAP based APIs.
The patch is available in the mailing list archive at URL:
http://www.kannel.org/pipermail/devel/2011-February/004339.html
It requires you though some minor skills in C to wrap this code as base
framework and adopt to an own version of the MNO's API.
BTW, I never had a consideration to abstract this SOAP/XML stuff in Kannel,
since we don't want to drive the motor that support SOAP in the telco messaging
fields.
Best Regards,
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
smime.p7s
Description: S/MIME Cryptographic Signature
Re: SMSC returned error code 0x00000102 (Specified service_type is unavailable) in response to submit_sm.
Am 28.09.2011 19:28, schrieb Mpeirwe Benjamin: Hello Good People, I have a challenge connecting to a new smpp connection, I bind to the connection so that when I send SMS, they are Accepted for delivery. Challenge is they are not delivered because at the SMSC side the response given is: SMSC returned error code 0x0102 (Specified service_type is unavailable) in response to submit_sm. as shown in the kannel.log file where I picked: 2011-09-28 20:13:10 [4362] [11] DEBUG: boxc_receiver: sms received 2011-09-28 20:13:10 [4362] [6] DEBUG: SMPP[VMA1]: Sending PDU: 2011-09-28 20:13:10 [4362] [6] DEBUG: SMPP PDU 0x9fcda60 dump: 2011-09-28 20:13:10 [4362] [6] DEBUG: type_name: submit_sm 2011-09-28 20:13:10 [4362] [6] DEBUG: command_id: 4 = 0x0004 2011-09-28 20:13:10 [4362] [6] DEBUG: command_status: 0 = 0x 2011-09-28 20:13:10 [4362] [6] DEBUG: sequence_number: 12 = 0x000c 2011-09-28 20:13:10 [4362] [6] DEBUG: service_type: 2011-09-28 20:13:10 [4362] [6] DEBUG: source_addr_ton: 5 = 0x0005 2011-09-28 20:13:10 [4362] [6] DEBUG: source_addr_npi: 0 = 0x 2011-09-28 20:13:10 [4362] [6] DEBUG: source_addr: abcde 2011-09-28 20:13:10 [4362] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2011-09-28 20:13:10 [4362] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2011-09-28 20:13:10 [4362] [6] DEBUG: destination_addr: 1546785921 2011-09-28 20:13:10 [4362] [6] DEBUG: esm_class: 3 = 0x0003 2011-09-28 20:13:10 [4362] [6] DEBUG: protocol_id: 0 = 0x 2011-09-28 20:13:10 [4362] [6] DEBUG: priority_flag: 0 = 0x 2011-09-28 20:13:10 [4362] [6] DEBUG: schedule_delivery_time: NULL 2011-09-28 20:13:10 [4362] [6] DEBUG: validity_period: NULL 2011-09-28 20:13:10 [4362] [6] DEBUG: registered_delivery: 0 = 0x 2011-09-28 20:13:10 [4362] [6] DEBUG: replace_if_present_flag: 0 = 0x 2011-09-28 20:13:10 [4362] [6] DEBUG: data_coding: 0 = 0x 2011-09-28 20:13:10 [4362] [6] DEBUG: sm_default_msg_id: 0 = 0x 2011-09-28 20:13:10 [4362] [6] DEBUG: sm_length: 47 = 0x002f 2011-09-28 20:13:10 [4362] [6] DEBUG: short_message: 2011-09-28 20:13:10 [4362] [6] DEBUG:Octet string at 0x9fce680: 2011-09-28 20:13:10 [4362] [6] DEBUG: len: 47 2011-09-28 20:13:10 [4362] [6] DEBUG: size: 48 2011-09-28 20:13:10 [4362] [6] DEBUG: immutable: 0 2011-09-28 20:13:10 [4362] [6] DEBUG: data: 57 65 64 20 53 65 70 20 32 38 20 32 30 3a 31 33 Wed Sep 28 20:13 2011-09-28 20:13:10 [4362] [6] DEBUG: data: 3a 31 30 20 45 41 54 20 32 30 31 31 20 74 65 73 :10 EAT 2011 tes 2011-09-28 20:13:10 [4362] [6] DEBUG: data: 74 69 6e 67 20 63 6f 6e 6e 65 63 74 69 6f 6e ting connection 2011-09-28 20:13:10 [4362] [6] DEBUG:Octet string dump ends. 2011-09-28 20:13:10 [4362] [6] DEBUG: SMPP PDU dump ends. 2011-09-28 20:13:10 [4362] [11] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-09-28 20:13:10 [4362] [6] DEBUG: SMPP[VMA1]: Got PDU: 2011-09-28 20:13:10 [4362] [6] DEBUG: SMPP PDU 0x9fcd870 dump: 2011-09-28 20:13:10 [4362] [6] DEBUG: type_name: submit_sm_resp 2011-09-28 20:13:10 [4362] [6] DEBUG: command_id: 2147483652 = 0x8004 2011-09-28 20:13:10 [4362] [6] DEBUG: command_status: 258 = 0x0102 2011-09-28 20:13:10 [4362] [6] DEBUG: sequence_number: 12 = 0x000c 2011-09-28 20:13:10 [4362] [6] DEBUG: message_id: 2011-09-28 20:13:10 [4362] [6] DEBUG:Octet string at 0x9fcedb0: 2011-09-28 20:13:10 [4362] [6] DEBUG: len: 30 2011-09-28 20:13:10 [4362] [6] DEBUG: size: 31 2011-09-28 20:13:10 [4362] [6] DEBUG: immutable: 0 2011-09-28 20:13:10 [4362] [6] DEBUG: data: 50 30 31 2e 31 33 31 37 32 32 39 30 37 35 30 38 P01.131722907508 2011-09-28 20:13:10 [4362] [6] DEBUG: data: 36 36 33 35 30 30 30 2e 34 34 30 30 32 35 6635000.440025 2011-09-28 20:13:10 [4362] [6] DEBUG:Octet string dump ends. 2011-09-28 20:13:10 [4362] [6] DEBUG: SMPP PDU dump ends. 2011-09-28 20:13:10 [4362] [6] ERROR: SMPP[VMA1]: SMSC returned error code 0x0102 (Specified service_type is unavailable) in response to submit_sm. formally this submit_sm_resp PDU breaks the SMPP v3.4 spec. Reason: a message_id values SHOULD be only returned for command_status = 0x00 results. ;) 2011-09-28 20:13:17 [4362] [6] DEBUG: SMPP[VMA1]: Sending enquire link: 2011-09-28 20:13:17 [4362] [6] DEBUG: SMPP PDU 0x9fcd870 dump: 2011-09-28 20:13:17 [4362] [6] DEBUG: type_name: enquire_link 2011-09-28 20:13:17 [4362] [6] DEBUG: command_id: 21 = 0x0015 2011-09-28 20:13:17 [4362] [6] DEBUG: command_status: 0 = 0x 2011-09-28 20:13:17 [4362] [6] DEBUG: sequence_number: 13 = 0x000d 2011-09-28 20:13:17 [4362] [6] DEBUG: SMPP PDU dump ends. 2011-09-28 20:13:18 [4362] [6] DEBUG: SMPP[VMA1]: Got PDU: 2011-09-28 20:13:18 [4362] [6] DEBUG: SMPP PDU 0x9fcd870 dump: 2011-09-28 20:13:18 [4362] [6] DEBUG: type_name: enquire_link_resp 2011-09-28 20:13:18 [4362] [6] DEBUG: command_id: 2147483669 = 0x8015
Re: communication between two ESMEs using opensmppbox
Am 13.07.2011 03:59, schrieb Francisco Andrades Grassi:
Is there a way to use Kannel/smppbox under these conditions? How can I use
opensmppbox to route messages between two ESMEs?
yes, you can use opensmppbox to connect the ESMEs and bearerbox via SMSC module
'loopback' to bounce the MT coming in from ESME A to a MO going to ESME B.
This means you still need to run opensmppbox and bearerbox.
The Kannel SMPP v3.4 server (smppbox) commercial add-on is able to handle
ESME-to-ESME communication directly in the smppbox, without moving the messages
to bearerbox and bouncing them back to smppbox via the loopback SMSC module.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Regarding Opensmmpbox;
Am 15.07.2011 06:19, schrieb Vijay kumar Dadhich:
Hello Sir,
Is there any licence version available for the same.
Hello Vijay,
yes, we provide the Kannel SMPP v3.4 server (smppbox) as commercial add-on which
is capable of handling remote management of accounts and prepaid/postpaid
accounting via DB callbacks, along with a wide feature set.
Please let me know if you need further informations.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Getting in touch with Stipe Tolj
Am 09.06.2011 11:56, schrieb Filippo Natali:
Hello,
sorry for bothering the list, I have to get in touch with Stipe for urgent
(job-related) matters but he's not responding my emails and Skype messages
since two months.
However I see that he posted some messages here and committed some stuff on
svn...if someone can put Stipe in contact with me, I'll really appreciate it.
Hello group,
no worries, I'm fine, I had a slight motorcycle accident in April, with a broken
leg, and all the nice things that you get afterwards. (hope all get the irony).
Now, got into touch with Filippo, no reasons to ring the big bells anywhere.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
smime.p7s
Description: S/MIME Cryptographic Signature
Re: The wap gateway
Am 04.06.2011 21:09, schrieb mattias:
So the gateway are only for old dialup on mobile phones
Not for modern gprs?
the normal Kannel WAP gateway provides the WAP 1.2.1 stack (including WAP Push),
which uses UDP as IP bearer and can be utilized via CSD or GPRS. In fact the
underlying radio transmission technology is not specified in the specs.
For WAP 2.0 you use more or less plain HTTP, with some addition of WTCP which
uses a radio-efficient TCP implementation.
Essentially today, the WAP gateway takes 2 roles:
a) transcode from WAP 1 phones the WTP/WSP layers to TCP for the target HTTP
servers.
b) provisioning of RADIUS values in HTTP headers towards the target HTTP, i.e.
for registered VASP or the MMSC of the operator to receive the MSISDN of the user.
The normal Kannel can handle both, where the Kannel-CG includes a full WAP 2.0
stack and a more complex RADIUS AAA framework. Both are relevant for mobile
network operators, and don't make any sense for VASPs, as long as they are not
in control of the GGSN of the network, or the MNO provides a dedicated APN via
it's GGSN towards the VASP, i.e. for closed user base functionality.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Kannel and SS7
Am 04.05.2011 20:59, schrieb Juan Nin:
No, it can't
well, don't want to foul Juan hard here ;) but yes, it could.
There are SS7 gateways that allow you to interface to it via SMPP v3.4. So
Kannel can send SMPP PDUs to the SS7 gateway, which acts hence as as SMPP server
on the one side, and inter-connects as own point code machine in the signaling
network, performing the signal point resolution of the destination MSISDN and
signaling the message to the phone.
So the answer is: yes, if the signaling gateway acts as SMPP server on the IP
based side.
If not, then you need to develop a bearerbox module that talks the interface API
of the signaling gateway to interact with it, which IS of course possible.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [Ticket #15] Kannel and SS7
Am 05.05.2011 13:19, schrieb Milan P. Stanic:
Mailing list admin should block this e-mail address to prevent spam to
the list.
agree, I have removed the user from the list.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
smime.p7s
Description: S/MIME Cryptographic Signature
