Chad, good addition to documents, by chance have you also discovered how to enable mod_av, but not use H264? I ask as I observe that enabling mod_av adds the h264 codec even if it’s not listed in vars.xml. In my particular case I would like to use mod_av but select when to use h.264 by destination as opposed to it being included in every sip sdp, but I have not yet worked out how to do so - by chance have you any tips from your testing ?
Awesome. No problem.
Yep, that was it, thanks!
load mod_av? if thats not the issue, I’d need to see a debug log w/ sip trace to tell you more.
> On Jun 15, 2018, at 2:50 PM, Chad Phillips <chad@apartmentlines.com> wrote:
>
> I have a slightly older install where I’m using H264 with Verto, and it works fine. However, I’m not able to get it working on latest master.
>
> I’m guessing there’s some esoteric setting I’m missing, but can’t seem to find it. I do have the following in verto.conf.xml:
>
> <param name="outbound-codec-string" value="opus,h264"/>
> <param name=“inbound-codec-string” value="opus,h264"/>
>
> I also have mod_h26x disabled, as I remember that’s passthrough only and causes issues when loaded in this case.
>
> When I try in Chrome I see it offering H264 in the SDP, but the answer SDP contains this, and the stream is audio only:
>
> m=video 0 UDP/TLS/RTP/SAVPF 19
>
> What am I missing??