Hello,
I'm trying to setup kamailio as load balancer Behind that load balancer
I've a registrar and a presence server.
When I start a client for the REGISTER and subscribe messages all looks to
work fine. The messages from clients are properly balanced to the backend
and responses are forwarded
Hello,
We found an issue when using nat pinger
Previously our system had 1 Kamailio as entry point and we were using
usrloc in mode 2 so:
modparam("usrloc", "db_mode",2)
modparam("usrloc", "db_url",
"mysql://openser:openserrw@/openser")
On our system we like to use the pinger NAT_HELPER
I'm using dispatcher module for load balancnig purposes I read
active/inactive nodes from the database
So I define on my kamailio.cfg:
modparam("dispatcher", "db_url","mysql://openser:openserrw@
/openser")
Then, on my route(DISPATCH) I call:
* ds_select_dst("1", "4");*
* t_relay();*
*
> Hello,
>
>
> On 1/10/12 3:11 PM, Albert Petit wrote:
>
>
> I'm using dispatcher module for load balancnig purposes I read
> active/inactive nodes from the database
>
> So I define on my kamailio.cfg:
> modparam("dispatcher", "db_url",
Hi,
SIP UAS1
SIP LB <->
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-
Hi , Sorry for previous email. Hit send too soon .
Good morning,
On my system i've a structure similar to:
SIP ClientsSIP Platform
[---][-]
S1 @IP2
clients"
> and "SIP servers".
Yes you're right, not correct use of the term, sorry for that.
>
>
> On 03.02.2012 10:26, Albert Petit wrote:
>
>> Hi , Sorry for previous email. Hit send too soon
good morning
When provisioning subscriebrs to Kamailio with the kamctl tool i see the
passwords are stored in clear on the database. For my use-case I would not
like to have that passwords in clear on the db.
What can I do to avoid this problem? Should I provision the users in a
different way an
Hello,
On a Kamailio deployment it seems some users get to a wrong state
and permanently keeping in: CS_DIRTY Expires==0 for some long times
(even half an hour). When they're in this status seems system cannot
reach them.
Normally , when working on USRLoc mode 2 if the registration expires
u
Hello,
On a Kamailio deployment it seems some users get to a wrong state
and permanently keeping in: CS_DIRTY Expires==0 for some long times
(even half an hour). When they're in this status seems system cannot
reach them.
Normally , when working on USRLoc mode 2 if the registration expires
u
Hi,
For load testing I would like to setup rsyslog so Kamailio logs are written
asynchronously
Would the following configuration be enough for that purpose in *
rsyslog.conf*?
#
# Write log file in asynchronous mode and use an IO Buffer of 64 Kb
# IO buffer config http://www.rsyslog.com/doc/rsy
Hi community,
We updated our deployment to Kamailio 3.2 and we would like to use it now
as presence server but we need to keep backwards compatibility wth previous
services.
We found that when we use kamailio as PS several tuples can be stored on
the database even if they are from different publ
Hi list
I have installed a newer version of rtpproxy (2.0) in our development
server , i was happy because it brings lot of performance improvements
However i have found an issue when clients use TLS+SRTP
In that scenario i do not want rtpproxy to decrypt/reencrypt the traffic as
my B2BUA does t
essages should be
used, and "p" indicates that the regular RTCP profile should be used. As
such, the combinations "sp", "sP", "Sp" and "SP" select between RTP/AVP,
RTP/AVPF, RTP/SAVP and RTP/SAVPF, respectively.)
Thanks
Albert
2016-06-01 12:18 GMT+02:00
Dear list,
I've recently upgraded to Kamailio 5 in order to avoid issue parsing SDP
multipart bodies which think are fixed in the update ( - symbol rejected in
content type) .
I could upgrade without issues from my kamailio 4 dev deployment but i
cannot load anymore MI_Datagram module (seems not
Hi list,
I am having some issues parsing multipart INVITE [1] when
calling force_rtp_proxy . I tried to upgrade to Kamailio 5 to see if maybe
i was using too old code but seems not the case.
Log of error is:
Apr 3 18:31:21 mcptt /usr/sbin/kamailio[3232]: INFO:
Ok did not check upgrade guide
Thanks for your comments Patrick and Daniel! :-)
Albert
2017-04-03 13:27 GMT+02:00 Albert Petit :
> Dear list,
>
> I've recently upgraded to Kamailio 5 in order to avoid issue parsing SDP
> multipart bodies which think are fixed in the update (
17 matches
Mail list logo