Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion VUC: Friday August 13th Part 2 - Chris Veazy of Blink Mind On Video Calling
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Michael Graves  
View profile  
 More options Aug 8 2010, 7:40 pm
From: "Michael Graves" <mgra...@mstvp.com>
Date: Sun, 08 Aug 2010 18:40:08 -0500
Local: Sun, Aug 8 2010 7:40 pm
Subject: Re: VUC: Friday August 13th Part 2 - Chris Veazy of Blink Mind On Video Calling
In the interest of being correct:

It's Chris Veazey, VP Engineering of Blink Mind

Although two others from Blink Mind will be on the call:

Joe Baird, CEO
Nathan Stratton, CTO

On Sat, 07 Aug 2010 17:20:05 -0500, Michael Graves wrote:
>This coming Friday, August 13th will be yet another Voip Users
>Conference double-header. Starting at our usual 12 Noon EDT we have an
>overview of the Freetalk Connect SMB PBX featuring Skype integration.

>Then immediately following, at 1pm EDT, we have Chris Veazy, CTO of
>Blink Mind, to discuss the current state of the industry with regard to
>multi-media phones and SIP-based video calling.

>Blink Mind has agreed to provide a video conference bridge (MCU) as
>part of their appearance. Further, as Blink Mind are a Polycom partner,
>Polycom has graciously provided a pair of Polycom VVX-1500 Business
>Media Phones on loan. One VVX is at Randy’s location in California, and
>the other in my home office.

>As we aim to explore the capabilities of the VVX-1500 and similar desk
>phones the video portion of the Blink Mind call with be limited to CIF
>(352 x 240) resolution using H.264 compression.

>The Blink Mind bridge will allow compatible connections from a variety
>of clients. If you have access to a Polycom VVX-1500 or Grandstream GXV
>series phone you will be able to join the video bridge. Also, many
>larger video conference systems will drop down to CIF resolution, so
>they too can join the bridge.

>If you don’t have access to such hardware you may be able to use a
>compatible soft phone. Rudimentary testing with the Mirial soft phone
>last Friday proved successful. Mirial is available for Windows and OSX.
>Mirial is a commercial product, but a 30 day trail download is
>available.

>Since we have a relatively low-resolution video stream this time we’ll
>be issuing two kinds of connect details for the Blink Mind bridge.
>There will be two SIP URIs for access to the Blink Mind bridge.

>Some will be able to join in a fashion that allows them to participate
>in the video stream. Others will join the bridge using a
>non-participatory SIP URI that gives them a view of the video stream
>but does not add their video to the MCU feed. In this manner we will
>avoid having a 16+ way split where everyone looks like a tiny animated
>smudge on-screen.

>If you have a suitable hardware based means of joining the video
>conference please let me know. While I hate to be arbitrary, there are
>a limited number of participatory seats available and preference will
>be given to those who have suitable hardware.

>The details of the non-participatory connection and the web stream will
>be announced to the VUC mailing list early in the week before the call.
>We’ll also announce a SIP URI for anyone who needs to test that their
>end-point is capable of joining the Blink Mind video bridge.

>Of course, we will join the ZipDX wideband audio bridge to the Blink
>Mind video bridge. A recording of the video stream will also be
>available after the fact, along with the regular podcast.

>If you don’t have a webcam or suitable soft phone you can still view
>the video stream. Blink Mind will be providing a Flash-based streaming
>feed of the call. Since the stream is post-processed it’s a few second
>delayed from the bridge, but it includes the audio and video. This is a
>“view only” feed so you would not be able to participate in the call if
>this is your only means of connection.

>If you are joined to the web stream and the ZipDX bridge we’d asked you
>to be very careful. The audio will be out of sync between these two
>bridges and it could become very confused for everyone if you allow the
>delayed audio into the ZipDX conference.

>Of course, we will join the ZipDX wideband audio bridge to the Blink
>Mind video bridge. A recording of the video stream will also be
>available after the fact, along with the regular podcast

>Watch the VUC mailing list over the coming few days. As more details
>get locked down things will be announced there.
>--
>Michael Graves
>mgraves<at>mstvp.com
>http://www.mgraves.org
>o713-861-4005
>c713-201-1262
>sip:mgra...@mstvp.onsip.com
>skype mjgraves
>Twitter mjgraves

>--
>------------------------------------------------------------------------
>http://vuc.me  - Fridays 12 Noon ET : http://vuc.me/next

>SIP g722: 200...@login.zipdx.com
>PSTN: ZipDX +1 567 252 2286
>SIP URI: 7463#22622#...@proxy.ideasip.com
>Skype:vuc.me
>IRC freenode.net #vuc or web: http://vuc.me/irc

>Twitter: follow 'voipusers' and 'vucmailinglist' for the RSS feed of this list

>Thanks to:  Digium, Junction Networks, e4Strategies IdeaSIP.com ZipDX.com and to all the participants

>Unsubscribe email: VOIP-Users-Conference-unsubscribe@googlegroups.com

>Amazon is not effectively dealing with EC2 attackers.

--
Michael Graves
mgraves<at>mstvp.com
http://www.mgraves.org
o713-861-4005
c713-201-1262
sip:mgra...@mstvp.onsip.com
skype mjgraves
Twitter mjgraves

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.