THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened. Details are below.

User who did this - Anonymous user ()

Attached to Project - sip-router Summary - TLS modul problem Task Type - Bug Report Category - tls Status - Assigned Assigned To - Andrei Pelinescu-Onciul Operating System - Linux Severity - Critical Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - I am experiencing problem "Invalid connection state (bug in TCP code)"in tls_server.c in function <code> static int tls_complete_init(struct tcp_connection* c) </code> <code> if (c->state == S_CONN_ACCEPT) { dom = tls_lookup_cfg(cfg, TLS_DOMAIN_SRV, &c->rcv.dst_ip, c->rcv.dst_port); } else if (c->state == S_CONN_CONNECT) { dom = tls_lookup_cfg(cfg, TLS_DOMAIN_CLI, &c->rcv.dst_ip, c->rcv.dst_port); } else { BUG("Invalid connection state (bug in TCP code)\n"); goto error; } </code>

Incoming tls connection is working fine. The problem only occurs if a worker received a new invite and want forward and open a new TLS connection by <code>int tls_h_blocking_write(struct tcp_connection *c, int fd, const char *buf, unsigned int len) </code> I am debugged with gdb and i catch that c->state is S_CONN_OK So it seems it TCP is already connected.

My TCP config in ser.cfg <code> #TLS enable_tls=yes

#TCP settings disable_tcp=no tcp_async=no tcp_send_timeout=2 #tcp_accept_aliases=yes # accepts the tcp alias via option (see NEWS) tcp_delayed_ack=no tcp_fd_cache=no

</code>

More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=14

You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.