September 2014 archive

Walk-Through: Skype 5.4 For iPhone Lets You Host Audio Conference Calls

Skype 5 4 for iosSkype released a new version 5.4 of it's iPhone app that includes an interesting ability to host "group audio calls". In a post on Skype's "Garage & Updates" blog today, Skype's Gary Wong writes that the goal of this release is "to make it easy for you to host a group audio call with just one tap." They did that... and I'll show that below in a series of images walking through the process.

A couple of caveats and thoughts from the testing:

  • As Gary Wong noted in his blog post this first release is limited to four people in a group audio call.
  • It seems from the testing described below that the "group audio call" is limited to Skype users. I couldn't find a way to add in a call to an external phone number.
  • It also seems to be limited to the iPhone and is not yet available on the iPad.
  • Image sharing isn't seamless between Skype for iPhone users and Skype desktop users.
  • The user interface was a bit troubling when switching between parts of the group call.

With that in mind, here are more details...

An Architecture Change For Audio Conferencing

What's interesting is that this capability is a change from the way that Skype has historically "hosted" audio conferences. With the existing Skype desktop clients, when you launch an audio conference call, your computer does all the mixing of the audio streams.

For this reason, if you want the best quality audio conference (or "group audio call"... I note that Skype is pointedly avoiding using the term "conference call") your smartest plan is usually to find the person with the fastest computer and fastest Internet connection. The combination of those two factors can make your audio call work the best.

Perhaps obviously, as powerful as they are, today's smartphones aren't going to have the CPU or bandwidth to do all the mixing of the audio streams and sending them back out to all participants.

So this new "group audio call" feature from Skype has to be using some audio mixing happening back in servers in Microsoft/Skype's "cloud" (also known as their "central data centers"). Your iPhone then becomes the control center for the group audio call and also sends your audio stream and receives back the mixed audio stream.

Walking Through Group Audio Calls

Naturally I had to try this out and enlisted the help of two long-time fellow testers - Jim Courtney and Phil Wolff.

Part of this new feature is that there is now a "phone" icon at the bottom of every chat window on your iPhone. A simple tap of that phone icon will initiate a group call with "everyone" in that chat. I didn't have Jim and Phil in a group chat smaller than the 4-person limit, so I started out with a regular voice call via Skype to Jim. I then tapped on the "add a person" icon in the lower right and added in Phil. As the call was connecting to Phil, here is what it looked like:

Skype 5 4 p2

After Phil accepted the call, I could tap on the "multiple person" (or "group") icon at the top and see a list of who was on the call:

Skype 5 4 p3

Tapping the "star" icon on the bottom would add this to my "Favorites" in the iPhone Skype client. Tapping the "..." button brought up a small set of options:

Skype 5 4 p4 0

Choosing to "rename group" let me give it a new name ("Testing Skype") which then appeared at the top of the window:

Skype 5 4 p4 1

Now, Jim and I were both using Skype on our iPhones while Phil was connected using Skype on his Mac. Neither Jim nor I could easily figure out how to start a text chat, but as part of the call Phil had a chat open up in his Mac Skype client. Once he typed in that, Jim and I both had a chat window on our iPhone:

Skype 5 4 p5

Jim and I could then enter in messages in our iPhone clients without any problems. I also had a Mac Skype client open and Jim had a Windows Skype client open and we could see the chat messages there, too, and could type messages in those clients - it all worked fine.

One interesting issue was the support of sharing files or photos across the clients. When Phil dropped a photo into the chat on his Mac desktop client, I was unable to see it in my iPhone:

Skype 5 4 p6

Tapping the "i" icon next to the message brought me to a page explaining that the iPhone client only used Skype's new "cloud-based" photo sharing service. Curious to explore this more, I tapped the camera icon and shared out an image I had on my iPhone. The result was visible to both Jim and I (and no, that's not me but rather a contractor working on our house):

Skype 5 4 p7

However, now Phil was not able to see the photo in his Mac desktop client (nor was I) but was instead directed to go to a URL in his browser to see the image:

Skype

Phil said on our call that in order to view that photo he had to login to his Skype account. After our 10 minutes or so of testing this, Phil dropped off and navigating back to the "call" screen I could see that he was no longer on the call:

Skype 5 4 p8

At this point I could have tapped on the green phone icon to bring Phil back in, but we were done.

