Re: SMSC Modules (Was: Kannel Swisscom)

2003-02-26 Thread Stipe Tolj
Hi list,

this thread leads us to a discussion I had yesterday with Alexander
from Centrium (and also Harrie Hazewinkel, who is hopefully still
subscribed to the list :)

We need to design a clean module API interface (which is already there
in some extended sense) and allows to plug them in via dynamical
loading of shared objects.

In that way you would only load the SMSC module types you need and we
may offer template, bare-bone source for new ones to follow.

Has anyone checked the approach Harrie did for it? It's available on
the web site at 

  http://www.kannel.org/module_api/

Please do have a look and let's get started with this.

Stipe

[EMAIL PROTECTED]
---
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are



RE: SMSC Modules (Was: Kannel Swisscom)

2003-02-26 Thread Angel Fradejas
Nicholas Rahn wrote:
 iServer is a proprietary Swisscom SMSC.  It abstracts multiple EMI/UCP
 connections with a proprietary HTTP/socket interface in order to provide
 billing, throughput, etc.  There is currently no way to use kannel to
 connect to it.

 You could, however, write a new kannel smsc module to do it.  :-)

 Nick

Is there anyone willing to share his Swisscom iServer smsc module? If not,
I'll have to write one soon.

Angel Fradejas
Mediafusión España, S.A.
[EMAIL PROTECTED]
www.mediafusion.es
Tel. +34 91 252 32 00
Fax +34 91 572 27 08




Re: SMSC Modules (Was: Kannel Swisscom)

2003-02-25 Thread Nisan Bloch
At 04:20 PM 2/25/03 +0100, Rene Kluwen wrote:
Talking about SMSC modules. Where would one start, writing a new one?
Which source files have to be altered...
gw/smscconn.c: to add an entry for your new smsc module
gwlib/cfg.def: if u need special config params for that connection
then u need to write your module. Start, mmm look at the smpp module or the 
emi2 module.

 And what are the requirements that
a module should have?
Well, it should meet the requirements of your upstream provider, it should 
meet the requirements as in smscconn_p.h and it should be nice and well 
behaved ;-)

Is there any documentation?


Start with smscconn_p.h

nisan