12 Aug
2009
12 Aug
'09
12:12 p.m.
TCP code currently supports blocking and non-blocking mode. But, TLS
code (which depends of course on TCP) supports only blocking-TCP.
Maybe this causes your problems
regards
klaus
MÉSZÁROS Mihály schrieb:
Hi,
It seems to me that, TLS TCP socket must be a blocking,
but it set to NONBLOCK in function:
static int init_sock_opt(int s)
.
.
.
if (fcntl(s, F_SETFL, flags|O_NONBLOCK)==-1){
LOG(L_ERR, "ERROR: init_sock_opt: fcntl: set non-blocking
failed:"
" (%d) %s\n", errno, strerror(errno));
goto error;
}
Of course it can be easily, that i misunderstand something and the
problem is not that....
If it is the problem can anyone help me to correct it,
or point me where the real problem is?
Thanks,
Misi
MÉSZÁROS Mihály wrote:
More details:
You can find attached the back trace.
Misi
MÉSZÁROS Mihály wrote:
_______________________________________________
sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users Hello!
Another problem
I am using sip-router git version with the attached configuration files.
I am getting the error mentioned in subject.
Please see the debug log and my configuration files.
Can anyone help me figure out what i a configured wrong?
Misi
------------------------------------------------------------------------
_______________________________________________
sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
------------------------------------------------------------------------
_______________________________________________
sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users