17 Apr
2010
17 Apr
'10
1:03 p.m.
Hello,
On 4/17/10 11:51 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
I think the codes are taken from error.h now, at least for this
particular case is E_CFG, which is -6 -- on the idea that error code was
triggered by cfg action. Andrei should confirm whether is error.h
driving the codes or not with the new tm. However, k 1.5 codes don't apply.
Cheers,
Daniel
i had it in mind by was busy yesterday. it
needed a way to filter this
case apart of adding branches errors. Can you give it a try? I committed
on master brnach, if is ok, i will cherry pick to kamailio 3.0.
daniel,
now the error message is gone. when i call drop() in branch route,
t_relay() fails with result code -6:
Apr 17 12:50:47 localhost /usr/sbin/sip-proxy[25815]: INFO: Routing initial
INVITE<sip:0407058055@gw1.test.fi> to<sip:192.98.100.2:5060>
Apr 17 12:50:47 localhost /usr/sbin/sip-proxy[25815]: INFO: dropping
Apr 17 12:50:47 localhost /usr/sbin/sip-proxy[25815]: INFO: t_relay failed with result
-6
as inaki asked, do you know if these k 1.5 result codes are still valid
in sr?
-1 - generic internal error
-2 - bad message (parsing errors)
-3 - no destination available (no branches were added or request
already cancelled)
-4 - bad destination (unresolvable address)
-5 - destination filtered (black listed)
-6 - generic send failed
-- juha
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla * http://www.asipto.com/ *
http://twitter.com/miconda *
http://www.linkedin.com/in/danielconstantinmierla