Re: Question about routing

Oscar Medina Duarte wrote:
> Hello !
> 
> I'm not getting what I want I don't know what is missing, I have 5 smsc
> connections, configured that bound correctly, and only one smsbox that
> gets all the messages, and that is working fine. The problem is that
> outbound messages are not sent, with the message :
> 
> ...
> 2004-08-26 13:11:59 [9373] [2] DEBUG: HTTP: Creating HTTPClient for `<an
> IP>'.
> 2004-08-26 13:11:59 [9373] [3] DEBUG: HTTP: Resetting HTTPClient for
> `<an IP>'.
> 2004-08-26 13:12:44 [9373] [4] WARNING: smsbox_list empty!
> 2004-08-26 13:12:44 [9373] [4] WARNING: smsbox_list empty!
> 2004-08-26 13:12:50 [9373] [3] DEBUG: HTTP: Resetting HTTPClient for
> `<an IP>'.
> 2004-08-26 13:13:38 [9373] [12] DEBUG: boxc_receiver: sms received
> 2004-08-26 13:13:38 [9373] [12] WARNING: Cannot find SMSCConn for
> message to <a telephone>, rejected.
> 2004-08-26 13:13:38 [9373] [12] WARNING: Message rejected by bearerbox,
> no router!
> 2004-08-26 13:13:38 [9373] [12] DEBUG: send_msg: sending msg to boxc:
> <smsbox_01>
> 2004-08-26 13:13:44 [9373] [4] WARNING: smsbox_list empty!
> 2004-08-26 13:13:44 [9373] [4] WARNING: smsbox_list empty!
> ...
> 
> at the bearerbox, as you can see, I'm using sendsms to out bind
> messages, but that is not working.
> 
> NOTE: The data included within "<" and ">" is data that depending on its
> context may be an IP, password, phone number, etc...
> 
> Thanks !!
> 
> == Oscar
> 
> 
> ------------------------------------------------------------------------
> 
> ######################################
> ###    bearerbox.conf  ###############
> ###  Author: Oscar Medina ############
> ######################################
> 
> 
> ###########################
> ########    Core     ######
> ###########################
> 
> group = core
> admin-port = <some_data>
> admin-password = <some_data>
> status-password = <some_data>
> admin-deny-ip = "*.*.*.*"
> admin-allow-ip = "127.0.0.1;<some_IP>"
> smsbox-port = <some_port>
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "127.0.0.1;<some_IP>"
> log-level = 0
> log-file = "logs/bearerbox.log"
> access-log = "logs/bearerbox.access"
> 
> 
> 
> ########################################
> #####       SMSC's     #################
> ########################################
> 
> 
> ############################
> ## SMSC:     test         ##
> ## Number:   <some_data>  ##
> ## smscID:   <some_data>  ##
> ############################
> 
> group = smsc
> smsc = smpp
> smsc-id = <smsc_1>
> denied-smsc-id = "<smsc_2>;<smsc_3>;<smsc_4>;<smsc_5>"
> allowed-smsc-id = <smsc_1>
> preferred-smsc-id = <smsc_1>
> host = <some_IP>
> #host = localhost
> port = <some_port>
> transceiver-mode = true
> smsc-username = <some_data>
> smsc-password = <some_data>
> system-type = VMA
> interface-version = 0x34
> enquire-link-interval = 60
> max-pending-submits = 10
> reconnect-delay = 30
> source-addr-ton = 0
> source-addr-npi = 1
> source-addr-autodetect = true
> dest-addr-ton = 2
> dest-addr-npi = 1
> log-level = 0
> log-file = "logs/smsc_TelcelTest.log"
> 
> ... plus other 4 smsc's with the same kind of config,
>     from with the corresponding smscID... 

config looks good. This is a more "semantical problem".

Your smsc groups do 'allow-smsc-id = <smsc-id>' which means, only a 
message carrying this smsc-id will be allowed to be passed to this 
smsc link.

So, if you call the sendsms HTTP interface _without_ the 
'smsc=<foobar>' parameter, this would result exactly in the "no 
router" error message inside the main routing facility of bearerbox.

Actually you are trying to send messages without "specifying" which 
way to go, but on the other hand, do require (with the 
allowed-smsc-id) the smsc links to have that specification.

Stipe

mailto:stolj_{at}_wapme.de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.2 (Cygwin)

mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-----END PGP PUBLIC KEY BLOCK-----