Hi, I have one provider here using SOAP for external parties who wish to send and receive SMS through their centre. They are also one of the major and best providers here.
We are using Kannel as our gateway. 3 major providers here have their own different standard interface/protocol for external party to connect to their center. One is using SOAP, another using normal HTTP calls with headers, and the other one using bytes transfer and only one using industrial SMPP protocols. I involve a lot in Kannel features customization to meet our own needs, and thus I do some debugging and coding in Kannel C codes. I don't mind if I take part to continue completing this module. But my skills and knowledge is limited and I need more guidance from you guys to complete it. Kannel has its own library for all protocols like HTTP, Socket, etc. What I need is actually a bit more detailed description and how it all layered in the Kannel. It takes time for me to understand all codes and I have other tasks to do as well. Perhaps some documents for technical stuffs would help. Can you roughly brief here what else need to be done or to be changed in smsc_soap modules? Thanks James -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Oded Arbel Sent: Thursday, February 12, 2004 12:33 AM To: [EMAIL PROTECTED] Cc: Stipe Tolj; James Wong Subject: Re: SOAP ביום רביעי 11 פברואר 2004, 11:10, נכתב על ידי Stipe Tolj: > Hi James, > > Kannel has a smsc_soap.c Module that implements a SOAP/XML transport > layer via HTTP for MT and MO SMS tranmission. The SOAP module hasn't > been yet "linked" into the abstraction layer. You would have to modify > slightly the bb_smscconn and smsccon files and simply "add" the > smsc_soap.c functions prototype callers into the files and recompile. > > Actually I don't know which SOAP version it speaks. It actually doesn't speak SOAP at all - the SOAP part of the name is completly a distraction. what it does is provide infrstructure for handling XML based messaging. unless the xml your provider speaks is very simple (and SOAP is anything but simple - its an MS standard after all) the smsc_soap won't work out of the box for you. smsc_soap uses user supplied template files to generate XML messages by sending the template as is over HTTP after replacing specially crafted keywords in the text of the template with data from the sms message structure of kannel. it supports all the attributes of the sms structure (at the time of the writing) as well as some special names that denote special formatting. if you need anything else I'm afraid you'd have to add formatting functions into smsc_soap - but its very easy to do if you know some C. for MO and DLR handliing it reads user supplied mapping files that map XML tags and attributes into kannel sms message structure fields. > The maintainer of > the Module (Oded), seems to be inactive currently, even while he is > still subscribed to the list AFAIK. Alive and well, just awfully busy doing non-kannel related stuff. I still have your email on my "to answer" list, sorry for not getting to it right now. > @Oded: are you going to keep this up-to-date or may an other person > pick up the module and keep maintaining it? Any one who want to pick this up is welcome to do and will get all the help from me (assuming I'm not too busy to answer emails, that is ;-). Currently the company I work for is phasing out our Kannel installations and is moving away from using Kannel based SMS products, so no company sponsored time from me is going to be going into kannel in the foreseeable future. OTOH I have full intention to keep working on Kannel in my spare time (whenever I find some I'll let you know :-). > Another option may be the > usage of gSOAP, which is a superb SOAP server/client pre-processor > layer for C. This would avoid all the fuzzy XML parsing and SOAP > element handling itself inside. Which is very good for real SOAP messaging. Unfortunatly I have not yet encountered any SMS connectivity provider that actually uses SOAP. they may label their products as SOAP (and some do) but its always some sort of proprietary XML schema, which is what smsc_soap was designed to handle. -- Oded Arbel m-Wise mobile solutions [EMAIL PROTECTED] +972-9-9581711 (116) +972-67-340014 ::.. We'll cross that bridge when we come back to it later.
