Hello,
the message content is encoded just before writing to socket, so no way
to get it in the config route block right now. With a bit of
development, topoh can export a function/pv/transformation that can
return the encoded value.
Cheers,
Daniel
On 6/13/12 7:49 PM, Alex Balashov wrote:
G
Given the transparency with which 'topoh' operates, is there any way to
capture the new, fake values that it has substituted? In other words,
can I, for example, xlog the new Call-ID produced by it? Or does that
all take place on a level of abstraction that cannot be intercepted in
script?
