Ricky Wibowo wrote:

> No.. :-(
> i think i'm a little stupid in here...
> i just want to receive all messages inbound, and injected to mysql
> database

This will need an external script/app that can handle http get requests,
and can be in any language of your choice

> and all connection via SMPP Protocol to the operator..
>
for the connection the kannel documentation gives enough information on
setup, but you will need to contact an operator to get some of the
configuration details eg. port numbers.

> thanx
>
> Gareth Reakes wrote:
>
>> Hi Ricky,
>>
>> Ricky Wibowo wrote:
>>
>>> By the way,
>>> sorry if i'm wrong, your configuration seems that if any incoming
>>> messages, it will be send again to the sender (MO)...
>>
>>
>>
>>
>>
>>>> group   = smsc
>>>> smsc   = smpp
>>>> smsc-id   = SMSC-1
>>>>
>>>> group  = smsc
>>>> smsc  = smpp
>>>> smsc-id    = SMSC-2
>>>
>>>
>>
>> Above you set up 2 smsc that talk smpp.
>>
>>
>>>> group   = sms-service
>>>> keyword  = default
>>>> get-url  =
>>>> "http://localhost:8080/cgi-bin/sendsms?smsc=SMSC-2&?username=test2&password=test2&sender=%p&text=%a&recipient=%P";
>>>>
>>>> accepted-smsc   = SMSC-1
>>>>
>>>> group   = sms-service
>>>> keyword   = default
>>>> get-url   =
>>>> "http://localhost:8080/cgi-bin/sendsms?smsc=SMSC-1&username=test2&password=test2&sender=%p&text=%a&recipient=%P";
>>>>
>>>> accepted-smsc   = SMSC-2
>>>
>>>
>>
>> Here you set up 2 services with the magic keyword default that only
>> accept messages (all messages though) from 1 of the smsc. So incoming
>> messages from each of the smsc will go to a particular sms-service.
>> From there they call a sendsms - but notice the smsc=SMSC-x in the
>> parameter list. This routes the message back to the other smsc to be
>> sent out over smpp.
>>
>>
>> Is that clear? :)
>>
>>
>> Gareth
>>
>


-- 
Kyriacos Sakkas
Development Team
Netsmart
Tel: + 357 22 452565
Fax: + 357 22 452566
Email: [EMAIL PROTECTED]
http://www.netsmart.com.cy

Taking Business to a New Level!

** Confidentiality Notice: The information contained in this email
message may be privileged, confidential and protected from disclosure.
If you are not the intended recipient, any dissemination, distribution,
or copying of this  email message is strictly prohibited.
If you think that you have received this email message in error, please
email the sender at [EMAIL PROTECTED] **


Reply via email to