Hello, Tuesday, November 28, 2006, 8:47:06 AM, you wrote:
TS> .. or any other storage for that matter - the only thing used to match in TS> internal (mem), mysql and pgsql is 'ts' and 'smsc' I'm seeing the same erratic behaviour here running a pool of 5 symmetric UCP connections to a single SMSC. My problem is that DLR's often come down a different link than the original SMS was sent to, so i had to nake all SMSC's in the pool the same, in order for them to use a common storage. Now, with only checking smsc and ts, and a throughput of 5 sms/s per link, i often get false DLR reports and URL calls from kannel. Can this behaviour be modified to include at least the destination number or is there another solution to 'pool' connections like I require? -- Best regards, Thomas mailto:[EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
