Hi Ricky,
             I've forgotten to add the "sms-service" part of the
config file to the email.
Anyway, I've managed to connect the other Network's Operators SMSC by
creating my own fake SMSC program, that listens to 2 ports, one for
incoming messages from the other Network SMSC and another  for SMSs
comming from Kannel.

The problem I'm having now is with the sms-service group configuration.

group   = sms-service
keyword  = default
get-url  = 
"http://localhost:13013/cgi-bin/sendsms?smsc=MYSMSC&username=XXX&password=XXX&sender=%p&text=%a&recipient=%P&to=%P&priority=0";
allowed-receiver-prefix = "111"

When I send a message from my FAKESMSC to a 111 prefix number, I get
on the smsbox output the following:

2005-06-28 11:12:08 [32326] [4] INFO: Starting to service <Prueba2>
from <123> to <111750106>
2005-06-28 11:12:08 [32326] [9] DEBUG: Parsing URL
`http://localhost:13013/cgi-bin/sendsms?smsc=MYSMSC&username=XXX&password=XXX&from=123&text=Prueba2&to=13013&priority=0':
2005-06-28 11:12:08 [32326] [9] DEBUG:   Scheme: http://
2005-06-28 11:12:08 [32326] [9] DEBUG:   Host: localhost
2005-06-28 11:12:08 [32326] [9] DEBUG:   Port: 13013
2005-06-28 11:12:08 [32326] [9] DEBUG:   Username: (null)
2005-06-28 11:12:08 [32326] [9] DEBUG:   Password: (null)
2005-06-28 11:12:08 [32326] [9] DEBUG:   Path: /cgi-bin/sendsms
2005-06-28 11:12:08 [32326] [9] DEBUG:   Query:
smsc=MYSMSC&username=XXX&password=XXX&from=123&text=Prueba2&to=13013&priority=0
2005-06-28 11:12:08 [32326] [9] DEBUG:   Fragment: (null)
2005-06-28 11:12:08 [32326] [9] DEBUG: HTTP: Reusing connection to
`localhost:13013' (fd=26).
2005-06-28 11:12:08 [32326] [9] DEBUG: Socket connected at once
2005-06-28 11:12:08 [32326] [9] DEBUG: HTTP: Sending request:
2005-06-28 11:12:08 [32326] [9] DEBUG: Octet string at 0xa047ad8:
2005-06-28 11:12:08 [32326] [9] DEBUG:   len:  191
2005-06-28 11:12:08 [32326] [9] DEBUG:   size: 1024
2005-06-28 11:12:08 [32326] [9] DEBUG:   immutable: 0
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 47 45 54 20 2f 63 67 69
2d 62 69 6e 2f 73 65 6e   GET /cgi-bin/sen
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 64 73 6d 73 3f 73 6d 73
63 3d 50 4f 52 54 48 41   dsms?smsc=MYSMSC
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 42 4c 45 26 75 73 65 72
6e 61 6d 65 3d 74 65 73   &username=XXX
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 74 65 72 26 70 61 73 73
77 6f 72 64 3d 66 6f 6f   &password=XXX
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 62 61 72 26 66 72 6f 6d
3d 31 32 33 26 74 65 78   &from=123&tex
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 74 3d 50 72 75 65 62 61
32 26 74 6f 3d 31 33 30   t=Prueba2&to=130
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 31 33 26 70 72 69 6f 72
69 74 79 3d 30 20 48 54   13&priority=0 HT
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 54 50 2f 31 2e 31 0d 0a
48 6f 73 74 3a 20 6c 6f   TP/1.1..Host: lo
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 63 61 6c 68 6f 73 74 3a
31 33 30 31 33 0d 0a 55   calhost:13013..U
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 73 65 72 2d 41 67 65 6e
74 3a 20 4b 61 6e 6e 65   ser-Agent: Kanne
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 6c 2f 31 2e 34 2e 30 0d
0a 58 2d 4b 61 6e 6e 65   l/1.4.0..X-Kanne
2005-06-28 11:12:08 [32326] [9] DEBUG:   data: 6c 2d 46 72 6f 6d 3a 20
31 32 33 0d 0a 0d 0a      l-From: 123....
2005-06-28 11:12:08 [32326] [9] DEBUG: Octet string dump ends.

You can see on the first log that destination number is well received
and that the correct sms-service group is called. But, when the
get-url is called, a wrong destination number is sent. It's sending
the SMSBOX port number.

Could you give me a hand? I've also checked the mailing list archives
and found that somebody has asked about this before, but didn't
receive an answer.

regards,
           Pablo Salinas
    

