Hello,
as discussed during our devel meeting, next major release 3.1 is
scheduled for this autumn. Therefore the freezing should happen soon.
Would be 2 weeks from now enough for everyone to push planned new
features to repo?
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
Hi Guys,
I have 2 kamailio servers.
I need to load balancing for this 2 kamailio servers.
Scenario:
------------
Each kamailio server call limit is 5000 approx.
kamailio server 1
kamailio server 2
If kamailio server 1 reach call limit (5000) then call go on kamailio server
2.
What is the best way for achieve this?
Thanks in advance.
--
Best Regards,
Rajnikant Vanza
Hello,
some time ,there is no signal in phone line for a while ,also the server become very slow then it fix him self ,i don't know how . ,could any body give me possible reasons ,and how i can fix that, i checked syslog file every thing normal as i can see ,please help me.
regards,
hala
Hi All,
I'm in the lab with sip router 3.0 mocking up some trunk-group prefix
routing with PDT and load balancing with Dispatcher. This is working
great and as expected. I would like to incorporate some sort of LCR
matching on NPA-NXX but I'm having some difficulty. The PDT module
automatically strips the prefix so for trunk group routing it works
great but really can't be used for matching NPA-NXX.
The Carrierroute module is pretty nice and works as expected but the
issue I'm having, it appears that I have to have a NPA-NXX entry for
each domain gateway I want to send calls to. For instance if I have 3
gateways in domain 1, then I would need the same NPA-NXX record entry
in the database for each gateway. The database entries would be
[NPA-NXX] x [Number of Gateways] per domain. So having 100K routes
would mean having 300K records. Am I looking at this correctly? This
is really what it seems like to me but logically I would think this
should not be the case?
I really like the Dispatcher polling functions to actively know what
gateways are on-line and off-line plus the different distribution
algorithms to choose from. So it makes sense to me to implement a
pseudo PDT/Distpacher scenario as an LCR but with PDT stripping the
prefix, that can not be done. Is there another mechanism whereby I
can dip the database looking for the NPA-NXX, extract the domain group
and send that to the Dispatcher function, without stripping the
prefix?
Or can a PDT module parameter be added to not strip the prefix. But
I'm not sure this will work, can the PDT module hold in memory a few
hundred thousand records?
Thanks.
JR
--
JR Richardson
Engineering for the Masses
Hi,
I started using Kamailio 3.0 as redirect server about 2 months ago,
basically I'm quite new to it. Now I need to change current setup to
redundant active-active system but I'm struggling where to find
documentation that can lead me to achiving it. Can anyone pls advise me
where to start looking ?
Many thanks,
Maw Tun
Hi, I'm trying to test the new 3.0.2 release ... but with no luck ...
sbc02:/etc/kamailio# kamailio -ddddddddd -u kamailio -g kamailio -c -E
0(1036) DEBUG: <core> [main.c:1800]: read 343643572 from /dev/urandom
0(1036) DEBUG: <core> [main.c:1806]: seeding PRNG with 1622837431
0(1036) DEBUG: <core> [main.c:1810]: test random numbers 396346077 2140170049
1800197589
0(1036) : <core> [cfg.lex:1390]: included file name must be between quotes
If i'm not wrong ... I should get the line/caracter at witch the parser get
the error ... but that's not true ... I'm missing something really stupid ?
Best regards
--
Raúl Alexis Betancor Santana
Dimensión Virtual
How difficult would it be to make ds_select_domain(set, alg) accept a pseudo
variable for the "set" argument? I would like to map the $rU to a specific
dispatcher set via a database table. I suppose i could just hard code three
or four sets with a conditional if() statement, but I would prefer to make
it a little more dyanimc.
Correct me if I am wrong in my assumption that ds_select_domain() doesn't
accept pseudo variables.
Thanks.
Hi, what does it mean this error message?:
CRITICAL:tm:set_timer: set_timer for 1 list called on a "detached"
timer -- ignoring: 0x7f1106077a60
Thanks a lot.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
Hi Daniel,
I have followed your instruction (I'm using kamailio 1.5) and before the
t_relay("0x05") statement I've setted:
$du="sip:" + $rd + ";transport=tls";
but I get the following mesasge:
Jul 14 15:17:55 OVSIPP /usr/local/sbin/kamailio[7790] Request leaving server, *D_-URI='sip:garr.it;transport=tls'_* - M=INVITE RURI=sip:xxx@garr.it
F=sip:yyyyy@sip.mydomqin.it:5066 T=sip:123456789@sip.mydomain.it:5066
Jul 14 15:17:55 OVSIPP /usr/local/sbin/kamailio[7790]: CRITICAL:core:mk_proxy: could not resolve hostname: "garr.it"
Jul 14 15:17:55 OVSIPP /usr/local/sbin/kamailio[7790]: ERROR:tm:uri2proxy: bad host name in URI <sip:garr.it;transport=tls>
Jul 14 15:17:55 OVSIPP /usr/local/sbin/kamailio[7790]: ERROR:tm:t_forward_nonack: failure to add branches
Therefore I would like to use information about TLS connection (tls
port?) got from NAPTR record.
Doesn't it possible with kamailio 1.5 ?
Many thanks,
Daniel
Il 08/07/2010 18.12, Matteo Campana ha scritto:
>
>
> -------- Messaggio originale --------
> Oggetto: Re: [SR-Users] Kamailio and NAPTR lookup with TLS
> Data: Thu, 08 Jul 2010 18:10:35 +0200
> Mittente: Daniel-Constantin Mierla <miconda(a)gmail.com>
> A: matteo.campana(a)klarya.it
> CC: sr-users(a)lists.sip-router.org
>
>
>
> Hello,
>
> On 7/8/10 5:59 PM, Matteo Campana wrote:
> >
> > Hi all,
> > I'm using kamailio 1.5 with TLS module.
> > I need to make ENUM query and get NAPTR record.
> > > From NAPTR lookup, I'd like to relay my SIP Invite with tls protocol.
> >
> > How can I tell Kamailio to use TLS protocol ( instead of udp) after NAPTR lookup ?
> >
> > I've try to set :
> >
> > dns_tls_pref=1
> > dns_udp_pref=2
> > dns_tcp_pref=3
> >
> > in the general section of kamailio.cfg, but I get a parse error.
> >
> >
> these parameters were introduced in kamailio with version 3.0.
>
> If you need TLS then it is recommended to use 3.0 anyhow, it is a far
> better implementation. That will make the life easier to migrate to
> upcoming 3.1 that will bring asynchronous TLS.
>
> No matter what you have in R-URI, you can force TLS via setting outbound
> proxy address to be a TLS uri:
>
> $du = "sip:__ip_or_host__;transport=tls";
> t_relay();
>
> The IP or host you can take from R-URI without any problem via PV $rd.
> Other option is to use function from tm - t_relay_to_tls():
>
> http://kamailio.org/docs/modules/stable/modules/tm.html#t_relay_to_udp
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla
> http://www.asipto.com/
>
>