Hello,
On 8/20/11 10:16 PM, Omar wrote:
The only difference is we have added some AVPs variables to process, and
kamailio stops processing new calls, is not regular, but seems is related to
the number of calls received.
No additional calls can be processed after certain time, or maybe some am
Hi Daniel,
Do you need more information to track this issue?
Best regards,
On Mon, 08 Aug 2011 11:08:28 +0200, Richard DEMONGEOT
wrote:
> Hi Daniel,
>
> Following network capture about this error
>
> Establishing dialog :
>
> U 192.168.1.15:22490 -> 192.168.238.66:5060
> INVITE sip:mike@193.
Hello,
just a short reminder that we will close the development of new features
for version 3.2.0 at the end of today, GMT. Then the focus should be on
testing (e.g., bug fixing) and enhancements to documentation.
If you have something to commit, do it today, or if it is impossible for
you t
Hello,
the 10 years SER conference in Berlin is full booked, meaning that new
registrations will be accepted only if someone that registered
previously will cancel his/her participation.
Since we just discovered such a situation, in the case you did register
and you haven't received a confir
Hi Richard,
should be fine for now, just need the time to set it up for
troubleshooting -- traveling, freezing for 3.2 and 10 years SER
conference kept me busy with other things that needed done so far.
Should get back to things reported to me very soon, since tomorrow we
get into testing pha
Hi,
On Sat, Aug 20, 2011 at 10:16 PM, Omar wrote:
>
>
> The only difference is we have added some AVPs variables to process, and
> kamailio stops processing new calls, is not regular, but seems is related to
> the number of calls received.
> No additional calls can be processed after certain ti
On 22.08.2011 14:04, Morten Isaksen wrote:
> On Sat, Aug 20, 2011 at 10:16 PM, Omar wrote:
>>
>>
>> The only difference is we have added some AVPs variables to process,
> and kamailio stops processing new calls, is not regular, but seems is
> related to the number of calls received.
>> No addition
I think that can easily become a problem if all the users decide to send
registrations as they please. I tried looking into ratelimit and pike and it
wont solve my problem.
What is the extent of the setting min_expires on this module? Will it create a
423 reply to the user or is not the intende
There is no way to prevent that a SIP client sends you a request at any
time.
The standard defined behavior for setting REGISTER interval is by
setting the expires header.
Of course you could block which does not use the provided expires
header, but then it may increase load on your support team
Hi Marius,
You are right.. It will fail for parse_accept_body... I hope you will be
able to open this issue on bug tracker..
Thanks
Jijo
On Fri, Aug 19, 2011 at 10:12 PM, Bucur Marius <
bucur_marius_ovi...@yahoo.com> wrote:
> Hello Jijo,
>
> About the example I pointed, the parse_accept_body wi
Hello,
It seems kamailio 3 does not save message flags set in branch route into the
transaction. In reply_route and failure_route the flag set in branch_route is
unset. In 1.4 this used to work. I would like to get that behaviour back, is
this possible?
Testscenario:
route {
setflag(0
On Monday 22 August 2011, Alex Hermann wrote:
> It seems kamailio 3 does not save message flags set in branch route into
> the transaction. In reply_route and failure_route the flag set in
> branch_route is unset. In 1.4 this used to work. I would like to get that
> behaviour back, is this possible
On Monday 22 August 2011 16:43:43 Alex Hermann wrote:
> On Monday 22 August 2011, Alex Hermann wrote:
> > It seems kamailio 3 does not save message flags set in branch route into
> > the transaction. In reply_route and failure_route the flag set in
> > branch_route is unset. In 1.4 this used to wor
Hello,
a new person has joined our development squad - Matthew Williams,
currently working for Flowroute, USA. He is already a developer of SEMS
(SIP Express Media Server) and he going to add shortly, just in time for
3.2, some Json related extensions, including a JSON-RPC client module.
His
Hi Daniel
1.
modul purple is not compiled for me.
hal:/usr/local/src/sip-router/modules_k/purple# make
CC (gcc) [M purple.so] clientpipe.o
In file included from purple.h:23,
from clientpipe.c:28:
/usr/include/libpurple/status.h:93: error: expected
specifier-qualifier-list before ‘gpointer’
ma
El Mon, 22 Aug 2011 22:04:44 +0200
MÉSZÁROS Mihály escribió:
> Hi Daniel
>
> >>
> >> 1.
> >> modul purple is not compiled for me.
> >> hal:/usr/local/src/sip-router/modules_k/purple# make
> >> CC (gcc) [M purple.so] clientpipe.o
> >> In file included from purple.h:23,
> >> from clientpipe.c:28:
interestingly i am using memory only instead to read or write the DB in disk
with carrierroute.
Should i clear the AVP variables that i am using after in send the call out,
maybe that is the problem?!
Omar
On Aug 22, 2011, at 8:04 AM, Morten Isaksen wrote:
> Hi,
>
> On Sat, Aug 20, 2011 at
I know this might not be totally on-topic for the list, but I figured the
list participants might have experience in this domain, so I'm lobbing it
out there...
I've got some situations where I'd like to connect users who are oftentimes
sitting on very locked-down networks (ie, corporate networks)
18 matches
Mail list logo
