<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
If you add another branch, you should also be able to add uri params,
so it shouldn't be a problem.<br>
You can send to a route from failure route and use the function there.<br>
g-)<br>
<br>
Zappasodi Daniele wrote:
<blockquote
cite="mid:14A9059A37EF9A45BC2520DE64C30F600C6831@slttex002.seltatel.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator"
content="MS Exchange Server version 6.5.7652.24">
<title>R: [Serusers] t_relay_to_tcp/udp/tls</title>
<!-- Converted from text/plain format -->
<p><font size="2">thanks It works,<br>
but why it can be used only in ROUTE? <br>
is there any problem if I add "transport=tcp" from failure_route
enabling add_uri_param of the uri module or building something similar
to add_uri_param in a new module?<br>
<br>
<br>
<br>
-----Messaggio originale-----<br>
Da: Greger V. Teigre [<a moz-do-not-send="true"
href="mailto:greger@teigre.com">mailto:greger@teigre.com</a>]<br>
Inviato: mar 26/06/2007 15.31<br>
A: Zappasodi Daniele<br>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:serusers@lists.iptel.org">serusers@lists.iptel.org</a><br>
Oggetto: Re: [Serusers] t_relay_to_tcp/udp/tls<br>
<br>
add_uri_param("transport=tcp");<br>
<br>
Zappasodi Daniele wrote:<br>
><br>
> Hello,<br>
> Is it possible to choose the protocol, without specifying the<br>
> destination as we do with the t_relay()?<br>
> With the t_relay_to_[tcp|udp|tls] I can choose the protocol but I
must<br>
> specify a destination address in the config file.<br>
><br>
> Thanks<br>
><br>
>
**********************************************************************<br>
> The information in this message is confidential and may be legally<br>
> privileged. It is intended solely for the addressee. Access to
this message<br>
> by anyone else is unauthorized. If you are not the intended
recipient, any<br>
> disclosure, copying, or distribution of the message, or any action
or<br>
> omission taken by you in reliance on it, is prohibited and may be
unlawful.<br>
> Please immediately contact the sender if you have received this
message inerror.<br>
><br>
>
**********************************************************************<br>
>
------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> Serusers mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>
> <a moz-do-not-send="true"
href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br>
> <br>
<br>
</font>
</p>
<pre>**********************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message inerror.
**********************************************************************</pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Serusers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a>
<a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a>
</pre>
</blockquote>
</body>
</html>