The problem is the other way. BYE from UDP to TCP. However I do see the problem now.<br>
<br>
Thanks Klaus for pointing me to the URI as it that is indeed the problem. <br>
<br>
The TCP UA has transport=tcp in the Contact: header and SER correctly
leave that intact when forwarding to UDP. The UDP UA, when sending the
loose routed BYE back to SER, does not correctly add the URI param from
the Contact URI to the RURI.<br>
<br>
I expected SER to not care about this because the rr params clearly
have the transport=tcp coming back in the local route header. Its also
my understanding thet URI params in Contact headers are optional so the
UDP UA need not return them.<br>
<br>
Anyway, I've fix my problem by adding the transport=tcp param to the
RURI in the loose route section of the script prior to t_relay.<br>
<br>
I dont know who is at fault here - the TCP UA, the UDP UA, or SER
but since there are many of these UAs in the field I needed to fix the
problem.<br>
<br>
I would like to know why transport=tcp is ignored in the Route header
by SER. If the RURI must have transport=tcp then why bother having it
in the Route header at all? I would think that information in the Route
would trump lack of information in the RURI.<br>
<br>
Mark<br>
<br><br><div><span class="gmail_quote">On 9/29/05, <b class="gmail_sendername">Cesc</b> <<a href="mailto:cesc.santa@gmail.com">cesc.santa@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>I would say that as long as your UA's contact header registered in
ser specifies UDP, t_relay should do the trick when receiving the bye
(tcp) and relaying it (udp).</div>
<div>It works in my lab :) I cannot be more specific as i am away now ... sorry.</div><span class="sg">
<div> </div>
<div>Cesc<br><br> </div>
</span><div><div><span class="e" id="q_106a29406641090e_3"><span class="gmail_quote">On 9/29/05, <b class="gmail_sendername">Mark Aiken</b> <<a href="mailto:aiken.mark@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
aiken.mark@gmail.com</a>> wrote:</span>
</span></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"><div><span class="e" id="q_106a29406641090e_5">HI,<br><br>The
original RURI does have but when SER relays to UDP UA it places
transport=tcp in the Record-Route but not in the RURI to the UDP UA,
which seems correct to me.
<br><br>I guess the problem is when using relay_to_udp on an INVITE
from a TCP UA, to force SER to act as a TCP to UDP proxy, SER cant
handle loose routing new requests in the same dialog back via TCP.<br><br>There
seems to be no code in SER to handle this, from the small bits I've
looked at anyway. The information is in the rr params that SER added,
but SER just ignores the information on loose routed requests when the
route is a local one.
<br><br>Does anyone know if there is some special trick to get SER to
handle TCP<->UDP conversion of loose routed requests? Should the
UA be adding the transport=tcp from the rr param to the RURI of the BYE
( I would not think so, since its the 2nd route added by SER anyway,
not the topmost).
<br><br>For SER to work as a TCP<=>UDP proxy, one needs to
"search" for the transport=tcp, somehow be sure its in a local route
header, and add the transport=tcp to the uri before calling t_relay, I
guess. I haven't tried that yet. All this for loose routed requests.
<br><br>This seems like a lot of work in the .cfg file which is better done in rr/tm module. <br><br>I still think I must be doing something wrong as SER should handle this automatically for loose routed requests.<br><br>
Is using relay_to_udp not the proper way to force TCP to UDP proxy of an INVITE? <br><span><br>Mark</span>
<div><span><br><br>
<div><span class="gmail_quote">On 9/29/05, <b class="gmail_sendername">Klaus Darilion</b> <<a href="mailto:klaus.mailinglists@pernau.at" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">klaus.mailinglists@pernau.at
</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Mark!<br><br>I do not know it exactly, but I think the important thing is the contact<br>
header URI of the INVITE. Does it contain a transport=tcp parameter?
<br>Otherwise, ser is correct when using UDP.<br><br>klaus<br><br>Mark Aiken wrote:<br>> Hi,<br>><br>> I'm having problems getting SER to (loose) route requests from UDP to<br>> TCP. I'm not sure if the UA is at fault here or some SER config issue.
<br>><br>> SER receives an INVITE over TCP, record_route() is called and then the <br>> request is relayed via UDP (t_relay_to_udp) to the UA. The<br>> INVITE relayed to the UDP UA now has 2 Record-Route headers added by
<br>> SER. One has the transport=tcp parameter.<br>><br>> Record-Route: <sip: xx.xx.xx.xx;r2=on;ftag=xyz;lr=on><br>> Record-Route: <sip:xx.xx.xx.xx;transport=tcp;r2=on;ftag=xyz><br>><br>> When the UA sends the BYE to SER, it has the 2 Route headers like so (on
<br>> a single line): <br>><br>> Route:<br>> <sip:xx.xx.xx.xx;r2=on;ftag=xyz;lr=on>,<sip:xx.xx.xx.xx;transport=tcp;r2=on;ftag=xyz;lr=on><br>><br>> The SER script simply calls t_relay() in the loose_route section of the
<br>> script.<br>><br>> I expected t_relay() to relay the BYE via TCP, since the Route header<br>> has transport=tcp, but it sends the BYE via UDP instead.<br>><br>> Anyone seen this problem before? Do I need to check for transport=tcp
<br>> and call t_relay_to_tcp, rather than using t_relay after loose_route()?<br>><br>> Mark<br>><br>><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________
<br>> Serusers mailing list<br>> <a href="mailto:serusers@lists.iptel.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">serusers@lists.iptel.org</a><br>> <a href="http://lists.iptel.org/mailman/listinfo/serusers" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.iptel.org/mailman/listinfo/serusers</a><br><br></blockquote></div><br></span></div><br></span></div>_______________________________________________<span class="q"><br>Serusers mailing list<br><a href="mailto:Serusers@iptel.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
serusers@lists.iptel.org</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.iptel.org/mailman/listinfo/serusers</a><br><br><br></span>
</blockquote>
</div><br>
</blockquote></div><br>