Hi,
I'm having some issues with recording in rtpproxy when I parallel fork
an incoming call.
The scenario is that I want to record incoming calls to a small number
of operators, and the call is converted to an 'all-call' by the local
kamailio instance - parallel forking.
It appears - though I co
Kamailio 1.5.4 segmentation faulted today. I was able to determine
with gdb that the error occurred at mediaproxy.c line 1104. Line 1104
is a call to memcpy
Core was generated by `/sbin/kamailio -m 512'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f1469db6bb5 in replace
I had this problem on one (dual xeon) system. The cause was a very slow
disk system - it was SAS but the OS decided to use it as IDE - and the
killer was bandwidth logging by iptables.
Checking with wireshark it could sometimes take over a second for a
packet to get out of an interface.
When I ch
Anders writes:
> I have two different trunks with one carrier. The IP where I send the
> INVITE is the same, but the prefix differs. So in the gw table, I
> enter the two lines, - same IP, but with different digits in the 'tag'
> column, and different grp_id numbers. I then set up the lcr table an
Anders writes:
> I cannot find an answer to this in the documentation: Is there a limit
> to how many fail-overs Kamailio does? I have lcr setup for a
> destination where it is rejected with 403 on the first and second
> priority, but then it goes no further, even though I have a third
> priority
Hello,
I did a fix for drouting module which opened a connection to DB in a
wrong way. Can you fetch the latest version of branch 3.1 and try again?
Tomorrow is planned 3.1.1 which will contain the fix as well.
Thanks,
Daniel
On 11/30/10 10:03 PM, Daniel-Constantin Mierla wrote:
Hello,
se
On 12/1/10 9:47 PM, Vic Jolin wrote:
Hi my syslog.conf already has something like that, any other place I
should look at?
you can use benchmark module to try localizing what is taking too long
to execute.
Cheers,
Daniel
On Thu, Dec 2, 2010 at 4:44 AM, Daniel-Constantin Mierla
mailto:mico
Hi my syslog.conf already has something like that, any other place I should
look at?
On Thu, Dec 2, 2010 at 4:44 AM, Daniel-Constantin Mierla
wrote:
>
>
> On 12/1/10 9:41 PM, Vic Jolin wrote:
>
> debug level is 9, do I have to set syslog to be configured asynchronously
> for this?
>
> The rate of
On 12/1/10 9:41 PM, Vic Jolin wrote:
debug level is 9, do I have to set syslog to be configured
asynchronously for this?
The rate of the calls is not more than 20 cps
if you diverted the log messages to a specific file, then add a dash '-'
in front of file path:
http://www.kamailio.org/dok
debug level is 9, do I have to set syslog to be configured asynchronously
for this?
The rate of the calls is not more than 20 cps
On Thu, Dec 2, 2010 at 4:35 AM, Daniel-Constantin Mierla
wrote:
> Hello,
>
>
> On 12/1/10 9:33 PM, Vic Jolin wrote:
>
>> Hi all,
>>
>> Just want to ask if anybody her
Hello,
On 12/1/10 9:33 PM, Vic Jolin wrote:
Hi all,
Just want to ask if anybody here has come across this problem of mine,
when single call proxy is ok, but when you send more traffic to it,
calls somehow get stuck, trying to make a new call it takes a lot of
time and so it times out.
Does
Hi all,
Just want to ask if anybody here has come across this problem of mine, when
single call proxy is ok, but when you send more traffic to it, calls somehow
get stuck, trying to make a new call it takes a lot of time and so it times
out.
Does anybody know what could be the problem?
Thanks!
_
Maybe you have to call t_on_failure() in failure route again?
klaus
Am 01.12.2010 16:22, schrieb Anders:
Hi there,
Kamailio 1.5:
I cannot find an answer to this in the documentation: Is there a limit
to how many fail-overs Kamailio does? I have lcr setup for a
destination where it is rejected
Iñaki Baz Castillo wrote:
> This is the Samsung model in which I've detected the bug:
>
> OfficeServ 7200 with firmware 4.40.
OK, thanks.
I am not sure if we need to fiddle with that, but I hope 4.48e helps you.
--
Mikko Lehto
___
SIP Express Router
Hello Anders,
There is no limitation on the number of failovers in lcr.
You need to properly populate your lcr tables.
Below you will find an example for openser 1.3. You can adjust it to
work with kamailio 1.5.
http://voipembedded.com/resources/openser_dbtext_lcr.cfg
The lcr module was improve
Hi there,
Kamailio 1.5:
I cannot find an answer to this in the documentation: Is there a limit
to how many fail-overs Kamailio does? I have lcr setup for a
destination where it is rejected with 403 on the first and second
priority, but then it goes no further, even though I have a third
priority
Hi All,
thought I would give you a small little perl program I quickly hacked up to
help with some memory leaks I was getting. Turns out I was forgetting to
call release_urecord after a get_urecord on the usrloc module. Because I use
Kamailio in DBOnly mode - the memory was never being freed. This
Yes. I have Bison 2.4.3 installed.
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Tuesday, November 30, 2010 4:29 PM
To: Sherker, Christa
Cc: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Kamailio Solaris Install
Hello,
do you have bison (or byacc) tool installed?
Che
Thank you Daniel,
That works great.
Cheers
Alex
On Wed, Dec 1, 2010 at 12:23 PM, Daniel-Constantin Mierla wrote:
> Hello,
>
>
> On 12/1/10 9:34 AM, Marius Zbihlei wrote:
>
>> Hello
>>
>> I think you should try:
>>
>> $sel(@via[1].params[x-route-tag])
>>
> indeed, selects need a bit of care r
2010/12/1 Mikko Lehto :
> Iñaki Baz Castillo wrote:
>
>> I've asked the client about model and version of his Samsung. I'll
>> tell it to you when I get it.
This is the Samsung model in which I've detected the bug:
OfficeServ 7200 with firmware 4.40.
--
Iñaki Baz Castillo
Iñaki Baz Castillo wrote:
> I've asked the client about model and version of his Samsung. I'll
> tell it to you when I get it.
OK, thanks!
For the record, here is the CANCEL we captured:
CANCEL sip:+3589x...@proxy.siplab.fi:5060;user=phone SIP/2.0
From:
;tag=13a7588-26fb446d-13c4-50017-4cf
2010/12/1 Mikko Lehto :
> Hi Iñaki
>
> We tried to reproduce the Samsung behavior you recently described.
> My observation is that the CANCEL, which was generated after the received
> provisional response (183 with SDP), has no To tag nor SDP body.
>
> According to local Samsung representative, the
Hi Iñaki
We tried to reproduce the Samsung behavior you recently described.
My observation is that the CANCEL, which was generated after the received
provisional response (183 with SDP), has no To tag nor SDP body.
According to local Samsung representative, the tested model and version is
OfficeS
Hi,
Running Kamailio 1.5:
I have two different trunks with one carrier. The IP where I send the
INVITE is the same, but the prefix differs. So in the gw table, I
enter the two lines, - same IP, but with different digits in the 'tag'
column, and different grp_id numbers. I then set up the lcr tabl
Hello,
On 12/1/10 9:34 AM, Marius Zbihlei wrote:
Hello
I think you should try:
$sel(@via[1].params[x-route-tag])
indeed, selects need a bit of care regarding documentation -- they come
from SER and I added pseudo-variable class $sel(selectid) to be able to
use them whenever a PV can be used.
Hello,
a reminder for everyone that has to push fixes to branch 3.1 before
tomorrow noon.
Thanks,
Daniel
On 11/26/10 9:25 AM, Daniel-Constantin Mierla wrote:
Hello,
there are almost 2 months since release of Kamailio 3.1.0, so it is
time for 3.1.1 as there were several important fixes done
Marius hi,
I got the value I needed with:
$avp(s:xroutetag) =
$(hdr(Via){re.subst,/^SIP(.*)x-route-tag="tgrp:(.*)(")/\2/});
You are right about Daniels way so I will continue trying in that.
Thanks for your time
Alex
On Wed, Dec 1, 2010 at 10:26 AM, Marius Zbihlei wrote:
> Hello Alex,
>
>
Hello
I think you should try:
$sel(@via[1].params[x-route-tag])
Marius
From: alex pappas [rebel.pap...@gmail.com]
Sent: Wednesday, December 01, 2010 9:09 AM
To: Daniel-Constantin Mierla
Cc: Marius Zbihlei; sr-users@lists.sip-router.org
Subject: Re: [SR-U
Hello Alex,
Can't test it right now, but it should work better with this :
$var(s:xroutetag) = $(hdr(Via){re.subst,/^.*;x-route-tag="(.*)"/\1/})
You want to substitute (only affects $var) the whole via header with the regex
found between () and referenced by \1. Keep in mind that Daniel's solut
Marius hi,
Thank you for your replay.
With the regular expression you provided me I get "*SIP/2.0/UDP
172.16.0.13:5060;tgrp:TNDEM-ACR*"
Can I isolate only *tgrp:TNDEM-ACR ?
*Thank you
Alex
*
*
On Tue, Nov 30, 2010 at 5:07 PM, marius zbihlei wrote:
> On 11/30/2010 01:58 PM, alex pappas wrote:
>
Daniel hi,
When I'm trying the bellow I get the following error:
Dec 1 10:06:17 opensips1 kamailio: ERROR: [select.c:149]:
parse_select: invalid index, no closing ]
Dec 1 10:06:17 opensips1 kamailio: ERROR: pv [pv_select.c:45]: invalid
select name [...@via.params[x-route-tag]]
Dec 1 10:06:17
31 matches
Mail list logo
