| 00:24.29 | *** join/#asterisk-dev Kobaz (~kobaz@its.kobaz.net) |
| 00:24.29 | *** mode/#asterisk-dev [+o Kobaz] by ChanServ |
| 06:01.30 | *** join/#asterisk-dev feo (~feo@195.209.116.22) |
| 06:49.53 | jkroon | file, thanks for https://gerrit.asterisk.org/c/asterisk/+/15632/1/res/res_rtp_asterisk.c#7086 |
| 06:56.12 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d00dd6c39e4e3d4e964.ipv6.abo.wanadoo.fr) |
| 11:06.05 | tsearle | is there a way to see the types of messages that are currently in a messages that are in a stasis topics backlog? |
| 11:06.16 | file | no |
| 11:07.16 | tsearle | basically I'm having 2 theories, 1. since I'm using only 2 endpoints, there ends up being a large number of channels for each of the two endpoints, and can't handle that well |
| 11:07.42 | tsearle | or 2. there is some sort of event being generated per-call not getting consumed and somehow getting stuck on the stasis buss |
| 11:08.04 | file | messages can't get stuck |
| 11:08.19 | file | well, unless the subscriber blocks indefinitely |
| 11:09.10 | tsearle | ok, and I guess that would probably appear in show deadlocks, which gives a clean bill of health |
| 11:09.16 | file | yes. |
| 11:09.47 | tsearle | so then going back to 1, having 2.5k channel subscribers to a single endpoint topic |
| 11:09.58 | tsearle | would that have serious performance impacts? |
| 11:10.10 | file | probably, all channel events are forwarded to the endpoint topic |
| 11:10.35 | file | so depending on things that would result in a substantial number of messages |
| 11:11.20 | tsearle | I assume the best mitigation would be to ensure as few messages as possible get generated in the first place? |
| 11:12.03 | file | I don't know, because I haven't looked at that specific usage pattern or the ramifications of such things |
| 11:12.41 | tsearle | ok |
| 11:13.18 | file | less messages is less work, but it's the ripples of messages not existing that can cause problems depending on usage |
| 11:45.34 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d00dd6c39e4e3d4e964.ipv6.abo.wanadoo.fr) |
| 13:21.07 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-skmlabozypwgkyzp) |
| 13:21.07 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 13:39.05 | seanbright | can multiple m lines in an SDP have the same port? |
| 13:42.07 | file | hum |
| 13:43.33 | file | seanbright: yes - BUNDLE |
| 13:44.14 | seanbright | ah |
| 13:45.35 | file | at least I think so, but if it were to be done then you'd need to do something like BUNDLE |
| 13:45.40 | file | or be very clever |
| 13:53.59 | seanbright | well i am not very clever, so my options are clear |
| 14:10.56 | *** join/#asterisk-dev CELYA_1 (~Thunderbi@2a01cb0583d31d00f4d7ddd1bc0987bc.ipv6.abo.wanadoo.fr) |
| 14:14.24 | *** join/#asterisk-dev CELYA_ (~Thunderbi@lfbn-nan-1-1579-121.w90-93.abo.wanadoo.fr) |
| 14:15.04 | *** join/#asterisk-dev kharwell (uid358942@gateway/web/irccloud.com/x-ofhprfsycdptjony) |
| 14:15.04 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 16:37.55 | *** join/#asterisk-dev HannaM (~quassel@p54849510.dip0.t-ipconnect.de) |
| 18:07.04 | *** join/#asterisk-dev gtjoseph (~gtjoseph@unaffiliated/gtj) |
| 18:07.04 | *** mode/#asterisk-dev [+o gtjoseph] by moon.freenode.net |
| 19:44.22 | *** join/#asterisk-dev Ravenheart (Ravenheart@95-43-79-254.ip.btc-net.bg) |
| 20:06.18 | seanbright | https://github.com/asterisk/asterisk/commit/99666117be32160b522cb04ffb30637c11d5e8c2#diff-595501477be3bf70132a32a3dc657b48a2e03a34668f120c1fbe7992f978c31cR1524 |
| 20:06.21 | seanbright | doesn |
| 20:06.31 | seanbright | doesn't fmt need to be deref'd in that loop? |
| 20:11.50 | file | argh, yes |
| 20:19.51 | seanbright | i'll put up a review |
| 21:47.56 | *** join/#asterisk-dev elguero (~miguel323@c-73-238-205-3.hsd1.nh.comcast.net) |
| 21:48.07 | *** join/#asterisk-dev elguero (~miguel323@c-73-238-205-3.hsd1.nh.comcast.net) |
| 21:48.08 | *** mode/#asterisk-dev [+o elguero] by ChanServ |