RE: empty sms being ignored

[Tshimanga Minkoka]

Look at the omit-empty parameter in sms-service and sendsms-user groups and the 
reply-emptymessage parameter in smsbox group.

TSHIMANGA Minkoka
VAS Manager
È +243 814443113
* +243 815560341 ext. 0583
*  +243 813010373
* tshimanga.mink...@vodacom.cd
ü http://www.vodacom.cd
[cid:image003.jpg@01CC0584.FE93C1E0]

From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of 
Jan Ardosa
Sent: Wednesday 27 April 2011 08:58
To: users@kannel.org
Subject: empty sms being ignored

Hi Kannel users,

I've been encountering Got empty SMS ignoring error and have already tried the 
patch to smsc_oisd.c code but im still getting the same error. Any tip to 
resolve this error?

regards

Jan


<>

Transmitter and Receiver as two different server

[Ravindra Gupta // Viva]

hi,

I am using kannel 1.4.3 ,how to send messages in two different server means
we have configure two server one server as a transmitter and other server as
a receiver.

kindly provide the help for the same.

Re: Transmitter and Receiver as two different server

[Alejandro Guerrieri]

Setup two different connections with the same smsc-id.

Configure the proper host and port for your servers.

Use port= and receive-port=0 for your Transmitter.
Use port=0 and receive-port= for your Receiver.

Check the user guide for further details.

Regards,

Alex
On Thu, Apr 28, 2011 at 12:07 PM, Ravindra Gupta // Viva <
ravin...@vivainfomedia.com> wrote:

> hi,
>
> I am using kannel 1.4.3 ,how to send messages in two different server means
> we have configure two server one server as a transmitter and other server as
> a receiver.
>
> kindly provide the help for the same.
>

Re: Transmitter and Receiver as two different server

[Ravindra Gupta // Viva]

Dear Alejandro,

Thanks for your response.

I already use kannel server for last 3 years, i have bind transmitter and
receiver in same server (smskannel.conf) file.

I want to change transmitter and receiver in different server means messages
going on one server and (submit_sm) and receive response
(submit_sm_respo) from other server.

Kindly help me for the same.

RESOLVED: Packet too short while unpacking Msg Error

[mwamba chishimba]

Hello Everyone,

I managed to figure out how to go round this one. Am not sure what
the repercussion for my actions are but this is what I did. I changed the
store-type in kannel.conf to spool and then created a directory which I
named spool in var/log/kannel. I then restarted bearerbox, sqlbox and smsbox
and all seems well so far. Prior to changing the store-type and creating the
spool directory I had renamed the existing kannel.spool files and tested
bearerbox which created new files so you may want to explore that option as
well.

Thank you to all those that took time to help me resolve this problem.

Kind Regards,

On Thu, Apr 28, 2011 at 8:47 AM, mwamba chishimba wrote:

> Hi Nikos,
>
> Thank you for your kind response, much appreciated.
>
> I have 2 follow up questions. I have backup kannel.spool files and
> apparently I have two files that were changed at the time am suspecting
> bearerbox crashed. They are named *kannel.spool.new* changed at *
> 12:45:35PM* and *kannel.spool.bak* changed at *12:45:11PM*
>
> I have this in my *kannel.conf* file which I believe is suppose to point
> to the above file. However I do not have the kannel.spool file indicated on
> the store-location file shown below. How do I restore or fix this the
> kannel.spool file and what extension should it have if any?
> *store-type = file*
> *store-location = "/usr/local/kannel/kannel.spool"*
>
> My second question is how do I access the store tools by Alex? Lastly,
> you've talked about changing to spool store-type, is it just a matter of
> changing they store type indicated above?
>
> Again, am very grateful for your help!
>
> Kind Regards,
>
> 2011/4/28 Nikos Balkanas 
>
>> Hi,
>>
>> Your problem is with store-file corruption. You will have to restore from
>> backup, or fix using vi. Alex G has provided some store tools, maybe they
>> can help. Better switch to spool store type, it is much easier to handle and
>> recover from problems.
>>
>> BR,
>> Nikos
>> - Original Message - From: mwamba chishimba
>> To: users
>> Sent: Thursday, April 28, 2011 12:11 AM
>> Subject: Packet too short while unpacking Msg Error
>>
>>
>>
>> Hello Everyone,
>>
>> I have run into serious trouble with my kannel setup. Been working just
>> fine and until a few hours ago whe it suddenly stopped working.
>> When I start bearerbox with : /usr/local/kannel/sbin/bearerbox -v -1
>> /usr/local/kannel/smskannel.conf
>>
>> I get the following error:
>> .
>> truncated
>> .
>> .
>> 2011-04-27 21:49:22 [25924] [0] ERROR: Packet too short while unpacking
>> Msg.
>> 2011-04-27 21:49:22 [25924] [0] ERROR: Msg packet was invalid.
>> 2011-04-27 21:49:22 [25924] [0] ERROR: Garbage at store-file, skipped.
>> 2011-04-27 21:49:22 [25924] [0] PANIC: Internal error: unknown message
>> type: 1747722356
>> 2011-04-27 21:49:22 [25924] [0] PANIC:
>> /usr/local/kannel/sbin/bearerbox(gw_panic+0xe2) [0x80d0992]
>> 2011-04-27 21:49:22 [25924] [0] PANIC:
>> /usr/local/kannel/sbin/bearerbox(msg_unpack_real+0x76) [0x8065946]
>> 2011-04-27 21:49:22 [25924] [0] PANIC:
>> /usr/local/kannel/sbin/bearerbox(msg_unpack_wrapper+0x29) [0x8065d19]
>> 2011-04-27 21:49:22 [25924] [0] PANIC: /usr/local/kannel/sbin/bearerbox
>> [0x805f2cf]
>> 2011-04-27 21:49:22 [25924] [0] PANIC:
>> /usr/local/kannel/sbin/bearerbox(main+0x91d) [0x80553fd]
>> 2011-04-27 21:49:22 [25924] [0] PANIC:
>> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb78b5ebc]
>> 2011-04-27 21:49:22 [25924] [0] PANIC: /usr/local/kannel/sbin/bearerbox
>> [0x8053de1]
>>
>> i have attached my smskannel.conf file and my kannel.log file for your
>> review.
>>
>> Thank you in advance for your kind help
>>
>> Kind Regards,
>>
>>
>>
>> --
>> Mwamba Chishimba
>>
>> "For I am persuaded, that neither death, nor life, nor angels, nor
>> principalities, nor powers, nor things present, nor things to come, nor
>> height, nor depth, nor any other creature, shall be able to separate us from
>> the love of God, which is in Christ Jesus our Lord"
>>
>
>
>
> --
> Mwamba Chishimba
>
> "For I am persuaded, that neither death, nor life, nor angels, nor
> principalities, nor powers, nor things present, nor things to come, nor
> height, nor depth, nor any other creature, shall be able to separate us from
> the love of God, which is in Christ Jesus our Lord"
>



-- 
Mwamba Chishimba

"For I am persuaded, that neither death, nor life, nor angels, nor
principalities, nor powers, nor things present, nor things to come, nor
height, nor depth, nor any other creature, shall be able to separate us from
the love of God, which is in Christ Jesus our Lord"

Re: Transmitter and Receiver as two different server

[Alejandro Guerrieri]

That's not something you'd be able to setup from Kannel side... you cannot
dictate from which server the message will arrive from. If the remote side
response comes on the "second" server, Kannel should be able to handle it,
but again, it's a matter of how the remote side is configured, not yours.

Regards,

Alex

On Thu, Apr 28, 2011 at 1:10 PM, Ravindra Gupta // Viva <
ravin...@vivainfomedia.com> wrote:

> Dear Alejandro,
>
> Thanks for your response.
>
> I already use kannel server for last 3 years, i have bind transmitter and
> receiver in same server (smskannel.conf) file.
>
> I want to change transmitter and receiver in different server means
> messages going on one server and (submit_sm) and receive response
> (submit_sm_respo) from other server.
>
> Kindly help me for the same.
>

sms-service failover

[Vincent Themereau]

Hello,

I have the following configuration: SMS-C connected to Kannel and two 
application servers used to handle inbound SMS. I want all inbound SMS 
to be handled by the first application server but in case the first 
application server is down I want Kannel to automatically use the second 
application server.


Is it possible to configure Kannel with two sms-service:
 - The first one with a get-url pointing to the first application server.
 - The second one with a get-url pointing to the second application server.

The target is : If first application server is down  - the HTTP GET of 
Kannel fails - then Kannel automatically use the second sms-service. So 
is it possible to do that with Kannel ? Or do I have to add an HTTP 
proxy between Kannel and my application servers ?


Thanks for your help
Vincent

Re: routing from cgi via loopback to opensmppbox

[Semion Spivak]

Update - Solved.

Added meta-data support to generic http smsc and used the previous 
routing setup.


If anyone is interested, here's the patch attached.

On 04/27/2011 01:08 AM, Semion Spivak wrote:

Hi All,

I have a service that needs to pass MO messages via HTTP to SMPP clients.

I've managed to configure the following setup:

MO --> generic http smsc --> bearerbox --> opensmppbox -- esme

but there is a set of meta-data params to be passed along with the
message, and generic http smsc doesn't handle "meta-data" parameter of
incoming request.

So, I guess, the setup that uses smsbox cgi handler, would look like

MO --> smsbox (cgi-bin/sendsms handler) --> loopback smsc --> bearerbox
--> opensmppbox --> esme

Can anyone suggest the routing-related settings for smsbox and
the loopback, please?

Thank you in advance for your help,


--
Regards,
Semion Spivak
Smscoin.com Technical support.
Index: gw/smsc/smsc_http.c
===
--- gw/smsc/smsc_http.c (revision 4904)
+++ gw/smsc/smsc_http.c (working copy)
@@ -142,6 +142,7 @@
 Octstr *service;
 Octstr *account;
 Octstr *binfo;
+Octstr *meta_data;
 Octstr *dlr_mask;
 Octstr *dlr_url;
 Octstr *dlr_mid;
@@ -217,6 +218,7 @@
 octstr_destroy(fieldmap->service);
 octstr_destroy(fieldmap->account);
 octstr_destroy(fieldmap->binfo);
+octstr_destroy(fieldmap->meta_data);
 octstr_destroy(fieldmap->dlr_mask);
 octstr_destroy(fieldmap->dlr_url);
 octstr_destroy(fieldmap->dlr_mid);
@@ -1748,7 +1750,7 @@
 {
 ConnData *conndata = conn->data;
 FieldMap *fm = conndata->fieldmap;
-Octstr *user, *pass, *from, *to, *text, *udh, *account, *binfo;
+Octstr *user, *pass, *from, *to, *text, *udh, *account, *binfo, *meta_data;
 Octstr *dlrurl, *dlrmid;
 Octstr *tmp_string, *retmsg;
 intmclass, mwi, coding, validity, deferred, dlrmask;
@@ -1867,6 +1869,7 @@
 }
 account = http_cgi_variable(cgivars, octstr_get_cstr(fm->account));
 binfo = http_cgi_variable(cgivars, octstr_get_cstr(fm->binfo));
+meta_data = http_cgi_variable(cgivars, octstr_get_cstr(fm->meta_data));
 
 debug("smsc.http.generic", 0, "HTTP[%s]: Constructing new SMS",
   octstr_get_cstr(conn->id));
@@ -1887,6 +1890,7 @@
 msg->sms.time = time(NULL);
 msg->sms.account = octstr_duplicate(account);
 msg->sms.binfo = octstr_duplicate(binfo);
+msg->sms.meta_data = octstr_duplicate(meta_data);
 Msg *resp = msg_duplicate(msg);
 ret = bb_smscconn_receive(conn, msg);
 if (ret == -1) {

Re: routing from cgi via loopback to opensmppbox

[Semion Spivak]

self fix: missed fieldmap initialisation from the settings, please use 
the attached patches for the gw/smsc/smsc_http.c, gwlib/cgf.def and 
doc/userguide/userguide.xml


On 04/28/2011 06:19 PM, Semion Spivak wrote:

Update - Solved.

Added meta-data support to generic http smsc and used the previous
routing setup.

If anyone is interested, here's the patch attached.

On 04/27/2011 01:08 AM, Semion Spivak wrote:

Hi All,

I have a service that needs to pass MO messages via HTTP to SMPP clients.

I've managed to configure the following setup:

MO --> generic http smsc --> bearerbox --> opensmppbox -- esme

but there is a set of meta-data params to be passed along with the
message, and generic http smsc doesn't handle "meta-data" parameter of
incoming request.

So, I guess, the setup that uses smsbox cgi handler, would look like

MO --> smsbox (cgi-bin/sendsms handler) --> loopback smsc --> bearerbox
--> opensmppbox --> esme

Can anyone suggest the routing-related settings for smsbox and
the loopback, please?

Thank you in advance for your help,




--
Regards,
Semion Spivak
Smscoin.com Technical support.
Index: gwlib/cfg.def
===
--- gwlib/cfg.def   (revision 4904)
+++ gwlib/cfg.def   (working copy)
@@ -415,6 +415,7 @@
 OCTSTR(generic-param-validity)
 OCTSTR(generic-param-deferred)
 OCTSTR(generic-param-foreign-id)
+OCTSTR(generic-param-meta-data)
 OCTSTR(generic-message-sent)
 OCTSTR(generic-status-sent)
 OCTSTR(generic-status-error)
Index: gw/smsc/smsc_http.c
===
--- gw/smsc/smsc_http.c (revision 4905)
+++ gw/smsc/smsc_http.c (working copy)
@@ -142,6 +142,7 @@
 Octstr *service;
 Octstr *account;
 Octstr *binfo;
+Octstr *meta_data;
 Octstr *dlr_mask;
 Octstr *dlr_url;
 Octstr *dlr_mid;
@@ -217,6 +218,7 @@
 octstr_destroy(fieldmap->service);
 octstr_destroy(fieldmap->account);
 octstr_destroy(fieldmap->binfo);
+octstr_destroy(fieldmap->meta_data);
 octstr_destroy(fieldmap->dlr_mask);
 octstr_destroy(fieldmap->dlr_url);
 octstr_destroy(fieldmap->dlr_mid);
@@ -1013,7 +1015,7 @@
 } else if (apimsgid == NULL || status == NULL || timestamp == NULL || dest 
== NULL) {
 error(0, "HTTP[%s]: Insufficient args.",
   octstr_get_cstr(conn->id));
-httpstatus = HTTP_OK;
+httpstatus = HTTP_BAD_REQUEST;
 retmsg = octstr_create("Insufficient arguments, rejected.");
 } else {
switch (atoi(octstr_get_cstr(status))) {
@@ -1727,6 +1729,9 @@
 if (fm->deferred == NULL)
 fm->deferred = octstr_create("deferred");
 fm->foreign_id = cfg_get(grp, octstr_imm("generic-param-foreign-id"));
+fm->meta_data = cfg_get(grp, octstr_imm("generic-param-meta-data"));
+if (fm->meta_data == NULL)
+fm->meta_data = octstr_create("meta-data");
 if (fm->foreign_id == NULL)
 fm->foreign_id = octstr_create("foreign-id");
 fm->message_sent = cfg_get(grp, octstr_imm("generic-message-sent"));
@@ -1748,7 +1753,7 @@
 {
 ConnData *conndata = conn->data;
 FieldMap *fm = conndata->fieldmap;
-Octstr *user, *pass, *from, *to, *text, *udh, *account, *binfo;
+Octstr *user, *pass, *from, *to, *text, *udh, *account, *binfo, *meta_data;
 Octstr *dlrurl, *dlrmid;
 Octstr *tmp_string, *retmsg;
 intmclass, mwi, coding, validity, deferred, dlrmask;
@@ -1867,6 +1872,7 @@
 }
 account = http_cgi_variable(cgivars, octstr_get_cstr(fm->account));
 binfo = http_cgi_variable(cgivars, octstr_get_cstr(fm->binfo));
+meta_data = http_cgi_variable(cgivars, octstr_get_cstr(fm->meta_data));
 
 debug("smsc.http.generic", 0, "HTTP[%s]: Constructing new SMS",
   octstr_get_cstr(conn->id));
@@ -1887,6 +1893,7 @@
 msg->sms.time = time(NULL);
 msg->sms.account = octstr_duplicate(account);
 msg->sms.binfo = octstr_duplicate(binfo);
+msg->sms.meta_data = octstr_duplicate(meta_data);
 Msg *resp = msg_duplicate(msg);
 ret = bb_smscconn_receive(conn, msg);
 if (ret == -1) {
Index: doc/userguide/userguide.xml
===
--- doc/userguide/userguide.xml (revision 4904)
+++ doc/userguide/userguide.xml (working copy)
@@ -4427,6 +4427,13 @@
Overrides the default parameter for the 'foreign-id' field
used on incoming requests.
  
+ 
+   generic-param-meta-data (o)
+ string
+ 
+   Overrides the default parameter for the 'meta-data' field
+   used on incoming requests.
+ 
 
generic-message-sent (o)
  string
@@ -8119,8 +8126,8 @@
 
 
 
+generic-param
 
-
 
 Setting up Push Proxy Gateway
   This chapter explains how to set up a push proxy gateway (PPG). 

SMSC routing problem

[Gerardo Corro]

Hi Kannel people,
I have a SMSC routing problem:
We have one smsbox:# SMSBOX SETUPgroup = smsboxbearerbox-host = 
localhostsendsms-port = 13013log-file = "/opt/kannel/log/smsbox.log"log-level = 
1access-log = "/opt/kannel/log/access.log"
two smscs#SMSCsgroup = smscsmsc = smppsmsc-id = first_smsc...group = smscsmsc = 
smppsmsc-id = second_smsc...

two sender users:# SEND-SMS USERSgroup = sendsms-userusername = 
first_userpassword = firstmax-messages = 200concatenation = trueforced-smsc = 
first_smsc
group = sendsms-userusername = second_userpassword = secondmax-messages = 
200concatenation = trueforced-smsc = second_smsc

one sms service# SMS SERVICE Defaultgroup = sms-servicekeyword = 
defaultcatch-all = trueaccepted-smsc = 
"first_smsc;second_smsc"max-messages=0get-url = 
http://localhost:13180/smsreceiver/sms?from=%p&to=%P&msg=%a&orig=%
When I want to send an SMS using the "first_smsc" SMSC I do 
this:http://localhost:13013/cgi-bin/sendsms?username=first_user&password=first&from=1234&to=4321&coding=1&udh=%06%05%04%40%f2%0e%84&text=COOKIE
when I want to send an SMS to "second_smsc" I do 
this:http://localhost:13013/cgi-bin/sendsms?username=second_user&password=second&from=1234&to=4321&coding=1&text=ok
But some SMSs that are supposed to go throught the first SMSC go through the 
second one, and viceversa.
Please assist, thanks.
  

Re: SMSC routing problem

[Semion Spivak]

Hi Gerardo,

try this:

group = smsc
smsc = smpp
smsc-id = first_smsc
allowed-smsc-id = first_smsc
...
group = smsc
smsc = smpp
smsc-id = second_smsc
allowed-smsc-id = second_smsc

On 04/28/2011 11:47 PM, Gerardo Corro wrote:

Hi Kannel people,

I have a SMSC routing problem:

We have one smsbox:
# SMSBOX SETUP
group = smsbox
bearerbox-host = localhost
sendsms-port = 13013
log-file = "/opt/kannel/log/smsbox.log"
log-level = 1
access-log = "/opt/kannel/log/access.log"

two smscs
#SMSCs
group = smsc
smsc = smpp
smsc-id = first_smsc
...
group = smsc
smsc = smpp
smsc-id = second_smsc
...


two sender users:
# SEND-SMS USERS
group = sendsms-user
username = first_user
password = first
max-messages = 200
concatenation = true
forced-smsc = first_smsc

group = sendsms-user
username = second_user
password = second
max-messages = 200
concatenation = true
forced-smsc = second_smsc


one sms service
# SMS SERVICE Default
group = sms-service
keyword = default
catch-all = true
accepted-smsc = "first_smsc;second_smsc"
max-messages=0
get-url = http://localhost:13180/smsreceiver/sms?from=%p&to=%P&msg=%a&orig=%

When I want to send an SMS using the "first_smsc" SMSC I do this:
http://localhost:13013/cgi-bin/sendsms?username=first_user&password=first&from=1234&to=4321&coding=1&udh=%06%05%04%40%f2%0e%84&text=COOKIE

when I want to send an SMS to "second_smsc" I do this:
http://localhost:13013/cgi-bin/sendsms?username=second_user&password=second&from=1234&to=4321&coding=1&text=ok

But some SMSs that are supposed to go throught the first SMSC go through
the second one, and viceversa.

Please assist, thanks.



--
Regards,
Semion Spivak
SmsCoin.com Technical support.

Re: routing from cgi via loopback to opensmppbox

[Hillel]

Hi Semion,

Why don't you send your patches to the devel group with the subject Patch?
Then we can all benefit if it's accepted.
You would have the advantage of the experts looking through your code and
commenting.

thanks

From: Semion Spivak 
To: users@kannel.org
Subject: Re: routing from cgi via loopback to opensmppbox
Message-ID: <4db9857e.4010...@smscoin.com>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

Update - Solved.

Added meta-data support to generic http smsc and used the previous 
routing setup.

If anyone is interested, here's the patch attached.

On 04/27/2011 01:08 AM, Semion Spivak wrote:
> Hi All,
>
> I have a service that needs to pass MO messages via HTTP to SMPP clients.
>
> I've managed to configure the following setup:
>
> MO --> generic http smsc --> bearerbox --> opensmppbox -- esme
>
> but there is a set of meta-data params to be passed along with the
> message, and generic http smsc doesn't handle "meta-data" parameter of
> incoming request.
>
> So, I guess, the setup that uses smsbox cgi handler, would look like
>
> MO --> smsbox (cgi-bin/sendsms handler) --> loopback smsc --> bearerbox
> --> opensmppbox --> esme
>
> Can anyone suggest the routing-related settings for smsbox and
> the loopback, please?
>
> Thank you in advance for your help,

-- 
Regards,
Semion Spivak
Smscoin.com Technical support.

Re: routing from cgi via loopback to opensmppbox

[Semion Spivak]

Hi Hillel,

Thank you for your comment.

You're right, and I'm planning to do so during this weekend, when I'll 
be less in a hurry.



On 04/29/2011 01:38 AM, Hillel wrote:

Hi Semion,

Why don't you send your patches to the devel group with the subject Patch?
Then we can all benefit if it's accepted.
You would have the advantage of the experts looking through your code and
commenting.

thanks

From: Semion Spivak
To: users@kannel.org
Subject: Re: routing from cgi via loopback to opensmppbox
Message-ID:<4db9857e.4010...@smscoin.com>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

Update - Solved.

Added meta-data support to generic http smsc and used the previous
routing setup.

If anyone is interested, here's the patch attached.

On 04/27/2011 01:08 AM, Semion Spivak wrote:

Hi All,

I have a service that needs to pass MO messages via HTTP to SMPP clients.

I've managed to configure the following setup:

MO -->  generic http smsc -->  bearerbox -->  opensmppbox -- esme

but there is a set of meta-data params to be passed along with the
message, and generic http smsc doesn't handle "meta-data" parameter of
incoming request.

So, I guess, the setup that uses smsbox cgi handler, would look like

MO -->  smsbox (cgi-bin/sendsms handler) -->  loopback smsc -->  bearerbox
-->  opensmppbox -->  esme

Can anyone suggest the routing-related settings for smsbox and
the loopback, please?

Thank you in advance for your help,




--
Regards,
Semion Spivak
SmsCoin.com Technical support.

Re: sms-service failover

[Nikos Balkanas]

Hi,

smsbox doesn't have such redundacy options. It will simply retry the same 
request. You can either try with a load balancer, or a specially designed 
proxy.


BR,
Nikos
- Original Message - 
From: "Vincent Themereau" 

To: 
Sent: Thursday, April 28, 2011 5:11 PM
Subject: sms-service failover



Hello,

I have the following configuration: SMS-C connected to Kannel and two 
application servers used to handle inbound SMS. I want all inbound SMS to 
be handled by the first application server but in case the first 
application server is down I want Kannel to automatically use the second 
application server.


Is it possible to configure Kannel with two sms-service:
 - The first one with a get-url pointing to the first application server.
 - The second one with a get-url pointing to the second application 
server.


The target is : If first application server is down  - the HTTP GET of 
Kannel fails - then Kannel automatically use the second sms-service. So is 
it possible to do that with Kannel ? Or do I have to add an HTTP proxy 
between Kannel and my application servers ?


Thanks for your help
Vincent

Re: RESOLVED: Packet too short while unpacking Msg Error

[Nikos Balkanas]

Hi,

From now on you will have a working service. Repercussions are that you will 
loose all other SMS in old queue along with the corrupted one. You could 
recover those witth Alex's store tools (search mail archives). Recovery is 
easier if you had spool store type to begin with.


BR,
Nikos
- Original Message - 
From: mwamba chishimba

To: Nikos Balkanas
Cc: users
Sent: Thursday, April 28, 2011 3:20 PM
Subject: RESOLVED: Packet too short while unpacking Msg Error


Hello Everyone,


I managed to figure out how to go round this one. Am not sure what the 
repercussion for my actions are but this is what I did. I changed the 
store-type in kannel.conf to spool and then created a directory which I 
named spool in var/log/kannel. I then restarted bearerbox, sqlbox and smsbox 
and all seems well so far. Prior to changing the store-type and creating the 
spool directory I had renamed the existing kannel.spool files and tested 
bearerbox which created new files so you may want to explore that option as 
well.



Thank you to all those that took time to help me resolve this problem.


Kind Regards,


On Thu, Apr 28, 2011 at 8:47 AM, mwamba chishimba  
wrote:


Hi Nikos,


Thank you for your kind response, much appreciated.


I have 2 follow up questions. I have backup kannel.spool files and 
apparently I have two files that were changed at the time am suspecting 
bearerbox crashed. They are named kannel.spool.new changed at 12:45:35PM and 
kannel.spool.bak changed at 12:45:11PM



I have this in my kannel.conf file which I believe is suppose to point to 
the above file. However I do not have the kannel.spool file indicated on the 
store-location file shown below. How do I restore or fix this the 
kannel.spool file and what extension should it have if any?

store-type = file
store-location = "/usr/local/kannel/kannel.spool"


My second question is how do I access the store tools by Alex? Lastly, 
you've talked about changing to spool store-type, is it just a matter of 
changing they store type indicated above?



Again, am very grateful for your help!


Kind Regards,


2011/4/28 Nikos Balkanas 

Hi,

Your problem is with store-file corruption. You will have to restore from 
backup, or fix using vi. Alex G has provided some store tools, maybe they 
can help. Better switch to spool store type, it is much easier to handle and 
recover from problems.


BR,
Nikos
- Original Message - From: mwamba chishimba
To: users
Sent: Thursday, April 28, 2011 12:11 AM
Subject: Packet too short while unpacking Msg Error



Hello Everyone,

I have run into serious trouble with my kannel setup. Been working just fine 
and until a few hours ago whe it suddenly stopped working.
When I start bearerbox with : /usr/local/kannel/sbin/bearerbox -v -1 
/usr/local/kannel/smskannel.conf


I get the following error:
.
truncated
.
.
2011-04-27 21:49:22 [25924] [0] ERROR: Packet too short while unpacking Msg.
2011-04-27 21:49:22 [25924] [0] ERROR: Msg packet was invalid.
2011-04-27 21:49:22 [25924] [0] ERROR: Garbage at store-file, skipped.
2011-04-27 21:49:22 [25924] [0] PANIC: Internal error: unknown message type: 
1747722356
2011-04-27 21:49:22 [25924] [0] PANIC: 
/usr/local/kannel/sbin/bearerbox(gw_panic+0xe2) [0x80d0992]
2011-04-27 21:49:22 [25924] [0] PANIC: 
/usr/local/kannel/sbin/bearerbox(msg_unpack_real+0x76) [0x8065946]
2011-04-27 21:49:22 [25924] [0] PANIC: 
/usr/local/kannel/sbin/bearerbox(msg_unpack_wrapper+0x29) [0x8065d19]
2011-04-27 21:49:22 [25924] [0] PANIC: /usr/local/kannel/sbin/bearerbox 
[0x805f2cf]
2011-04-27 21:49:22 [25924] [0] PANIC: 
/usr/local/kannel/sbin/bearerbox(main+0x91d) [0x80553fd]
2011-04-27 21:49:22 [25924] [0] PANIC: 
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb78b5ebc]
2011-04-27 21:49:22 [25924] [0] PANIC: /usr/local/kannel/sbin/bearerbox 
[0x8053de1]


i have attached my smskannel.conf file and my kannel.log file for your 
review.


Thank you in advance for your kind help

Kind Regards,



--
Mwamba Chishimba

"For I am persuaded, that neither death, nor life, nor angels, nor 
principalities, nor powers, nor things present, nor things to come, nor 
height, nor depth, nor any other creature, shall be able to separate us from 
the love of God, which is in Christ Jesus our Lord"





--
Mwamba Chishimba

"For I am persuaded, that neither death, nor life, nor angels, nor 
principalities, nor powers, nor things present, nor things to come, nor 
height, nor depth, nor any other creature, shall be able to separate us from 
the love of God, which is in Christ Jesus our Lord"





--
Mwamba Chishimba

"For I am persuaded, that neither death, nor life, nor angels, nor 
principalities, nor powers, nor things present, nor things to come, nor 
height, nor depth, nor any other creature, shall be able to separate us from 
the love of God, which is in Christ Jesus our Lord"