| 01:28.08 | *** join/#asterisk-bugs darkbasic (~quassel@niko.linuxsystems.it) |
| 03:33.44 | *** join/#asterisk-bugs tzafrir (~tzafrir@bzq-218-28-58.cablep.bezeqint.net) |
| 14:05.14 | *** join/#asterisk-bugs putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 14:05.14 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 14:16.41 | *** join/#asterisk-bugs tzafrir (~tzafrir@bzq-84-109-18-138.red.bezeqint.net) |
| 14:18.50 | *** join/#asterisk-bugs mjordan (~mjordan@nat/digium/x-zcdfyxmvvfqpsxwd) |
| 14:18.50 | *** mode/#asterisk-bugs [+o mjordan] by ChanServ |
| 14:43.17 | *** join/#asterisk-bugs newtonr (~newtonr@nat/digium/x-bnhvwzbuqppjkasf) |
| 14:43.17 | *** mode/#asterisk-bugs [+o newtonr] by ChanServ |
| 15:35.06 | *** join/#asterisk-bugs malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 15:35.06 | *** mode/#asterisk-bugs [+o malcolmd] by ChanServ |
| 18:44.16 | dwayne | I'm trying to debug 1.8.23.1 SSL_shutdown() failed: 5 errors that can be reproduced in a 1.8.23.1 <--> 1.8.23.1 environment. My scenario doesn't seem like the other SSL_shutdown bugs that are currently open. Can anyone please confirm that SSL_shutdown() should or should not be called on a per-call basis ? |
| 18:46.25 | dwayne | seems like the connection is staying up after calls and then if there is a period of inactivity (not sure how long yet) that SSL_shutdown() will fail and then I can't make any more SIP TLS calls to that destination until either side is restarted to break the SSL connection |
| 20:14.49 | *** join/#asterisk-bugs Qwell (~north@pdpc/sponsor/digium/Qwell) |
| 20:14.53 | *** mode/#asterisk-bugs [+o Qwell] by ChanServ |
| 20:41.36 | *** join/#asterisk-bugs leifmadsen (~lmadsen@asterisk/documenteur-extraordinaire/blitzrage) |
| 20:41.36 | *** mode/#asterisk-bugs [+o leifmadsen] by ChanServ |
| 21:42.30 | *** join/#asterisk-bugs tzafrir (~tzafrir@bzq-84-109-18-138.red.bezeqint.net) |