UCM User facing features when publisher is down

Starting from UCM 6.0, the User facing features (such as CFA, hunt login / logout, extension mobility, DND, etc) can be changed while the publisher is down.  However you can only make the changes from the phone, but NOT the UCM admin page or UCM user page.

Take CFA as an example.  When the publisher is down, users can update CFA on their phones, but not from the CCM user portal.  Admin can't change it from the CCMAdmin page too.  All web based UCM admin and user updates must be done on the publisher.

Although the above is the expected behaviour, in my lab I can configure CFA for my phone on the self-service portal (CCMUser page) when the publisher is down.  However I can't cancel the CFA from the web self-service portal.  Hope this is only an issue specific to my lab as it doesn't make any sense to me.  The CFA activate and cancel works perfectly on the phone though, while the pub is down.

Warning: Less than a month to order add-on UCM licenses

Check this out, all of the version before 8.6 will be end of sale its add on license options which means you are not able to order add on license after 31 Jul 2016
https://communities.cisco.com/docs/DOC-57172

UDS API - Query User info

You can query the user information with the UDS API, it is a HTTP GET request and if the LDAP search UDS proxy feature is enabled on 11.5, you can use it to query the LDAP users with this API.

This is the HTTP GET request that I've used for the below screen capture:
https://10.1.90.11/cucm-uds/users?name=aeinstein

Read-only AXL in UCM 11.5

One of the improvements in UCM 11.5 is it has a new standard user roles that restrict users to have read-only AXL access.  It provides better security and reduce chance of human errors in accessing the UCM database.

User management > User settings > Role

Field notice - old phones are not going to support on UCM 11.5

As per my previous post regarding old phone is no longer support on UCM 11.5:

http://pandaeatsbamboo.blogspot.hk/2016/06/old-phones-will-not-be-supported-in-ucm.html

There is an official field notice issued a few days ago, so make sure you plan ahead before upgrading your system if you are still using these old phones:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/fieldNotice/cucm_b_fn-deprecated-phone-models-1151.html

• Cisco IP Phone 12 SP+ and related models
• Cisco IP Phone 30 VIP and related models
• Cisco Unified IP Phone 7902
• Cisco Unified IP Phone 7905
• Cisco Unified IP Phone 7910
• Cisco Unified IP Phone 7910SW
• Cisco Unified IP Phone 7912
• Cisco Unified Wireless IP Phone 7920
• Cisco Unified IP Conference Station 7935

UCM 10.0 - Video on Hold

Video on hold is a new feature available in UCM 10.0, working together with MediaSense.  In my lab I have my UCM 10.0 and MediaSense 10.0 integrated, and in this blog post I will not go through how we integrate them as it is a quite straightforward.  I will focus on how to get the Video on Hold to work.

1.  On UCM, check out the new "Video On Hold Server" option under "Media Resources"

2.  Add a new VoH server.  The Default Video Content Identifier is the video SIP URI configured on MediaSense.  You can make a call to, say in my case, ciscovideo@10.1.90.61 and view the video streaming.  The configuration on the MediaSense side will be done later.  Unlike audio MoH which you can choose the audio music source, in UCM 10.0 I can't find a place that you can play different video files by different endpoints, which means all the phones need to play the same video file for their VoH.  If anyone find it is not true, feel free to let me know.

3.  Create a Media resource group to contain this VoH, and add this MRG to your MRGL.  Try to move this VoH above your MoH MRG in your MRGL.

4.  On the MediaSense side, you need to upload the move to the MediaSense server.  You need to make sure your video file is H.264 with audio track, and what I have done is I will convert my video source file first before upload to the MediaSense server.  This is the convertor I used on my Mac.  I used the iPhone 4 profile to do the conversion.

5.  Go to MediaSense > Media File Management, upload your file to the MediaSense server.  The file resolution will be converted to either 640x480 or 640x360.

6.  Then the final step is the most important.  In the Incoming Call Configuration, add an try reference to your video file.  This is the URI that is exposed to outside world so that the UCM can use it as the video on hold source.  It is the name you use in your UCM Video on Hold server "Default Video Content Identifier" field.

Done!  To see how it works you can checkout my youtube demo video:

https://www.youtube.com/watch?v=Tl8OZclN0fM

Cisco Remote Expert Smart Solution Demonstration

Just managed to see Cisco Remote Expert Smart Solution Demonstration, and I have created a demo video on how it works.

Cantonese:

English: