On Thursday 16 June 2011 01:48:45 Herve Couplet wrote:
> I had a setup with an old version where I used the function
> t_relay_to("0x02").
> Following the 3.1 documentation, flag :
> * 0x02* - do not generate reply on internal error (NOTE: has no effect
> anymore)
>
> I used that function as a
On 06/15/2011 08:09 PM, Herve Couplet wrote:
Kamailio is replying with a SIP/2.0 478 Unresolvable destination
(478/TM). I got the error from t_relay_to but the drop() didn't
prevent the 478 to be sent.
Oh, I see. This is an internally-generated error from TM.
There is probably not much you c
Already tried that.
Documentation on t_relay from 1.5 says :
*0x02* - do not internally send a negative reply in case of forward failure
(due internal error, bad RURI, bad message, etc). When a forward failure
occurs, no SIP request is relayed and therefore no negative reply or timeout
will show u
You can catch and drop replies in an an onreply_route or failure_route.
if(t_check_status("478"))
exit;
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On Jun 15,
