Maybe it could help you
http://openser.org/dokuwiki/doku.php?id=openser_core_cookbook
Regards,
Paul
De : serusers-bounces@lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org] De la
part de Ilker Aktuna (Koç.net)
Envoyé : lundi 10 avril 2006
14:31
À : Ladislav Andel
Cc : serusers@lists.iptel.org
Objet : RE: [Serusers]
variables which can be used when writing log
Hi,
Not particularly some variables but anything that would hep me find the
problem...
In fact, it would be best to learn all of them. Is there a table that shows all
?
Maybe in the source code ? (where ?)
Thanks,
ilker
-----Original Message-----
From: Ladislav Andel [mailto:ladia6@centrum.cz]
Sent: Monday, April 10, 2006 4:31 PM
To: İlker Aktuna (Koç.net); serusers@lists.iptel.org
Subject: Re: [Serusers] variables which can be used when writing log
Can you tell me what variables you are particularly looking for?
Ladislav
İlker Aktuna (Koç.net) wrote:
>
>
> Hi,
>
> Thanks for your reply. I know the use of XLOG command but how can I
> learn other variables ?
> Thanks,
> ilker
>
> -----Original Message-----
> From: Ladislav Andel [mailto:ladia6@centrum.cz]
> Sent: Monday, April 10, 2006 10:22 AM
> To: İlker Aktuna (Koç.net)
> Subject: Re: [Serusers] variables which can be used when writing log
>
> Look at XLOG module .. it is very nice tool for logging SIP message
> flow through ser.cfg.
>
> for example
> xlog("L_ERR"," Request Method is <%rm>"); an
other useful variables
>
> Ladislav
>
> İlker Aktuna (Koç.net) wrote:
> > Hi,
> >
> > I need to learn what variables I can use when writing log, for
> > debugging purposes.
> > Can anyone tell me variables that are avilable in logging ?
> > Especially a variable for method name and sip message direction
> > would be very useful.
> >
> > Thanks,
> > ilker
> >
> > --------------------------------------------------------------------
> > --
> > --
> > *From:* serusers-bounces@lists.iptel.org
> > [mailto:serusers-bounces@iptel.org]
> > *On Behalf Of *İlker Aktuna (Koç.net)
> > *Sent:* Friday, April 07, 2006 3:36 PM
> > *To:* serusers@lists.iptel.org
> > *Subject:* [Serusers] variables which can be used when writing log
> >
> > How can I write the uri and myself variables to log file ?
> > I know that %tu and %fu are used for to uri and from uri but what
> > other variables can I use when writing log ?
> > I need to see the "myself" variable in the log because a
uri==myself
> > statement does not match where it should.
> >
> > Thanks,
> > ilker
> > C "-//W3C//DTD HTML 4.0 Transitional//EN"> Hi,
> >
> > I need to learn what variables I can use when writing log, for
> > debugging purposes.
> > Can anyone tell me variables that are avilable in logging ?
> > Especially a variable for method name and sip message direction
> > would be very useful.
>
>
_____________________________________________________________________________________________________________________________________________
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.
_____________________________________________________________________________________________________________________________________________