Re: SMPP Asynchronous mode
Hi, look at max-pending-submits. Alex Am 01.08.2013 um 20:02 schrieb [Digital^Dude] ® millennium@gmail.com: Hello, I happened to take a tcpdump of my kannel smpp connection with a telco. Every submit_sm was followed by a submit_sm_resp. It seemed like kannel operating in synchronous mode I fear that the outbound throughput is adversely affected by the submit_sm waiting for a submit_sm_resp and not immediately sending a burst of submit_sm at once. Any hints how I can forcefully make it go async? -- Thanks.
ERROR: Group 'sms-service' may not contain field 'alt-charset'
Hi guys,
I have configured kannel to work with SMPP.
I can send and receive ASCII messages without any problem.
I can send Persian messages without any problem. but when receiving it is
converted to ASCII characters.
Based on user guide I have set sms-service section like this:
group = sms-service
keyword = default
get-url = http://1.1.1.1/income/Submit?from=%pto=%Pcontent=%a;
concatenation = true
forced-smsc = my-smsc
catch-all = true
max-messages = 0
alt-charset = UTF8
But when starting bearerbox it says:
ERROR: Group 'sms-service' may not contain field 'alt-charset'
user guide says about alt-charset:
Defines which character
encoding is used for the SMS
message when passed to a
remote HTTP application. This
includes how the SMS message
text is send in the HTTP GET
parameter list and in the HTTP
POST bidy. Uses iconv()
routines to convert from and to
that specific character set
encoding. See your local
iconv_open(3) manual page
for the supported character
encodings and the type strings
that should be presented for this
directive.
Then why not it is working?
the get-url is a servlet like this:
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
/* set character encoding */
request.setCharacterEncoding(UTF-8);
response.setCharacterEncoding(UTF-8);
/* process message */
}
Also when I set al-charset in smsc section it doesn't change anything.
Can anyone help?
Re: SMPP Asynchronous mode
Hi, look at max-pending-submits. Assuming the operator delivers sms without problems with delay of submit_sm_resp, I was just wondering how kannel would behave if max-pending-submits is more than 200... Alex Am 01.08.2013 um 20:02 schrieb [Digital^Dude] ® millennium@gmail.com : Hello, I happened to take a tcpdump of my kannel smpp connection with a telco. Every submit_sm was followed by a submit_sm_resp. It seemed like kannel operating in synchronous mode I fear that the outbound throughput is adversely affected by the submit_sm waiting for a submit_sm_resp and not immediately sending a burst of submit_sm at once. Any hints how I can forcefully make it go async? -- Thanks.
unsubscribe
unsubscribe
SMS Accounting
Hello, I have 3 SMSC (gsm1, gsm2, gsm3) in my Kannel-Setup and Im using sqlbox to save all kind of information about the messages in a database. My question is how can I store the sending SMSC of every message in the database ? For example: If I call the webservice with the argument smsc=gsm1 and the message is sent, I see this information in the database entry : +-++--+-+-+-+---++-+-+-+--+--++--++--+--+--+--+-+--+-+--+-+-+---+ date sql_id momt sender receiver udhdata msgdata time smsc_idservice account id sms_type mclass mwi coding compress validity deferred dlr_mask dlr_url pid alt_dcs rpi charset boxc_id binfo +-++--+-+-+-+---++-+-+-+--+--++--++--+--+--+--+-+--+-+--+-+-+---+ 2013-08-05 15:43:3110 MT xx xx NULL bla x gsm1 user1 NULL NULL 2 NULL NULL0NULLNULLNULLNULL NULL NULL NULL NULL NULL smsbox1 NULL But I configured message-routing in a way, which eventually allows me to bypass a SMSC which is not working at this given moment. Because of this message-routing I cant call the webservice with the argument smsc= ! But if i dont use that argument, the information about the sending SMSC is not stored in the database :( Once a month, I need to know how many messages were sent through gsm1, gsm2 and gsm3. Im not able to get this information, if the database field is not getting filled :( Regards, Florian
DLR expiration
Today one of our kannel instances became increasingly slow. After some troubleshooting, we realized that the internal DLR storage was too big and the threads were taking too much time to store a new DLR. Is there some configuration to cause expiration of the DLRs in memory? I could not find anything such as this. Thanks in advance, Luis
