Hi All.<br>
<br>
I'm using t_check_status() to do call forwarding on 486 Busy responses.
I have an odd thing happening where SER receives the 486 Busy message
(for which SER properly sends an ACK response) and then the
failure_route calls append_branch() and t_relay() to try another
destination.<br>
<br>
After the new leg of the call is setup and then torn down, the original
486 Busy seems to be hung in the tm module, because it magically
appears in ngrep, which shows it being sent back to the caller as if
the append_branch() never took place.<br>
<br>
Is there anything special that I should be doing to &quot;swallow&quot; the 486
Busy response to prevent it from being sent to the caller UA?<br>
<br>
Regards,<br>
Paul<br>