On 6/23/05, Ricky Wibowo <[EMAIL PROTECTED]> wrote:
> in your configuration,
> which statement is declared your prefix??
> i didn't see any thing... :-)
> 
> thanx
> 
> Pablo Salinas wrote:
> 
> >First of all, thanks everybody for all the responses. Now, let me be
> >more specific on the my network scenario:
> >
> >As I said before, I need Kannel to work as an SMS-Gateway, this is the
> >network configuration:
> >
> >
> >                                Foreign Operator A
> >   ----------
> >--------- Server SMPP V3.4 Client-----------------
> >| My SMSC  |                                         | SMS GW
> >|-----------------------------| Routing Prefix| |                  |
> >                                      |                 |
> >               |               222 |
> >| Routing      |Server   SMPP V 3.4  Client |                 |
> >                      --------------------
> >| Prefix        |------------------------------------------| Kannel      |
> >|                 |                                          |
> >        |Server SMPP V3.4 Client--------------
> >| 111           |                                           |
> >      |-----------------------------| Routing Prefix|
> >-------------------
> >----------------                              |        333         |
> >
> >                                      ---------------------
> >
> >                              Foreign Operator B
> >
> >Numbers on my Network start with prefix 111, while I have two other
> >Operators (A and B) connected to my SMS GW with number prefixes 222
> >and 333.
> >
> >I need SMSs from my SMSC to be routed to Operator A or B depending on
> >the Destination Number Prefix. And I need SMSs coming from Operators A
> >and B to be routed to my SMSC (In case its destinated to Numbers with
> >Prefix 111).
> >
> >As you can see, only "My SMSC" works as an SMPP server, the other two
> >network operators get connected to my SMS GW as SMPP Clients.
> >
> >I've tried the sendsms script in order to send SMSs to my SMSC, but
> >it's not working, I'm getting an "Unknown request." response. Although
> >the reception from SMS sent to my SMSC are working fine.
> >
> >Also, let me say that only connection from my SMSC to SMS GW is
> >private, connections from other Operators are public, so security
> >issues should be taken into account.
> >
> >Find attached my configuration file:
> >
> ># Core Configuration
> >####################
> >group = core
> >admin-port = 13000
> >smsbox-port = 13001
> >admin-password = xxx
> >box-allow-ip = "*.*.*.*"
> >access-log = "/var/log/kannel/access.log"
> >
> >######################################################################################
> ># SMSC CONNECTIONS
> >###################
> ># My SMSC
> >group = smsc
> >smsc = smpp
> >smsc-id = MYSMSC
> >host = xxx.xxx.xxx.xxx
> >port = xxxx
> >receive-port = xxxx
> >smsc-username = "xxx"
> >smsc-password = "xxx"
> >system-type = ""
> >address-range = ""
> >
> >########################################################################################
> ># SMSBOX SETUP
> >###############
> ># This part of the configuration file defines the SMS properties of Kannel
> >group = smsbox
> >bearerbox-host = localhost
> >sendsms-port = 13013
> >global-sender = 13013
> ># there should be default always
> >
> >########################################################################################
> ># SEND-SMS USERS
> >################
> ># This part of the configuration file enable an SMS push. Each of
> >these sendsms-user groups define one account,
> ># which can be used for the SMS push, via HTTP interface
> >group = sendsms-user
> >username = xxx
> >password = xxx
> >
> >#######################################################################################
> ># SERVICES
> >############
> >group = sms-service
> >keyword = default
> >text = "No service specified"
> >
> >Can you give me more hints on how to implement my network configuration?
> >
> >Why the sendsms script isn't working?
> >
> >Thanks again.
> >
> >regards,
> >        Pablo Salinas
> >
> >
> >-----Mensaje original-----
> >De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nombre
> >de Kyriacos Sakkas
> >Enviado el: miƩrcoles, 22 de junio de 2005 4:36
> >Para: [email protected]
> >Asunto: Spam:Re: Configuring Kannel as an SMS Gateway
> >
> >
> >Beats mine for simplicity...
> >
> >
> >
> >    Kyriacos "must re read the docs" Sakkas.
> >
> >Gareth Reakes wrote:
> >
> >
> >
> >>Hey,
> >>
> >>    Take a look at reroute properties for SMS centers. I have not used
> >>them but they look like they should do what you want.
> >>
> >>
> >>http://www.kannel.org/download/1.4.0/userguide-1.4.0/userguide.html#AEN1085
> >>
> >>
> >>Cheers,
> >>
> >>Gareth
> >>
> >>Ricky Wibowo wrote:
> >>
> >>
> >>
> >>>Gareth Reakes wrote:
> >>>
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>Pablo Salinas wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Hi there,
> >>>>>    I want Kannel to work as an SMS Gateway between different
> >>>>>SMSCs. But I don't know how to set on the config file so that
> >>>>>messages from SMSC A are routed to SMSC B and viceversa. Could you
> >>>>>send me a sample configuration file?
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>It depends what protocols each are speaking. For example, if it was
> >>>>HTTP create a new http type in smsc_http and then either match all
> >>>>incoming messages from that smsc and send to another smsc in the
> >>>>geturl parameter. This is all explained in the docs (although it is
> >>>>hard to understand sometimes). What particular part of the docs are
> >>>>you having problems with?
> >>>>
> >>>>
> >>>>
> >>>How about SMPP Prtotocol that used?? If we want to fetch all incoming
> >>>messages from smsc, get-url paramater needed??
> >>>Or it's only for smsc_http type? I'm still confuse about this...
> >>>
> >>>thanx
> >>>
> >>>
> >>>
> >
> >
> >--
> >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