hello all
i have been taking a look to the rtpengine.c code and i found that the
issue has relation with the queried_nodes_limit which had 50 defalut
value, so before it was reached in the loop, we received a
request/response retransmision doing all the same.
anycase, the issue it's because when allow_op is applied, the
select_rtpp_node gets a node even having the node disabled by the first
attemp (having the rtpengine node down), and it does the loop.
if it's not applied, we dont get a node at the retry.
but adjusting the number of queried_nodes_limit to a value to be reached
before a request retransmission arrives, i guess it should be enough
(¿?)
best regards
david escartin
Hi,
I am testing on
CentOS 6.6 x86.64
kamailio-4.3.5
postgresql-9.4.6
pgpool-II-pg94-3.5.2
When I using floating IP as 192.168.192.143 that kamailio is working.
But I could not access to
psql -h 192.168.192.143 -p 9999 -U postgres asterisk.
Let me know if you have this issue with much appriciated.
Thank you.
#!define DBURL "postgres://asterisk:password@192.168.192.143:9999/kamailio"
#!ifdef WITH_ASTERISK
#!define DBASTURL
"postgres://asterisk:password@192.168.192.143:9999/asterisk"
#!endif
#!endif
Noriyuki Hayashi Japan.
Hello everybody,
I have a local kamailio+rtpproxy under NAT listening on multiple local
interfaces (vlans) which works fluenty for all local user indipendently and
engages rtpproxy correctly.
I have another working kamailio+rtpproxy which is accessible from
everywhere at a public address and I would like to route to it some
specific calls from the local server.
So, in the local kamailio configuration file I defined WITH_PSTN (all the
necessary option) and INVITE/OK/BYE messages are going correctly to the
destination. The problem is that I have no audio on both ways.
After some packet sniffing, I tried killing local rtpproxy process and now
calls to PSTN have also audio both ways.
>From these tests, if my configuration is correct, when routing the call to
PSTN gateway I should disable the local rtpproxy, and I'm in doubt about
how I can do this.
Could you help me? Should I change NAT flags in the PSTN route?
Thanks
Hello,
Kamailio SIP Server v4.4.2 stable release is out.
This is a maintenance release of the latest stable branch, 4.4, that
includes fixes since the release of v4.4.1. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v4.4.x. Deployments running previous v4.x.x
versions are strongly recommended to be upgraded to v4.4.2.
For more details about version 4.4.2 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2016/06/kamailio-v4-4-2-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Enjoy the summer holidays!
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hello,
i've installled the new version of kamailio 4.4.1 . in 2 different server ,
with acc module and these parameters:
modparam("acc", "time_mode", 2)
modparam("acc", "time_attr", "seconds") should be seconds.millisec
On the first server in acc table , in field seconds i have values like this
1466493457.85, this is correct timestamp ( this server have centos 86_64)
In the other server , i have values like 1913113.702 , that is wrong
timestamp . (this is old centos 32 bit )
What can be the problem? The different version 32,64 bit ? or some compiler
option ?
Thanks
Hello,
I am considering to release kamailio v4.4.2 next week along with the
corresponding patch releases for branches 4.3 and 4.2. It will likely be
the last release in series 4.2 to mark its end of official packaging.
I would also consider a new patch release in 4.1.x, if that is still
used by many out there to get packages that fix the libssl version
matching -- Victor should say if the packages for this branch can still
be generated in order to make sense doing this release.
Anyhow, report any issues you are aware and are not yet announced for
branches 4.4 and 4.3 to the bug tracker as soon as possible to get a
chance to be fixed by release date. Likely 4.4.2 will be next Tuesday,
June 29, with the other branches done in the following days.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.orghttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hello,
I'm trying to use the userblacklist module to implement a global
blacklist. I have a few questions about the module.
Is it possible to use a avp for the check_blacklist function? If i'm
correct it will only parse the request URI, but i'm rewriting the URI in
a branch route to allow different formats to different destinations. Or
is this only possible with the check_user_blacklist function?
I also have a issue with numbers in E164 format with a leading +. I
tried to escape this with a \ in the database but it will not load the
entry's when i use the + in front of the number. Is the + supported by
this module or should i strip it before the function and add it again
afterwards?
Thanks,
Jan
