Hi,
It means the I-CSCF does not know about your S-CSCF or cannot reach it.
Check the diameter UAA message coming from HSS, it should contain an AVP
called Server-Name, with the value of S-CSCF.
Regards,
Dragos
On 17/08/2016 02:45, Rodrigo Moreira wrote:
> Hi,
>
> What is it means?
>
> Thank y
Hi,
What is it means?
Thank you.
Regards.
On Tue, Aug 16, 2016 at 8:49 PM, Alex Balashov
wrote:
> It's in the example I-CSCF config:
>
> ---
>
> failure_route[register_failure]
> {
> if (t_branch_timeout() || t_check_status("([5-6][0-9][0-9])")){
> if (I_scscf_select("
It's in the example I-CSCF config:
---
failure_route[register_failure]
{
if (t_branch_timeout() || t_check_status("([5-6][0-9][0-9])")){
if (I_scscf_select("1")) {
t_on_reply("register_reply");
t_on_failure("register_failure
Hello,
You can help me to due with the error:
SIP 500 - Server error on UAR select next S-CSCF.
What am I doing wrong?
Thanks.
Regards.
--
Rodrigo M.
(37) 9132-4539
(34) 9889-3069
rodrigo.moreira2007
___
SIP Express Router (SER) and Kamailio (OpenSE
Hi,
Perhaps you could try adjusting your sysctl params:
Here are some values, but they should be adjusted for your machine:
net.core.rmem_max=16777216
net.core.wmem_max=16777216
net.ipv4.tcp_rmem=4096 87380 16777216
net.ipv4.tcp_wmem=4096 65536 16777216
net.ipv4.udp_mem=16777216 16777216 16777216
Then you should check kamailio.log and see why it start to fail.
It should be quite easy to see why it start to fail from the log.
Daniel
- Original Message -
From: Jack Stevens
To: Kamailio (SER) - Users Mailing List
Sent: Tue, 16 Aug 2016 18:26:55 +0200 (CEST)
Subject: Re: [SR-Users]
Hi Dan,
We have checked all of that and we also not using pike its really strange
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Daniel Grotti
Sent: 16 August 2016 17:24
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Stress Testing
Hi,
a couple of suggestions:
you may running out of RTP ports.
kamailio may start to block requests if you are using pike module.
UAC may start to de-register after a short expires time, so they won't
be reachable anymore if they do not refresh their registration.
You may check your natping inte
On Tue, Aug 16, 2016 at 04:14:15PM +0200, Olle E. Johansson wrote:
> > I'm seeing a different behavior of t_set_fr depending on transports.
> Which is correct. UDP is connectionless and thus SIP has timers for
> retransmits and fails when there’s no response. With connection-oriented
> protocols,
> On 16 Aug 2016, at 16:26, Jack Stevens wrote:
>
> Hi Guys,
>
> I have been stress testing my Kamailio box but I am unable to get it upto
> 2000 concurrent calls it starts to fall over at 1300 have you got any ideas
> on how I can increase the performance of kamilio btw I am also using rtpe
Hi Guys,
I have been stress testing my Kamailio box but I am unable to get it upto 2000
concurrent calls it starts to fall over at 1300 have you got any ideas on how I
can increase the performance of kamilio btw I am also using rtpengine
Kind Regards
--
CONFIDENTIAL EMAIL FROM NETCALL TE
> On 16 Aug 2016, at 11:41, Daniel Tryba wrote:
>
> I'm seeing a different behavior of t_set_fr depending on transports.
Which is correct. UDP is connectionless and thus SIP has timers for
retransmits and fails when there’s no response. With connection-oriented
protocols, the failure happens wh
hel
>From time to time (it does not depend upon traffic) we see in logs:
ERROR: [tcp_read.c:274]: tcp_read_data(): error reading: Bad file
descriptor (9) ([ip_address]:49832 -> [ip_address]5060) ERROR:
[tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error readingERROR:
[io_wait.h:60
Hey Guys,
Have hit an issue when using uacreg.
When working with Broadsoft (I know, life is not perfect), it appears
that their SBC sitting in front of registration server is caching
REGISTRATION requests and it will not be able to re-REGISTER in case of
credential changes for example.
This w
On Tue, Aug 16, 2016 at 02:50:19AM +0300, jaflong jaflong wrote:
> I have kamailio as a redirect server. It responds with 302 to invites.
> The problem I am having is it continues to send the 302 multiple times.
> How can i get it to stop sending once it gets the first ACK
That should just work (t
I'm seeing a different behavior of t_set_fr depending on transports.
Scenario is that a endpoint has a failover defined in the registrat
after 10s (t_set_fr(1) and handling the locally generated 408 to the
failover destination). This works fine when the request and response
where delivered over
16 matches
Mail list logo
