Hi,
I've noticed that one of the providers in an installation using kannel is
giving back big message ID's - see Bill error 2 below.. The provider is
using SMPP and using the msg id type 0x03, so hex is given in both the
submit_sm_resp and the deliver_sm. However I'm seeing problems where the
of an int on the bottom one when it
converts it from the hex to long/string..
Any ideas? I've spent the afternoon being quite confused about it all!
Cheers,
Bill.
-Original Message-
From: Stipe Tolj [mailto:[EMAIL PROTECTED]
Sent: 23 November 2005 16:49
To: Bill Brigden
Cc: devel
Malysh
Sent: 23 November 2005 19:37
To: devel@kannel.org
Subject: Re: Message ID issues
Hi,
just drop msg-id-type config option and it should work fine...
Thanks,
Alex
Bill Brigden wrote:
These are my own debugging lines added - more info from log follows:
Alex - setting
Hi all,
Looking through the status's available to start bearerbox under - is it
possible to start with (possibly set with a flag per smsc, or generally) all
the smsc connections in a down state, ie - you have to use the admin port to
start the smsc's needed?
Cheers,
Bill.
Further to your patch, I noticed when there is a bearerbox attached and no
smsbox's attached to it, the bearerbox doesn't appear in the Box
Connections. This is due to the test being an empty() test with a few spaces
in the variable $x... Doing a trim solved this..
Cheers,
Bill
-Original
Hi there,
I stopped 2 connections via stop-smsc this morning, and after restarting
them kannel crashed! From what I can tell, there were 2 mesages in the store
file destined for one of the connections I stopped, and after restarting the
2nd connection, kannel died - it had been started with -d
Hi there,
I just wondered under what circumstances, I should be getting the following
errors:
2004-04-16 16:26:54 [1] ERROR: Error reading from fd 30:
2004-04-16 16:26:54 [1] ERROR: System error 104: Connection reset by peer
2004-04-16 16:26:54 [1] ERROR: Error reading from fd 30:
2004-04-16
Surely if you just set your dlr-url to:
dlrurl=http://10.0.0.211/traker/WebForm1.aspx?receiver=%Psender=%ptid=91
in each request instead of being in the config file, ie:
http://10.0.0.3:13013/cgi-bin/sendsms?user=foopass=barfrom=61428884524to=
Hi
there,
I know this has been
reported in the past, but Ive noticed it again... We have around 12 smpp
connections out from our kannel server, and most of the uptimes are what i would
expect, however some are off, ie:
smscnameSMPP:smpp1.xxx/nameidsmpp1/idstatusonline
The plus should be urlencoded to %2B... as a plus means a space when doing
http gets...
Regards - Bill.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Nicholas Calugar
Sent: 07 January 2004 01:41
To: [EMAIL PROTECTED]
Subject: International SMS
Hi there,
I have just tried sending messages through another provider via smpp, and
they are giving DLR's back ok, except for not using spaces inbetween fields,
ie:
2003-12-16 08:16:50 [24] DEBUG: short_message:
2003-12-16 08:16:50 [24] DEBUG: Octet string at 0x8272ad0:
2003-12-16 08:16:50
Hi All..
I just noticed that there weren't any auto emails this morning with patches
to the devel with re the site / gateway / test compilation
David Holland did report some downtime for the webserver yesterday - would
that have affected cron jobs?
Bill.
Hi,
Really obvious question. when I submit a message via sendsms with a
dlrmask as 7 - why do I get a code 16 back if its rejected via the
submit_sm_resp? Surely the dlrmask 7 stops this - or am I missing something?
Bill.
I think there is an easy response to this: duh!
- Original Message -
From: Alexander Malysh [EMAIL PROTECTED]
To: Bill Brigden [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, September 16, 2003 5:32 PM
Subject: Re: dlr mask question...
Hi,
On Tuesday 16 September 2003 18:25, Bill
Hi,
Looking around mantis earlier, I came across:
http://bugs.kannel.org/view_bug_page.php?f_id=075
Where Stipe has discussed load balancing and failover setup for smsc's. I
did look in the latest snapshot and this kind of information would be useful
as an example there...
Bill.
Hi,
The server only uses one smsbox and it never disconnected from bearerbox -
also I don't have an smsbox id set as there is only one smsbox (and no
routing within smsbox)
Cheers - Bill.
- Original Message -
From: Alexander Malysh
To: Bill Brigden ; [EMAIL PROTECTED]
Sent: Tuesday
Message -
From: Alexander Malysh
To: Bill Brigden ; [EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 1:04 PM
Subject: Re: DLR's staying in kannel.store
On Tuesday 02 September 2003 13:14, Bill Brigden wrote:
Hi,
The server only uses one smsbox and it never disconnected from bearerbox
Hi,
I have noticed that in our config we use these config parms for the dlr-db
group:
group = dlr-db
id = dlr-db
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-service = service
field-url = url
field-mask = mask
field-status = status
field-source =
It may be (as Stipe said) that the phone uses the source address ( or
) as well as the concatenation Id (in this case 00), for re constructing
messages.
- Original Message -
From: DILWORTH MICHAEL [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 2:12 PM
Hi,
I recently started using the CVS version instead of 1.2.1, and have noticed
that when using DLR's - if there is a smsc failure, ie:
2003-08-20 15:10:11 [7] DEBUG: SMPP[xxx-smpp1]: Got PDU:
2003-08-20 15:10:11 [7] DEBUG: SMPP PDU 0x81d62c8 dump:
2003-08-20 15:10:11 [7] DEBUG: type_name:
As far as changing it to that form - it would make it a bit easier from our
perspective. Also - yes, it is mblox's server.
Regards,
Bill.
- Original Message -
From: Alexander Malysh [EMAIL PROTECTED]
To: Bill Brigden [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 4
Hi,
It seems like a small thing, but could the reply-to be set to the list - as
I have replied to messages before and not replied to the list - so when
people look through archives it seems like some questions remain unanswered
when infact they may have done!
Also - a really small thing, but
I think that it was a poor suggestion / comment to make, as that part hadnt
quite sunk in relating to all the bogus messages that would get onto the
list!
Regards,
Bill.
- Original Message -
From: Bruno Rodrigues [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 18, 2003 2:55
PROTECTED]
Sent: Monday, August 18, 2003 4:21 PM
Subject: Re: reply to setting list request
Bill Brigden [EMAIL PROTECTED] wrote:
I think that it was a poor suggestion / comment to make, as that part
hadnt
quite sunk in relating to all the bogus messages that would get onto the
list!
I don't
Message -
From: Andreas Fink [EMAIL PROTECTED]
To: Bill Brigden [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, August 15, 2003 1:36 PM
Subject: Re: Possible bug with smsc-stop
On Freitag, August 15, 2003, at 01:58 Uhr, Bill Brigden wrote:
Hi,
Im running cvs-20030811, and we have 9
Hi,
Using kannel cvs-20030811, I have sent a mobile originating message that
comes in via smpp 3.4:
This is bill's test... @ ?
But smsbox posts it to me like:
This+is+bill's+test...+%A1+%3F+%22
And the bearerbox log says:
2003-08-14 18:01:03 [8] DEBUG: SMPP PDU 0x81e04c8 dump:
2003-08-14
On 1st of this month at 23:48, in an attached text file with other problems
(well, the DLR problems are no more), but in the output I got a panic from
bearerbox:
2003-08-01 22:24:40 [5] PANIC: gwlib/octstr.c:2150: seems_valid_real:
Assertion `ostr-data == NULL' failed. (Called from
Hi,
With the CVS version (and maybe 1.3.1), it allows you to set the
service-type for a connection. Is it possible to change to so that you can
set it per message with a CGI / Kannel header variable - as we use Kannel to
connect to an operator that gives one username and password different
Replying to my own message :)
When I said useless - I said that because we want to use the routing
abilities of the provider per message instead of having to connect to the
same operator 4 times, just to be able to use each different route
- Original Message -
From: Bill Brigden
Hi,
I've just started using the dlrmask 31 for an application to track when
messages get to our smpp provider, however the DLR code to say its been
submitted i thought was 8, however this is the log from the bearerbox access
log:
2003-08-01 17:43:33 send-SMS request added -
Attached is the debug log...
The line in particular is:
2003-08-01 17:21:33 [4] DEBUG: sql: UPDATE dlr SET status=12 WHERE
smsc='smpp1' AND ts='27164850' LIMIT 1;
Any ideas?
- Original Message -
From: Alexander Malysh [EMAIL PROTECTED]
To: Bill Brigden [EMAIL PROTECTED]; [EMAIL
Also - this was using the CVS version - the same behaviour as 1.2.1 that we
use on production machines...
- Original Message -
From: Bill Brigden [EMAIL PROTECTED]
To: Alexander Malysh [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Friday, August 01, 2003 6:33 PM
Subject: Re: smpp 3.4 DLR's
Looking through the script - the server indicator does have a bug where the
expiry date was hardcoded in the past - there was a patch to the devel list
a short while ago which removed this bug - a simple way to change it is to
comment out these lines in sendsms.php around line 236:
33 matches
Mail list logo
