10 Apr
2006
10 Apr
'06
4:40 p.m.
Hi,
This surely helps a lot but XLOG uses 2 character variable names to write in logging. I
need those variable names and this document does not include them as far as I can see.
Thanks,
ilker
________________________________
From: PREVOT Paul [mailto:prevot@enseirb.fr]
Sent: Monday, April 10, 2006 4:36 PM
To: İlker Aktuna (Koç.net); 'Ladislav Andel'
Cc: serusers(a)lists.iptel.org
Subject: RE: [Serusers] variables which can be used when writing log
Maybe it could help you
http://openser.org/dokuwiki/doku.php?id=openser_core_cookbook
Regards,
Paul
________________________________
De : serusers-bounces(a)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(a)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(a)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:
_____________________________________________________________________________________________________________________________________________
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.
_____________________________________________________________________________________________________________________________________________
<http://387555.sigclick.mailinfo.com/sigclick/010A0504/030C4E03/01004E03/22221692.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.
_____________________________________________________________________________________________________________________________________________
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(a)lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org]
*On Behalf Of *İlker Aktuna (Koç.net)
*Sent:* Friday, April 07, 2006 3:36 PM
*To:* serusers(a)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.
10 Apr
10 Apr
4:59 p.m.
New subject: [Serusers] variables which can be used when writing log
If you wan to use xlog just look into xlog's source. You'll find long
switch statement there listing all the available dual char codes.
Or see "grep -A 1 case xl_lib.c" result and use pattern:
%br - branch
%bR - branches, and so on
%C. are color switches.
case 'b':
case 'r':
e->itf = xl_get_branch;
case 'R':
e->itf = xl_get_branches;
case 'c':
case 'i':
e->itf = xl_get_callid;
case 's':
e->itf = xl_get_cseq;
case 't':
e->itf = xl_get_contact;
case 'C':
case 'x':
case 's': case 'r': case 'g':
case 'y': case 'b': case 'p':
case 'c': case 'w': case 'S':
case 'R': case 'G': case 'Y':
case 'B': case 'P': case 'C':
case 'W':
case 'x':
case 's': case 'r': case 'g':
case 'y': case 'b': case 'p':
case 'c': case 'w':
case 'd':
case 's':
e->itf = xl_get_dset;
case 'f':
case 'u':
e->itf = xl_get_from;
case 't':
e->itf = xl_get_from_tag;
case 'H':
case 'n':
e->hindex = XL_HOST_NAME;
case 'd':
e->hindex = XL_HOST_DOMAIN;
case 'f':
e->hindex = XL_HOST_FULL;
case 'i':
e->hindex = XL_HOST_IPADDR;
case 'm':
case 'b':
e->itf = xl_get_msg_buf;
case 'f':
e->itf = xl_get_flags;
case 'i':
e->itf = xl_get_msgid;
case 'l':
e->itf = xl_get_msg_len;
case 'x':
e->itf = xl_get_msgid;
case 'n':
case 'h':
e->itf = xl_get_nexthop;
case 'p':
case 'p':
e->itf = xl_get_pid;
case 'x':
e->itf = xl_get_pid;
case 'r':
case 'm':
e->itf = xl_get_method;
case 'u':
e->itf = xl_get_ruri;
case 's':
e->itf = xl_get_status;
case 'r':
e->itf = xl_get_reason;
case 't':
e->itf = xl_get_refer_to;
case 'R':
case 'i':
e->itf = xl_get_rcvip;
case 'p':
e->itf = xl_get_rcvport;
case 's':
case 'i':
e->itf = xl_get_srcip;
case 'p':
e->itf = xl_get_srcport;
case 't':
case 'u':
e->itf = xl_get_to;
case 't':
e->itf = xl_get_to_tag;
case 'T':
case 's':
e->itf = xl_get_times;
case 'f':
e->itf = xl_get_timef;
case 'x':
e->itf = xl_get_times;
case 'u':
case 'a':
e->itf = xl_get_useragent;
case 'q':
e->itf = xl_get_unique;
Michal
On Mon, Apr 10, 2006 at 05:40:15PM +0300, İlker Aktuna (Koç.net) wrote:
Hi,
This surely helps a lot but XLOG uses 2 character variable names to write in logging. I
need those variable names and this document does not include them as far as I can see.
Thanks,
ilker
6811
days inactive
6811
days old
1 comments
2 participants
participants (2)
-
İlker Aktuna (Koç.net) -
Michal Matyska