<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi,
<p> How to check for TLS packets in ethereal.
<p>Regards,
<br>Jayasree.
<p>"Ýlker Aktuna (Koç.net)" wrote:
<blockquote TYPE=CITE> <!-- Converted from text/plain format -->
<p><font size=-1>Hi,</font>
<p><font size=-1>No actually they don't come to SER. I've already checked
with ngrep.</font>
<br><font size=-1>I also check them with Ethereal on the client side.</font>
<br><font size=-1>They are directly sent to the destination where RTP is
established.</font>
<br><font size=-1>This is how Eyebeam acts. (I use Counterpath's Eyebeam
softphone and they said that they are forwarding the BYE message to RTP
sender and I should change route path on my SIP proxy)</font>
<p><font size=-1>How can I do that ?</font>
<p><font size=-1>Thanks,</font>
<br><font size=-1>ilker</font>
<p><font size=-1>-----Original Message-----</font>
<br><font size=-1>From: Michal Matyska [<a href="mailto:michal.matyska@iptel.org">mailto:michal.matyska@iptel.org</a>]</font>
<br><font size=-1>Sent: Friday, May 12, 2006 5:13 PM</font>
<br><font size=-1>To: ?lker Aktuna (Koç.net); serusers@lists.iptel.org</font>
<br><font size=-1>Subject: Re: [Serusers] How to use record route to change
path of BYE messages</font>
<p><font size=-1>Hi,</font>
<p><font size=-1>Yes I know and still I think your BYE messages went through
SER, but you expect them at wrong place of the script.</font>
<p><font size=-1>Run "ngrep -d any -p port 5060 -W byline"</font>
<br><font size=-1>or "tethereal -i any -p port 5060" and you'll find them
out. What I wanted to say is, that they come to SER and due to the predefined
route set, they leave SER at the point route(1) is callend within the loose_route
check.</font>
<p><font size=-1>I expect you have the route[1] look like this:</font>
<br><font size=-1>{ if !t_relay() {</font>
<br><font size=-1> sl_reply_error();</font>
<br><font size=-1> }</font>
<br><font size=-1>}</font>
<p><font size=-1>Well you can e.g. add</font>
<br><font size=-1>if (method==BYE) {</font>
<br><font size=-1> # handle the
bye message</font>
<br><font size=-1> ....</font>
<br><font size=-1> # e.g. xlog("L_ERR","My
message: %mb\n"); }</font>
<p><font size=-1>between append_hf() and route(1) in your script</font>
<p><font size=-1>Michal</font>
<p><font size=-1>On Fri, May 12, 2006 at 04:25:04PM +0300, ?lker Aktuna
(Koç.net) wrote:</font>
<br><font size=-1>> Hi,</font>
<br><font size=-1>></font>
<br><font size=-1>> Thanks for your reply.</font>
<br><font size=-1>> But I didn't understand what to do. I already have
that configuration in the ser.cfg.</font>
<br><font size=-1>> What should I add to it so that BYE messages would
allways go through SER ?</font>
<br><font size=-1>></font>
<br><font size=-1>> Thanks,</font>
<br><font size=-1>> ilker</font>
<br><font size=-1>></font>
<br><font size=-1>> -----Original Message-----</font>
<br><font size=-1>> From: serusers-bounces@iptel.org [<a href="mailto:serusers-bounces@iptel.org">mailto:serusers-bounces@lists.iptel.org</a>]</font>
<br><font size=-1>> On Behalf Of Michal Matyska</font>
<br><font size=-1>> Sent: Friday, May 12, 2006 1:32 PM</font>
<br><font size=-1>> To: serusers@lists.iptel.org</font>
<br><font size=-1>> Subject: Re: [Serusers] How to use record route to
change path of BYE</font>
<br><font size=-1>> messages</font>
<br><font size=-1>></font>
<br><font size=-1>> On Fri, May 12, 2006 at 10:38:51AM +0300, ?lker Aktuna
(Koç.net) wrote:</font>
<br><font size=-1>> > Hi everyone,</font>
<br><font size=-1>> ></font>
<br><font size=-1>> > I am still trying to find a solution to my problem
with BYe messages that are not going through SER.</font>
<br><font size=-1>> > Maybe someone with enough knowledge about route recording
could help me with the configuration:</font>
<br><font size=-1>> ></font>
<br><font size=-1>> > My main problem with BYE messages is that they are
not going through SER; the client sends it directly to my rtp proxy. as
the RTP is established with it.</font>
<br><font size=-1>> > I need them to go through SER. How can I achieve
this ?</font>
<br><font size=-1>> ></font>
<br><font size=-1>> > I don't know how to use route recording, could you
explain what</font>
<br><font size=-1>> > following config block does ? (this is in the default
configuration</font>
<br><font size=-1>> > but doesn't make BYE messages to go through SER)</font>
<br><font size=-1>> ></font>
<br><font size=-1>></font>
<br><font size=-1>> It does (you can check by ethereal, ngrep etc.),</font>
<br><font size=-1>></font>
<br><font size=-1>> > if
(!method=="REGISTER") {</font>
<br><font size=-1>> >
record_route();</font>
<br><font size=-1>> > }</font>
<br><font size=-1>></font>
<br><font size=-1>> but as it has another Route header pointing to the
RTP proxy it leaves SER within the next block which is entered when
loose_route() function has found any reasonable target in the Route headers
to forward the request to ....</font>
<br><font size=-1>></font>
<br><font size=-1>> > if
(loose_route()) {</font>
<br><font size=-1>> >
# mark routing logic in request</font>
<br><font size=-1>> >
append_hf("P-hint: rr-enforced\r\n");</font>
<br><font size=-1>></font>
<br><font size=-1>> so you can add your logic either here or into route[1]
block, which</font>
<br><font size=-1>> might be called from other places as well (be aware)</font>
<br><font size=-1>></font>
<br><font size=-1>> >
route(1);</font>
<br><font size=-1>> >
break;</font>
<br><font size=-1>> > };</font>
<br><font size=-1>> ></font>
<br><font size=-1>></font>
<br><font size=-1>> And you'll get all the subsequent dialog request and
target refresh requests (not only BYE) from both parties, which basically
means the To and From could be swapped (e.g. BYE is sent by the proxy,
net the client).</font>
<br><font size=-1>></font>
<br><font size=-1>> > thanks,</font>
<br><font size=-1>> > ilker</font>
<br><font size=-1>> ></font>
<br><font size=-1>> Hope Google will index this to help more people :-)
Michal</font>
<br><font size=-1>></font>
<br><!--445D5241795C-->
<br><a href="http://387555.sigclick.mailinfo.com/sigclick/070A040C/040C4A07/0C004F0B/24239196.jpg"><img SRC="cid:part1.4464A298.5E4253B3@hyd.hellosoft.com" BORDER=0 nosend="1" ></a><!--445D5241795C//-->
<div STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<div STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<div STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">_____________________________________________________________________________________________________________________________________________</div>
<div STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">Bu e-posta
mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta
mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz
ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya
hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz.
Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz,
yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere
karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu
e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile
- virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak
hicbir sorumlulugu kabul etmez.</div>
<div STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">This message
is intended solely for the use of the individual or entity to whom it is
addressed , and may contain confidential information. If you are
not the intended recipient of this message or you receive this mail in
error, you should refrain from making any use of the contents and from
opening any attachment. In that case, please notify the sender immediately
and return the message to the sender, then, delete and destroy all copies.
This e-mail message, can not be copied, published or sold for any reason.
This e-mail message has been swept by anti-virus systems for the presence
of computer viruses. In doing so, however, sender cannot warrant
that virus or other forms of data corruption may not be present and do
not take any responsibility in any occurrence.</div>
<div STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">_____________________________________________________________________________________________________________________________________________</div>
</div>
</div>
<pre>
<hr WIDTH="90%" SIZE=4>_______________________________________________
Serusers mailing list
serusers@lists.iptel.org
<a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a></pre>
</blockquote>
<pre>
The information contained in this e-mail message and/or attachments to it may
contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail immediately and permanently delete the message and any attachments.
</pre>
</html>