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??
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??
Yep, that was it, thanks! I added a section to the Verto docs to clarify all the steps to get H264 working: https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html On Mon, Jun 18, 2018 at 4:21 PM Michael Jerris <mike@jerris.com> wrote:
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??
_________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
Awesome. No problem.
On Jun 19, 2018, at 11:04 AM, Chad Phillips <chad@apartmentlines.com> wrote:
Yep, that was it, thanks!
I added a section to the Verto docs to clarify all the steps to get H264 working: https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html <https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html> On Mon, Jun 18, 2018 at 4:21 PM Michael Jerris <mike@jerris.com <mailto:mike@jerris.com>> wrote: 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 <mailto: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??
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 ? Regards Magnus
On 19 Jun 2018, at 17:34, Michael Jerris <mike@jerris.com> wrote:
Awesome. No problem.
On Jun 19, 2018, at 11:04 AM, Chad Phillips <chad@apartmentlines.com> wrote:
Yep, that was it, thanks!
I added a section to the Verto docs to clarify all the steps to get H264 working: https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html
On Mon, Jun 18, 2018 at 4:21 PM Michael Jerris <mike@jerris.com> wrote: 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??
_________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
No idea how H264 plays with SIP. In Verto, codecs are tried in the order they are listed in verto.conf.xml, pretty sure it uses the first codec that the client supports. On Tue, Jun 19, 2018 at 2:06 PM Magnus <magnus.kelly@gmail.com> wrote:
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 ?
Regards Magnus
On 19 Jun 2018, at 17:34, Michael Jerris <mike@jerris.com> wrote:
Awesome. No problem.
On Jun 19, 2018, at 11:04 AM, Chad Phillips <chad@apartmentlines.com> wrote:
Yep, that was it, thanks!
I added a section to the Verto docs to clarify all the steps to get H264 working: https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html
On Mon, Jun 18, 2018 at 4:21 PM Michael Jerris <mike@jerris.com> wrote:
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??
_________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
_________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
Just configure codec preferences appropriately. We filter prefs based on whats loaded so that would be why you wouldnt see it until module is loaded.
On Jun 19, 2018, at 2:40 PM, Magnus <magnus.kelly@gmail.com> wrote:
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 ?
Regards Magnus
On 19 Jun 2018, at 17:34, Michael Jerris <mike@jerris.com <mailto:mike@jerris.com>> wrote:
Awesome. No problem.
On Jun 19, 2018, at 11:04 AM, Chad Phillips <chad@apartmentlines.com <mailto:chad@apartmentlines.com>> wrote:
Yep, that was it, thanks!
I added a section to the Verto docs to clarify all the steps to get H264 working: https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html <https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html> On Mon, Jun 18, 2018 at 4:21 PM Michael Jerris <mike@jerris.com <mailto:mike@jerris.com>> wrote: 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 <mailto: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??
Well the issue I have is I trying to remove H.264 from the codecs listed in the SDP, as although its not listed in the codec section of vars.xml at all, enabling mod_av appears to mean that by default H.264 is added in the SDP for each outbound SIP invite, resulting in calls to PSTN SIP G/W failing with unacceptable codec. Advice on how to prevent or make selective per SIP profile most welcome. Thanks Magnus On Wed, 20 Jun 2018 at 14:49, Michael Jerris <mike@jerris.com> wrote:
Just configure codec preferences appropriately. We filter prefs based on whats loaded so that would be why you wouldnt see it until module is loaded.
On Jun 19, 2018, at 2:40 PM, Magnus <magnus.kelly@gmail.com> wrote:
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 ?
Regards Magnus
On 19 Jun 2018, at 17:34, Michael Jerris <mike@jerris.com> wrote:
Awesome. No problem.
On Jun 19, 2018, at 11:04 AM, Chad Phillips <chad@apartmentlines.com> wrote:
Yep, that was it, thanks!
I added a section to the Verto docs to clarify all the steps to get H264 working: https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html
On Mon, Jun 18, 2018 at 4:21 PM Michael Jerris <mike@jerris.com> wrote:
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??
_________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
It would not be added just because the module is loaded (it would be removed potentially if its not loaded), its either coming from the other leg, or in codec preferences.
On Jun 20, 2018, at 11:38 AM, Magnus Kelly <magnus.kelly@gmail.com> wrote:
Well the issue I have is I trying to remove H.264 from the codecs listed in the SDP, as although its not listed in the codec section of vars.xml at all, enabling mod_av appears to mean that by default H.264 is added in the SDP for each outbound SIP invite, resulting in calls to PSTN SIP G/W failing with unacceptable codec. Advice on how to prevent or make selective per SIP profile most welcome. Thanks Magnus
On Wed, 20 Jun 2018 at 14:49, Michael Jerris <mike@jerris.com <mailto:mike@jerris.com>> wrote: Just configure codec preferences appropriately. We filter prefs based on whats loaded so that would be why you wouldnt see it until module is loaded.
On Jun 19, 2018, at 2:40 PM, Magnus <magnus.kelly@gmail.com <mailto:magnus.kelly@gmail.com>> wrote:
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 ?
Regards Magnus
On 19 Jun 2018, at 17:34, Michael Jerris <mike@jerris.com <mailto:mike@jerris.com>> wrote:
Awesome. No problem.
On Jun 19, 2018, at 11:04 AM, Chad Phillips <chad@apartmentlines.com <mailto:chad@apartmentlines.com>> wrote:
Yep, that was it, thanks!
I added a section to the Verto docs to clarify all the steps to get H264 working: https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html <https://evoluxbr.github.io/verto-docs/tut/adding-h264-support.html> On Mon, Jun 18, 2018 at 4:21 PM Michael Jerris <mike@jerris.com <mailto:mike@jerris.com>> wrote: 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 <mailto: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??
My ten cent’s worth .. this is my verto profiles… <profiles> <profile name="default-v4"> <param name="bind-local" value="$${local_ip_v4}:8081"/> <param name="bind-local" value="$${local_ip_v4}:8082" secure="true"/> <param name="force-register-domain" value="$${domain}"/> <param name="secure-combined" value="$${certs_dir}/wss.pem"/> <param name="secure-chain" value="$${certs_dir}/wss.pem"/> <param name="userauth" value="true"/> <!-- setting this to true will allow anyone to register even with no account so use with care --> <param name="blind-reg" value="false"/> <param name="mcast-ip" value="224.1.1.1"/> <param name="mcast-port" value="1337"/> <param name="rtp-ip" value="$${local_ip_v4}"/> <param name="ext-rtp-ip" value="************MY PUBLIC UP ADDRESS********"/> <param name="local-network" value="localnet.auto"/> <param name="outbound-codec-string" value="opus,vp8"/> <param name="inbound-codec-string" value="opus,vp8"/> <param name="apply-candidate-acl" value="localnet.auto"/> <param name="apply-candidate-acl" value="wan_v4.auto"/> <param name="apply-candidate-acl" value="rfc1918.auto"/> <param name="apply-candidate-acl" value="any_v4.auto"/> <param name="timer-name" value="soft"/> </profile> <profile name="default-v6"> <param name="bind-local" value="[$${local_ip_v6}]:8081"/> <param name="bind-local" value="[$${local_ip_v6}]:8082" secure="true"/> <param name="force-register-domain" value="$${domain}"/> <param name="secure-combined" value="$${certs_dir}/wss.pem"/> <param name="secure-chain" value="$${certs_dir}/wss.pem"/> <param name="userauth" value="true"/> <!-- setting this to true will allow anyone to register even with no account so use with care --> <param name="blind-reg" value="false"/> <param name="rtp-ip" value="$${local_ip_v6}"/> <param name="ext-rtp-ip" value="************MY PUBLIC UP ADDRESS********"/> <param name="outbound-codec-string" value="opus,vp8"/> <param name="inbound-codec-string" value="opus,vp8"/> <param name="apply-candidate-acl" value="wan_v6.auto"/> <param name="apply-candidate-acl" value="rfc1918.auto"/> <param name="apply-candidate-acl" value="any_v6.auto"/> <param name="apply-candidate-acl" value="wan_v4.auto"/> <param name="apply-candidate-acl" value="any_v4.auto"/> <param name="timer-name" value="soft"/> </profile> </profiles> From: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org> On Behalf Of Chad Phillips Sent: venerdì 15 giugno 2018 20:51 To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Subject: [Freeswitch-users] Using H264 with Verto 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??
participants (5)
-
Chad Phillips
-
Francesco Facco de Lagarda
-
Magnus
-
Magnus Kelly
-
Michael Jerris