Cheikh Sidiya schrieb: > > Dears > can you explain the general architecture of sms application using kannel > as gateway > 1-is it recommended to separate kannel and application server (not > install kannel in the application server?)?? > 2-how and which protocols are used for communication between Kannel and > application server > only HTTP and HTTPS or SMPP or others?? > carrier---------SMPP------------KannelGateway______http?or > SMPP?_______application server
Hi Cheikh, let me point out here: 1. as often in science, the answer is: it depends. If the load is signification, (figures in terms of concurrency depends on various aspects) then it is recommendable to separate the layers. Please recall that Kannel is considered as a SMS transportation layer itself, from the point of view of the application layer/logic. 2. the normal Kannel as SMS gateway abstracts all SMSC client side protocols, encapsulated in the bearerbox daemon to the HTTP and HTTPS protocols used in smsbox towards the application layer. So what you have is this: SMSCs <-SMPP/UCP/CIMD2/GSM/HTTP/..-> bearerbox <-> smsbox <-HTTP/HTTPS-> application layer in a higher abstractive layer this means: SMSCs <-> (client side)bearerbox <-> smsbox(server side) <-> application layer If you want to utilize SMPP v3.4 or/and EMI/UCP 4.0 on the server side, you may consider the commercial add-on Kannel SMPP v3.4 server (smppbox) that I provide. It allows you to add the following chaining: SMSCs <-SMPP/UCP/CIMD2/GSM/HTTP/..-> bearerbox <-> smppbox <-SMPP-> external client Regards, Stipe -- ------------------------------------------------------------------- Kölner Landstrasse 419 40589 Düsseldorf, NRW, Germany tolj.org system architecture Kannel Software Foundation (KSF) http://www.tolj.org/ http://www.kannel.org/ mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org -------------------------------------------------------------------
