ling List
Subject: Re: [SR-Users] Transport issue thought
I think the reason for the second issue listed below is that Kamailio never
receives the ‘200 OK’ from back from the INVITE to Asterisk. I have noticed
that starting sometime after version 14.6, Asterisk puts its Public IP-Address
in th
-Address.
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of
Wilkins, Steve
Sent: Friday, May 18, 2018 12:15 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Transport issue thought
I sent the log but I just wanted to clear up the issue.
This is a WebRTC to
y, May 18, 2018 8:49 AM
To: Kamailio (SER) - Users Mailing List
mailto:sr-users@lists.kamailio.org>>
Subject: Re: [SR-Users] Transport issue thought
Can you print the logs when it tries to send the ACK?
Check also that the ACK ruri contains the same destination port which was used
for the INVITE
> Of *Federico Cabiddu
> *Sent:* Friday, May 18, 2018 8:49 AM
>
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] Transport issue thought
>
>
>
> Can you print the logs when it tries to send the ACK?
>
> Check also that the ACK ru
R) - Users Mailing List
Subject: Re: [SR-Users] Transport issue thought
Can you print the logs when it tries to send the ACK?
Check also that the ACK ruri contains the same destination port which was used
for the INVITE, otherwise a new connection will be created.
Best regards,
Federico
On Fri, Ma
=yes;’ and $fs; this has been to no avail as
> ‘ACK’s’ are still using the high port number randomly assigned by Kamailio.
>
>
>
> Thank you all for sharing your knowledge!
>
>
>
>
>
> *From:* sr-users [mailto:sr-users-boun...@lists.kamailio.org] *On Behalf
>
...@lists.kamailio.org] On Behalf Of
Federico Cabiddu
Sent: Friday, May 18, 2018 8:49 AM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Transport issue thought
Can you print the logs when it tries to send the ACK?
Check also that the ACK ruri contains the same destination port which was
ou all for sharing your knowledge!
>
>
>
>
>
> *From:* sr-users [mailto:sr-users-boun...@lists.kamailio.org] *On Behalf
> Of *Federico Cabiddu
> *Sent:* Friday, May 18, 2018 12:57 AM
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] Transport issue
!
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of
Federico Cabiddu
Sent: Friday, May 18, 2018 12:57 AM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Transport issue thought
You are right Alex, Linux kernel didn't support SO_REUSEPORT, which all
You are right Alex, Linux kernel didn't support SO_REUSEPORT, which allows
a socket to be used as source for a tcp connection while is already bound,
until version 3.9.
Kamailio's parameter tcp_reuse_port, if enabled and your OS has support for
SO_REUSEPORT (so not only Linux but FreeBSD, OSX and o
When an outgoing TCP connection is opened, either a port can be
explicitly bound, or it is auto-assigned by the OS's networking stack. I
believe Kamailio does the latter and does not offer options to constrain
the range. If it does, I'm not aware of any apart from this one:
https://www.kamailio.or
It appears that the bottom line of my TCP transport not working is that
Kamailio is randomly assigning large port numbers to send the TCP traffic out
on.
I am not able to randomly open high ports for this purpose. Is there a way to
tell Kamailio to only use specific ports for this. I have trie
12 matches
Mail list logo
