3 ms·
I like: 0) The use of a set of different phone numbers instead of different conference rooms. I don't like: 1) Why only a US number, when people are used to
by rahimnathwani 11y ago
I like:
0) The use of a set of different phone numbers instead of different conference rooms.
I don't like:
1) Why only a US number, when people are used to freeconferencecall.com, which has access numbers in many countries?
2) Why make someone visit a web site to set up a call? Isn't the user's calendar (e.g. on their mobile) the natural place for them to set up virtual meetings?
3) Why do I have to enter the PIN manually? RFC2806 defined pause and wait characters for URLs, back in the year 2000: https://www.ietf.org/rfc/rfc2806.txt https://www.ietf.org/rfc/rfc2806.txt
Also:
4) The link on the bottom-right of the page leads to https://emerge.cisco.com/ https://emerge.cisco.com/ but that server is refusing connections on port 443. I can connect with plain http.
- dylanbfox 11y agoThanks for your feedback! Right now this is product is just in a pilot phase, but we are absolutely looking into more international options in the future. To your second point, what we think about a lot is an API developers could use to build this functionality into their apps or websites. So while you're in your calendar app, or in your task management app, you could easily accomplish the same thing (quickly scheduling a call and having a number provisioned). Would love your thoughts/feedback on this. And thanks for catching that protocol mismatch!