Hi Stipe, why did you setup both smsc-ids into the allowed-smsc-id configuration directive?
Ok - what I'm think is that TEST1 and TEST2 both receive/deliver messages. Both share delivery randomly so are both 'allowed' from each other. From what I read in docs I thought specifying a smsc cgi variable it would force delivery via the specified link. I don't want to hardwire the preference for all so use cgi rather than 'preferred' in config. Why else would we have such a cgi variable? I guess I'm just trying to figure out why we have the cgi variable (and how it fits in with allowed/preferred). Was just trying to use it while testing. I can do everything I need by setting config variables (in production) but I'm confused as to what the cgi variables do - they are documented to perform a function they don't seem to. Has the use of smsc in cgi variables been superseded with the new routing process? Should it be removed? Cheers, Alan On Mon, 2003-12-01 at 12:24, Stipe Tolj wrote: > Alan McNatty wrote: > > > > 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. > > why did you setup both smsc-ids into the allowed-smsc-id configuration > directive? I tought you would like to have explicite routing to the > specific smsc-id? > > 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-----
