We recently conducted a webinar announcing the v12 release and highlighting some of the features included in that release. For those of you that were not able to attend, you can view the recording here: http://pex.me/whatsin12 (sign up required). As a follow up, here are the questions that were asked during the session: http://pex.me/28LMASF.
Q: As your support for WebRTC becomes more prevalent across browsers, such as Microsoft Edge, are you seeing more usage with the web app when compared to traditional video conferencing systems?
A: We are absolutely seeing an increasing interest within the customer community around WebRTC and the new opportunities that it can open. In fact, many customers are starting to adopt outward-facing means of connectivity, embracing customers connecting to internal resources over a WebRTC connection. For example, we are working with a number of banking and medical customers that are using custom built web front ends to handle incoming customer/client/patients joining an interoperable video conferencing call. One such use case was demonstrated at the recent InfoComm 2016 trade show with a demo video (demo recording).
Q: What streaming solution did you use for the v12 launch webinar?
A: The v12 launch webinar was brought to you by TalkPoint, a PGi company. TalkPoint, a proud Pexip customer, offers a number of webcasting services. Give them a look: http://www.talkpoint.com.
Q: Regarding embedded PIN codes, the “**” delimiter is not allowed by the consumer Skype client. Is there a way to change the “**” delimiter so that this method will be “friendly” to consumer Skype?
A: You can also use the “#” parameter for those systems who will not accept the “**” delimiter. More information can be found directly via our docs site (direct link: https://docs.pexip.com/admin/pins_hosts_guests.htm#bypass). If you have any suggestions or comments on how we can improve this function, please do not hesitate to reach out to your Pexip representatives so we can understand the need a bit better.
Q: Regarding conference lock. Would you consider introducing an icon in the video display (similar to the “streaming” icon) when the conference is locked?
A: Absolutely. We are planning on increasing the amount of information presented to all end users when they join a VMR, including the lock/unlock status. Stay tuned as you will see a number of user enhancement improvements coming.
Q: Is it possible to make 1080p selection more granular so that we can choose which conferences support it and which don’t?
A: We didn’t want to make 1080p a per VMR setting as it has a greater impact to overall platform behavior, specifically around content. In other words, if we disable 1080p for a conference, we cannot leverage the high resolution capabilities for the content stream. Instead, however, you can reduce the amount of bandwidth allocated to that VMR to 1700 Kbps or below to remove 1080p from our preferential transmit video resolution.
Q: Can we include additional announcements around conference lock status?
A: Absolutely. User experience and empowerment is a large area of focus for us as we continue down our development and product investment. We want to enable the end user to be more aware of what is going on inside their VMR with actionable information such that they can adjust their behavior as necessary. It certainly stands to reason that announcing conference lock status will play a role in this mechanism.
Q: Audio output device selection – is it supported already? Not sure browsers that support it.
A: Selection of the audio output device within the Pexip Infinity web and installable client is supported today with an upgrade to v12 (of note, the Infinity Connect installable client will also require an update to the next public release of the Pexip Infinity Connect installable client). This selection is only supported for Chrome web browsers today, but support will be expanded as other browsers provide the API hooks necessary to identify and modify the selected audio output devices.
Q: Are there any plans to expand the call bandwidth capabilities above and beyond the current 128 kbps to 4096 kbps support?
A: One quick clarification: Pexip can support call bandwidths as low as 16 kbps. Although such connections will be audio only, connectivity does work without an issue. To answer the specific question that is asked, though, we have not considered expansion of our top end bandwidth requirement to date. Although increasing the top level bandwidth is a possibility, we would want to better understand the requirement and problem that is trying to be solved through this request. We would therefore ask you to consult your Pexip representative to have a deeper conversation so we can understand things a bit better.
Q: Why do you have to reboot the Pexip solution when enabling SIP UDP?
A: Once major protocols are changed, such as enabling SIP UDP, Pexip requires a reboot of all Conferencing Nodes to initialize the services properly. When these services are disabled, we turn them off completely as to further secure and prevent interference with other services.
Q: Are there any plans to develop more automation around the initial configuration?
A: This is certainly possible, but any development here would need to be repeatable and apply across a wide range of deployments. We would certainly like to hear more information about this feature requests, though. Please consult your Pexip representative for a further discussion.