Monthly Archives: December 2011

Enterprise Video on the iPad #2 (2 of 2)

A few weeks back I posted that I was able to get video working on the iPad2 and that video integrated with our Cisco/Tandberg environment.

I’m pleased to provide an update based on version 1.03 of the Polycom iPad2 app that fixes three issues I had with the previous version.

Fix #1 – DTMF now working – Thanks @paland for the heads up on that issue

Fix #2 – Correct resolution when calling a Telepresence Content Server (TCS).  On the previous Polycom version I could only connect @ 192×144 vs. the 480×352 that I was expecting.  I could connect at the higher resolution to any other endpoint, it was only the TCS that would result in a lower resolution connection.

Fix #3 – Unpredictable SIP registration on TCP vs. UDP – I would sometimes need to toggle between TCP and UDP due to failed registration.  On the new version I haven’t seen any failures regardless of protocol.

At first when downloading the new version, I thought Polycom was going to lock me out of the app unless I had their infrastructure.  This screenshot was why I thought this…

Fortunately it turns out that login is their attempt at autodiscovery of their CMA server.

You can put in bogus information, tap Sign In, and still get to the main screen.

Notice the Alert icon on the bottom of the screen.  Tapping on it shows you that your login to the automatically detected CMA server (that doesn’t exist in my case) failed.

 

From here the settings are nearly identical to the last version.

Tap the Gear (Settings) icon in the bottom right corner of the screen and be presented with the main settings page:

First, toggle the Polycom CMA service to OFF.

That adds the familiar H323 and SIP options.

Then toggle the 3G/4G Call Rate to 512Kbps.  This is a new setting, in the past it only knew about 3G.

Your screen should look like:

Tap to go into the H.323 Settings.  I have H.323 calling disabled on mine to more closely match how the Movi client operates (SIP only).

Once into SIP settings enter the settings as shown below.

Enjoy!!

Acquisition #2 – Complete!

Well, the Presidio acquisition of INX is now complete!

I’m now working for the second largest company I’ve ever worked for.

Time will tell but I’m looking forward to having a similarly positive impact in the new sea I find myself swimming in.

Presidio is now 1,800 employees strong and the Cisco Collaboration market on all coasts.  If I am to admit, I would acknowledge (with great anticipation) that the region I’m in has the greatest untapped potential for growth.

Presidio now has over 45 offices in the US, three of which fall in my region.

Presidio wisely acknowledges INX’s delivery framework as a key asset in the acquisition, and is looking to adopt this model across the organization.  THAT is exciting to me – taking a proven process and using it to light a match on a powder keg of human and financial capital – leading to explosive growth!

First Video call from iPad2 to Cisco environment! (1 of 2)

I’ve been wanting to get my hands on an iPad2 long enough for a while to try out a perhaps unexpected way to use it for video calls with our internal Cisco VCS/VCS-X/TMS/Tandberg Endpoints, Cisco Video Phones, Cisco Immersive TP endpoints environment.

The unexpected way?  Use the Polycom mobile app announced and released a few weeks ago.

I picked up a few iPad2’s tonight, and got some time while the wife and kids were away to hack at it for a while.

So far I’ve tested successful 2-way video calls between the iPad2 and:

  1. Cisco Movi 4.2 running on iMac 27″
  2. Cisco Movi 4.2 running on MacBook Pro
  3. Cisco Cius running firmware sipcius.9-2-1SR2-21SEC through call to MCU 4501
  4. Cisco Cius running firmware sipcius.9-2-1SR2-21SEC through call to Cisco TPS

Directly dialing between the Cius and the iPad2 results in only audio coming from the Cius to the iPad2.

I’ve also tested and expect it is working (but can’t verify the other side of the call) calls to:

  1. Cisco C40 registered to VCS-Control (whereas I’m registered to the Expressway)
  2. Cisco EX60 registered to VCS-Control

Lastly (cuz I need sleep) I tested presentation from the Movi client and it worked successfully.

A few screen shots showing what settings I used:

This is the main settings screen.  I ignored the Polycom specific settings:

Now for the SIP settings – I haven’t gotten H323 calls working just yet:

I blurred out the specific settings, however you will want to set them as the following:

  • SIP Proxy Server – set this to your external VCS Expressway address (I’m using DNS, haven’t tried IP) – exactly how you would have it setup in your Movi client
  • SIP Registrar Server – Same as above
  • Domain – your domain – for me it was simply inxi.com.  Exactly what you would use for your Movi client.
  • SIP User Name – This is the SIP address you will register with.  I’ve played with this a bit and found that as long as you can authenticate, you can tweak your SIP URI.  As such you can call me @ josh.miller.ipad@inxi.com if my client is running.  It also works to register as the same URL you use for Movi (most practical) and the Expressway will ring all of your logged in Movi endpoints.
  • Authorized Name – This is the login name, no @domain or DOMAIN was needed for me.
  • SIP Password – Password you would use to login to Movi
  • Transport Protocol – UDP – didn’t work on TCP

From what I understand there has been a Tandberg Movi app for several years that simply hasn’t seen the light of day.  Here’s to hoping I can get my hands on a real Cisco video client for the iPad and Android soon!

 

 

UPDATE:  I also tried out the ClearSea service and am rather displeased at the full-court bait and switch they employ.  They offer a service, and then e-mail you a few days later to let you know you are on a trial and you are going to be limited to a nearly useless account if you don’t cough up $40/month.  Screen shot below shows pricing.