Hi Daniel,
I have advertise as:
listen=tcp:10.116.15.237:443 advertise sbc01.stg.gii.me:443
(normally it would be tls, I switched to tcp so I could get unencrypted
traffic in tcpdump for you)
Record-route is done as:
# Dispatch requests
if (is_method("INVITE")) {
Hello,
how do you set the record-route? Do you have advertised address for the
socket receiving TCP/HAproxy loadbalancer connections?
Can you give all the debug messages when processing the BYE that doesn't
go through?
Cheers,
Daniel
On 21.11.19 19:44, Joel Serrano wrote:
> Hi Daniel,
>
> I
Hi Daniel,
I sent you (privately) 2 pcaps. Please let me know if you need anything
else.
My current TCP params are:
disable_tcp=no
tcp_children=1
tcp_max_connections=12288
tcp_rd_buf_size=65536
tcp_conn_wq_max=131072
tcp_keepalive=yes
tcp_crlf_ping=yes
tcp_keepcnt=3
tcp_keepidle=30
I don’t, but I’ll repeat the test with tcpdump active! I’ll report back
shortly
On Thu, Nov 21, 2019 at 03:50 Daniel-Constantin Mierla
wrote:
> Hello,
>
> do you have the pcap with the sip traffic for this case?
>
> Cheers,
> Daniel
> On 20.11.19 19:45, Joel Serrano wrote:
>
> Hello,
>
> I
Hello,
do you have the pcap with the sip traffic for this case?
Cheers,
Daniel
On 20.11.19 19:45, Joel Serrano wrote:
> Hello,
>
> I added to the config file:
>
> tcp_no_connect=yes
>
> And with that param, the same test results in a different behavior,
> but still not working:
>
> "message":"
Hello,
I added to the config file:
tcp_no_connect=yes
And with that param, the same test results in a different behavior, but
still not working:
"message":" DEBUG: {1 12583750 BYE RVXZVMHKop}
[core\/msg_translator.c:161]: check_via_address(): (198.1.54.228,
198.1.54.228, 0)"}
"message":"
Bumping this thread up!
I did some more tests trying to narrow down the problem and this is what I
found...:
On the INVITE, I add the TCP connection information I want to save (for
later reuse). Snippets:
...(found this in the misc/examples/pkg/sip-router-oob.cfg, but I haven't
noticed any
Hi Yuriy,
Thanks for your suggestion, I've tried tcp_accept_aliases=yes in config and
I added force_tcp_alias() in the request route, but I haven't seen any
changes.
All the VIA headers look exactly the same, and I still get this in the logs:
"message":" DEBUG: {1 11762916 BYE d2T9-YOxYk}
You have to use
tcp_accept_aliases=yes
But this is not enough as this param will be triggered by function
force_tcp_alias() you need to use in the route for request ( for example
record_route or subroutes)
It will add param paramname= (I Don't remember specific name)
to Via header that will be