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.

Prime Collaboration Manager 1.2 - Device Discovery Tips & Tricks

- Make sure the phones (e.g. 9971) that are registered to UCM with web access enabled

- To discover devices on UCM, make sure a JTAPI application user is created.  This user needs to associate to all devices that wants to monitor

- For EX60, you cannot use empty password for http, otherwise it cannot be discovered

- In order to get the mediatrace to work, correct WSMA configuration is needed on routers and switches, here is the sample:

username panda priv 15 password panda

ip http authentication local

ip http secure-server

ip sla responder

mediatrace responder

mediatrace initiator source-interface GigabitEthernet0/0

wsma agent exec profile WSMA-LISTENER-HTTPS

wsma agent config profile WSMA-LISTENER-HTTPS

!

wsma profile listener WSMA-LISTENER-HTTPS

 transport https

Enable Root Access for EX60 / 90

To enable EX60 / 90 linux kernel with root access, you can first access the unit using the admin user right from a SSH client:

[root@panda ~]# ssh -l admin 192.168.10.1
Welcome to
TANDBERG Codec Release TC5.0.1.275220
SW Release Date: 2011-12-19

OK

systemtool rootsettings get

off

OK

systemtool rootsettings on

OK

Then you can access the unit with root access:

[root@panda ~]# ssh -l root 192.168.10.1
[tandberg:~] $

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!

Changing EX60 Background

My environment:  EX60, TC4.2

To change the EX60 background, access the EX60 admin web page - http://1.2.3.4

Default username admin and no password.  Upload the wallpaper, make sure the file format is png and the maximum size is 1920x1200.  If you upload the file resolution larger than 1920x1200, you will see a black screen on EX60 instead of your preferred wallpaper.

After uploading your wallpaper at the admin page, go to Advanced Configuration > Video > Wallpaper, change it to custom.  If you don't see the change, switch it to "None" then switch it back to custom.