Re: X-Kannel-SMSC and message splitting

Alan McNatty <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <1070222007.1118.8.camel@euterpe>
Hi Stipe,

Tested again with TEST1 and TEST2 connections both with allowed-smsc-id
= "TEST1;TEST2" - this makes them available as 'best' choices but not
preferred (so the first best choice wins, TEST1 or TEST2). So, if I have
smsc=TEST2 I still can't guarantee delivery via TEST2. I don't want to
set preferred-smsc-id because I don't want all messages to go via that
link. I still can't see how the cgi variables have any impact. 

Cheers,
Alan

DEBUG: smscconn_usable: checking to see if conn is usable for msg - smsc
id <TEST1>
DEBUG: smsc2_rout: best_ok <TEST1>
DEBUG: smscconn_usable: checking to see if conn is usable for msg - smsc
id <MODEL>
DEBUG: smscconn_usable: checking to see if conn is usable for msg - smsc
id <TEST2>
DEBUG: send_msg: sending msg to box: <127.0.0.1>
DEBUG: SMPP[TEST1]: Sending PDU:

On Sat, 2003-11-29 at 00:47, Stipe Tolj wrote:
> Alan,
> 
> > Note my config doesn't include any allowed or preferred sections in smsc
> > configurations (except for MODEL connection). So it seems to run only
> > random (ie: cgi variables are ignored).
> 
> now, you *have to* restrict the smsc groups to ensure that the set
> 'smsc' value at sendsms interface is obeyed. 
> 
> Which means if you don't have any allowed rules on the smsc groups,
> the routing process will not care about your "preference" that you
> gave smsbox to route a specific message to a specific smsc.
> 
> So simply add the following to the smsc groups:
> 
>   group = smsc
>   ...
>   smsc-id = A
>   allowed-smsc-id = A
> 
> to ensure that only messages that have been explicetly injected to
> sendsms interface with "...&smsc=A" are routed to this link and to
> *none other*.
> 
> Stipe
> 
> mailto:[email protected]
> -------------------------------------------------------------------
> Wapme Systems AG
> 
> Münsterstr. 248
> 40470 Düsseldorf, NRW, Germany
> 
> phone: +49.211.74845.0
> fax: +49.211.74845.299
> 
> mailto:[email protected]
> 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-----
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.