| 02:40.54 | *** join/#asterisk-dev sahmed (~sahmed@cpe-70-114-236-63.austin.res.rr.com) |
| 04:20.51 | *** join/#asterisk-dev CELYA_1 (~Thunderbi@lfbn-nan-1-758-77.w86-236.abo.wanadoo.fr) |
| 05:49.16 | *** join/#asterisk-dev jkroon (~jkroon@165.16.203.122) |
| 07:11.39 | *** join/#asterisk-dev pchero_work (~pchero@87.213.247.82) |
| 07:32.57 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01:e0a:d:1111:b749:768d:ed77:7c9a) |
| 11:27.48 | *** join/#asterisk-dev oej (~olle@h-205-16.A165.corp.bahnhof.se) |
| 11:27.48 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 11:36.57 | tzafrir | oej: hi, PM? |
| 12:34.50 | *** join/#asterisk-dev oej (~olle@h-205-16.A165.corp.bahnhof.se) |
| 12:34.50 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:19.12 | *** join/#asterisk-dev sahmed (~sahmed@66.64.44.146) |
| 13:32.29 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 14:04.57 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-waleymzjmupgqzqg) |
| 14:04.57 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 14:16.23 | *** join/#asterisk-dev sduthil (~sduthil@modemcable094.94-70-69.static.videotron.ca) |
| 14:27.26 | *** join/#asterisk-dev gtjoseph (~gtjoseph@unaffiliated/gtj) |
| 14:27.26 | *** mode/#asterisk-dev [+o gtjoseph] by ChanServ |
| 15:04.40 | *** join/#asterisk-dev pchero_work (~pchero@87.213.247.82) |
| 15:18.53 | *** join/#asterisk-dev kharwell (uid358942@gateway/web/irccloud.com/x-edohllbbifmflzmr) |
| 15:18.53 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 15:51.31 | *** join/#asterisk-dev jkroon (~jkroon@165.16.203.101) |
| 16:02.15 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-qbynkhonolemtfyp) |
| 16:02.15 | *** mode/#asterisk-dev [+o rmudgett] by ChanServ |
| 16:20.15 | *** join/#asterisk-dev sahmed (~sahmed@66.64.44.146) |
| 18:27.06 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d00f4d7ddd1bc0987bc.ipv6.abo.wanadoo.fr) |
| 18:32.38 | kharwell | in an SDP with multi-stream video would it be true that in a response to the offered video from an endpoint we should reply with a=recvonly, but in the reinvite for any other video that's not the remote video stream we should offer a=sendonly? |
| 18:33.20 | file | that's a question |
| 18:33.54 | file | within the context of bridge_softmix I think yes |
| 18:34.45 | kharwell | to be sure then in the single video stream case it'd be a=sendrecv? |
| 18:34.51 | file | yes |
| 18:36.06 | kharwell | so what gets interesting then is how to tell down in the channel driver (in this case pjsip_sdp_rtp that we're in a bridge softmix (sfu mode required?) with multi-stream video so we can build an appropriate sdp |
| 18:37.00 | file | you do that in bridge_softmix when building the topology and renegotiating? |
| 18:38.04 | kharwell | oh can use stream state then? |
| 18:38.15 | file | yes, that shoulddddddd control it |
| 18:38.48 | file | reinvite the joiner so their video is unidirectional I guess |
| 18:38.50 | kharwell | rfcfile strikes again :-) |
| 18:40.12 | kharwell | wouldn't that occur in the first 200 response from Asterisk? |
| 18:40.37 | file | it gets set up as bidirectional |
| 18:41.57 | kharwell | okay thanks. this gives me a direction to start going in |
| 18:42.27 | file | north? |
| 18:44.19 | kharwell | To Canada and beyond! |
| 18:46.27 | tzafrir | file: hi |
| 18:46.34 | file | hello |
| 18:46.39 | tzafrir | PM? |
| 18:46.45 | file | sure |
| 19:52.54 | *** join/#asterisk-dev Corydon76 (~quassel@96.69.98.139) |
| 19:52.54 | *** mode/#asterisk-dev [+o Corydon76] by ChanServ |
| 21:11.32 | *** join/#asterisk-dev sahmed (~sahmed@cpe-70-114-236-63.austin.res.rr.com) |
| 22:06.17 | *** part/#asterisk-dev rmudgett (rmudgett@nat/digium/x-qbynkhonolemtfyp) |
| 22:06.50 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-qbynkhonolemtfyp) |
| 22:06.50 | *** mode/#asterisk-dev [+o rmudgett] by ChanServ |
| 22:07.20 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-oiefeblcmghjqkrq) |
| 22:07.20 | *** mode/#asterisk-dev [+o rmudgett] by ChanServ |
| 23:23.34 | snuff-work | i hope to provide a alembic patch in the coming week for an older issue on tracker |