> Hello, guys. > > I need to conciliate for the first time with an operator. > They are using SMPP v3.4 and we are using kannel 1.4.1 CVS. > > So, the problem is I'm using my own transaction ID in messages/dlrs, but > kannel uses another transaction ID with operator. > Has anybody worked on a solutions changing the source to solve this problem > in the future, or has anybody got a parser to > find the correlation between both IDs, from the logs ? > > Regards, > rm
A *very wrong* way to do this, but also the only one functional way that i've found and i use, is to add to the dlr-url dinamically a custom generate uniqueid. Using an external dlr storage on postgres or mysql in this way you can correlate the kannel transaction id with the operator one when the first dlr message come in. I know, this is a crappy method, anyway, it work. I think that the better way is to add something in the dlr-url that pass to our external web application a variable with the operator transaction id, but this seem to be not an option actually with kannel. -- Franco (nextime) Lanza Busto Arsizio - Italy SIP://[EMAIL PROTECTED] NO TCPA: http://www.no1984.org you can download my public key at: http://danex.nexlab.it/nextime.asc || Key Servers Key ID = D6132D50 Key fingerprint = 66ED 5211 9D59 DA53 1DF7 4189 DFED F580 D613 2D50 ----------------------------------- echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D212153574F444E49572045535520454D20454B414D204F54204847554F4E452059415020544F4E4E4143205345544147204C4C4942snlbxq | dc -----------------------------------
signature.asc
Description: PGP signature
