Vikram Ragukumar writes:
> Why is the SDP connection parameter not being rewritten for the 180
> Ringing message alone ?
are you sure that you are calling a function, such as use_media_proxy()
or corresponding rtpproxy function, on the ringing reply? does both
ringing and session progress con
Jon Bonilla (Manwe) writes:
> I was manually setting this avp before load_gws() call. This was causing to
> have another branch and two INVITEs to leave my proxy:
>
> modparam("lcr", "ruri_user_avp", "$avp(s:lcr_ruri_user)")
you are not supposed to set or do anything with that avp. does it
Iñaki Baz Castillo writes:
> Hi, IMHO it's not ok after netx_gw(). Note that the incomig INVITE is:
>
> INVITE sip:4644235465675...@77.77.77.77
>
>
> When hostname is "sindominio.org" then after t_relay() ru ad du should
> look like:
>
> ru = sip:4644235465675...@sindominio.org
Daniel-Constantin Mierla writes:
> >for 3.1 we should get
> > rid of them and have only one mode. it also makes writing the docs
> > easier, when people can concentrate on one version of the docs instead
> > of two or three.
> >
> I agree we should reduce as much as possible, but as
Daniel-Constantin Mierla writes:
> When #!KAMAILIO is defined and the value of timeout avp is less than
> 120, then it is multiplied with 1000 (auto-correction from second to
> milisecond), but since it actually second for AVP case, will result in a
> very long timeout :-).
>
> I will fi
Jon Bonilla (Manwe) writes:
> I have xloged $du and $ru just after next_gw() call and also in branch_route:
>
> Afer next_gw
> ru=sip:58658765876587...@77.77.77.77
> du=sip:91.121.117.27:5080
>
> Branch
> ru=sip:58658765876587...@77.77.77.77
> du=sip:91.121.117.27:5080
>
>
jon,
since you have hostname defined, next_gw() function sets r-uri and
destination uri and t_relay() should relay only based destination uri
unless you call t_relay() more than once.
> No append_branch is executed at all. I have two INVITES IMHO because
> next_gw() function does create the sec
Andreas Granig writes:
> Anyhow, it seems to be deprecated anyways, so I'm looking to get
> t_set_fr() working. I'm just curious how I can use a var or AVP loaded
> from DB to set the value on-the-fly? t_set_fr(...) seems to allow only
> constants to be set. Couldn't find anything in the do
Iñaki Baz Castillo writes:
> Would it affect when use LCR module 'next_gw()' funtion in
> failure_route? It creates a new branch internally
inaki,
next_gw() sets dst uri if you have given a hostname for the gateway in
hostname column of gw table. otherwise, it is not setting dst uri.
-- juha
Vikram Ragukumar writes:
> In scenario 1 calls from the cellphone using a SIP softphone app go
> through 100% of the time with both endpoints of the call being audible.
> However in scenario 2, calls from the cellphone go through with both
> endpoints of the call being audible only sometimes
i played a bit more with selects and found that statement
if ($sht(auth=>foo::count) > @cfg_get.local.gw_timeout) {
xlog("foo");
}
produces error
0(9213) : [cfg.y:3379]: parse error in config file
/etc/sip-proxy/sip-proxy.cfg, line 507, column 28-55: bad expression: type
mismatch: str ins
Daniel-Constantin Mierla writes:
> Like with devel mailing lists, existing email addresses for users ML can
> still be used, just that end on same ML. Natural choice will be to have
> us...@kamailio and serus...@iptel to be directed to
> sr-us...@lists.sip-router.org
sounds good to me, juh
I aki Baz Castillo writes:
> But how is possible that the effective fr_inv_timer per branch is
> exactly divided by the number of gateways loaded after load_gatways()
> ?
> How could the TM module do something like this?
load_gws() just assigns a set gws to an avp and next_gw() creates a
new
I aki Baz Castillo writes:
> As I said (kamailio 1.5.4) I set "fr_inv_timer=200" for TM module and
> use LCR for serial forking (failover). I also do failover is no final
> reply is received from the first gateway, however I do not manually
> override fr_inv_timer, neither using LCR AVP's (as
Bruno Machado writes:
> And so on until this, the last contact:
>
> DBG:tm:t_next_contacts: next contact is ERROR:core:add_avp: 0 ID or NULL NAME AVP
> ERROR:tm:t_next_contacts: setting of fr_inv_timer_avp failed
>
> The proxy sent INVITEs for all them, except the last one because this
>
Iñaki Baz Castillo writes:
> Ok, I'll try it. However it seems that lcr is modyfing the
> fr_inve_timer value
> by itself. Perhaps it depends on the number of gateways per lcr rule? Anyhow
> it shouldn't IMHO.
inaki,
lcr module does nothing to any timer nor does not explicitly refer to
any.
Iñaki Baz Castillo writes:
> I use Kamailio 1.5.2.
> I don't override the timer value with an AVP, I mean the default
> fr_inv_timer parameter of TM module.
i have always set the avp explicitly after calling next_gw() and before
calling t_relay() and i have set the avp again in failure route.
Iñaki Baz Castillo writes:
> Hi, I set fr_inv_timer=150 and use lcr module to balance (and failover)
> between two gateways.
is this with kamailio or sr? how did you set the timer? in k, it
should be something like this:
$avp(FR_TIMER_AVP) = GW_TIMEOUT;
t_relay();
where GW_TIMEOUT is in se
Hemanshu Patel writes:
> When i test with radius authentication, means using radius_www_authorize
> at max i am getting around 500 cps for Registration, but when i use normal
> www_authorize i am getting around 2000 CPS
are you sure that you have turned your radius server properly? in cas
Kris Amy writes:
> Is there anything special required to get radius support into the acc
> module?
in modules/acc/Makafile:
# set ENABLE_RADIUS_ACC to true if you wish to enable RADIUS accounting
# (uncomment next line or 'ENABLE_RADIUS_ACC=true make all')
#ENABLE_RADIUS_ACC=true
ifeq ($(ENA
Kris Amy writes:
> I've been ripping my hair out for a little with load_gws().
>
> How do I know what the lcr_id is and the caller_uri?
lcr_id specifies an lcr instance. if you only have one set of gateways
and rules, you can use lcr_id 1 for them.
-- juha
_
Kris Amy writes:
> Seems not to be in the kam 3.0.0 file.
there is no ping column in kam 3.0.0. see
http://www.kamailio.org/dokuwiki/doku.php/install:1.5.x-to-3.0.0
-- juha
___
Kamailio (OpenSER) - Users mailing list
Users@lists.kamailio.org
http:/
Kris Amy writes:
> Could we get the lcr-create.sql updated to have the ping field?
i just checked and kamailio/branches/1.5/scripts/mysql/lcr-create.sql
does have ping field:
INSERT INTO version (table_name, table_version) values ('gw','9');
CREATE TABLE gw (
id INT(10) UNSIGNED AUTO_INCREM
Klaus Darilion writes:
> * perform NAT traversal always, unless I know for sure that the client
> does not support symmetric SIP. For doing NAT traversal you can either
> use fix_nated_contact() - which is not standard conform but works - or
> use the new add_contact_alias/handle_ruri_alias
Alex Balashov writes:
> This is the expected behaviour, but seems different from how the
> mediaproxy module handles the issue.
even in case of mediaproxy, media sessions needs to be released using
end_media_session() call.
-- juha
___
Kamailio (Op
Daniel-Constantin Mierla writes:
> welcome! Be sure you understand the idea behind the instances. Not being
> a user of lcr don't know exactly the internal architecture, so as I
> understood from discussions on mailing lists, you can have more lcr
> instance on same kamailio grouped under s
Denis Putyato writes:
> When I add a new gw in gw table via kamctl addgw or direct via mysql
> command, never mind, after doing lcr reload, in memory loaded only gw with
> lcr_id = 1.
kamctl lcr commands are no longer supported (far too many parameters)
and should be removed. use a web based
Daniel-Constantin Mierla writes:
> Is q value allowed to be any number or just floating point less or equal
> 1? The example has greater q values.
q value is a floating point number and definitely not bigger values than
1.0. there may also be a limit in rfc3261 syntax on how many decimal
digi
Chandrakant Solanki writes:
> But when I call 101 to 102 it gives me error, as show below
>
> *Media Dispatcher error*
>
> error: No suitable relay found
>
> *Media Relay error*
>
> warning: Cannot use port pair 8684/8685
> warning: Cannot use port pair 8686/8687
for some reason rel
Daniel-Constantin Mierla writes:
> > How I can configure to send fist to sip:55341#540...@192.168.0..10
> > and after if I not sucess it sends to
> > sip:55341#540...@192.168.0.9, etc...?
> >
> >
> After get_redirects() try to use t_load_contacts() and t_next_contacts():
> http://
Antonio Goméz Soto writes:
> I have noticed that some phones only accept SIP NOTIFY from the registrar
> server, and some request authentication, and accept them from the same
> port that the register replies came from, or use SIP transaction
> numbers.
>
> This would make it mandatory for
Antonio Goméz Soto writes:
> I have used asterisk before, but now am looking at kamailio for scaling up.
> I've read 'Building Telephony Systems with OpenSER', but I still have lots
> of questions so, here it goes:
>
> - I could not find a way to reboot a phone remotely, can it send
>
Ricardo Martinez writes:
> So... for me to be clear. This is an accepted method for un-register
> a device?. Where can I find more information¡?
section 10.2.2 of rfc3261.
-=- juha
___
Kamailio (OpenSER) - Users mailing list
Users@lists.kamailio.or
recardo,
looks like your phone is first un-registering the aor.
-- juha
___
Kamailio (OpenSER) - Users mailing list
Users@lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listi
Brian writes:
> Looking at the documentation for MI_DATAGRAM and MI_XMLRPC, there does not
> seem to be a way to authenticate the request, or a way to restrict requests
> to specific IP ranges. I want to be able to send management commands
> remotely, but I don't to make this wide open.
sip r
Denis Putyato writes:
> Yes I have pv.so loaded before lcr.so
i forgot already, what is your problem and how it shows up? in which
version of k?
-- juha
___
Kamailio (OpenSER) - Users mailing list
Users@lists.kamailio.org
http://lists.kamailio.org/c
Henning Westerholt writes:
> just guessing, but do also load the "pv" module before the lcr
> module? I think this is needed in 1.5 for all pseudo-variables to
> work.
henning,
my understanding is that pv module only exports some pvs and
transformations and lcr module does not depend on it by
Daniel-Constantin Mierla writes:
> thanks! Did you do some updates to db structure of permissions
> module?
forgot that one. it is now added.
-- juha
___
Kamailio (OpenSER) - Users mailing list
Users@lists.kamailio.org
http://lists.kamailio.org/cgi-
Ricardo Martinez writes:
> I compiled the lcr_mod.c that Juha sent to me. And I made a "make
> install", but I did not restart the kamailio process. Before I
> restart kamailio I tested one more time the "bug" and I changed again
> the value in the "id" column from two correlatives "id" to
Iñaki Baz Castillo writes:
> So when a gateway is selected its attributes (strip, tag...) should be
> loaded. If there are various entries in "gw" table with same ip_addr
> but different attributes belonging to different groups, then the
> selected attributes should be those included in the se
Iñaki Baz Castillo writes:
> What do you mean with "gw group"? I just know "gateways" (in "gw"
> table) and rules (in "lcr" table).
gw groups have been in lcr module as long as it has existed. see
readme. a gw group consists of one or more gws. it is gw groups that
are referred in lcr table,
it turned out that the problems ricardo reported on gw selection in
lcr module were due to the fact that he has the same gw (same in terms of
ip address) in more than one gw group and in each group the gw has
different trip/tag attributes.
load_gws() function tries the same gateway only once, but
Andrei Pelinescu-Onciul writes:
> It's ready, but I would feel more confident with more testing (and I
> won't be able to do anything about it for the rest of this week).
>
> Do you need drop support for branch routes too?
andrei,
no, i don't need drop in branch routes. i'm myself badly co
Daniel-Constantin Mierla writes:
> since we still have to add migration documents plus some tweaks and I
> would like to do more testing before labeling it as stable release, I
> propose to do a RC tomorrow and delay final 3.0.0 with one week or so.
as long as $du setting in branch_router is
Iñaki Baz Castillo writes:
> IMHO Kamailio shouln't start if there are more gateways than MAX_NO_OF_GWS.
> This is, lcr module should give an error. Does it? (I've not tryed
> it).
the piece of code that i showed does that.
> > i can also add info about the limit in module documentation.
>
Ricardo Martinez writes:
> I modified the MAX_NO_OF_GWS to 256
> And the lcr_has_size to 256 and I'm still have the problem.
> Do you have the chance to reproduce the problem with kamailio 1.5.2 ?
i just tried with latest 1.5 version and priorities worked fine. i'm
thus unable to reproduce y
Iñaki Baz Castillo writes:
> Hi Juha, as this limitation is not present in the module
> documentation, and the module doesn't notify it when starting, it
> could create serious issues if an admin adds more than 128 gateways
> and he doesn't inspect the module source
> (really should he do t
Ricardo Martinez writes:
> Can i change the lcr_has_size from the configuration file with the
> parameter?
>
> modparam("lcr", "lcr_hash_size", 1024)
yes, you can do that.
> Another thing.
> Looking at the lcr_mod.c file there is a parameter called MAX_NO_OF_GWS
> defined as follows :
Ricardo Martinez writes:
> I was trying to replicate the problem with another prefix, and was using
> the "id's" 132 and 133, correlative, however the problem persists.
id numbers should not have anything to do with this, because nowhere in
the module is id column used. the only thing that mig
ricardo,
in situation where you see higher priority valued gateway group selected
first, do you know if the lower priority valued group would be used if
none of the gateways in the higher priority valued gateway group can
serve the request? if it is used, then both exist in the hash table.
the li
Ricardo Martinez writes:
> This is a production machine..
> I can't do too much debug.
without more info it is hard to say more because i cannot reproduce the
problem here in simple setup.
-- juha
___
Kamailio (OpenSER) - Users mailing list
Users@li
Ricardo Martinez writes:
> This is happening to me with version 1.5.2 svnrevision: 2:5918M.
> In your test, do you have records between the id's 89 and
> 127?... could this something to do with it ?
no, just those two records. if you are able to try, i could add some
more debugging to the gro
ricardo,
i cannot reproduce your problem using sr_3.0 lcr module. i don't have
access to k 1.5 system right now, but this part of the code, i.e.,
selecting gateway groups is the same.
in my test i have
r...@rautu:~# sip-proxy_ctl lcr.dump_gws
{
lcr_id: 1
grp_id: 1
ip_add
Ricardo Martinez writes:
> mysql> select * from lcr where prefix=1351 order by id;
> +-++--++--+
> | id | prefix | from_uri | grp_id | priority |
> +-++--++--+
> | 127 | 1351 | | 51 |1 |
> | 128
Ricardo Martinez writes:
> This keep happening even if change the priority value 2 for priority
> value 5. I even changed the priority 1 for priority 0 as follows :
>
> +-++--++--+
>
> | id | prefix | from_uri | grp_id | priority |
>
> +-+-
Ricardo Martinez writes:
> Could this be related with the parameter "lcr_hash_size", the default
> value is 128, maybe I need to make it larger?
as the name says, lcr_hash_size affects the size of the hash table. any
power 2 size is ok. larger size just means smaller likelihood for
collisions.
Alex Balashov writes:
> A DB crashbug. Perhaps it has already been backported to existing
> 1.5.x tarballs, in which case I am glad.
i pretty sure that i backported the fix to 1.5 branch.
-- juha
___
Kamailio (OpenSER) - Users mailing list
Users@l
Henning Westerholt writes:
> Perhaps the person who introduced this functionality can comment on this? I
> reviewed the patches but not found the commit in question and not
> remember at the moment. Of course its also possible that you just
> take a look to the code and try to find the bug by
Ricardo Martinez writes:
> So I'm not understanding why LCR keep marking the gateways as down, even
> if they are answering to the OPTIONS request. Could this be a bug in
> the LCR module? Or maybe I'm missing something?. The silly part of all
> this is the gateways marked as down are always
Iñaki Baz Castillo writes:
> SIP & XMPP integration is a hack!!
user simply chooses, based on ua capability, which protocol to use. why
can't the same authentication data be used for both?
> Yes, it's true that until now the only feasible IM and presence
> solution is XMPP, but we are in SI
Victor Pascual Avila writes:
> Klaus has gone directly to the point: this is not about religion but
> about pragmatism.
yes and one pragmatic solution might be to add a xmmp server to the
infrastructure so that user can use the same uri both as a sip uri and
xmmp uri depending on client's capab
Olle E. Johansson writes:
> Otherwise, I'm sure that we can get a lot of good stuff from both 3GPP
> and OMA work. But far from all of it is useful. You have to be very
> selective.
i agree with that. well specified xml document formats are one example.
-- juha
__
Klaus Darilion writes:
> Using IMS/OMA on a technical basis does not require to adopt the telco's
> business model.
klaus,
many years ago when i looked at ims, it placed lots of restrictions on
how request must be routed through the mace of proxies and what
information has to be transmitted b
Iñaki Baz Castillo writes:
> Yes, that's a good vision. The problem here is that IETF *didn't*
> finish its work for SIMPLE and XCAP. Instead, IETF has published
> half-done specifications.
>
> I paste a mail I sent to IETF SIMPLE maillist:
>
> http://www.ietf.org/mail-archive/web/simpl
Iñaki Baz Castillo writes:
> - SIMPLE (OMA):
> http://oversip.net/public/SIP_SIMPLE_OMA.jpeg
why OMA? it is part of closed mobile operator walled garden that we
should have nothing to do with.
-- juha
___
Kamailio (OpenSER) - Users mailing list
U
catalina oancea writes:
> I understand your point, but let's say the dialog is created:
>
> asteriskkamailioprovider(hostname)
> >dns lookup >
> INVITE
catalina oancea writes:
> I probably misunderstood the RFC. But an INVITE does create a dialog,
> and the situation:
>
> asteriskkamailioprovider(hostname)
> >dns lookup >
> INVITE 1
catalina oancea writes:
> It seems that kamailio does dns lookup again when receiving REGISTER
> 2, although both registers are part of the same dialog. Is this the
> expected behavior?
i don't think that register requests establish any dialogs. when
registrar receives the second register, it
Schumann Sebastian writes:
> My lastest tested versions did only write to the database at proxy
> shutdown. After room creation (and also after startup) the whole imc
> rooms and members are in the memory.
you are correct. it is possible to check in-memory rooms and membership
with mi command
Rajesh writes:
> IAm trying to configure IMC in kamailio.I created two tables in the
> database named, imc_rooms and imc_members.IN my xlite phone i give the
> command q:s...@192.168.64.75 ('q' is used as the default chatroom name in
> .cfg).
> when i give the command , # create room_name,
Rajesh writes:
> ERROR:imc:imc_handle_message: room [q] does not exist!
> ERROR:imc:imc_manager: failed to handle 'message' .
perhaps you should create the room first. read README carefully.
-- juha
___
Kamailio (OpenSER) - Users mailing list
User
Rajesh writes:
> I havae been trying to configure imc for quite some
> time..If any of you have configured IMC successfully, kindly send me the
> cfg file .Iam pretty sure that it would help me greatly and reduce my
> time taken to implement the module,IMC.I would appreciate
Edson Gellert Schubert writes:
> http://lists.kamailio.org/pipermail/users/2009-August/024463.html
ok, looks like size has the same meaning as in lcr module, i.e., it just
affects the size of hash table, not number of entries stored in it.
-- juha
__
Edson - Lists writes:
> Some time ago, Daniel explained exactly Your question... I'm trying to
> find the thread, but maybe is quickier if you look also for it... it
> involved Alex, Daniel and someone else and discussed htable hash table
> size...
ok, i'll try to dig that and update readm
htable module readme says abotu htable param:
size - number specifying the size of hash table. The number of entries
in the table is 2^size
does it mean the size of the hash table or how many entries can be
stored in hash table?
in lcr module, for example, lcr_hash_size param specifies the forme
Daniel-Constantin Mierla writes:
> you can put abort() in some if conditions - e.g., based on src ip, some
> header/uri value.
daniel,
i tried that on my own system and got a core dump from normal lookup()
call. however, when i look at the core, it doesn't tell me much why
this normal lookup
Daniel-Constantin Mierla writes:
> could you test to the other server with same kind of request to see if
> you get some problem?
i have tired but no luck.
> Maybe better, add an abort() in lookup() function and generate the core.
> Then with gdb check the backtrace.
the problem is that l
Daniel-Constantin Mierla writes:
> Maybe some objects got corrupted in a way or
> another. Would it be possible to get sources and compile/install on
> faulty machine?
i have build more than one debian package and the lookup thing has
happened on all of them. so i don't think anything that
Daniel-Constantin Mierla writes:
> this is really strange if you say that the other machine works ok with
> same binaries and config. Maybe some objects got corrupted in a way or
> another. Would it be possible to get sources and compile/install on
> faulty machine?
same binaries and confi
Juha Heinanen writes:
> ...
> xlog("L_INFO", "INFO: : Request URI when leaving Initial_Tasks: <$ru>\n");
> route(2);
i changed that to
$avp(REQUEST_URI_AVP) = $ru;
xlog("L_INFO", "INFO: EXTR: Request URI when leaving Initial_Ta
i checked the host hw and it is a normal intel dual core processor, so
normal debian i386 package should be fine for it.
i also added more logging to config file like this:
...
xlog("L_INFO", "INFO: : Request URI when leaving Initial_Tasks: <$ru>\n");
route(2);
and in front of route block
Ricardo Martinez writes:
> Sorry i didn't understand this.
> So I will have 100 "OPTIONS" message every 180 secs If I have have
> 100gw's defined?
from reading the code, looks like it is what happens.
> Is there any way to avoid this? , but still keep using the ping
> feature?
not using th
Daniel-Constantin Mierla writes:
> are the hosts with same os? i can't find a reason for such behavior,
> unless objects are corrupted. try a make proper; make all; make install
> (if you use sources).
both run debian, but i don't know if the non-working host is an amd 64 or
something non-in
Daniel-Constantin Mierla writes:
> just to be sure, you said you don't have lookup() at all, right?
i have, but much later in processing of the script. the info message
about the r-uri host not being local, comes much before the lookup would
have been executed, it request-uri host would have be
Daniel-Constantin Mierla writes:
> lookup(location) is called as I can see from log. AFAIK there is no
> other module calling it internally. However, there is a rewrite_uri()
> done before, since 'Not found in usrloc' message comes afterwards. That
> can be from other module: rr, enum, etc.
catalina oancea writes:
> Could someone please explain the usage of the watchers table? I
> understand the usage active_watchers, but why the watchers table too?
as the same says, active watchers contains information about currently
active watchers of a presentity. watchers table contains info
when analyzing the weird problem, where request uri gets rewritten with
aor's contact even when there is no command in config file that would do
it, i noticed these lines in syslog:
Aug 31 16:41:50 /usr/sbin/kamailio[23139]: DBG:core:rewrite_uri: rewriting
Request-URI with 'sip:foo@ip-address
sorry, i sent this message to wrong mailing list. it was sip-router,
not kamailio, where i observed the described behavior.
-- juha
> i have always thought that AVPs exits per transaction. that does not
> seem to be the case, however, because when i put in the beginning of my
> script
>
>
i have always thought that AVPs exits per transaction. that does not
seem to be the case, however, because when i put in the beginning of my
script
xlog("L_INFO", "Caller lcr_id $avp(CALLER_LCR_ID_AVP)\n");
this gets printed to syslog:
Aug 29 11:34:34 localhost /usr/sbin
Ricardo Martinez writes:
> If I have 100 gw's defined, there are going to be 100 "OPTIONS" messages
> at the same time every 180 secs?.
> Or there is a way to randomize the check interval for the gateways?
looks like it sends the pings back-to-back each time the timer fires.
-- juha
Ricardo Martinez writes:
> Another question (in line).
i just restored the somehow missing documentation related to pinging of
gws.
> So, when you first create the Gateway in the mysql table, the column
> ping is filled with what value?
from the restored doc:
A gateway is subject for c
Ricardo Martinez writes:
> One more question. About the column "weight". According to the
> README file, weight is "an integer value from 1 to 254". So I guess
> if I have two gateways for a particular prefix, and I want to send
> 50% of the calls to one gateway and the other 50% of the cal
Ricardo Martinez writes:
> The first one is about the "ping" column in the gw table. I guess this
> column stores the "results" of execute a ping to the gateways in the
> LCR.gw table isn't?.
i don't think that anything is stored in the column by the proxy.
> So how this "ping" is executed?
Daniel-Constantin Mierla writes:
> :-) -- ahh, yes, imo, srctl sort of exists already, but is called
> kamctl.
are you saying that one can control s modules with kamctl? i know that
one can control both s and k modules with serctl (except for async
t_uac_dlg).
-- juha
___
Daniel-Constantin Mierla writes:
> kamctl is in sip-router, check tools directory.
ok, i looked at scripts dir where it used to be in k.
> You are more than welcome to implement the srctl, I am going to
> contribute if I am able to and use it.
srctl sort of exists already, but is is called
Daniel-Constantin Mierla writes:
> Kamailio is the same -- will be a new major release of the sip server
> everybody know so far -- new features in core plus some new modules,
> either new development (memcache) or imported from ser (iptrtproxy). To
> update from kamailio 1.5 to 3.0 you wil
Iñaki Baz Castillo writes:
> What I don't understand is the reasons to make current SR working with
> K and S features/modules compatibility. We don't need a SR working
> solution right now (since Kamailio and SER do exist), do we?. Wouldn't
> be better to spent devel time in porting the requi
Daniel-Constantin Mierla writes:
> You can still use one interface though - MI is fully available and does
> (pseudo) async xmlrpc commands.
that is not true if you use modules from both s and k (like domain
domain module, for example, that is much more advanced in s).
besides, s xmlrpc inter
Daniel-Constantin Mierla writes:
> If you have discovered something else, let us know.
well, just before your message i send a question to andrei about async
(or delayed reply) support for t_uac_dlg. without that i'm not able to
start using sip router, because having to use two xmlrpc managemen
Daniel-Constantin Mierla writes:
> MI tm stats are exported natively via tmx module.
since i need to use xmlrpc module anyway, i prefer to use mi_rpc only
when necessary. if idea behind mi_rpc is backwards compatibility, then
also its output should look like before, which is not now the case,
e
1 - 100 of 357 matches
Mail list logo
