12 May
2006
12 May
'06
1:25 p.m.
Hi,
Thanks for your reply.
But I didn't understand what to do. I already have that configuration in the ser.cfg.
What should I add to it so that BYE messages would allways go through SER ?
Thanks,
ilker
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of
Michal Matyska
Sent: Friday, May 12, 2006 1:32 PM
To: serusers(a)lists.iptel.org
Subject: Re: [Serusers] How to use record route to change path of BYE messages
On Fri, May 12, 2006 at 10:38:51AM +0300, İlker Aktuna (Koç.net) wrote:
Hi everyone,
I am still trying to find a solution to my problem with BYe messages that are not going
through SER.
Maybe someone with enough knowledge about route recording could help me with the
configuration:
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.
I need them to go through SER. How can I achieve this ?
I don't know how to use route recording, could you explain what
following config block does ? (this is in the default configuration
but doesn't make BYE messages to go through SER)
It does (you can check by ethereal, ngrep etc.),
if (!method=="REGISTER") {
record_route();
}
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 ....
if (loose_route()) {
# mark routing logic in request
append_hf("P-hint: rr-enforced\r\n");
so you can add your logic either here or into route[1] block, which might be called from
other places as well (be aware)
route(1);
break;
};
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).
thanks,
ilker
Hope Google will index this to help more people :-) Michal
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
<http://387555.sigclick.mailinfo.com/sigclick/03010604/01044804/070E4D03/10911414.jpg>
_____________________________________________________________________________________________________________________________________________
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.
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.
_____________________________________________________________________________________________________________________________________________