Hi man, did you try to set identical smsc id of the two smsc connections ?
if this approach failed contact me on skype or gtalk or ICQ skype: seikath icq: 1920417 gtalk: seikath cheers Iain Dooley wrote: > > >> man, dont know for the mysql triggering > > i've done it a couple of times, it's not too hard. > >> i use postgresql mostly, and yes, >> this could be achieved with trigger or with rule on insert >> >> the trigger updates the data, the rule just changes the data before to >> be inserted .. :) anyway its not sql issue here > > if you could be so kind as to share your postgresql rule (maybe off > list?) then i could adapt that to work as a mysql trigger and then i'd > be more than happy to share that with the rest of the community as i > reckon this is probably something people will come across if they want > to use multiple smsc connections with mblox. > >> and, have to say, the idea to ask mblox for assistance is the best idea > > i have :) whether or not they can provide that assistance is another > story!! > > cheers > iain > >> cheers >> >> >> >> Iain Dooley wrote: >>> >>>> the workarround .. :) >>>> in short, use postgresql for the dlr storage >>>> >>>> and use rule on insert to overwrite the smsc_id so when kannel does its >>>> sql query to find the message when DLR comes from the smsc. >>>> >>>> im not so familiar with mysql, but dont think mysql is able to do that. >>> >>> wow. okay, i'll also check with mblox if they can please send my dlr's >>> back to the originating server which would solve the problem without me >>> having to do anything. >>> >>> what you're describing above sounds like a trigger, is that correct? if >>> so you can do that with mysql. is there any documentation anywhere that >>> describes what has to happen in more detail? >>> >>> i need to setup kannel with mysql dlr storage soon anyway .. >>> >>> cheers >>> iain >>> >>> >>> >> >> > > >
