Augmented Reality Proof of Concept Demo

A proof of concept demo, to show augmented reality on Cisco Telepresence EX series video endpoints.  The Atomic tool is used for the augmented reality part.

Jabber for iPad - 18-way conference with Telepresence MCU

Did something interesting (stupid) today.  Enjoy!

MCU 4510 - Initial IP Configuration

Although this is listed in the Getting Started guide, if you so happen find my post ranked earlier than Cisco guide, this is a quick procedure on how to set / modify the IP address from console.

1.  Console connection is 38400 8n1

2.  Change Port A IP address and default gateway
static A 192.168.90.2 255.255.255.0 192.168.90.254

3.  Change DNS Server
dns 192.168.90.10 192.168.90.11

Creating Rendezvous (Meetme) Conference on UCM + Cisco Telepresence MCU

My environment:  UCM 8.6.1-20000-1, Cisco Telepresence MCU 4510 4.3(1.27)

Previously in the last blog post:

http://pandaeatsbamboo.blogspot.com/2011/09/cisco-ucm-86-using-cisco-telepresence.html

We have successfully configured Cisco Telepresence MCU as ad-hoc conference resource on UCM.  The caveat is this ad-hoc video conference resource can’t be used on Tandberg endpoint such as EX60 today, because there is no conference soft key or hard key for the conference initiator to start the conference.  The alternative is meetme conference.  However you might want password protected meetme conference, you can achieve it by configuring Rendezvous meeting on Cisco Telepresence MCU.

1.  Add the Cisco Telepresence MCU as H323 gateway on UCM

 

2. Create Route List, Route Group, then Route Pattern.  Standard stuff.

3. Create Route Pattern with the destination to this H323 gateway.  In my case, my route pattern is 1357.

4. Then go to Cisco Telepresence MCU.  Add UCM IP address as H323 gateway.

5. Create Rendezvous Conference, the numeric ID is the number that you previously created on UCM route pattern, 1234 is the PIN to protect this meeting.

Test it by calling 1357.  Then you should see the screen asking for PIN.  Enter the PIN then you are now in the rendezvous meeting.

Caveats:

This is not official support.  Currently you can’t configure the MCU as media resource (UCM ad-hoc, meetme) and MCU rendezvous at the same time with the same MCU, however it works.  Make sure you are not using the UCM software MTP.  With that MTP in your MRGL or your default <none> MRGL, EX60/90 will become audio only. 

Cisco UCM 8.6 using Cisco Telepresence MCU as Ad-hoc Video Conferencing Resource

My environment:  UCM 8.6.1-20000-1, Cisco Telepresence MCU 4510 4.3(1.27)

WIth the latest UCM 8.6, Cisco Telepresence MCU (previously known as Codian) can be registered to UCM via SIP as an ad hoc video conference resource, similar to what CUVC can do before.

1.  Media Resource > Conference Bridge, choose Cisco Telepresence MCU from the dropdown box.  Fill in the Conference bridge name, IP address as well as the HTTP username and password.

2.  Secondly, add this video conference bridge into your Media Resource Group and then assign it to Media Resource Group List.  Assign it to the phone that will initiate the ad-hoc video conferencing.

3. Go to the Cisco Telepresence MCU web page, Settings > SIP, the SIP registrar domain is the IP address of your UCM, the username is the Conference Bridge name specified in UCM.  Choose “Enabled” in SIP registrar usage.  In my beta release there is a bug saying that it is unregistered on MCU web page, however in UCM it shows that the MCU is registered.  You can ignore this unregistered message as it is actually working according to my testing.

4.  Then initiate a call from the Cisco video-enabled IP phone.  You will see the multiparty video conference is established successfully.  In my testing I have a 8945, 9951 and a EX60 with TC5.0 beta that is registered to UCM natively.

Enjoy!