We don't support SRTP de/re-encryption at this point, neither in master nor
in 2.0. The work to add it is underway, but we are not quite there yet.
Pass-through mode should be working fine though, we've tested it recently
specifically.
On Jun 7, 2016 12:27 PM, "Albert Petit" wrote:
> Hi ,
>
> Sor
Sergey, these days Rtpproxy can also do ipv4-ipv6 gatewaying, media
pinning/topology hiding, session recording, MOH/prompt injection, media
timeout notification, media accounting generation and stats collection.
As far as original question goes, I suggest you guys check some IPv6
scenarios availa
Hello,
the problem is that the ACK doesn't have in R-URI the address from
Contact header in 200ok, as required by RFC.
The R-URI and the Route are both having the IP of Kamailio, so there is
no other address where to send the ACK.
ACK sip:10.15.1.30:5060 SIP/2.0
*Route: sip:10.15.1
Hi there,
I'm having an issue in a SBC (ACME) -> KAMAILIO -> Asterisk scenario with an
ACK that gets ignored in Kamailio because it does not match any transaction.
The INVITE coming from the SBC looks like this (only relevant headers and
hidden numbers for simplicity - SBC has IP .12 , Kamailio
Thanks Chabert. Very comprehensive post. Maybe it is very easy for me to
understand because my strongest background is networking. Actually, I have been
involved in few projects where I used BGP to do what you mention to flip an
entire datacenter over 400Kms distantance from each other. What we
You cannot use the userPasswort addtribute for SIP auth unless you
remove the encryption in your LDAP.
The best why is to use H.350 module and use the relevant LDAP attribute
to store the SIP password,
Emmanuel
Le 16-06-08 11:53, wanmon a écrit :
Dear list,
I have Kamailio 4.4.1 running with
Hello,
I currently have Freeswitch acting as a B2BUA, handling registrations,
routing, etc for a prototype voice application I have built.
Now I'm at the point where it's time to actually scale it out, and I'm
looking at a few different options for the SIP proxy + registration later.
Essentially,
You would be correct to assume that it's adequate to call rtpengine_manage() in
the loose_route section for the offer, and in the corresponding onreply_route
for the answer.
-- Alex
--
Principal, Evariste Systems LLC (www.evaristesys.com)
Sent from my Google Nexus.
_
Dear list,
I have Kamailio 4.4.1 running with local mysql authentication
(WITH_MYSQL/WITH_AUTH).
i have RADIUS and LDAP services running.
I would like to use all of them (MYSQL+RADIUS+LDAP) for Authentication.
How is the best "kamailio.cfg" approach to use all defined users on RADIUS and
L
Hello,
How should reINVITEs be handled in the kamailio script and also in combination
with rtpengine?
I was reading the RR docs and loose_route function pretty much handles this if
I'm correct.
We're currently receiving reINVITEs for checking if a session is still active,
not for session modifi
Hello,
following past discussions about different formats resulted when
generating readme files for modules on various systems, which typically
led to conflicts when backporting, I put in place a cron job running on
kamailio.org to fetch from github the docbook files, generate the readme
and push
I let compile go through all modules that I use and noticed that now
also tls module warning are gone! That is great. The only remaining
ones are on cfg/cfg_ctx.
-- Juha
CC (gcc) [sip-proxy]cfg/cfg_ctx.o
cfg/cfg_ctx.c: In function 'cfg_set_now':
cfg/cfg_ctx.c:485:5: warning: derefere
Daniel-Constantin Mierla writes:
> Can you try with master branch and see if the warning for tlsf malloc
> disappeared? I changed the prototypes of malloc functions to use size_t
> to be compatible with standard malloc(). Changes are only in master branch.
The warning are now gone:
CC (gcc) [sip
Can you try with master branch and see if the warning for tlsf malloc
disappeared? I changed the prototypes of malloc functions to use size_t
to be compatible with standard malloc(). Changes are only in master branch.
Cheers,
Daniel
On 21/05/16 22:11, Juha Heinanen wrote:
> I'll come back to mem
Hi Moaci,
If you want to provide Kamailio HA in two different datacenters, BGP will
be the best tool to achieve that.
Passing keepalived packets throught VXLAN could be a solution, but if you
have any packet loss or bugs in VXLAN implementation in linux kernel, your
service will be down.
I have t
On 08/06/16 09:11, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> Indeed there was a fix yesterday afternoon, backported right now to
>> older stable branches.
> Thanks, now it still remains to fix xmlrpc module.
>
Just replied on sr-dev about xmlrpc, as I can't reproduce it with st
Daniel-Constantin Mierla writes:
> Indeed there was a fix yesterday afternoon, backported right now to
> older stable branches.
Thanks, now it still remains to fix xmlrpc module.
-- Juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users m
On 08/06/16 08:07, Juha Heinanen wrote:
> Juha Heinanen writes:
>
>> Sorry, the version of Kamailio on this host is 4.3 build on April 7,
>> 2016.
> I rebuilt Kamailio on latest Jessie and after that Kamailio stared OK.
>
> Just a warning to those who have automatic security updates on: your
> Ka
Indeed there was a fix yesterday afternoon, backported right now to
older stable branches.
Cheers,
Daniel
On 08/06/16 07:14, Juha Heinanen wrote:
> Was this fixed on master?
>
> Jun 8 08:12:46 sars /usr/bin/sip-proxy[19017]: : tls [tls_init.c:557]:
> init_tls_h(): ERROR: tls: init_tls_h: insta
19 matches
Mail list logo
