Hi Alex > As is often the case, there is a useful opportunity here to step back, switch > to decaf, and ask why you want to call 'exit' from a branch_route in the > first place.
:-) Actually I intended to call 'return(1)' to stop processing that actual route and continue in the calling route at the point when all work is done. I wrapped everything in if/else and I am re-testing. But on the first glimpse, I still seem to get corrupted stuff at a certain point in branching like $du being null instead of the intended destination of that branch. Am I right, that $du should contain the sip URI of where the INVITE is being routed to in the branch route? Or am I mistaking here? In most of my branches, $du is correctly pointing to the next hop (so I can use it to determine how to engage RTPengine), but sometimes it's null and I still didn't figure out why. I'll probably send another email with more details of what I try to accomplish a bit later when done testing and still facing the issue. Your help is very appreciated! Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
