Dave Donovan wrote:
Yes. I also had a truly evil suggestion earlier this evening, namely that I encode the information in the extension being dialed, using that to unify (i.e. add 3 or 4 digits to the start of the extension that provide a (temporary) unique ID). There's probably dozens of ways to hack around it, I'd just hoped there would be a straightforward and correct one (i.e. one that could be added to pyst as a general solution, not something that is application-specific and fragile).I haven't tested this, it's just a thought. What about sending through a variable as part of the Originate message, then Noop(${Variable} ${CHANNEL}) in the extension after the call setup. I think that would send back a manager message with the variable (supplied at originate) and the channel_ID. Would that let you correlate the two?Do I understand what you're asking correctly?
I think the ideal thing would be for messages to include the ACTIONID of the manager command that spawned them if that's possible.
Indeed, that would seem to be the proper operation. Have fun, Mike -- ________________________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com
