i call drop() in branch route and it is the only branch left. the
branch gets correctly dropped, i.e., the request is not send out, but
the reply to UAC is strange:
U 2010/04/14 21:03:43.750712 192.98.102.10:5060 - 192.98.103.2:5074
SIP/2.0 477 Unfortunately error on sending to next hop occurred
Daniel-Constantin Mierla writes:
drop in branch_route was missing, as Andreas Granig reported few days
ago. I just committed the patch, can you test again?
daniel,
ok, i'll try. if failure route is set when i call drop(), will it be
executed and if so with which reply code?
-- juha
Alex Balashov writes:
However, we all have to make pragmatic concessions to
the realities of real-world operation, which I assume is the
motivation for dialog timeouts, dlg_bye(), and other perversions from
the point of view of a purist. :-)
I welcome your thoughts and
Iñaki Baz Castillo writes:
However after checking the module code it seems that there are just
two cases:
- IP addresses (mask = 32).
- Subnets (mask != 32).
So first the source address is always matched against he address hash,
and if it doesn't match then it is matched against
Iñaki Baz Castillo writes:
Could I get into problems if I remove such UNIQUE key (gw_name column)
in gw table and create two entries with same gw_name? (kamailio
1.5.4).
gw_name is not used by lcr module. it is for information only. you can
change the index.
-- juha
Daniel-Constantin Mierla writes:
I am planning to release kamailio 3.0.2 this Thursday. There were some
fixes since 3.0.1 that worth to be packaged. If you have major reports
for current stable version, please write to
sr-...@lists.sip-router.org
in all versions, next_contacts() and
Alex rsm writes:
I couldn't find the module that has the functions for modifying
pAsserted field. Your help would be appreciated.
you don't modify it. instead you remove it in incoming request and add
a new one to outgoing request.
-- juha
___
SIP
Daniel-Constantin Mierla writes:
I think Juha added a new way lately, to encode/decode source ip/port in
the contact uri.
yes, but that only replaces with fix_nated_contact and can be used if
someone wants to re-use tcp connections between proxy and UAs and wants
to always deliver to UAs
Dmitry Kirillov writes:
Program received signal SIGSEGV, Segmentation fault.
0x2880c2c0 in qop () from /usr/local/lib/ser/modules_s/auth.so
(gdb) bt
#0 0x2880c2c0 in qop () from /usr/local/lib/ser/modules_s/auth.so
#1 0x28816555 in authorize (_msg=0x8343b58, _realm=0x0, _uri_user=0x0,
Andrei Pelinescu-Onciul writes:
We need either to quickly merge the auth apis or revive
modules_s/auth_radius (and probably the other modules_s/*radius).
Unfortunately merging the auth api doesn't look like a quick job:
ser auth api:
+ build_challenge()
+ qop
+ calc_response()
k auth
Andrei Pelinescu-Onciul writes:
Moved modules_k/auth_radius and modules_k/misc_radius to modules and
removed modules_s/auth_radius, modules_s/avp_radius, and
modules_s/uri_radius
This means that when using modules_s/auth, one would have to use
modules_s/auth_radius and for
Klaus Darilion writes:
Is it possible to use modules_s/auth as a replacement for
modules_k/auth? Are they compatible from user point of view?
if i remember correctly, at least this is missing from s version:
1.4.3. auth_extra (string)
Semi-colon separated list of extra RADIUS attribute
Juha Heinanen writes:
if(to_gw(1)){
force_send_socket($shv(gw_one));
}else if(to_gw(2)){
force_send_socket($shv(gw_two));
}
also, in 3.0 and later, to_gw takes lcr_id as argument, not gw group.
-- juha
___
SIP Express
Geoffrey Mina writes:
OK, but since this is 1.5, I would still use the GW Group ID, correct?
yes, juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http_query function takes an url as the first argument, for example,
http_query(http://localhost/test.php?uri=$(ru{s.escape.param}),
$var(result));
what i would like to do is this:
http_query($sel(cfg_get.local.http_query_url), $var(result));
that is, instead of giving url argument as
you need to call to_gw_grp(1).
That is not documented in 1.5:
http://kamailio.org/docs/modules/1.5.x/lcr.html#id2527249
In fact suh documentation states that to_gw(1) is the correct
syntax.
inaki,
thanks for the report. i just fixed the documentation.
-- juha
Geoffrey Mina writes:
1 - to_gw_grp(1). How would I ensure that subsequent in-dialog requests
are sent from the same socket as the original INVITE to my ITSP.
Asterisk -- INVITE -- KAMAILIO --
(next_gw()/to_gw_grp(1)/force_send_socket() -- INVITE -- ITSP
Asterisk -- BYE -- KAMAILIO --
Ernest Mavrel writes:
I use same scenario as Geoffrey. But I have problem with
force_send_socket() in failure_route[1].
If is first gw online, then everything is ok, force send socket work.
But when first gw is offline and lcr try second gw, then message go
trough socket which is called
Geoffrey Mina writes:
I have added a lot of debug lines, so I am 100% sure the second call to
force_send_socket is happening.
try calling force_send_socket in branch route (after setting
t_on_branch) in failure route.
Am I misusing this module in some way?
lcr module has nothing to do with
JR Richardson writes:
Well, you sure are a smart fella. I reverted the patch and reloading
the address table works as expected now. For clarification I was
testing with kamailio-3.0.2_src_2010-06-30_a6141a.tar.gz snapshot.
Let me know when you have the updated fix and I'll do sime testing.
Juha Heinanen writes:
reverting the patch thus most likely reintroduced this other bug.
perhaps the bug that you saw has something to do with the last sentence
of the commit.
jr,
did you try with db_mode=1? it works ok here.
-- juha
___
SIP
Daniel-Constantin Mierla writes:
I guess you use this command via rpc interface, not via mi.
yes, i use 'ctl mi address_reload', noticed that it didn't work and then
went and fixed it.
Looking at
the code, the mi init child is not done for rpc processes, resulting in
some mi commands not
Daniel-Constantin Mierla writes:
Juha, I just committed on master and tested over MI where works fine.
Can you do some tests over rpc? If all ok then can be backported.
it would be nice if i could, but after trying to cherry-pick my msilo
commit to sr_3.0, i got errors about debian-lenny
Daniel-Constantin Mierla writes:
this is another issue ... the mi commands were designed to be run from
special processes, created by mi transport modules (mi_fifo,
mi_datagram, etc). There are special init functions called for these
processes. However, with 3.0 xmlrpc module can call
Daniel-Constantin Mierla writes:
No time to do real tests, if you can run some and report back, it would
be great. Once some testing is done, can be ported to 3.0.
daniel,
i tested address_reload, trusted_reload, and sht_reload mi commands over
xmlrpc and they all worked fine. also 'ctl mi
Maciej Bylica writes:
Could I use regex in prefix column (lcr table)?
no you can't. searching for longest matching prefix would not really
slow if prefix could be regex.
dialplan module supports regexs. perhaps you can you that to produce an
attribute that you can match to lcr prefixes.
--
Maciej Bylica writes:
dialplan module supports regexs. perhaps you can you that to produce an
attribute that you can match to lcr prefixes.
What do You mean by saying that?
How to produce an attribute that may be matched to lcr prefixes?
if dp_translate matches a dialplan match_exp then
fyi: summary of the devel meeting in Berlin, June 8, 2010, was uploaded to:
http://sip-router.org/wiki/meetings/berlin-2010-minutes
there is also quite a few items on the tracker. it would be nice if
those could be classified somehow.
-- juha
___
Maciej Bylica writes:
So it means that weights are calculated different way, not directly
and only according to weight column.
it is weight column, not priority column. weight gives a probability of
the gw being chosen from among gws of the same group.
-- juha
Anders writes:
Region 1: prefix 55, trunk 1, priority 10
Region 1: prefix 55, trunk 2, priority 20
Sub-region A: prefix 5512, trunk 1, priority 30
I do not want the calls to prefix 5512 to fail-over to trunk 2 in case
of 404, 503 or the like. So I have tried to put priority 30 on
Anders writes:
Talking about ugly solutions - maybe this could work: The from_uri in
lcr always shows the domain name I have given to my customers - to
where they send calls. So I could create a new domain name (pointing
to the same IP), and then ask the customer to send to this domain -
and
Jiri Kuthan writes:
good news is my company has a solution that can handle this easily
-- it can be configured to handle routing tasks of complex structures
at high speed even with large tables. bad news is it is not available
open-source :(
jiri,
you should know that it is not appropriate
is there anything one can do when 'mi ul_dump' gives
error: 500 - Internal server error processing 's': buffer too small
i guess there is too many contacts.
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
Iñaki Baz Castillo writes:
I retrieve the value of an integer column in a MySQL table. In this
case the value is NULL. I store the result in a $var:
$var(client_max_calls) = $dbr(client=[0,0]);
But the stored value is (empty string) rather than 0. Isn't a bit
confussing?
inaki,
yes,
Daniel-Constantin Mierla writes:
you can increase the buffer size via mod param:
http://kamailio.org/docs/modules/stable/modules/ctl.html#binrpc_max_body_size
daniel,
after increasing binrpc_struct_max_body_size to 30:
modparam(ctl, binrpc_max_body_size, 30)
error message:
error: 500 -
Daniel-Constantin Mierla writes:
ERROR: reply too big
how to get rid of that?
this seems to come from sercmd tool. Quickly grepping its sources, the
internal limit is 4K for rpc replies. You can try to recompile sercmd
after setting bigger value for MAX_*_SIZE defines.
ok. i'll try
Ricardo Martinez writes:
I’m wondering how the “Weight” column in the LCR ‘gw’ table Works.
weight is probabilistic weight of the gateway that applies when
priorities of the gateways are the same.
If I have 100 calls, I was expecting was to have 20 to GW05, 20 to GW06, 20
to GW09 and 20 to
Ricardo Martinez writes:
I’m observing something like this : (these are “Simmultaneous calls”
graphs)
ricardo,
my email client does not know to display your data, but weight is
assigned to gws like this:
matched_gws[gw_index].weight = t-weight * (rand() 8);
where t-weight comes from db
Ricardo Martinez writes:
As you can see there is no a 20,20,20,20,10,10 call repartition.
Could this be a bug?
ricardo,
it is a feature of the way randomized weights are currently
calculated. if you have two wgs with weights 1 and 2 and then generate
two random numbers
1 * random number
2 *
ricardo,
i studied the weight problem a bit more and came to the conclusion that
implementing a fair weighting algorithm would be too complicated.
below is a script that can be used to find weight values matching
desired probabilities for lcr gateways. i don't know if it would be
appropriate to
Daniel-Constantin Mierla writes:
maybe there are other options, but here is what I did for dispatcher
weighted load balancing:
- each destination set has associated an array of 100 integers
- when destination set is loaded, this array is filled with indexes of
destination addresses in the
Daniel-Constantin Mierla writes:
you can create as well an utils or tools directory inside lcr module
folder, that will suggest direct relation with the module.
ok, juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
Ovidiu Sas writes:
If the script can be provided in bash, then it would be nice to be
integrated in kamctl:
- kamctl lcr weight_eval weight_1 weight_2 ... weight_n
ovidiu,
possibly it could be done, but i'm not that good in bash.
-- juha
___
SIP
Ovidiu Sas writes:
The awk version of the script is now integrated in kamctl.
thank you very much,
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
there is a broken grandstream sip ua that sometimes sends two initial
invites back-to-back. according to wireshark, sr received them about 10
microseconds apart. sr then forwards the request to pstn gw, but i
don't have wireshark dump of that side of the traffic. anyway, from the
ua side i see
Daniel-Constantin Mierla writes:
SC and xcap support is in an early stage as well, I mentioned in the
tutorials some things, like auto-adding accept rule for an watcher when
you subscribe to it (you become watcher for your watcher). I am waiting
for a bug to be fixed in bria 3.1 for more
Daniel-Constantin Mierla writes:
what are the models for these nokia phones? I have some with sip client
inside, but they might be old -- i haven't seen any xcap settings
there.
daniel,
the phone should have VoIP Release 3.0 or later:
now that 3.1 has async tls support, i decided (first time ever) to try
to test tls. things went quite smoothly when i followed Create
Certificates to be used with Kamailio document
http://kamailio.org/dokuwiki/doku.php/tls:create-certificates#using_the_certificates_with_tls
during the process,
one question about the certificate tutorial: is something else needed in
the config or certificate business, when sr talks over tls with another
sip proxy, e.g. another sr? namely in that case sr may be in client
role when tls session is established.
-- juha
Daniel-Constantin Mierla writes:
Also, in my configs I set:
tcp_connection_lifetime=3610
so do i. i added that line to the wiki doc.
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
Andrei Pelinescu-Onciul writes:
enable_tls=1
tcp_async=no # do not include in 3.1
listen=udp:0.0.0.0:5060
listen=tcp:0.0.0.0:5060
it should not be 0.0.0.0 but an actual IP.
If you use 0.0.0.0 you _must_ set adevertised_adress or
you will
Andrei Pelinescu-Onciul writes:
However if you want to have different certificates in function of the
role (server or client, or who are you talking with, you need to use a
separate tls config
file
(http://sip-router.org/docbook/sip-router/branch/master/modules/tls/tls.html#config)
ok
Juha Heinanen writes:
i tried with command
ssldump -i any -k /etc/sip-proxy/certs/sip-proxy/key.pem tcp and port 5061
where /etc/sip-proxy/certs/sip-proxy/key.pem is the same file as
specified as tls module private key:
modparam(tls, private_key, /etc/sip-proxy/certs/sip-proxy/key.pem
Daniel-Constantin Mierla writes:
I made a dedicated section for lcr module and mentioned the upgrade
script. Please make any changes you want to improve it.
thanks,
another thing. i don't think this is valid anymore:
modules_k/auth_radius
Functions www_challenge()/proxy_challenge() are
in tm readme there is this kind of example regarding use of
t_relay_cancel:
if (method == CANCEL) {
if (!t_relay_cancel()) { # implicit drop if relaying was successful,
# nothing to do
# corresponding INVITE transaction found but error
does www_challenge(realm, flags) know to send its challenge reply
statefully or statelessly depending on if t_newtran() has been called or
not?
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
after playing with t_newtran(), i started to get these to syslog:
Oct 7 15:39:11 sip /usr/sbin/sip-proxy[26119]: WARNING: tm [t_lookup.c:1543]:
WARNING: script writer didn't release transaction
as far as i remember, in k these messages were not printed, because
transactions were freed
Andrei Pelinescu-Onciul writes:
The transaction are freed automatically in sr too, but the message is
there to show a script bug (transaction created but no action taken, no
forward, no reply, no release).
ok, that came because of the buggy www_challenge() that existed the script
without
Andrei Pelinescu-Onciul writes:
P.S.: changing www_challenge() would be trivial, but requires testing.
Only auth_send_reply() would need to be changed to use slb.send_reply()
and probably a module param. added to select between forced stateless
replies (lower processing) or auto replies.
i
can t_check_trans() be also used to check if t_newtran() has been
called on the request earlier in the script?
if so, is it so heavyweight thing that it would be better to set a flag
when t_newtran() is called and then test the flag?
-- juha
___
SIP
Erico Oliveira writes:
Now, I have almost everything functional (like freeradius and mediaproxy
and mysql requests), but the Openser can't startup. For a while, I copy
his binary (*/usr/local/sbin/openser*) to* /usr/local/sbin/openserhost* and
change the openser file's content --
Jon Bonilla (Manwe) writes:
Sure, I just meant a very small change in a module (regex). I use it
in production for long months with no problems, so I wonder if it
could be commited in 1.5.5 so I wouldn't need to modify the sources in
new deployments :)
I think that's a bad idea.
Morten Isaksen writes:
When OpenSer sends the message to Kamailio the recourd-routes look like this:
Record-Route: sip:x.x.248.20;r2=on;lr;ftag=3d9e7d131b
Record-Route: sip:x.x.248.20;transport=tcp;r2=on;lr;ftag=3d9e7d131b
But when the message comes back from Kamailio it is:
Sergey Okhapkin writes:
Is Record-Route: a,b,c
analog of
Record-Route: a
Record-Route: b
Record-Route: c
yes. new rr entries are added in front of the list.
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
i have stored in htable a key_value=0 with key_type=1, i.e., string.
then i have this piece of test code:
if (defined($sht(htable=$var(carrier_key)::id))) {
xlog(L_INFO, $sht(htable=$var(carrier_key)::id) is defined\n);
} else {
xlog(L_INFO,
Andrei Pelinescu-Onciul writes:
Because == works only with arguments of the same type, 0 it's
autoconverted to 0. The alternative would be to log an error.
andrei,
please log an error, because it is hard to remember this uncommon
comparison rule and seeing an error message would reveal the
Daniel-Constantin Mierla writes:
I don't think a strict type checking is suitable for configuration file
- e.g., if I want to check value in cseq, don't want to get lost in type
conversions.
If there is going to be such error messages, they must be enclosed in a
config parameter.
yes,
i have stored in htable a key_value=0 with key_type=1, i.e., string.
then i have this piece of test code:
if (defined($sht(htable=$var(carrier_key)::id))) {
xlog(L_INFO, $sht(htable=$var(carrier_key)::id) is defined\n);
} else {
xlog(L_INFO,
Andrei Pelinescu-Onciul writes:
Regarding this case, I agree that changing it now for 3.1 is a bad idea
and this is also not the best example of how things could go wrong.
yes, there should not be any changes in 3.1. whatever is done, should
go to master.
-- juha
Daniel-Constantin Mierla writes:
rant?!? maybe you got the message wrong. It was about the purpose of
configuration file and the target users for it.
your message was very emotional. you defined the target users in your
message. i have not seen that discussed or agreed earlier. my claim is
Andrei Pelinescu-Onciul writes:
No, there is no is_int function, but you could use a hack:
if (($v == 0) ($v + 0 == (str)0))
will be true only if $v is int and == 0 ($v == 0 makes sure that
$v!=).
daniel,
here you go. is that in your opinion something that a non-programmer
could
Daniel-Constantin Mierla writes:
Changing current behavior will be killing, using new operators (iirc,
you added something with le, lt, ...) would be an option, but we add
more to the confusion of what and how to use.
i agree with daniel here. introducing new operators is not user
Javier Gallart writes:
thanksI think It's working now; I had defined the key_type and
value_type columns as char; I've changed them to integer and now it's
showing the correct values.
it is not a good idea to create tables by hand. use the script that is
provided.
-- juha
Anders writes:
I'm with an odd problem now, though, - running
/usr/local/sbin/kamdbctl create gives a no such file or directory
- but if I run locate kamdbctl, it actually finds the file in that
directory...but an ls shows nothingwhat am I missing?
i suggest you install kamailio from a
Uriel Rozenbaum writes:
What would be best to optimize the system is to have some statistic
information, save every now and then the status of the htable and act
accordingly to:
it would indeed be nice of htable module would exports stats about
collisions.
-- juha
Nicolas Rüger writes:
what about the idea to just copy the function check_blacklist()
change the parsed variable as I need to and then store it as
check_blacklist_1()!?
if you intend to get your patch included in sr, you need to consult the
author of the module. if not, then what you propose
Henning Westerholt writes:
it just has been implemented that way, and so far we don't needed $var. I've
no objections against a extension like this.
ok. i looked at pdb.c and its fixing of params looked quite complicated.
therefore rather that trying to provide a patch, i added tracker item
Daniel-Constantin Mierla writes:
this kind of privacy is affecting the calls as well, for example. I can
send you a call or other SIP request to discover you are online/offline.
So this is another service that should be applied globally: black-white
lists.
Having a mechanism just for
Daniel-Constantin Mierla writes:
This is sorted out by location server. iirc, you implemented the
filtering based on allowed methods.
yes, that takes care of sending subscribe to ua that does not support
it. the sad thing is that there are UAs on the marker that don't
advertise their
Daniel-Constantin Mierla writes:
The problem right now is interpreting the content - presence information
is content. If the server does not understand the Event you subscribe
to, bye bye...
i agree with that. in one sip ua is was not possible to configure
voicemail uri. it assumed that
Iñaki Baz Castillo writes:
The proxy must be ready to route a request not just based on the RURI
but also on the method and also on the Event type (a PUBLISH for
presence must be routed to the presence server while a PUBLISH for
dialog must be routed to some other server).
inaki,
method is
Iñaki Baz Castillo writes:
Then how do you get the proxy routing Event: presence PUBLISH to a
server-1 and Event: dialog PUBLISH to server-2?
you cannot do it. it is not supported.
Could you explain it please?
there is not much to explain. request uri must tell where request is
Iñaki Baz Castillo writes:
The fact is that I agree with you. But note that with REGISTER the
same occurs. It's very common an architecture in which the client is
just provisioned with a domain name, which resolved to its proxy, and
such proxy router the REGISTER to a registrar server (even
Iñaki Baz Castillo writes:
Yes, but isn't nicer provisioning a UA just with AoR, password and
domain letting DNS NAPTR/SRV and routing in the proxy to do their
magic? :)
you need to draw the line somewhere regarding how much magic proxy does
and knows about. there are many levels to it:
while doing some tests, i noticed that one of my proxies started to
receive lots of register requests with different user names starting
from a letter. there was also invite attempts in the logs. they came
from ip 202.82.16.99 which according to traceroute is somewhere in
china.
should we start
Daniel-Constantin Mierla writes:
iirc, it was always the same from the time of ser 0.8. If you don;t
change the protocol, the core tries to send from the same socket it
received. You have to use mhomed=1 in order to have detection of
outgoing interface. 3.x has significant improvements for
Efelin Novak writes:
The request uri after redirect will be us...@another_domain. I have to store
the original request_uri(us...@my_domain) and after redirect, insert it to
Billing Party header in radius message.
yes, i had a typo in my answer. you, of course, need to use request uri
before
based on core cookbokk, it is not clear to me what happens when drop is
executed in branch route:
drop
Stop the execution of the configuration script and alter the implicit
action which is done afterwards.
If the function is called in a 'branch_route' then the branch is
discarded
Kosilov Fedor writes:
Do you mean ul_add? This is not quite what I want to have.. I want
everything to work automatically ;). By the way, how do you make permanent
registrations?
either use long expires value or there may be internal usrloc flag that
tells that the registration is permanent.
marius zbihlei writes:
I must stress the fact that you must first test mhomed before deploying.
I have heard reports (not yet confirmed) that for certain
implementations it behaves badly. I haven't yet managed to
confirm/infirm these reports but I am currently looking into it so you
wait
Sébastien Cramatte writes:
Does someone can give me resources where I can found :
- required modparam for LCR and CARRIERROUTE
- SQL examples datas for both modules
- example of route logic using both modules
regarding lcr, modparams are all described in readme. i don't know
about
marius zbihlei writes:
For carrierroute you can have blacklist
capabilities as well.
regarding white/blacl listing, that is trivial to implement generically
using dialplan module. i suspect that neither carrierroute or userblacklist
module provides any added value on top of dialplan module
Lee Archer writes:
Hi, I have kamailio configured to get it's LCR info from a mysql
database but when I try to get this info from the command line I am told
the command is disabled. Why is this?
lcr module rpc commands are listed in lcr module README:
5. Exported RPC Commands
5.1.
Miguel Baptista writes:
I want to enable pike module based on IP addresses. I mean ... I don't
want to check if requests from some specific IP addresses trigged the
Pike's threshold. but for all other IP addresses I want to check it.
I was thinking about using some kind of IP addresses'
Anders writes:
I cannot find an answer to this in the documentation: Is there a limit
to how many fail-overs Kamailio does? I have lcr setup for a
destination where it is rejected with 403 on the first and second
priority, but then it goes no further, even though I have a third
priority
Anders writes:
I have two different trunks with one carrier. The IP where I send the
INVITE is the same, but the prefix differs. So in the gw table, I
enter the two lines, - same IP, but with different digits in the 'tag'
column, and different grp_id numbers. I then set up the lcr table and
Anders writes:
But I added it manually to the tables, so maybe I
needed to load them to memory – but “kamctl lcr reload” has been
discontinued, so no loading. Is Siremis necessary as the input tool
for lcr and gws?
anders,
read what is new in 3.1 wiki page and lcr manual. also, ctl help
Anders writes:
Being able to reload the lcr didn't solve my problem though - still
not finding any gw when I run next_gw(), so I'm still open for
input...
use the dump ctl commands to check how the gw and routing stuff looks
like.
-- juha
___
Anders writes:
the dump ctl commands shows show commands like 'lcr dump_gws' and 'lcr
show_gws' - commands that only give a command disabled return when
run. According to the documentation of lcr (3.1.x), only three
commands are left (lcr.reload, lcr.dump_gws, lcr.dump_rules - that
with
i have been using radius for accounting, but now looked at db accounting
for another project. couple of issues:
- why is sip reason (the comment after reply's reason code) a mandatory
field in accounting table? if someone offers a good reason, my
opinion is that it should be removed. if
1 - 100 of 994 matches
Mail list logo
