<!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">
Inline.<br>
<br>
Zappasodi Daniele wrote:
<blockquote
cite="mid14A9059A37EF9A45BC2520DE64C30F60075154@slttex002.seltatel.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2800.1528" name="GENERATOR">
<div>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB">Many thanks for <span class="945332608-06092006">the </span>reply<span
class="945332608-06092006">,</span> it is very useful but it contains
bad news because, if is it possible, it is important for me to preserve
the possibility to have the SIP proxy and SIP gateway in the same
board. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB">Some other clarification:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB">1. I have two ethernet interfaces, if I give different IP
address to proxy and gateway, can I leave them on the same hardware?</span></p>
</div>
</blockquote>
Yes, the trick is to get the listen and alias directives correct in
your ser.cfg. You can run multiple servers or UAs on the same server,
you just have to make sure you don't have alias=myip in ser.cfg. This
will make SER believe messages for another server/UA is to be routed
locally.<br>
<blockquote
cite="mid14A9059A37EF9A45BC2520DE64C30F60075154@slttex002.seltatel.local"
type="cite">
<div>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB">2. If I correctly understand the transaction creation in
SER: SER absorbs the retransmission only if already exists a
transaction for the original INVITE and SER creates a new transaction
for an INVITE only when is invoked the t_relay. </span></p>
</div>
</blockquote>
Yes, if not, SER will be transaction stateless and just happily forward
any message.<br>
<blockquote
cite="mid14A9059A37EF9A45BC2520DE64C30F60075154@slttex002.seltatel.local"
type="cite">
<div>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB">Consequently<span class="945332608-06092006">,</span> If
a retransmitted INVITE arrives when the elaboration of the original
INVITE is still in progress, SER repeats all the elaboration also for
the second INVITE.</span></p>
</div>
</blockquote>
I'm not sure what you mean by "elaboration", but if you mean that the
script will be executed for retransmitted INVITEs, then yes.<br>
<blockquote
cite="mid14A9059A37EF9A45BC2520DE64C30F60075154@slttex002.seltatel.local"
type="cite">
<div>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB"><o:p></o:p></span></p>
<span style="" lang="EN-GB">
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB">Do you confirm my description?<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;">I have built a
function that in heavy load traffic condition could be slow (it does an
external query, something similar to an exec) and it is important that
I don’t invoke <span class="945332608-06092006">it </span>twice for
the same INVITE, so I try to use t_newtran to anticipate the
transaction creation before invoking this function.<o:p></o:p></p>
</span>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB">However<span class="945332608-06092006">,</span> <span
class="945332608-06092006">as first step, </span>I will remove the
t_newtran, t_forward_nonack_uri and I try again.</span></p>
</div>
</blockquote>
Normally, you should not have to worry about the transaction state,
just process the INVITE and use t_relay() and let SER handle the
retransmissions etc. I cannot see that your scenario would require more
fine-grained control over the transaction state, but then I don't know
what you are trying to do...<br>
g-)<br>
<blockquote
cite="mid14A9059A37EF9A45BC2520DE64C30F60075154@slttex002.seltatel.local"
type="cite">
<div>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB"></span> </p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB"><span class="945332608-06092006"><font color="#0000ff"
face="Arial" size="2">Thanks again.</font></span></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
lang="EN-GB"><o:p><span class="945332608-06092006"></span></o:p></span> </p>
</div>
<blockquote dir="ltr" style="margin-right: 0px;">
<div class="OutlookMessageHeader" dir="ltr" align="left"><font
face="Tahoma" size="2">-----Messaggio originale-----<br>
<b>Da:</b> Greger V. Teigre [<a class="moz-txt-link-freetext" href="mailto:greger@teigre.com">mailto:greger@teigre.com</a>]<br>
<b>Inviato:</b> mercoledì 6 settembre 2006 9.19<br>
<b>A:</b> Zappasodi Daniele<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:serusers@lists.iptel.org">serusers@lists.iptel.org</a><br>
<b>Oggetto:</b> Re: [Serusers] Retransmission problem<br>
<br>
</font></div>
1. DON'T have UA2 and SER on the same server. You are very likely to
get problems because SER sees it's own IP address in a message destined
for UA2<br>
2. Don't use t_newtran and t_forward_nonack_uri unless you know exactly
what you do (and probably not then either)<br>
3. When having problems like that, use a pretested Getting Started
config fil (<a class="moz-txt-link-freetext"
href="http://iptel.org/ser/doc/gettingstarted">http://iptel.org/ser/doc/gettingstarted</a>).
If you still have the problem, there is something external (like UA2 on
same box as SER). Fix it and then compare the logic of your config file
with the Getting Started reference config<br>
g-)<br>
<br>
Zappasodi Daniele wrote:
<blockquote
cite="mid14A9059A37EF9A45BC2520DE64C30F60075153@slttex002.seltatel.local"
type="cite">
<pre wrap="">Hello,
I have a big problem with the retransmissions.
In my tests sometimes the retransmission handler doesn't seem to work properly and it resends the INVITE after receiving a final response.
Moreover it doesn't respect the time-out (instead wait 1 second it resends the packet after few decimal), but this is a minor item.
An example:
INVITE sip:31203
>From 32201
UA1(32201) ---> SER ---> UA2(31203)
INVITE UA1 ---> SER ---> UA2
Trying UA1 <--- SER
183 UA1 <--- SER <--- UA2
480 UA1 <--- SER <--- UA2
ACK UA1 ---> SER ---> UA2
...
Other call.
After 0,5 msec SER sends again the first INVITE to UA2:
INVITE SER ---> UA2
183 SER <--- UA2
etc.
In the attached zipped file there are the syslog, the ser config file (only the relevant parts) and the ethereal captures related to this example.
Some additional information:
SER version is 0.9.2, compiled for arm.
In my scenario SER and UA2 are on the same box.
In LAN_capture.cap file there is the message flow between UA1 and SER, in lo_capture.cap between SER and UA2.
Can someone explain me this behaviour?
Maybe something wrong in my config file? Note that I use t_lookup_request, t_newtran, t_forward_nonack_uri in order to recognize retransmitted INVITE, could it be here the problem?
thanks
**********************************************************************
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>
</blockquote>
<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>
</blockquote>
</body>
</html>