Re: Another broken SMSC DLR implementation?

[Alex Kinch]

Of the four connections, two are for alpha sender and two for numeric (different source-addr-ton settings for alpha). I've seen the DLR for a message sent on one of the numeric connections comes back on the alpha connection - so same SMSC-ID across the two types of connection would break things.   Guess the best way of fixing this for the mo is different system_id and system_type for the numeric and alphas.   Alex ----- Original Message ----- From: Stipe Tolj To: David Tully Cc: [EMAIL PROTECTED] ; Alex Kinch Sent: Wednesday, November 12, 2003 1:09 PM Subject: Re: Another broken SMSC DLR implementation? David Tully wrote: > > Sounds like a provider issue.. > > We have a provider that does just this - delivers DLRs on one bind that > relate to another bind. I get round this by giving the binds the same > SMSC-ID. correct! This is currently the only practible solution. Name all SMPP smsc links with the *same* smsc-id and you will get it done. This issue is on the TODO for implementing smsc-groups. 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-----