6 Jul
2010
6 Jul
'10
3:59 a.m.
Hi all,
I'm in doubt of the means of setflag()'s parameter. I have looked for
it everywhere including internet and the ser source code, but no any
docs explained it in detail. can anybody tell me about it ?
--
With best regards
by sunone
6 Jul
6 Jul
4:02 a.m.
On 07/05/2010 09:59 PM, zhou tianjun wrote:
I'm in doubt of the means of setflag()'s
parameter. I have looked for
it everywhere including internet and the ser source code, but no any
docs explained it in detail. can anybody tell me about it ?
It sets bits in a 32-bit integer (it may be 64-bit on 64-bit
platforms, of this I am not sure) that is bound to a transaction, so
those "flags" may be accessed in requests and replies associated with
a given transaction, or, further down in the execution flow of same
message handler.
It is precisely equivalent to the way bit vectors are used in
general-purpose programming languages, e.g.
int flags = 0;
flags |= (1 << 4); /* Set bit 4 */
if(flags & (1 << 4)) {
printf("Bit 4 is set!\n");
} else {
printf("Bit 4 is not set!\n");
}
/* If bit 4 is set, unset it */
if(flags & (1 << 4))
flags &= ~(1 << 4);
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
10:05 a.m.
Hello,
here is a wiki page with some flag bitmask vector examples that might help:
http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-flag-operations
The cfg file examples are for older kamailio versions.
Cheers,
Daniel
On 7/6/10 4:02 AM, Alex Balashov wrote:
On 07/05/2010 09:59 PM, zhou tianjun wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com/
I'm in doubt of the means of setflag()'s
parameter. I have looked for
it everywhere including internet and the ser source code, but no any
docs explained it in detail. can anybody tell me about it ?
It sets bits in a 32-bit integer (it may be 64-bit on 64-bit
platforms, of this I am not sure) that is bound to a transaction, so
those "flags" may be accessed in requests and replies associated with
a given transaction, or, further down in the execution flow of same
message handler.
It is precisely equivalent to the way bit vectors are used in
general-purpose programming languages, e.g.
int flags = 0;
flags |= (1 << 4); /* Set bit 4 */
if(flags & (1 << 4)) {
printf("Bit 4 is set!\n");
} else {
printf("Bit 4 is not set!\n");
}
/* If bit 4 is set, unset it */
if(flags & (1 << 4))
flags &= ~(1 << 4);
10:16 a.m.
Daniel,
Based on this, I think I was erroneous in suggesting that plain flags
(setflag, isflagset) are transaction-associated. They seem to be
message-associated, not transaction. Is this right?
Thanks,
-- Alex
On 07/06/2010 04:05 AM, Daniel-Constantin Mierla wrote:
Hello,
here is a wiki page with some flag bitmask vector examples that might help:
http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-flag-operations
The cfg file examples are for older kamailio versions.
Cheers,
Daniel
On 7/6/10 4:02 AM, Alex Balashov wrote:
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On 07/05/2010 09:59 PM, zhou tianjun wrote:
I'm in doubt of the means of setflag()'s
parameter. I have looked for
it everywhere including internet and the ser source code, but no any
docs explained it in detail. can anybody tell me about it ?
It sets bits in a 32-bit integer (it may be 64-bit on 64-bit
platforms, of this I am not sure) that is bound to a transaction, so
those "flags" may be accessed in requests and replies associated with
a given transaction, or, further down in the execution flow of same
message handler.
It is precisely equivalent to the way bit vectors are used in
general-purpose programming languages, e.g.
int flags = 0;
flags |= (1 << 4); /* Set bit 4 */
if(flags & (1 << 4)) {
printf("Bit 4 is set!\n");
} else {
printf("Bit 4 is not set!\n");
}
/* If bit 4 is set, unset it */
if(flags & (1 << 4))
flags &= ~(1 << 4);
10:24 a.m.
Hello,
On 7/6/10 10:16 AM, Alex Balashov wrote:
Daniel,
Based on this, I think I was erroneous in suggesting that plain flags
(setflag, isflagset) are transaction-associated. They seem to be
message-associated, not transaction. Is this right?
in first place is associated to message, then inherited to transaction
(when that is created) and kept for the life of the transaction. So both
associations are true, of course, a matter of whether the transaction
was created or not at respective time.
Cheers,
Daniel
Thanks,
-- Alex
On 07/06/2010 04:05 AM, Daniel-Constantin Mierla wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com/
Hello,
here is a wiki page with some flag bitmask vector examples that might
help:
http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-flag-operations
The cfg file examples are for older kamailio versions.
Cheers,
Daniel
On 7/6/10 4:02 AM, Alex Balashov wrote:
On 07/05/2010 09:59 PM, zhou tianjun wrote:
I'm in doubt of the means of setflag()'s
parameter. I have looked for
it everywhere including internet and the ser source code, but no any
docs explained it in detail. can anybody tell me about it ?
It sets bits in a 32-bit integer (it may be 64-bit on 64-bit
platforms, of this I am not sure) that is bound to a transaction, so
those "flags" may be accessed in requests and replies associated with
a given transaction, or, further down in the execution flow of same
message handler.
It is precisely equivalent to the way bit vectors are used in
general-purpose programming languages, e.g.
int flags = 0;
flags |= (1 << 4); /* Set bit 4 */
if(flags & (1 << 4)) {
printf("Bit 4 is set!\n");
} else {
printf("Bit 4 is not set!\n");
}
/* If bit 4 is set, unset it */
if(flags & (1 << 4))
flags &= ~(1 << 4);
10:32 a.m.
On 07/06/2010 04:24 AM, Daniel-Constantin Mierla wrote:
On 7/6/10 10:16 AM, Alex Balashov wrote:
Oh, I see. The documentation on the dokuwiki suggests they are only
message-association.
I was pretty sure I had used flags in a transaction-bound way at some
point when I wrote the original response. However, I did not remember
for sure because I tend to use variables for almost everything
transaction-associated these days just due to the nature of the data
in most cases.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
Daniel,
Based on this, I think I was erroneous in suggesting that plain flags
(setflag, isflagset) are transaction-associated. They seem to be
message-associated, not transaction. Is this right?
in first place is associated to message, then inherited to transaction
(when that is created) and kept for the life of the transaction. So both
associations are true, of course, a matter of whether the transaction
was created or not at respective time.
10:41 a.m.
On 7/6/10 10:32 AM, Alex Balashov wrote:
On 07/06/2010 04:24 AM, Daniel-Constantin Mierla
wrote:
Probably would be good to improve the page a bit, is pretty old.
I found this statement:
"They provide a very easy and fast way of keeping states during
processing a request or during a transcation, if Kamailio (OpenSER) is
in stateful mode."
but none that says is for request only.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
On 7/6/10 10:16 AM, Alex Balashov wrote:
Oh, I see. The documentation on the dokuwiki suggests they are only
message-association.
I was pretty sure I had used flags in a transaction-bound way at some
point when I wrote the original response. However, I did not remember
for sure because I tend to use variables for almost everything
transaction-associated these days just due to the nature of the data
in most cases. Daniel,
Based on this, I think I was erroneous in suggesting that plain flags
(setflag, isflagset) are transaction-associated. They seem to be
message-associated, not transaction. Is this right?
in first place is associated to message, then inherited to transaction
(when that is created) and kept for the life of the transaction. So both
associations are true, of course, a matter of whether the transaction
was created or not at respective time. 
11:34 a.m.
On Jul 06, 2010 at 10:24, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:
Hello,
On 7/6/10 10:16 AM, Alex Balashov wrote:
Not exactly, the flags are updated at t_relay() time, even if the
transaction was created before by t_newtran().
E.g.:
flags a, b;
setflag(a);
t_newtran();
setflag(b);
t_on_failure("failure_route");
t_on_reply("reply_route");
t_relay();
=> both a & b will be set in the reply_route or failure_route.
Andrei
Daniel,
Based on this, I think I was erroneous in suggesting that plain
flags (setflag, isflagset) are transaction-associated. They seem
to be message-associated, not transaction. Is this right?
in first place is associated to message, then inherited to
transaction (when that is created) and kept for the life of the
transaction. So both associations are true, of course, a matter of
whether the transaction was created or not at respective time.
11:52 a.m.
On 7/6/10 11:34 AM, Andrei Pelinescu-Onciul wrote:
On Jul 06, 2010 at 10:24, Daniel-Constantin
Mierla<miconda(a)gmail.com> wrote:
right, maybe my phrasing was not clear. I wanted to mean that when the
transaction is created the flags become associated to the transaction -
they can be updated afterwards (e.g., failure/onreply route as well).
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
Hello,
On 7/6/10 10:16 AM, Alex Balashov wrote:
Not exactly, the flags are updated at t_relay() time, even if the
transaction was created before by t_newtran().
E.g.:
flags a, b;
setflag(a);
t_newtran();
setflag(b);
t_on_failure("failure_route");
t_on_reply("reply_route");
t_relay();
=> both a& b will be set in the reply_route or failure_route.
Daniel,
Based on this, I think I was erroneous in suggesting that plain
flags (setflag, isflagset) are transaction-associated. They seem
to be message-associated, not transaction. Is this right?
in first place is associated to message, then inherited to
transaction (when that is created) and kept for the life of the
transaction. So both associations are true, of course, a matter of
whether the transaction was created or not at respective time.
11:27 a.m.
On Jul 06, 2010 at 10:05, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:
Hello,
here is a wiki page with some flag bitmask vector examples that might help:
http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-flag-operations
The cfg file examples are for older kamailio versions.
Indeed.
The flags support names (you don't have to deal with flag numbers by
hand any longer).
E.g.:
flags test, a, b;
route {
#....
setflag(test);
if (isflagset(a)) {
...
}
}
One could also force a specific mapping between a flag name and the
actual flag "number" used, e.g.:
flags a:1, b:2 ;
Andrei
On 7/6/10 4:02 AM, Alex Balashov wrote:
On 07/05/2010 09:59 PM, zhou tianjun wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users I'm in doubt of the means of setflag()'s
parameter. I have looked for
it everywhere including internet and the ser source code, but no any
docs explained it in detail. can anybody tell me about it ?
It sets bits in a 32-bit integer (it may be 64-bit on 64-bit
platforms, of this I am not sure) that is bound to a transaction,
so those "flags" may be accessed in requests and replies
associated with a given transaction, or, further down in the
execution flow of same message handler.
It is precisely equivalent to the way bit vectors are used in
general-purpose programming languages, e.g.
int flags = 0;
flags |= (1 << 4); /* Set bit 4 */
if(flags & (1 << 4)) {
printf("Bit 4 is set!\n");
} else {
printf("Bit 4 is not set!\n");
}
/* If bit 4 is set, unset it */
if(flags & (1 << 4))
flags &= ~(1 << 4);
10:43 a.m.
2010/7/6 Alex Balashov <abalashov(a)evaristesys.com>om>:
It sets bits in a 32-bit integer (it may be 64-bit on
64-bit platforms, of
this I am not sure)
Hi, could it be clarified please? I also wonder how many integer AVP's
(i:N) can exist. Does it depend on the 32/64 bits architecture?
Thanks.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
11:37 a.m.
On Jul 06, 2010 at 10:43, Iñaki Baz Castillo <ibc(a)aliax.net> wrote:
2010/7/6 Alex Balashov
<abalashov(a)evaristesys.com>om>:
The flags are stored internally on 32 bits, but you should use names for
the flags so you shouldn't care (unless you use more then 32 :-)).
There is no limit on the number of AVPs, but the I:N format is
deprecated (use only names).
Andrei
It sets bits in a 32-bit integer (it may be
64-bit on 64-bit platforms, of
this I am not sure)
Hi, could it be clarified please? I also wonder how many integer AVP's
(i:N) can exist. Does it depend on the 32/64 bits architecture?
11:49 a.m.
2010/7/6 Andrei Pelinescu-Onciul <andrei(a)iptel.org>rg>:
Hi, could it
be clarified please? I also wonder how many integer AVP's
(i:N) can exist. Does it depend on the 32/64 bits architecture?
The flags are stored internally on 32 bits, but you should use names for
the flags so you shouldn't care (unless you use more then 32 :-)). There is no limit on the number of AVPs, but the I:N
format is
deprecated (use only names).
Thanks.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
11:56 a.m.
On 7/6/10 11:49 AM, Iñaki Baz Castillo wrote:
2010/7/6 Andrei
Pelinescu-Onciul<andrei(a)iptel.org>rg>:
was your question how many avps with ID N can be or how many distinct N
you can have?
Haven't check if has changed in SER 2.0 (therefore in 3.0 as well), but
in K 1.x and older S the ID was short int (16b), so N can be any number
from 1 to 2^16-1.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
Hi, could
it be clarified please? I also wonder how many integer AVP's
(i:N) can exist. Does it depend on the 32/64 bits architecture?
The flags are stored internally on 32 bits, but you should use names for
the flags so you shouldn't care (unless you use more then 32 :-)).
There is no limit on the number of AVPs, but the
I:N format is
deprecated (use only names).
Thanks.
12:07 p.m.
2010/7/6 Daniel-Constantin Mierla <miconda(a)gmail.com>om>:
was your question how many avps with ID N can be or
how many distinct N you
can have?
Haven't check if has changed in SER 2.0 (therefore in 3.0 as well), but in K
1.x and older S the ID was short int (16b), so N can be any number from 1 to
2^16-1.
My question was about the max number of N in avp(i:N). I expected that
the max numbers of ID N avps is N.
Anyhow my question was about K 1.5 as I know that in 3.X there are
changes in AVP indexing syntax.
Thanks.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
12:20 p.m.
On 7/6/10 12:07 PM, Iñaki Baz Castillo wrote:
2010/7/6 Daniel-Constantin
Mierla<miconda(a)gmail.com>om>:
hmm, unless I misunderstand you, this is wrong.
Say N=10, then you can have as many $avp(i:10) as you want -- is no limit.
For example:
$avp(i:10) = 50;
$avp(i:10) = 60;
$avp(i:10) = 70;
$avp(i:10) = 80;
results in 4 avps having same name (i:10) and different values.
Cheers,
Daniel
was your question how many avps with ID N can be
or how many distinct N you
can have?
Haven't check if has changed in SER 2.0 (therefore in 3.0 as well), but in K
1.x and older S the ID was short int (16b), so N can be any number from 1 to
2^16-1.
My question was about the max number of N in avp(i:N). I expected that
the max numbers of ID N avps is N.
Anyhow my question was about K 1.5 as I know that in
3.X there are
changes in AVP indexing syntax.
Thanks.
--
Daniel-Constantin Mierla
http://www.asipto.com/
12:39 p.m.
2010/7/6 Daniel-Constantin Mierla <miconda(a)gmail.com>om>:
I mean the indexes and not the values. My question was (related to K
1.5) which is the max value of an AVP index, is it 32 so we can use
from avp(i:1) to avo(i:32)? is it 64 (so it would depend on the CPU
architecture)?
But from your previous mail I understand the maximun value is 65535, am I right?
Thanks.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
My question
was about the max number of N in avp(i:N). I expected that
the max numbers of ID N avps is N.
hmm, unless I misunderstand you, this is wrong.
Say N=10, then you can have as many $avp(i:10) as you want -- is no limit.
For example:
$avp(i:10) = 50;
$avp(i:10) = 60;
$avp(i:10) = 70;
$avp(i:10) = 80;
results in 4 avps having same name (i:10) and different values.
5051
days inactive
5051
days old
16 comments
5 participants
participants (5)
-
Alex Balashov -
Andrei Pelinescu-Onciul -
Daniel-Constantin Mierla -
Iñaki Baz Castillo -
zhou tianjun