When this was over, I did now have my new "Testing Skype" chat with Jim and Phil in it - and at the bottom was a phone icon. Jim tapped the phone icon on his iPhone and reconnected all three of us into a call.

Final Thoughts

If I used Skype on my iPhone a great amount, I could see how this feature would be quite useful for initiating group audio calls. I could create a "group" (effectively a "chat") with a group of people and add that to my "favorites". Then I could simply go into my "favorites" on my iPhone client and initiate the call. Obviously the initial four-person restriction limits the usefulness to only small teams/groups right now, but presumably Microsoft/Skype will raise that limit over time as this feature rolls out more.

The audio quality was fine. I didn't see a way to find out the technical details, but the audio sounded high quality, i.e. it was using Silk or another wideband codec to give rich audio.

I did find the navigation to be a bit cumbersome and not intuitive. Switching between the chat window, the "call status" window (showing the participants) and the regular call window was not as easy as I would have liked. It took some poking and tapping to figure out how to move around.

We did wonder why Skype was rolling out this particular feature right now. Phil wondered if there might be competitive pressures with Apple's announcements coming on Tuesday - for example, will we see group audio calls for Apple's Facetime? We'll have to tune in to see!

It also may purely be Skype seeking to reclaim some of the leadership on features for OTT voice apps given that so many other players have entered the market. Whatever the case... the feature is now out there and available for iPhone users.

If you'd like to try this out yourself, you should be able to download an update from the AppStore.

If you have already tried it, what do you think?


An audio commentary on this topic is also available on SoundCloud:


If you found this post interesting or useful, please consider either:


TDYR 172 Testing Skype’s New Audio Conferencing On The iPhone

TDYR 172 Testing Skype's New Audio Conferencing On The iPhone by Dan York

WordPress 4.0 Provides A MUCH Better Editing Experience!

Wp 40 focus on your contentWordPress 4.0 is out today and I am VERY pleased with one small but incredibly important tweak - when you are editing a long blog post or article in the browser window the formatting menu bar no longer scrolls off the screen! This may seem like a trivial point... but every day when I am in the Deploy360 site editing some of our longer documents, I spend a good bit of time scrolling the browser window back up to be able to use the formatting menu. This will be a huge time saver for me!

The other features in WordPress 4.0 are also cool. Being able to more easily work with the media library will be nice. Having the embeds automagically appear in the post without needing to preview will also help save time and let you know how the post will look. Improving the plugin directory is nice, too, although right now I'm pretty set with the plugins I need on my various sites.

It's the improved editing experience that I'm really looking forward to using more. I've already upgraded several of my sites and I like the experience so far. Tomorrow I'll upgrade Deploy360 which is where I expect to reap the biggest benefit.

