Home Energy Control - On / Off AP via IP Phone

I have done this little trick at home and reason is to save energy and doesn't want to have my wireless network always on at home.  With this little trick, now I am managed to on / off my IOS AP with a single click.  :)

Demo Video (English)

Demo Video (Cantonese)

WebEx Social 3.0

Trying to setup WebEx Social 3.0 in my lab, and find it not as straight forward as I thought.  Some points to share:

1. First of all, there are 11 roles of WebEx Social VM and a minimum 12 VMs are required.  Make sure you have enough resource.

http://www.cisco.com/en/US/docs/collaboration/ecp/admin/3_0/guide/ecpsetup.html

2.  Make sure you install the Director FIRST.  Then RDBMS SECOND.  Make sure the App Server (the web server actually) install and add to the Director LAST.  This is very very important.  I forced to redo my work the first time I install because I didn't install the App Server last.

3.  According to the guide in the above link, the default admin user for WebEx Social Web Login is

Username:  test@cisco.com
Password:  test

But this is WRONG!

The correct one should be,

Username:  test@your_company.com
Password:  test

Don't substitute "your_company.com" with your company name, this is the exact text you need to input.

4.  For Search Store you need at least 2 VM, one for master and one for slave

5.  For RDBMS you can only have 1 VM, single point of failure?

Anyway still playing around, will update when I find something interesting.

Sample IPSLA VO Configuration

My environment:  15.0(1)SE3, 3560 8-port switch

IP SLA VO is a tools to simulate video traffic in a network, especially you want to test the network readiness before the video endpoints are in place.

To enable IP SLA VO:

ip sla 1

 video 10.1.91.2 27010 source-ip 10.1.93.2 source-port 20010 profile TELEPRESENCE

 duration 60

 frequency 75

ip sla schedule 1 life forever start-time now

ip sla enable reaction-alerts

ip sla responder

To make sure it is running:

Harbour-UC-SW02#sh ip sla stat 1

IPSLAs Latest Operation Statistics

IPSLA operation id: 1

Type of operation: video

Latest operation start time: 00:07:16 HKT Wed Aug 8 2012

Latest operation return code: OK

Packets:

     Sender Transmitted:  57487

     Responder Received:  57487

Latency one-way time:

     Number of Latency one-way Samples: 37020

     Source to Destination Latency one way Min/Avg/Max: 0/5/11 milliseconds

     NTP sync state: SYNC

Inter Packet Delay Variation, RFC 5481 (IPDV):

     Number of SD IPDV Samples: 37019

     Source to Destination IPDV Min/Avg/Max: 0/500/1008 milliseconds

Packet Loss Values:

     Loss Source to Destination: 0

     Out Of Sequence: 0

Number of successes: 4

Number of failures: 0

Operation time to live: Forever

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

Cisco VXC 6215 Demo (Cantonese)

Sorry again if you don't understand Cantonese!

Cisco Prime Collaboration Manager 1.2 Demo (Cantonese)

Sorry if you don't understand Cantonese!

Jabber for iPad - 18-way conference with Telepresence MCU

Did something interesting (stupid) today.  Enjoy!

URI Dialing on UC 9.0 - Directory URI

For UC 9.0, users can dial the called party via URI if they are using 8961, 9951 or 9971.  You can import a LDAP attribute from the AD server, say for example email address, as the URI for that particular DN, known as directory URI.

1.  From System > LDAP > LDAP Directory, choose the Directory URI mapping to the appropriate LDAP attribute.  In my case I will use the mail attribute as the directory URI.

2.  Configure the phone and DN as what you always did.  Then associate the User to the phone device.  Make sure the primary extension is chosen, which is the DN you want the directory URI to bind with.  This is VERY IMPORTANT.  Without that you will not find it working.

3.  Check your DN again, you should see the directory URI appears magically.

4. The Directory URI is put into an automatically generated partition called "Directory URI".  If you wanna call other DN with Directory URI configured, make sure your CSS has the partition Directory URI.

You can try to make a call now.  It only supports on hook dialing for URI dialing, so you press the new call softkey, the press the "A B C" softkey so that you can enter alphanumeric characters.

If you don't want to call the full directory URI, you want to call without the domain name, make sure you change the following in the Enterprise parameter.

One point to note, when you have the URI and name configured on the DN, even you call each other via DN number, the bubble display on phone will still shows URI instead of DN number, even in the Call List it will show URI instead of DN, so when you redial actually you are calling back via URI instead of DN.

Test your call now and good luck!

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

SSL VPN is not supported when multiple context is configured on ASA

Learnt a lesson today.  I believe this is something new, but this is something that I have experienced today which spent me a couple of hours to troubleshoot.

What I want to do is to configure a ASA 5540 (version 8.2) as the SSL VPN headend for the VPN phones.  After I write erase the unit, I've found that basic commands like IP address cannot apply to its management and GE interface.  What I have done is to create a context and after I changeto that new context, I can apply those commands.

However the webvpn command is not available, and I have the required license installed.  After a google search, I've found when multiple context is enabled, webvpn is not supported.

Then I deleted the context and start all over again.  Finally I've found that the ASA 5540 with default "mode multiple" enabled.  It means that default it support multiple context and therefore configurations such as IP address cannot apply in the system context.  After I change it to "mode single" and reboot, all the commands including webvpn are accepted.