Hey all, So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers. This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications. Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem? Best, Colin
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
Interesting. So far it has worked on all clients except WebRTC. It seems strange to me that putting a hostname in an SDP wouldn't be allowed, but it's far from the weirdest thing I've seen in some these specs. I'm fine with having IPs in the SDP for pretty much all cases, except for the iPhone where it is supposedly necessary to not use IP literals. So I guess I have two questions then: 1. Is there a way in FS to explicitly set an advertised IP address through a channel var? Actually, in this case I would just define a few options in vars.xml and then use expansion. Something like, advertised_rtp_ip=${local_ipv4} or advertised_rtp_ip=${local_ipv6} 2. How are people deciding whether to advertise IPv4/IPv6 if FS *isn't* handling registrations. Say, for example, Kamailio handles registrations. FS only knows if it'll talk to Kamailio via 4 or 6, but not what Kamailio will use to talk to the clients. Is there a best practice here for supporting dual stack? Best, Colin On Wed, Aug 3, 2016 at 1:13 AM Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
You should NOT be setting advertised_rtp_ip, We use a V4 profile or aV6 profile, you can't mix and match, doing so would probably not work at all. On Wed, Aug 3, 2016 at 8:53 AM, Colin Morelli <colin.morelli@gmail.com> wrote:
Interesting. So far it has worked on all clients except WebRTC. It seems strange to me that putting a hostname in an SDP wouldn't be allowed, but it's far from the weirdest thing I've seen in some these specs.
I'm fine with having IPs in the SDP for pretty much all cases, except for the iPhone where it is supposedly necessary to not use IP literals. So I guess I have two questions then:
1. Is there a way in FS to explicitly set an advertised IP address through a channel var? Actually, in this case I would just define a few options in vars.xml and then use expansion. Something like, advertised_rtp_ip=${local_ipv4} or advertised_rtp_ip=${local_ipv6}
2. How are people deciding whether to advertise IPv4/IPv6 if FS *isn't* handling registrations. Say, for example, Kamailio handles registrations. FS only knows if it'll talk to Kamailio via 4 or 6, but not what Kamailio will use to talk to the clients. Is there a best practice here for supporting dual stack?
Best, Colin
On Wed, Aug 3, 2016 at 1:13 AM Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
-- *Brian West* brian@freeswitch.org *Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com https://www.gofundme.com/freeswitch_ubuntu Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
So in this case I would just have to generate two invites (one for each profile) both to Kamailio, and then filter contacts in Kamailio (v6 invite goes to v6 registrations, v4 to v4, etc)? In any case, my use for setting something like advertised_rtp_ip (does anything like this exist?) would be to actually explicitly set a hostname (rather than an IP) for certain endpoints that are going to have compatibility issues with IP literals (such as iOS devices). I used a poor example there, as I wasn't intending to cross the v4/v6 bridge with it. Best, Colin On Wed, Aug 3, 2016 at 10:42 AM Brian West <brian@freeswitch.org> wrote:
You should NOT be setting advertised_rtp_ip, We use a V4 profile or aV6 profile, you can't mix and match, doing so would probably not work at all.
On Wed, Aug 3, 2016 at 8:53 AM, Colin Morelli <colin.morelli@gmail.com> wrote:
Interesting. So far it has worked on all clients except WebRTC. It seems strange to me that putting a hostname in an SDP wouldn't be allowed, but it's far from the weirdest thing I've seen in some these specs.
I'm fine with having IPs in the SDP for pretty much all cases, except for the iPhone where it is supposedly necessary to not use IP literals. So I guess I have two questions then:
1. Is there a way in FS to explicitly set an advertised IP address through a channel var? Actually, in this case I would just define a few options in vars.xml and then use expansion. Something like, advertised_rtp_ip=${local_ipv4} or advertised_rtp_ip=${local_ipv6}
2. How are people deciding whether to advertise IPv4/IPv6 if FS *isn't* handling registrations. Say, for example, Kamailio handles registrations. FS only knows if it'll talk to Kamailio via 4 or 6, but not what Kamailio will use to talk to the clients. Is there a best practice here for supporting dual stack?
Best, Colin
On Wed, Aug 3, 2016 at 1:13 AM Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com https://www.gofundme.com/freeswitch_ubuntu
Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch>
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
RFC4566 5. SDP Specification "A session description can contain domain names in the "o=", "u=", "e=", "c=", and "a=" lines." It's a detail I'd expect some implementations may have skipped over though so I'd expect it could lead to interop issues. Also you need to assume it will resolve to the IP you expect, not necessarily the case if it resolves to multiple IPs for example or it has changed and the TTL has not expired yet. And it might not play well with SIP ALGs. I'd avoid it. That's not evidence based, purely gut instinct. On 3 August 2016 at 06:10, Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
Steven, Thanks for the clarification - that's really helpful (it also means I can go file browser bugs which I'll do) Agreed it'll cause interop issues (for example the ones seen in WebRTC). It's too bad, because it could be helpful in a few different scenarios. That said, for now I'm just looking to slowly start using it on devices that will have problems with IP addresses. Does anyone know if there's a way, via a channel var, to set the advertised address in the SDP? Best, Colin On Thu, Aug 4, 2016 at 7:03 AM Steven Ayre <steveayre@gmail.com> wrote:
RFC4566 5. SDP Specification "A session description can contain domain names in the "o=", "u=", "e=", "c=", and "a=" lines."
It's a detail I'd expect some implementations may have skipped over though so I'd expect it could lead to interop issues. Also you need to assume it will resolve to the IP you expect, not necessarily the case if it resolves to multiple IPs for example or it has changed and the TTL has not expired yet. And it might not play well with SIP ALGs. I'd avoid it. That's not evidence based, purely gut instinct.
On 3 August 2016 at 06:10, Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
Should point out that although it might be allowed in SDP's RFC that doesn't necessarily mean it isn't restricted by other WebRTC specifications. You'll probably want to look into those as well. On 4 August 2016 at 12:17, Colin Morelli <colin.morelli@gmail.com> wrote:
Steven,
Thanks for the clarification - that's really helpful (it also means I can go file browser bugs which I'll do)
Agreed it'll cause interop issues (for example the ones seen in WebRTC). It's too bad, because it could be helpful in a few different scenarios.
That said, for now I'm just looking to slowly start using it on devices that will have problems with IP addresses. Does anyone know if there's a way, via a channel var, to set the advertised address in the SDP?
Best, Colin
On Thu, Aug 4, 2016 at 7:03 AM Steven Ayre <steveayre@gmail.com> wrote:
RFC4566 5. SDP Specification "A session description can contain domain names in the "o=", "u=", "e=", "c=", and "a=" lines."
It's a detail I'd expect some implementations may have skipped over though so I'd expect it could lead to interop issues. Also you need to assume it will resolve to the IP you expect, not necessarily the case if it resolves to multiple IPs for example or it has changed and the TTL has not expired yet. And it might not play well with SIP ALGs. I'd avoid it. That's not evidence based, purely gut instinct.
On 3 August 2016 at 06:10, Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
Hey Steven, I did check that as well. So far as I can tell, most of the shared portions of the SDP come from RFC 4566. The ICE additions in RFC 5245 also claim to allow FQDNs for candidate addresses. My assumption is that it's just not commonly used. But it seems much easier to support hostnames everywhere as more and more dual stack endpoints. Any thoughts on a per-channel advertised address? Best, Colin On Thu, Aug 4, 2016 at 8:14 AM Steven Ayre <steveayre@gmail.com> wrote:
Should point out that although it might be allowed in SDP's RFC that doesn't necessarily mean it isn't restricted by other WebRTC specifications. You'll probably want to look into those as well.
On 4 August 2016 at 12:17, Colin Morelli <colin.morelli@gmail.com> wrote:
Steven,
Thanks for the clarification - that's really helpful (it also means I can go file browser bugs which I'll do)
Agreed it'll cause interop issues (for example the ones seen in WebRTC). It's too bad, because it could be helpful in a few different scenarios.
That said, for now I'm just looking to slowly start using it on devices that will have problems with IP addresses. Does anyone know if there's a way, via a channel var, to set the advertised address in the SDP?
Best, Colin
On Thu, Aug 4, 2016 at 7:03 AM Steven Ayre <steveayre@gmail.com> wrote:
RFC4566 5. SDP Specification "A session description can contain domain names in the "o=", "u=", "e=", "c=", and "a=" lines."
It's a detail I'd expect some implementations may have skipped over though so I'd expect it could lead to interop issues. Also you need to assume it will resolve to the IP you expect, not necessarily the case if it resolves to multiple IPs for example or it has changed and the TTL has not expired yet. And it might not play well with SIP ALGs. I'd avoid it. That's not evidence based, purely gut instinct.
On 3 August 2016 at 06:10, Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
more and more dual stack endpoint
Bear in mind that the SDP contains 'IN IP4' or 'IN IP6' to pick the IP version so you aren't going to be a in position where they can pick at will from A and AAAA records for your FQDN. On 4 August 2016 at 13:25, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey Steven,
I did check that as well. So far as I can tell, most of the shared portions of the SDP come from RFC 4566. The ICE additions in RFC 5245 also claim to allow FQDNs for candidate addresses.
My assumption is that it's just not commonly used. But it seems much easier to support hostnames everywhere as more and more dual stack endpoints.
Any thoughts on a per-channel advertised address?
Best, Colin
On Thu, Aug 4, 2016 at 8:14 AM Steven Ayre <steveayre@gmail.com> wrote:
Should point out that although it might be allowed in SDP's RFC that doesn't necessarily mean it isn't restricted by other WebRTC specifications. You'll probably want to look into those as well.
On 4 August 2016 at 12:17, Colin Morelli <colin.morelli@gmail.com> wrote:
Steven,
Thanks for the clarification - that's really helpful (it also means I can go file browser bugs which I'll do)
Agreed it'll cause interop issues (for example the ones seen in WebRTC). It's too bad, because it could be helpful in a few different scenarios.
That said, for now I'm just looking to slowly start using it on devices that will have problems with IP addresses. Does anyone know if there's a way, via a channel var, to set the advertised address in the SDP?
Best, Colin
On Thu, Aug 4, 2016 at 7:03 AM Steven Ayre <steveayre@gmail.com> wrote:
RFC4566 5. SDP Specification "A session description can contain domain names in the "o=", "u=", "e=", "c=", and "a=" lines."
It's a detail I'd expect some implementations may have skipped over though so I'd expect it could lead to interop issues. Also you need to assume it will resolve to the IP you expect, not necessarily the case if it resolves to multiple IPs for example or it has changed and the TTL has not expired yet. And it might not play well with SIP ALGs. I'd avoid it. That's not evidence based, purely gut instinct.
On 3 August 2016 at 06:10, Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
____________________________________________________________ _____________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
____________________________________________________________ _____________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
____________________________________________________________ _____________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
True, but newer RFCs (6947 for example) are adding extensions such as "a=altc" which should allow you to advertise both IPv4 and IPv6 support in an SDP. Having simply a hostname could make that easier. But I see your point, if the two have to be advertised independently you might as well use IPs instead of hostnames - there's no clear advantage to be gained one way or the other. Best, Colin On Thu, Aug 4, 2016 at 11:29 AM Steven Ayre <steveayre@gmail.com> wrote:
more and more dual stack endpoint
Bear in mind that the SDP contains 'IN IP4' or 'IN IP6' to pick the IP version so you aren't going to be a in position where they can pick at will from A and AAAA records for your FQDN.
On 4 August 2016 at 13:25, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey Steven,
I did check that as well. So far as I can tell, most of the shared portions of the SDP come from RFC 4566. The ICE additions in RFC 5245 also claim to allow FQDNs for candidate addresses.
My assumption is that it's just not commonly used. But it seems much easier to support hostnames everywhere as more and more dual stack endpoints.
Any thoughts on a per-channel advertised address?
Best, Colin
On Thu, Aug 4, 2016 at 8:14 AM Steven Ayre <steveayre@gmail.com> wrote:
Should point out that although it might be allowed in SDP's RFC that doesn't necessarily mean it isn't restricted by other WebRTC specifications. You'll probably want to look into those as well.
On 4 August 2016 at 12:17, Colin Morelli <colin.morelli@gmail.com> wrote:
Steven,
Thanks for the clarification - that's really helpful (it also means I can go file browser bugs which I'll do)
Agreed it'll cause interop issues (for example the ones seen in WebRTC). It's too bad, because it could be helpful in a few different scenarios.
That said, for now I'm just looking to slowly start using it on devices that will have problems with IP addresses. Does anyone know if there's a way, via a channel var, to set the advertised address in the SDP?
Best, Colin
On Thu, Aug 4, 2016 at 7:03 AM Steven Ayre <steveayre@gmail.com> wrote:
RFC4566 5. SDP Specification "A session description can contain domain names in the "o=", "u=", "e=", "c=", and "a=" lines."
It's a detail I'd expect some implementations may have skipped over though so I'd expect it could lead to interop issues. Also you need to assume it will resolve to the IP you expect, not necessarily the case if it resolves to multiple IPs for example or it has changed and the TTL has not expired yet. And it might not play well with SIP ALGs. I'd avoid it. That's not evidence based, purely gut instinct.
On 3 August 2016 at 06:10, Michael Jerris <mike@jerris.com> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
> On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com> wrote: > > Hey all, > > So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers. > > This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications. > > Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
On Thursday, August 4, 2016, Colin Morelli <colin.morelli@gmail.com> wrote:
Hey Steven,
I did check that as well. So far as I can tell, most of the shared portions of the SDP come from RFC 4566. The ICE additions in RFC 5245 also claim to allow FQDNs for candidate addresses.
My assumption is that it's just not commonly used. But it seems much easier to support hostnames everywhere as more and more dual stack endpoints.
Any thoughts on a per-channel advertised address?
Best, Colin
Not currently possible, a feature request would be necessary.
On Thu, Aug 4, 2016 at 8:14 AM Steven Ayre <steveayre@gmail.com <javascript:_e(%7B%7D,'cvml','steveayre@gmail.com');>> wrote:
Should point out that although it might be allowed in SDP's RFC that doesn't necessarily mean it isn't restricted by other WebRTC specifications. You'll probably want to look into those as well.
On 4 August 2016 at 12:17, Colin Morelli <colin.morelli@gmail.com <javascript:_e(%7B%7D,'cvml','colin.morelli@gmail.com');>> wrote:
Steven,
Thanks for the clarification - that's really helpful (it also means I can go file browser bugs which I'll do)
Agreed it'll cause interop issues (for example the ones seen in WebRTC). It's too bad, because it could be helpful in a few different scenarios.
That said, for now I'm just looking to slowly start using it on devices that will have problems with IP addresses. Does anyone know if there's a way, via a channel var, to set the advertised address in the SDP?
Best, Colin
On Thu, Aug 4, 2016 at 7:03 AM Steven Ayre <steveayre@gmail.com <javascript:_e(%7B%7D,'cvml','steveayre@gmail.com');>> wrote:
RFC4566 5. SDP Specification "A session description can contain domain names in the "o=", "u=", "e=", "c=", and "a=" lines."
It's a detail I'd expect some implementations may have skipped over though so I'd expect it could lead to interop issues. Also you need to assume it will resolve to the IP you expect, not necessarily the case if it resolves to multiple IPs for example or it has changed and the TTL has not expired yet. And it might not play well with SIP ALGs. I'd avoid it. That's not evidence based, purely gut instinct.
On 3 August 2016 at 06:10, Michael Jerris <mike@jerris.com <javascript:_e(%7B%7D,'cvml','mike@jerris.com');>> wrote:
I have not once in my life seen someone use a hostname instead of an ip in an sdp, and I do not believe it is legal.
On Aug 2, 2016, at 1:00 PM, Colin Morelli <colin.morelli@gmail.com <javascript:_e(%7B%7D,'cvml','colin.morelli@gmail.com');>> wrote:
Hey all,
So it looks like WebRTC has issues dealing with hostnames in the SDP instead of IP addresses. Particularly, when including a hostname in the SDP there's no audio in either direction. This is the case in both the latest Firefox + Chrome browsers.
This is particularly problematic for applications that are WebRTC + mobile, now that Apple is enforcing applications to support IPv6-only networks. Using hostnames in the record-route and SDP addresses meets the requirement since the OS will synthesize an IPv6 address when a DNS query is performed, but according to the documentation they strongly urge applications to avoid using address literals in their applications.
Has anyone had success with methods to switch between advertising a hostname vs IP address in the SDP? Or other methods for solving this problem?
____________________________________________________________ _____________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','FreeSWITCH-users@lists.freeswitch.org');> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/ options/freeswitch-users http://www.freeswitch.org
____________________________________________________________ _____________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','FreeSWITCH-users@lists.freeswitch.org');> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/ options/freeswitch-users http://www.freeswitch.org
____________________________________________________________ _____________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','FreeSWITCH-users@lists.freeswitch.org');> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','FreeSWITCH-users@lists.freeswitch.org');> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II ♬ @anthmfs ♬ @FreeSWITCH ♬ ☞ http://freeswitch.org/ ☞ http://cluecon.com/ ☞ http://twitter.com/FreeSWITCH ☞ irc.freenode.net #freeswitch ☞ *http://freeswitch.org/g+ <http://freeswitch.org/g+>* ClueCon Weekly Development Call ☎ sip:888@conference.freeswitch.org ☎ +19193869900 https://www.youtube.com/watch?v=9XXgW34t40s https://www.youtube.com/watch?v=NLaDpGQuZDA
participants (5)
-
Anthony Minessale
-
Brian West
-
Colin Morelli
-
Michael Jerris
-
Steven Ayre