Hi all,
I try to use Kannel 1.1.6 to connect to SMSC via SMPP with a service
number assigned to GW. When a subscriber send any SM to service number,
the msg will deliver to GW.
In the source, file smsc_smpp.c, function: handle_pdu():
case deliver_sm
(void) bb_smscconn_receive(smpp->conn, pdu_to
Not everybody wold like to use development version either. But I would
agree, that
if we add an important feature to a development release, we should make a
new
release. Of course the problem is that someone must make the release.
Aarno
- Original Message -
From: "Oded Arbel" <[EMAIL PROT
Hi,
log files for succesfull v. unsuccessfull delivery attempt would be nice. In
addition, I would
like to see configuration files.
Aarno
- Original Message -
From: "Randeep Singh Bhatia" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 17, 2002 6:09 PM
Subject: FW: WAP Pus
Changing the sender ID with Kannel is possible, but module dependant as
some SMSCs do not support that. specificly, the pseodo-SMSC module for
GSM modems does not support that, as it is impossible to chane the
sender ID when sending through a GSM modem.
--
Oded Arbel
m-Wise Inc.
[EMAIL PROTECTED]
The deliver_sm is meant to make the ESME (in this case Kannel) respond
with a deliver_sm_resp PDU in order to confirm receipt of the deliver_sm
message. This message is only meant to go from the ESME (Kannel) to the
SMSC (your provider) as not a message to the phone subscriber that
submitted t
I agree with Oded that currently at the moment people are using the CVS
'live' tree as a release ready version and expecting it to work 100% - a
situation that has occured due to the delay of good new releases since the
demise of WapIT.
We should direct most 'newer user/developers' of the syst
Hi Bruno,
Good to hear it although I didn't understand it in the userguide.
Did you refer to Kanel 1.0.3 or 1.1.6?
I saw this line on Userguide version 1.0.3:
"store-file - filename A file in which any received SMS messages are stored
until they are successfully handled. By using this variable
Alex Judd wrote:
>
> I'm doing some fairly heavy work on the smsc_smpp.c driver at the moment
> to ramp it up a bit and I've got a couple of questions re: the esm_class
> values that the code currently thinks are DLR reports.
>
> The current code checks for 0x02 and 0x04 as DLR reports, however
Oded Arbel wrote:
>
> another problem with an SSL connection, is that if the socket connection
> in conn_open_tcp() called from conn_open_sll() fails, it returns NULL,
> but conn_open_ssl() immidietly tries to refer to it as initialized
> structure - which of course causes Kannel to crash.
> conn
Le Nhu Hai wrote:
>
> I try to use Kannel 1.1.6 to connect to SMSC via SMPP with a service
> number assigned to GW. When a subscriber send any SM to service number,
> the msg will deliver to GW.
> In the source, file smsc_smpp.c, function: handle_pdu():
>
> case deliver_sm
> (void) bb_smscconn_r
Dima Milentiev wrote:
>
> Hi Bruno,
> i've sent the patch to list 2 weeks ago and still have not any comments.
> May be you can look at it?
+1, commited to cvs.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
40470 D
Oded Arbel wrote:
>
> Agreed. I was hoping that at least the billing issue (I remember it
> being talked about in the list a while back) would interest people.
> I do think, though, that fixes to problems not yet detected "in the
> wild" should go in anyway : that's why it's called a "development
Dima Milentiev wrote:
>
> Hi Bruno,
> i've sent the patch to list 2 weeks ago and still have not any comments.
> May be you can look at it?
+1, commited to cvs.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
40470 D
Oded Arbel wrote:
>
> Agreed. I was hoping that at least the billing issue (I remember it
> being talked about in the list a while back) would interest people.
> I do think, though, that fixes to problems not yet detected "in the
> wild" should go in anyway : that's why it's called a "development
Le Nhu Hai wrote:
>
> I try to use Kannel 1.1.6 to connect to SMSC via SMPP with a service
> number assigned to GW. When a subscriber send any SM to service number,
> the msg will deliver to GW.
> In the source, file smsc_smpp.c, function: handle_pdu():
>
> case deliver_sm
> (void) bb_smscconn_r
Alex Judd wrote:
>
> I'm doing some fairly heavy work on the smsc_smpp.c driver at the moment
> to ramp it up a bit and I've got a couple of questions re: the esm_class
> values that the code currently thinks are DLR reports.
>
> The current code checks for 0x02 and 0x04 as DLR reports, however
Oded Arbel wrote:
>
> another problem with an SSL connection, is that if the socket connection
> in conn_open_tcp() called from conn_open_sll() fails, it returns NULL,
> but conn_open_ssl() immidietly tries to refer to it as initialized
> structure - which of course causes Kannel to crash.
> conn
Hi Andreas,
Firstly, thanks for you patience, what you've said sounds very good for me,
but I still have some doubts (or some worries):
a) Does Kannel allways store a message before contacting a SMSC and
vice-versa an Application? Is this true for SMS-MT, SMS-MO and DLR
messages?
b) If I send 1
Thank Alex, Andreas and others for replies.
However, I could not to find out the code that submit SM "No service
specified" to subcriber. Can you help me to find out?
Thanks again
Le Nhu Hai
--- Alex Judd <[EMAIL PROTECTED]> wrote:
> The deliver_sm is meant to make the ESME (in this case Kan
Hello,
Here's the final patches to include smpp reconnection timings etc to be
able to be set via config. As I mentioned before I have added the fields
to the smpp structure (see patches below for details).
Cheers,
Alan
On Tue, 2002-05-14 at 12:57, Alan McNatty wrote:
> Ok - here's a couple of
20 matches
Mail list logo
