Hi Andreas,
not sure about this. If you do serial forking, the reply selected to be sent back to the UAC is only from the last serial step. So if you have a first serial step ended with 302 and a second one ended with 486, the 486 (if no other code is forced from script) will be sent to the UAC.
hopefully I got your scenario correctly - if it doesn't work like this, please let me know.
regards, bogdan
Andreas Granig wrote:
Bogdan-Andrei Iancu wrote:
for re-writing the negative final replies, use the failure route:
Oh, yes, of course. But, however, it seems to be a little bit more complicated.
There are clients with adjustable ring-timeouts, which signal 302 and a Contact to refer to on such a timeout event. I intercept such replies and perform a server-side call-forward.
Now if the UAC the call is forwarded to is busy and replies with 486, I can intercept this reply, but if I call break (for example because there is no conditional call-forward for this busy UAC), the first 302 is handed back to the original caller, and I don't see a way how to catch this reply again and rewrite it.
Any ideas?
Thanks, Andy