Introducing Cisco Spark Nettools Bot

This is a new Cisco Spark bot I created to help with troubleshooting DNS and Cisco Expressway issues. Let me know what you think.

Thanks to John Howell who created this great video to help promote the bot.


Cisco Spark Node-Flint Support Space

Nick Marus and I have opened a Cisco Spark Space if you require support, share code or find issues for the Node-Flint Bot Framework for developing Cisco Spark Bots and Integrations developed by Nick. Please feel free to follow this link and join the Cisco Spark Space by entering your email on the page. I have also added the link in my gadgets space so if you need it at a later date its available.


Cisco Telepresence CapsetFilter Setting - Disabling H.239/BFCP

This is a not very well known setting going by how long it took me to find. The CapsetFilter setting available in TE and CE firmware on Cisco Telepresence endpoints can be used to change the layout of streamed content and video channels. Most modern video experiences call for separate video and content channels to allow local video layout customization and better content resolution. But what if you want content and video in the main video stream. This is negotiated usually but if you need to force this behavior CapsetFilter setting is how you do it. Disabling H.239/BFCP will force content and video into the main video stream.

Either SSH or using the web interface into the codec:

Disable H.239/BFCP using xCommand:
xConfiguration Experimental CapsetFilter: "H.239Ctrl"

Admin interface:


Parsing Inbound Cisco Spark Webhook Bot Mentions using Node-Flint

A while back I wrote a post on parsing inbound Cisco Spark webhook data using the hears method with the node-flint framework by Nick Marus. After much thought and general improvement in skill as a developer I have created a much simpler way that could be potentially used with other frameworks. This allows the parsing of slash commands and fallback to a NLP processing service.

Below is a conversations module that can be used with flint. Rather than have multiple flint.hears methods for the event I now have just one using the switch method. Switch allows me to test the contents of my request string variable using regex. A much better solution than multiple flint.hears methods that has limited control over when to stop processing. Once you hit a match using switch it stops processing and performs the function in the return statement.