As it turns out, we did, in fact set the flags wrong: We didn't set them
at all!
In route[NATMANAGE] we were missing a crucial 'b' in
isBflagset(FLBV4V6), leading to the RTPProxy flags never being set to
FAIE or FAEI.
A diff (shame on us for not trying it first) revealed the mistake, and
now all
Hello,
the personal branch must have git user id in the name (root of path),
for me would be:
daniel/newbranch
You can just push to the master branch, the pkg specs don't really break
anything related to kamailio working properly.
Thanks,
Daniel
On 12/3/13 5:11 PM, Victor Seva wrote:
Hi
The SIP packets are fine - we are able to establish SIP session with a
secured control channel as easily as with an unsecured one.
As long as the RTPProxy doesn't get involved (i.e. as long as it's
IPvX-IPvX and not IPv4-IPv6) everything works!
With the RTPProxy, the connection gets established (
Hi there,
this is my initial effort to get a new version [0].
This will create 4.2.0~dev0 packages for wheezy and jessie at master branch.
I've just removed the older releases. I will maintain only this two.
If everything is OK I will cherry-pick and create 4.1.0 packages at
the 4.1 branch
[0]
On 2013-11-29 14:37, Will Ferrer wrote:
Hi Andrew
A very simple place to start -- have you tried upping the memory
allocations in /etc/default/kamailio to see if it fixes the issues? We
had some issues with shared memory that went away when we changed
around these settings.
All the best.
Will
Hi,
I want to build a Kamailio version without the usage of futex. First of all
I notice that the variable "use_futex" within Makefile.defs is hardcoded
to the value "yes". Why is that? I want to get rid of this and build
Kamailio without futex support. In the same file there are GCC options
like
On 03.12.2013 14:23, Mark Zeman wrote:
Hello all,
The subject says most of it, I think.
We set up our Kamailio and RTPProxy according to
http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6
with the addition of an alias (siplab.ch), and the DNS to go with it, as
well as TLS and SRTP.
However
Hello all,
The subject says most of it, I think.
We set up our Kamailio and RTPProxy according to
http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6
with the addition of an alias (siplab.ch), and the DNS to go with it, as
well as TLS and SRTP.
However, we only get working calls IPv4-IPv4 and
REPOST:
Have successfully installed the latest stable Kamailio and Siremis. Have
perused countless online Wiki's and other documentation, but can't seem to
find any definitive tutorials or answers to the following:
1. Where would I set up a SIP registration to my carrier? (Server Services
-> U
Initially sent to sr-dev, but maybe some people from users community can
help as well...
Hello,
wondering if any debian/ubuntu fan has some time today/tomorrow morning
for updating the specs to include the new modules coming with 4.1.
The li
Hi
I am experiencing the exact same issue.
Did you ever find a working solution?
Thank you very much for your assistance.
All the best.
Will Ferrer
Aft nix wrote
> Hi,
>
> We have the following network architecture :
>
> UAC1->kamailio>VoipSwitc
Hello,
a quick reminder that v4.1.0 is scheduled for tomorrow. If there is any
issue you are aware of and hasn't been addressed, then write to the
mailing lists.
Cheers,
Daniel
On 11/28/13 12:02 AM, Daniel-Constantin Mierla wrote:
On 11/27/13 11:59 PM, Daniel-Constantin Mierla wrote:
Hell
Hello,
virtual box must have a network interface in bridge mode to get in from
outside.
Anyhow, be sure kamailio is running:
ps auxw | grep kamailio
Then you can set debug=3 in kamailio.cfg, restart and watch the logs
(/var/log/syslog or /var/log/messages) to see if kamailio receives any
s
Hello,
that backtrace is from shutdown, if you don't have another core file,
then the initial one was overwritten. You have to enable one core per
process. In most of system it is:
echo "1" > /proc/sys/kernel/core_uses_pid
You have to reproduce the issue again and get the backtrace from all
14 matches
Mail list logo
