Hello,
wouldn't be possible to reuse the event_route concept for this case? I
would try to avoid keep adding new routing block in the core.
Maybe something as:
...
t_on_branch_failure("xyz");
..
event_route[tm:branch-failure:xyz] {
...
}
In this way the flex/bison part from core does not need to be changed at
all.
Cheers,
Daniel
On 3/19/13 4:45 PM, Hugh Waite wrote:
Module: sip-router
Branch: hpw/branch_failure_route
Commit: 4e0cf550f75835b3f97bda9bb7934389a54b1f18
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=4e0cf550f75835b3f97bda9bb7934389a54b1f18
Author: Hugh Waite <[email protected]>
Committer: Hugh Waite <[email protected]>
Date: Tue Mar 19 15:41:55 2013 +0000
modules/tm: Initial revision of branch_failure_route
- New branch_failure_route defined
- cfg route is called but xlog() causes segfault
---
modules/tm/h_table.h | 4 ++
modules/tm/t_fwd.c | 1 +
modules/tm/t_hooks.h | 6 +++-
modules/tm/t_lookup.c | 1 +
modules/tm/t_reply.c | 97 +++++++++++++++++++++++++++++++++++++++++++++++++
modules/tm/t_reply.h | 7 ++++
modules/tm/tm.c | 27 ++++++++++++++
modules/tm/tm_load.c | 1 +
modules/tm/tm_load.h | 2 +
9 files changed, 145 insertions(+), 1 deletions(-)
Diff:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=4e0cf550f75835b3f97bda9bb7934389a54b1f18
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
- http://conference.kamailio.com -
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
