Hi Michal,<br><br>Unfortunately attr_destination and xlset_destination are not allow in the branch route.<br>When one can expect the patch and those functions to be available in main tree??<br><br>Tomasz<br><br><div class="gmail_quote">
On Dec 21, 2007 4:34 PM, Michal Matyska <<a href="mailto:michal@iptel.org">michal@iptel.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>you can try to use patch available here:<br><a href="http://tracker.iptel.org/browse/SER-213" target="_blank">http://tracker.iptel.org/browse/SER-213</a><br><br>Unfortunately it did not move into the main tree yet (and might be
<br>little bit outdated at the moment).<br><br>attr_destination and xlset_destination are available in the branch route<br>and branch value is available using @tm.xxx select I think.<br><br>Michal<br><div><div></div><div class="Wj3C7c">
<br>On Fri, 2007-12-21 at 14:29 +0100, Tomasz Zieleniewski wrote:<br>> Hi,<br>><br>> I have following issue.<br>> All my outgoing requests are forwarded through boundary proxy<br>> by setting the destination before t_relay()
<br>> my problem is when there is another branch created.<br>> This second branch is routed in the standard SIP way<br>> directly to destination in request URI.<br>> How can I force also branches to go through my
<br>> boundary proxy.<br>> Can I somehow check in branch_route that this branch is not the first<br>> one (not first message)<br>> but the second and and change the destination and make t_relay()?<br>><br>> Thank You for any feedback
<br>><br>> Regards<br>> Tomasz<br></div></div>> _______________________________________________<br>> Serusers mailing list<br>> <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>>
<a href="http://lists.iptel.org/mailman/listinfo/serusers" target="_blank">http://lists.iptel.org/mailman/listinfo/serusers</a><br><br></blockquote></div><br>