| 00:30.39 | *** join/#asterisk-dev jpepper (~jpepper@173-14-206-193-huntsville.hfc.comcastbusiness.net) |
| 00:59.59 | *** join/#asterisk-dev mjordan (~mjordan@user-24-214-136-35.knology.net) |
| 00:59.59 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 02:31.27 | *** part/#asterisk-dev mjordan (~mjordan@user-24-214-136-35.knology.net) |
| 05:58.14 | jmls | morning all |
| 05:58.53 | jmls | not a troll question , but I genuinely want to know if the manager port is more stable in 11 |
| 05:59.43 | jmls | A long time ago in a galaxy far away, it was not so robust, hence the emergence of astmanproxy. I was wondering if there is still a need for that, or is the actual manager port much better these days ? |
| 08:09.20 | wdoekes | jmls: I haven't seen any issues with the manager (port 5038) for my simple uses, ever (since 1.6). was there anything in particular that wasn't robust? keeping connections alive? sending garbage or nothing? |
| 10:25.01 | *** join/#asterisk-dev otherwiseguy (~otherwise@69.23.116.90) |
| 11:58.35 | *** join/#asterisk-dev kpfleming (~kpfleming@unaffiliated/kpfleming) |
| 14:17.00 | jmls | wdoekes: I started using it in 2005 (pre 1.2 I think) and then it was quite ropey - it kept getting "stuck" or non-responsive, memory leaks etc. It's good to hear that it's much more stable. Thanks |
| 15:19.00 | Greenlight | I use the manager port extensively and it never misses a beat (1.8 + 10) |
| 15:56.26 | *** join/#asterisk-dev wudles (~wudles@gateway.secureinstrument.com) |
| 16:06.44 | *** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell) |
| 16:06.44 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 16:39.47 | *** join/#asterisk-dev spditner (~simon@206-248-134-253.dsl.teksavvy.com) |
| 16:44.47 | jmls | Greenlight: ta |
| 17:18.14 | *** join/#asterisk-dev mjordan (~mjordan@user-24-214-136-35.knology.net) |
| 17:18.15 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 17:35.04 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 17:35.04 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 18:20.22 | *** join/#asterisk-dev wudles (~wudles@gateway.secureinstrument.com) |
| 19:18.14 | *** join/#asterisk-dev bradafoster (~brad@pool-173-74-203-181.dllstx.fios.verizon.net) |
| 19:19.39 | *** join/#asterisk-dev mjordan (~mjordan@user-24-214-136-35.knology.net) |
| 19:19.39 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 19:32.10 | *** part/#asterisk-dev bradafoster (~brad@pool-173-74-203-181.dllstx.fios.verizon.net) |
| 20:21.38 | *** join/#asterisk-dev wudles (~wudles@gateway.secureinstrument.com) |
| 21:33.07 | *** join/#asterisk-dev leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 21:33.07 | *** mode/#asterisk-dev [+o leifmadsen] by ChanServ |
| 21:54.07 | *** join/#asterisk-dev kpfleming (~kpfleming@unaffiliated/kpfleming) |