What about you? Have you upgraded yet? Do you like it? (Keeping in mind that there is nothing special about WordPress "4.0" other than that it is the release between "3.9" and "4.1"... i.e. it's not a "big" release but rather just another "regular" WordPress release.)

Here's the WordPress 4.0 release video showing some of the new features:


If you found this post interesting or useful, please consider either:


VoiceOps – Mitigating SIP Threats With SBC Policies, Auto-Blacklisting

Voice Ops mailing listThere’s a good discussion going on right now (September 2014) in the VoiceOps mailing list about how you can mitigate SIP threats by configuring the policies and settings on your session border controller (SBC).  It started out with a detailed question from Robert Nystrom asking about how to configure an Acme Packet SBC in the most secure manner and asking about how best to configure access control lists (ACLs).  Several answers can be seen in the VoiceOps archive from folks such as Ryan Delgrosso, Mark Lindsey, Jim Gast and Patrick McNeil, offering commentary and suggestions about how best to proceed.

If you are not already subscribed, the VoiceOps mailing list is a great resource.  As stated on the subscription page:

This list is for discussions related to managing voice networks, both traditional and IP.

The VOIP Operators’ Group (VOG) charter is to facilitate the creation, maintenance, and operations of Voice over Internet Protocol (VOIP) related networks, products, and services.

Similar to the North American Network Operators’ Group (NANOG), The Voice Operators’ Group seeks to assist in the creation of a robust, stable and growing VOIP ecosystem.

While the topics are definitely not all about security, I would encourage you to join the list if you do anything with the operation of VoIP networks – or if you are just curious to learn more about such networks.

TDYR #171 – The Dark Side Of Being A Prolific Writer

There is a dark side to being a prolific writer or prolific "content creator"... and that is that if you do NOT create content, you start to get a bit twitchy... in this episode I talk about that feeling of having your head exploding with ideas...

The Live Video Streaming Nightmare: What Do You Do When YouTube Won’t Start? (And Lessons Learned)

What do you do if you go to start live video streaming of an event - and the streaming service you use won't start??? How do let people waiting to watch know? How do you fall back to another service?

Last month at the IETF 90 meeting in Toronto I experienced this nightmare of anyone doing live video streaming across the Internet. We had a presentation at noon on Thursday that we had widely publicized in social media and via email. The cameras were all set up. The producer was all ready to do the switching and encoding out to YouTube. Everything was good to go.

Then at 11:45am, I went to do my part in the process. I needed to login to the IETF YouTube account and basically click the "Start Streaming" button inside the "live event". At that point the YouTube servers would accept the encoded stream from the producer's gear and the stream would go live.

BUT... instead I got this message in a bright red bar across the top:

Ytl maintenance 500 The message read:

YouTube live is undergoing maintenance. Events cannot be created, started or stopped. Events already started will continue to stream uninterrupted.

Yes... we had no way to START the live video stream!

Over the next few minutes I kept refreshing that page but the warning stayed up there. I was getting rather nervous as the launch time approached!

Now, as it happened, we had already planned to have a second live video steam going out for the event through a different service, Livestream.com, for a different reason.

Why The IETF Uses YouTube For Live Video Streaming

To explain a bit more, we have been using Google's YouTube live video streaming for some of the larger IETF plenary sessions for five reasons:

1. The live video stream is available over both IPv4 and IPv6.

2. The stream works easily across pretty much all desktop and mobile devices.

3. Google's live streaming infrastructure seems able to scale to whatever capacity is needed.

4. The recording of the stream is immediately available after the event in the IETF's YouTube channel.

5. There is no cost for using the service beyond our local costs to produce the content (and no infrastructure that the IETF itself has to maintain).

Of these, really the most critical reason for using YouTube live streaming is the first - that it streams out over IPv6.

The IETF is the organization behind the IPv6 specification and has declared that all new IETF standards need to incorporate IPv6. Therefore in the spirit of "eating your own dog food" the IETF tries to use services that work over IPv6 whenever possible. Other live video streaming services have met the reasons 2-5 above, but not the #1 reason of working over IPv6.

We have specifically been using what Google used to call "YouTube Live" but now seems to just be calling "YouTube live events" versus Google's newer "Hangouts On Air (HOA)". These YouTube live events are events you schedule in advance and can use with advanced video encoders. An advantage is that these events provide streaming configuration info that I can provide in advance to the company running the audio and video at the event so that they can be prepared in advance. YouTube also helpfully provides a countdown timer for people visiting the event page. We haven't switched to using HOAs because they haven't yet provided the advance configuration information we want.

Anyway it has all worked well for live streaming out plenary sessions for a couple of years now.

Google Doesn't Live Stream Into Germany

However, as we discovered again that week.... Google will not stream live video into Germany! It seems Google has a legal dispute with a German intellectual property rights organization (GEMA) and Google has decided that rather than run into trouble with GEMA they will simply NOT allow live streaming into Germany.

So, alerted to this issue by some IETF remote participants in Germany who were unable to watch the live video streams of the technical plenary earlier in the week, we had arranged to also stream this Thursday session out over the Internet Society's Livestream.com account. Now, unfortunately it would not be available over IPv6 because Livestream.com still only works on legacy IPv4 networks, but Livestream.com did not have the streaming restrictions Google had and so at least people could view the stream in Germany. As a bonus, all the "subscribers" to the Internet Society's Livestream.com channel would also get notified and potentially be able to watch the stream - but the primary reason was so that people in Germany could watch the video stream.

The great thing about IETF meetings is that a massive amount of Internet connectivity is brought into the meeting hotel (because you have 1,200+ engineers who do most of their work across the Internet!) and so there are NO bandwidth problems for streaming. We could probably stream out to a dozen different live streaming services simultaneously if we set up our local software/equipment to do so.

Making The Alternate Stream The Primary Stream

The good news for us was that this "alternative" live video stream set up purely for viewers in Germany could now become the primary video stream. I rapidly updated the Google+ "event page" for this session to note the new URL for streaming and we spread the word through IETF social media channels and email lists. It wasn't 100% seamless but we were able to get people watching the live video stream.

We were also able to direct people to some of the other IETF remote meeting participation mechanisms, including audio streaming and a conferencing system called "Meetecho" that streamed the slides and lower webcam-quality video.

Throughout the hour-long event I kept checking the Live Control Room inside of YouTube to see if we could start the original stream, but we were never able to do so. A couple of times the red warning box went away, but we could not establish a connection from YouTube's streaming service to our equipment on the ground there in Toronto. Finally, as the time went on it became clear that the connection wasn't going to happen and so I just gave up trying.

The good news is that the producer was also making a local copy of the stream that we would be able to upload later to the IETF's YouTube channel.

Lessons Learned

I took away from this experience three primary lessons for all future live streaming sessions. Do note, too, that I think of these as generic lessons for all live streaming services and events. It happens that this time the failure was with Google's YouTube live events service, but the failure could have been with Livestream.com, Google's Hangouts On Air, Ustream or any of the many other live video streaming services out there.

1. Always Promote An Event Page Separate From The Streaming Service

We were able to rapidly redirect people to the new location of the live video stream in large part because we had been promoting the Google+ event page as the place to go to watch the live stream. We had promoted this on the IETF's Twitter account, Facebook page, Google+ page and also over various IETF email lists and on various other websites. All the promotion pointed people to this page.

So the good news was that all we had to do was update this page with the new info and people could switch over to watch the new stream.

We had NOT been promoting the direct YouTube link for the stream. Had we done so, we could have still updated the page through editing the description of the YouTube video and/or leaving comments - but it would not have necessarily been as easy for visitors to see.

Promoting a separate page was a deliberate choice I made based on some previous bad experiences with live streaming where I had to stop a streaming session and restart with a brand new URL. For that reason I've been promoting a separate page.

In fact, for the IETF Plenary sessions, we've been promoting a separate page under IETF control on the IETF website - http://www.ietf.org/live/ - where we can embed the live stream video and also keep the page updated. At the IETF meeting it is possible for me or someone else to easily go in and update that page. Plus it is a very simple URL that we can promote widely.

I don't honestly remember why we didn't use the www.ietf.org/live/ page to stream out this Thursday morning sponsor presentation other than that the decision to live stream the session happened the day before and for whatever reason we went with a Google+ Event page as the page to promote.

Next time we'll probably promote the www.ietf.org/live/ page.

The key point is that you have a page separate from the live streaming service where you can post updates.

2. Have An Alternate Live Stream Either Active Or Ready To Go

As I mentioned previously, in this case we happened to be set up with a second live stream out through Livestream.com purely because we wanted to test the live streaming into Germany. Had remote IETF participants in Germany not asked about this after being unable to view the earlier technical plenary, we wouldn't have had this second stream active.

Next time, we will have a second live streaming service either active or at least on standby ready to go.

At the IETF meetings, we have the luxury of having an insane amount of bandwidth and so there are not the typical connectivity constraints you find in meeting venues. The software and equipment our producer was using could go out to multiple live streaming services. There is really no reason we can't run multiple streams.

For the IETF we still have the IPv6 requirement, which unfortunately Livestream.com does not yet meet. However, it occurred to us after the session that we could have streamed to a Google+ Hangout On Air (HOA) as that would have also streamed out over IPv6 in addition to IPv4. Of course, that would mean relying on two Google services and so you run the risk of having the technical issues affecting one live streaming service also affecting the other - plus there was the whole "streaming into Germany" thing.

We'll definitely keep investigating what other live streaming services may work over IPv6. There are a good number of live video streaming services out there and the number seems to be growing. The company producing the video stream for us also had their own streaming server that we might be able to use as a backup, too. And, yes, we can also have an IPv4-only streaming service available if everything else falls through.

Now, in non-IETF environments where I do have to worry about bandwidth constraints, I will at least have a plan for how I can rapidly spin up a second stream if the first one fails. That's really the key point. What is Plan B and how fast can you make it happen?

3. Have Access To Relevant Social Media Accounts And Other Methods Of Letting People Know

This is perhaps a subset of Lesson #1, but another critical part of our success in redirecting people to the second live stream was that we had access to the relevant social media accounts and other means of spreading the word. I had access to the IETF Google+ page and could make the updates there. Someone else was able to send out a tweet with the new link to the live stream. An email was sent out to all attendees and to other relevant email lists letting them know about the link.

The key point is that when we updated the event page with the new information, we could let people know!

In The End...

... the session was streamed live across the Internet. It was recorded and made available for later viewing. And... we learned a few lessons to make sure our live streaming infrastructure is more resilient next time so that this potential "nightmare" becomes nothing more than just a minor bump and redirection.

What about you? If you do live video streaming what steps have you taken to ensure you can keep streaming in cases like this?


I also recorded an audio commentary about this situation:


If you found this post interesting or useful, please consider either:


Watch the 2014 Internet Governance Forum (#IGF2014) Live All This Week from Istanbul (Featured Blog)

The Ninth Annual Internet Governance Forum (IGF) Meeting is taking place all this week, September 2-5, 2014, in Istanbul, Turkey and live video streams are available for all the sessions... I watched the opening session live stream today from my home office in New Hampshire, USA, and the quality was excellent. There was also a live text transcription. More...

Learn IPv6 Basics in VMware #vBrownBag Webinar On Sept 3

vBrownBag logoInterested in learning more about “IPv6 for IPv4 Brains”? By way of a tweet we learned that Jeff Carrell will be the guest on VMware’s “#vBrownBag” webinar/podcast on this Wednesday, September 3, 2014, at 19:30 US Central Time (which I calculate to be 00:30 UTC on Thursday, Sept 4, if I do the math correctly).

In another tweet Jeff said that he’ll be talking about “IPv6 basics, contrasted to IPv4 (where possible) to assist in the learning curve“.   On VMware’s #vBrownBag page there is a link to register for the event.

I don’t know much about VMware’s webinar series, nor have I personally seen Jeff in action providing training, but he’s one of the most active people I’ve seen on Twitter covering IPv6 issues.  I’m not going to be able to join in to tomorrow night’s session live, but I’m looking forward to listening to the archive once it is available.

And… if you are inspired after listening to the session to do more with IPv6, please do visit our Start Here page to find IPv6-related resources tailored to your type of organization or role.  The time for IPv6 is NOW!

DNSSEC Deployment Maps Updated Today (2 Sep 2014) With Latest New GTLDs

As part of our ongoing publishing of DNSSEC deployment maps showing visually the DNSSEC status of country-code top-level domains (ccTLDs), we also publish a comma-separated value (CSV) file that contains the DNSSEC status of all the generic top-level domains (gTLDs), including all the “new gTLDs” that have been published as part of ICANN’s program.  We do not yet have any visual display of the generic TLDs, although that is something we would like to eventually include in the distribution.  For the moment they are just listed in a CSV file – and primarily what we are listing is that they have a DS record in the root zone of DNS.

The latest maps and CSV files as of today, September 2, 2014, can now be found online.  These maps and CSV files are published every Monday morning with whatever updates have been made to the database.  If you would like to receive the maps and CSV files, please subscribe to the dnssec-maps mailing list. The list is “announce-only”, i.e. it is not a discussion list, and so you will only receive the weekly map updates and very occasional administrative updates.  You can visit the list archives to see the type of messages sent to the list.

Lifehacker: Disabling IPv6 Will NOT Speed Up Your Internet Connection

Lifehacker logoIPv6 is not exactly a topic we would normally expect to see on the hugely popular Lifehacker website, but there it was on Friday in a story by Patrick Allan, “Why Disabling IPv6 Won’t Speed Up Your Internet Connection“.  In the article, Patrick references an earlier article on How-To Geek that aims to dispel the idea  that disabling IPv6 would somehow speed up your Internet access.

In both articles, the authors make the point that earlier versions of web browsers would sometimes have significant delays in connecting to web sites if IPv6 was involved.  For example, if a website had a AAAA record with an IPv6 address a browser would sometimes try and try… and try…  to connect to the site over IPv6… even if the computer itself had no IPv6 connection!

Thankfully, in 2014 almost all web browsers now use some variation of the “Happy Eyeballs” algorithm defined in RFC 6555 where they try to connect over both IPv6 and IPv4 and use whichever connection works best and so these web browser problems are now a thing of the past.

As both articles note, you may do more damage to your computer by disabling IPv6 these days, simply because we are running out of IPv4 addresses and many sites and networks are already well underway with their transitions to IPv6 (or have already completed those transitions).

We’re very pleased to see Lifehacker pointing this out… and look forward to more such articles as the IPv6 transition is happening rapidly around us!

If you would like to make the transition to IPv6, please see our Start Here page to find resources that will help you out!