<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-16">
<META HTTP-EQUIV="EXPIRES" CONTENT="0">
<META HTTP-EQUIV="EXPIRESABSOLUTE" CONTENT="Tue, 01 Jun 1999 12:00:00 GMT">
<META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="PRIVATE">
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
<TITLE></TITLE>
<META content="MSHTML 6.00.2900.2838" name=GENERATOR></HEAD>
<BODY >
<DIV><!-- Converted from text/plain format -->
<P><FONT size=2>Hi,<BR><BR>No actually they don't come to SER. I've already
checked with ngrep.<BR>I also check them with Ethereal on the client
side.<BR>They are directly sent to the destination where RTP is
established.<BR>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)<BR><BR>How can I do that
?<BR><BR>Thanks,<BR>ilker<BR><BR>-----Original Message-----<BR>From: Michal
Matyska [<A
href="mailto:michal.matyska@iptel.org">mailto:michal.matyska@iptel.org</A>]<BR>Sent:
Friday, May 12, 2006 5:13 PM<BR>To: İlker Aktuna (Koç.net);
serusers@lists.iptel.org<BR>Subject: Re: [Serusers] How to use record route to change
path of BYE messages<BR><BR>Hi,<BR><BR>Yes I know and still I think your BYE
messages went through SER, but you expect them at wrong place of the
script.<BR><BR>Run "ngrep -d any -p port 5060 -W byline"<BR>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.<BR><BR>I expect you have the route[1]
look like this:<BR>{ if !t_relay()
{<BR> sl_reply_error();<BR>
}<BR>}<BR><BR>Well you can e.g. add<BR>if (method==BYE)
{<BR> # handle the bye
message<BR>
....<BR> # e.g. xlog("L_ERR","My
message: %mb\n"); }<BR><BR>between append_hf() and route(1) in your
script<BR><BR>Michal<BR><BR>On Fri, May 12, 2006 at 04:25:04PM +0300, İlker
Aktuna (Koç.net) wrote:<BR>> Hi,<BR>><BR>> Thanks for your
reply.<BR>> But I didn't understand what to do. I already have that
configuration in the ser.cfg.<BR>> What should I add to it so that BYE
messages would allways go through SER ?<BR>><BR>> Thanks,<BR>>
ilker<BR>><BR>> -----Original Message-----<BR>> From:
serusers-bounces@lists.iptel.org [<A
href="mailto:serusers-bounces@lists.iptel.org">mailto:serusers-bounces@iptel.org</A>]<BR>>
On Behalf Of Michal Matyska<BR>> Sent: Friday, May 12, 2006 1:32 PM<BR>>
To: serusers@lists.iptel.org<BR>> Subject: Re: [Serusers] How to use record route
to change path of BYE<BR>> messages<BR>><BR>> On Fri, May 12, 2006 at
10:38:51AM +0300, İlker Aktuna (Koç.net) wrote:<BR>> > Hi
everyone,<BR>> ><BR>> > I am still trying to find a solution to my
problem with BYe messages that are not going through SER.<BR>> > Maybe
someone with enough knowledge about route recording could help me with the
configuration:<BR>> ><BR>> > 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.<BR>> > I need them to go through
SER. How can I achieve this ?<BR>> ><BR>> > I don't know how to use
route recording, could you explain what<BR>> > following config block does
? (this is in the default configuration<BR>> > but doesn't make BYE
messages to go through SER)<BR>> ><BR>><BR>> It does (you can check
by ethereal, ngrep etc.),<BR>><BR>>
> if (!method=="REGISTER")
{<BR>>
>
record_route();<BR>> >
}<BR>><BR>> 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 ....<BR>><BR>>
> if (loose_route())
{<BR>>
>
# mark routing logic in request<BR>>
>
append_hf("P-hint: rr-enforced\r\n");<BR>><BR>> so you can add your logic
either here or into route[1] block, which<BR>> might be called from other
places as well (be aware)<BR>><BR>>
>
route(1);<BR>>
>
break;<BR>> > };<BR>>
><BR>><BR>> 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).<BR>><BR>> > thanks,<BR>> > ilker<BR>> ><BR>>
Hope Google will index this to help more people :-)
Michal<BR>><BR></FONT></P>
<!--445D5241795C-->
<br><br><a href="http://387555.sigclick.mailinfo.com/sigclick/070A040C/040C4A07/0C004F0B/24239196.jpg"><img src="http://387555.signature1.mailinfo.com/confirm2.6/070A040C/040C4A07/0C004F0B/24239196.jpg" border="0" nosend="1"></a><!--445D5241795C//--></DIV>
<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 STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana" ALIGN="justify">
</DIV>
</DIV>
</DIV></BODY></HTML>