and now for a change of pace

It has been a while friends, hasn't it?
Much has changed since I last wrote - I have taken a Senior Unified Communications Engineer position in San Francisco at a little company that is responsible for the great sound and video in yoru music, movies and television. They also branched out into conference phones a while back and announced a video system add on at Enterprise Connect 2018.

The last two months have been filled with a major deployment here at work while also trying to figure out how to exist in two places. You see, since my family and I have been established in the Tacoma area and with a daughter in high school, I don't want to move everyone down to the most expensive area of the left coast just yet. So I am splitting my time about 80% in the bay and then home for the rest. It is not easy, but it is becoming more familiar.

So about the work.....
   We are a major partner with BlueJeans so I jumped into the deep end of the pool right away to move all of our conference phones straight onto a new BlueJeans software and connect all of our Cisco VCS-based video infrastructure to BlueJeans and their Relay services that enable One Button To Join on almost any standards-based-endpoint.
   The Cisco infrastructure and endpoints are in need of some TLC as well so I've started learning and exploring their configurations. It's fun to do this part because sometimes there are creative things you discover but more often I learn so much by wondering why someone did something. Manual phone books in TMS for example - I will never understand how that is a good idea!
   The cowboy in me wants to fix all the things right away but I am measuring myself because My philosophy has been throughout this blog to document all the things and leave things so the next person can pick up where you left off.

Leaving things....
    With a long story made short, I did not leave everything as I wanted at my former place of work. There simply was not time and as the sole person knowing a technology, as much as I tried to share info I was never sure if that information was received.
    I think IT Organizations should place greater emphasis on some repository of information. It doesn't have to be pretty, but that helps. One place where all passwords are stored and one place where people should keep notes about the things they do. This isn't tickets or change control... let it be free-form open notepads if that works, but start somewhere.
    At my new place, we use combinations of Sharepoint for communication outside our group, Confluence and Box (and Box Notes) for internal things and even some SmartSheets. Then a common but hard to manage online password storage tool. These seem to work but I think part of that is a constant push to keep things off your computer and to share info. Frankly, the less I keep on my computer the better but that same practice makes it easier to share data with those that need it.


I will try to expand on these more and talk about my experience with BlueJeans (short take: it is nice) in the coming days. Now that I have my own little room I should have more time to myself, but I'm also going to start on a Cisco CyberOps course next month.

Reflecting on the year both personally and professionally

As the year comes to a close we frequently reflect back on what we have done. This is my first year of blogging so it's been the BEST ever!

A winter journey to Miami to connect with our headquarters made last winter more bearable. Then a little surgery followed up with a week of training in Dallas. It had been a long time since I had spent any time in Texas; it was more pleasant than I expected. So a few months later I followed up with additional training in Houston. In-between all of that my employer opened up a new building in Seattle that I had key involvements with. Oh, and the paychecks started coming from someone else (unfortunately) even though the job didn't really change.

As the year progressed I began an effort to be more active in social media as a technical professional whereas previously I was just a professional joker. When the 140 characters of Twitter no longer sufficed I expanded here. I attended many Microsoft Skype user groups and training, plus (as mentioned) even more Cisco Collaboration training, conferences and Cisco Champion program shenanigans.

I decided that working within the realms of my production corporate environment was not experimental enough, so a quick jaunt into the world of my own personal Microsoft Office 365 environment then later into Google's G Suite let me see what other environments could be like. This allowed chances to connect collaboration and telepresence products in new way and to fiddle with ones I have not otherwise been exposed to.

My family and I have adventured to Spokane Washington, where according to the hotel receptionist the most fun thing to do is drive to Montana! There was a day trip to Portland, Oregon but far more exciting was our 2017 Solar Eclipse impromptu excursion to Springfield (home of the Simpsons)! The typical 6 hour return drive only took us 14 hours! Camping out in a motorhome along the Canadian border got wedged in there too. More recently though, we experienced our first Oktoberfest in the mountain town of Leavenworth; where lederhosen were made for snapping and the hotel rates were astronomical. We might go back this weekend to see them light up the town.

I took up a new hobby, so considering it would be motorcycling it was only appropriate to do this come October. A solid 3 weeks of great weather and a fancy new 2017 Honda Rebel 500 has provided distraction as the season has turned colder. Or did it amplify my attention to the bitter wetness preventing me from riding? One shall see....

Thank you for sticking with me this year. I plan to make the next year more exciting and of course to share more!

Meetings sucked but they don't have to anymore!

Today I attended a seminar about the modern meeting. Thank you to Logitech who sponsored the seminar, and also to Microsoft and Pexip who presented, and finally to the guest speaker, Dave Michels, who gave an excellent talk which i will borrow from and expand upon below. These are my words and ideas, but Dave reinforced them and made me want to write a little about them here.

Let's reflect on a simple truth - meetings suck.

They are an anachronism from a time of TPS reports and heavily regimented hierarchical structures incompatible with the modern American organization.

Do you come out of a weekly 60 minute status/team meeting and feel 120 minutes older?
     I know I do...

Meetings must die.
     Long live the meeting!

Just to get started, here are my recommendations for meetings:

• Never host or goto a meeting without a clear agenda or purpose
• Include the agenda in the meeting invitation and relevant documents with the meeting (or even better - links to them)
• Never schedule a meeting for something that can be handled in email or IM
• Remember that status reports and project updates should be a part of a project management system and not a meeting
• Schedule meetings for WAY less than an hour - think 15, 30 but never more than 45 minutes
• Ask yourself, "do we NEED this meeting/time?" - remember this is probably time that everyone can be more productive doing their jobs
• Ending early isn't "giving you back your time," it's just a good idea
• If you don't need to be there, then you shouldn't have the meeting
• Meeting time isn't social or complaint time so a leader should direct the conversation so the agenda/purpose of the meeting can be completed efficiently and quickly (wrap business up before the social sessions)

These simple things are a first step in making meetings better.  Notice that they also discourage meetings. I intend to preach this idea far and wide because "meetings" are evolving; the act of consciously devoting cycles to stopping work and talking about your work has been componentized and redistributed in function by a number of different tools. Decades of thought have gone into this but the changes have come very quickly and are remain is a huge state of flux as the competitive markets see who wins.

What is changing these meetings? 

In the IT world a dozen or so years of Project Management, ITIL, and many other methodologies have standardized business practices. When we all work the same way, or at least have an understanding of how we should work towards a goal, we don't need to meet as often to figure out how we will wing our way through the next week. Standardization helps!    With this, we have many tools to track projects, assign tasks, and fiddle with all kinda of levers that traditionally we had meetings for. Just look at email - it killed the memo and has been leveraged to avoid meetings for forty years now! Many other areas have seen similar standardization and tools come into regular usage and we can always use them to reduce wasted meeting time.

Video and voice conferencing has become pervasive in the workplace and in our everyday lives. We've tied these into our phone systems and added messaging and made them all work from everywhere. This rapidly changing technology is nearly commoditized such that everyone everywhere can communicate as if they were in an old-fashioned meeting but in a short ad-hoc impromptu way. This can avoid the interruptive nature of a scheduled meeting yet still allow the face to face productive benefits than single model communications cannot.

Think about communications in the different models we might use: written < verbal < documents < visual. Each model provides more information and therefore more context than the previous but also requires more attention. Retention also increases with each as well.

The coming revolution might lie in what Dave referred to as "Work Stream Apps." I like that name as it appropriately describes what Slack, Cisco Spark, Microsoft Teams and similar can do. Think  about those models I just described; each was completely separate not long ago. Talking to someone on a phone required a very separate set of infrastructure than sending them a document but how often did you have to do both at the same time? A work stream app allows you to multitask your communication (or meeting) such that textual messages exist in the same space as the documents they reference and those involved can start a voice call about the topic instantly without leaving the same app, or even add in video participants. 

When we consider Work Stream Applications, the traditional meeting does not need to exist. We have distilled it down into a concentrate that fits better into the way we work. When a team or functional group is working on something from diversa locations and times, they can keep each other up to date without ever having interrupted their work. This isn't even an EOD handover - it's an active ongoing conversation (ok, a never ending meeting). When there is a situation that the keyboard/finger combo turns to head/desk, you can push a button to start using your words OR gesticulate a little. 

As I said, these ideas are in flux right now as the pioneers see the big guns crowding the market with their different take. Everything will change in the next few years. It is possible that "work stream apps" become too monolithic and are rejected by users. It is hard to tell for certain, but having seen how componentized these things are I am confident in saying that if you are in Collaboration, Telecommunications, Unified Communications or Messaging and you are not paying attention then you are behind the ball.

Meetings? Are ya with me?

The power of Social Media and Collaboration

I was asked last week about "social media" and work and I have been thinking about it a lot since then.

Twitter, blogging, chat groups and community message boards are definitely a very powerful tool, even more so in some of the more specialized fields like collaboration, voice, telepresence and UC. I am active in attending what user groups I can, but the online social communities really give me the feeling that I am not alone in this technology.

Some of the first user groups I ever attended were the Seattle chapter of the Avaya Users Group - it's one of the largest in the country so I was lucky to experience it. There is the natural chance to commiserate with people who handle the same stuff everyday, and the opportunity to learn form their experiences. But organizing these groups is difficult and takes a different type of leadership.

I make sure to attend the Skype Users Groups here - they are usually hosted by Microsoft and run by members and sponsored by companies and vendors with a keen interest in informing and engaging with their customers. I always learn good things - a few weeks ago we had a dive into Microsoft Teams (I came away impressed).

Social Media - that is Twitter, blogs, online communities, ongoing chats and the like - really fills that gap. It keeps me from feeling like I am the only one in the world working on this stuff. I get ideas from other, keep up to date with news, but more importantly I can put out my thoughts so they organize more easily. I'm not obsessive about my social activities and I probably overshare. If I occasionally sound like an idiot then hopefully someone calls me on it.  But really it has helped me grow and so I love it.

Please share your opinions and experiences! Has being social helped you? Where do you keep social?

Did I forget about the lab??

Golly no! I just haven't written much lately what with life and all and things work related. But my free Office365 licenses are running up soon so I better migrate to a less Microsoft world.

First and Last thoughts on O365

Look, Microsoft is the defacto standard for many reasons and there is little to fault with this stuff. Microsoft certainly did have it's 70's Detroit era products (Vista and Millennium for example), but brought it back strongly with XP and the associated Office suite. Their back office and server products took off about then and continued to accelerate. 

Take all rough to manage server voodoo, plop it up into the cloud then give it an attractive price - you've got something magic that should be hard for any small or medium business to resist. Seriously, At $20/month per head you get something whole IT orgs normally maintain. 

OK, I am not going to get any money trying to sell this so I'll move onto what i know more. and that's Skype4B and the collaboration tools provided. The hardest part about my trial and Skype is not in the configuration. It wasn't in the testing. No, everything went so incredibly easy! 

Without going into the not-gory detail review, after signing up, I had to insert a string into my DNS records for nosaturn.com to prove it's my domain and then follow the instructions to update the SRV records for Skype federation. I also had to setup some email redirection but again, everything was simple and I was up and running in a couple hours at most. Read Starting a business (or setting up an IT Department)  where I cover it more but that was about the size of it.

Back to the hardest part - why shouldn't everyone use Skype4B then? If you don't laugh after reading that then just do it and be very happy with great and easy to manage complete authentication, email, messaging, internal webpage, file sharing, and so much more IT organization that Microsoft is selling for a pretty amazing price. For a few extra bucks they will even let you call regular old phone numbers and accept incoming phone calls.

Office365 and Skype for Business are a bad choice

With that extreme statement I plant the flag down and boldly declare something that is actually pretty true. You see for every reason this O365 business is wonderful, the actual use might have different needs or objectives in mind. While O365 is amazingly flexible, it simply isn't everything everyone always needs. Every IT org and the software they use varies a little and so do their needs whether it is legacy choices or whatever. 

I could dive deep on the Skype4B is cheating with SIP bandwagon or i could leave it at it takes work for Skype4B to talk to things that are not Skype4B. There is good about that but having a background in voice and networking makes me see Skype4B as an interesting product but not a real telecommunications system. 

While VoIP and WebRTC are very different from their analog and TDM forbearers, you can get down in them and see their evolution. Skype4B grew out of a media streaming toy tossed into Windows 95 back in the days of dial up modems. Use a tidy little codec to slice up your noises and another to pixelate your good looks then sling across the information articles and boom! NetMeeting! It diverged some to and fro within Microsoft picking up new features and names along the way, but also changing the core bit that made it work (those little codecs). What we have ended up with is something that outwardly works and acts like a phone and a video conference application but doesn't use any of the fundamental "systems" that make those work for every other system sold. So you end up adding more and more bits and bling to make it work.......

/rant

What are your alternatives?

If you are small and need to stay in the cloud because you can't handle even the smallest data center your choices are quite abundant. Vonage, ShoreTel, and so many others offer out of the box solutions or you can roll your own quite easily in your pillowy AWS space with a little Asterisk punctuation*     (*must love Linux).    Ward Mundy's blog NerdVittles  has even better info for the roll your own crowd. 

Eventually an organization has to grow up and look at something grown ups choose from big industry players like Avaya and Cisco, right? Rght?      NO!     You be a tiny fish in the big pond of standards=based telecommunications and collaboration tools! 

Spark this fire, get things burning!

Cisco offers a cloud based communications and collaboration package that is flexible in sizing and powerful in it's reach. The basic package lets you make SIP standards-based calls and have persistent chat communications with anyone in the world for free. (for companies of one). Their option levels and pricing are reasonable for larger companies and that's when you get the more important administrator tools. When you fully option a user out, they will be able to host meetings in Spark or even in WebEx, can join from a PC or phone or tablet or regular phone as a voice call or get a desk phone that works directly on it or from any of Cisco's modern TelePresence endpoints or from any other standards-based endpoint and even from Skype. That's like 9 ways to connect without counting variants of each (Windows vs MacOS vs a web browser on Linux). 

Again, I shouldn't try to be selling these things. But I will be fair and remind you I am a Cisco Champion for Collaboration so I am a little biased to Cisco products. But I like Spark and Ive been using it for months now

Its late Brian.... wrap this up.

I opened this window and started typing about how I was moving my perfectly functioning IT department from Skype4B to Cisco Spark. 1000 words later and I haven't moved a thing. Let's see how this goes because I finally got my Spark trial pack :)

Whatcha doing tomorrow?
What are your thoughts?

Expertise is an illusion; A motivational essay about how you don’t know crap.

Many years ago, when I started at Microsoft in the ramp up to support Windows Millennium, they asked us “on a scale of 1 to 10, how well do you know windows?” My answer was 7-8. I reasoned that “5” must be the average and i knew way more than that; and since Microsoft hired me to support this amazing revolutionary new Windows, i must know *way more than that*. Everyone else rated themselves as 2-3 and the instructor chastised me for giving myself such a high score. “You see,” he explained, “the developer who worked on the exit button can explain everything about that button: the down click, the up click, every API it uses and all the implications of using it. But they probably can't tell you a single thing about the button next to it.”

Expertise *is* an illusion just like any technology sufficiently advanced enough is magic. No-one can know everything out of hand, but they can be pretty good at many things. More importantly they can learn and socialize. I’ve frequently told people whom I’ve helped so quickly that “i’m just a couple pages further in the manual than they are.”

How you attack issues and problems matter. Consistent strategies and knowing when it is the right time to stop the self research and call in the big dogs is important. (the big dogs being escalation in your org, mentors, coworkers, your vendors, manufacturers support or sacrificing goats). I know I’ve spent hours and hours exploring and trying to teach myself new things simply because there was a small issue. All that time wasn’t completely wasted, but small issues usually have simple solutions so those hours could have been avoided by asking around or calling support.     Of course i can tell you that learning the things I did paid off in other ways and sometimes I have called in support only for the answer to be worthless or so slow coming that I should have just worked it on my own.

So what is the best if expertise isn’t?

Fundamentals; solid understanding of core concepts and technology behind them. 
In collaboration I see these:

• Fundamentals of networks - what the OSI is and Isn’t, how to packet capture and recognize parts of it
• Fundamentals of communications protocols: SIP messaging (and to some extent h323), the common codecs involved (like 264, 265, g711 etc)
• Explain what modular architecture is - that everywhere different components have to work together but those components are often changeable. Be able to understand and map these components
• How audio video and all those physical layer components work - audio feedback, hdcp on hdmi, what is avc vs svc
• Security practises - (this should be core to every IT job) - good security practises (service accounts and unique passwords, social engineering, certificates and etc

If you have these fundamentals then you have a core that can be worked with… but what about the intangibles:

• Research - how well do you google and how well can you find documentation?
• Retention - can you recall things you researched later even if it didn't help or did you just forget it because it wasn't important (why get deep in research if you don't retain it)
• Communication - nobody ever tells you what the problem is; they just tell you the symptoms they experienced. Of that “It's broken” you also have to be able to talk to “non-technical” people, talk to other teams and talk to higher pay grades. Can you identify who is important (an admin is usually the most important contact you have)
• Documentation - look, this is the ugly part of the job and i’ve blogged about it already read here
• Knowing when to quit - will you call for help because you can't know everything? When?

We can build things in labs and classes a dozen times. 
We can deploy and migrate a hundred systems. 
None of that makes you an expert, does it? 
                  It just shows you've been doing your job.

But it’s ok to be an expert.

Ok, so I’ve used eight hundred words debunking the idea of an expert and I should probably rebuild it. 
If sufficiently advanced technology is magic, then someone who knows more is reasonably an expert. Or a wizard. At least from your perspective, for the question at hand and in the time needed. And the same is true for everyone coming to you. 

YOU CAN BE THE EXPERT THEY NEED. 

So be the expert they deserve! Help them solve the problem, learn a little so you both can move on better for the experience. They might be a new hire in a grunt position, the CEO, or someone outside; they came to you and you represent something so you might as well be an “expert” for them. 
Then later on you get to be just pretty good at something again ;)

Coming back from vacation and Cisco's Collaboration Solutions Analyzer

I spent the last week on vacation in Birch Bay, Washington. It's a little town just 5 miles south of the US/Canada border. We had very little to no cell phone service and no internet so this was a great vacation. The sunsets were fabulous!

I wanted to read up on Expressways and all sorts of other things but I skipped all of that hub-bub and just enjoyed the slow pace of doing nothing. I avoided tech except to play SimCity Build-It in offline mode :)   All of that to say that the fam did not want to kill me as I was previously worried about.

So what happens at work when you are the only one minding the shop and you are gone for a week? Thankfully not too much. So today being my first day back at work I had a few emails to parse but moved through them quickly. Now I'm looking for things to work on.

Collaboration Solutions Analyzer - the greatest thing ever?

Has anyone ever seen this? Collaboration Solutions Analyzer (Cisco how to use) is something I found before I left and took a cursory look at today. The doc I liked explains it pretty well, but of course I'm going to add my bits here.

Take a diagnostics log from your your Expressway, VCS-C, Conductor or even most endpoints and this puppy will parse out all the goodies that you probably need to know. The keen folks at Cisco TAC built this and must have had it in their secret weapon toolbox

I decided to make a few calls, gathers a couple of logs and see what it tells me. The first thing that popped up from a log captured on my VCS-c is this: POTENTIAL PROBLEMS!

Right there, the CSA tool tells me there might be some problem I didn't even know about. This is very cool. By following the link right there I was able to see what it was and in this case completely did not apply, but I like knowing that CSA can identify something I might not otherwise be looking for.

There is so much more to like in the CSA that I'm going to have to use it more and include it in the troubleshooting processes we use.
I will probably even write about it more later.

It didn't kill me, but my family might. (part 3 in a series)

So with the CMR's all backed up as Conductor Conferencing Aliases, I feel like things are "stabilized" for now and I'm preparing for vacation.

However,  the nature of my ADD means that sometimes it is hard to think of anything else than what excites me. Lately that's been all the things at work and that I'm working on. So a week up camping with my wife and daughter (plus her friend) may possibly lead to them killing me.

I guess you cannot escape death.

In order to clear my conscience and (maybe) wrap up this trilogy, I would like to explain a tiny bit more about that I've learned about what a "CMR" is. In part 1 I explained it as magic tied back to some SQL thing - pretty much magic begetting magic, am I right?

It really isn't quite that mystical. When you create a CMR - something you can only do in TMS - it makes an API call to the Conductor to build a conference that is then stored in the Conductor but you cannot modify it. If a CMR is in the Conductor and has the same video number or video address as a Conductor Conference Alias, the CMR will take priority. This way you can have a CCA that mirrors the CMR but they can coexist peacefully. If the CMR gets wiped from the Conductor because it's marked for deletion and you hit that Regenerate CMRs button you will be totally safe. the CCA is backing you up.

Until TMS creates a CMR for someone new that uses the same video number or address.

These moments of clarity were provided in the "Cisco-TMSPE-with_VCS-Deployment-Guide" on page 57 and 58. I also learned about how a CMR differs from a CCA and most significantly in guest access. I have never played with a host/guest meeting room in the Cisco environment so it's fun to exercise this. In short: with a CMR you can have the PIN determine the participant's role in a conference. User one PIN and you are a guest, or use the other PIN and you are the host. With a CCA, you must have a separate alias for the guest to call.

Where do we go from here?

I'm going on vacation. HA!

Not much of this really matters to many because ya'll are probably on to CUCM which totally changes what a CMR is. There is no Conductor. TMS is relegated to a purely scheduling function. Who knows, it might not even have a place in the future where Spark/WebEx converge to take over.

But I feel better putting this down and maybe you found this bit interesting. The Cisco documentation is deep. I've ready too many PDF's in the last month and I really should be working on my lab again. But for now i'm going to sit back, light a marshmallow on fire, and try not to talk about tech too much.

If it doesn't kill me, it makes me stronger.

Yesterday I wrote about how a bunch of Collaboration Meeting Rooms decided to self-immolate. Read "This thing is going to kill me." for the backstory.

Since I wrote about the problem I need to update my progress. I am diving much more into how TMS and TMSPE work and connect to Conductor to build a CMR, but in the meantime I need a work around for those who lost their CMR.

Here is a short summary of the temporary workaround. Don't' forget that

Steps to proceed:

1. Identify the bridges that were deleted 
2. Compile a list of TMS-based CMRs and CCAs
3. Merge and reconcile this list, then prioritize the ~50 deleted CMRs
4. Add new CCA based on the deleted CMR 
5. Inform users that their bridge has been restored and how it is different
6. Update the SMR Template in TMS so that if a new CMR is created it would be in a range that does not conflict with any of the CCAs or existing CMRs

The new CCAs will be built as such:

• Name and Conference Name = the CMR name
• Incoming Alias = ((bridge\.%EmailName%|%VideoNumber%)@vc\.%domain%\.com|(bridge\.\.%EmailName%|%VideoNumber%)@%domain%\.com)
• Priority = using the video number from the CMR (this will make them easy to identify later)
• Conference Template = HD Meeting
• Role Type = Participant
• Allow Conference To Be Created = Yes

Differences from a TMS-managed CMR and a Conductor Conference Alias:
• Users will not be able to use the TMS portal to edit them
• CMRs are linked to an Active Directory account so they are deleted when an employee leaves
• If a number (or URI) exists in both TMS and Conductor, the CMR will be connected (this is unrelated to Priority anywhere, it seems to be a default function of the system)

Once this is complete, I will research a little more to see if there is any other possibility to move the CCAs back. During this time we can resume using TMS to create and manage CMRs. If I could not move the CCAs back, then I might as well move the remaining CMRs over to Conductor just in case someone hits the “Regenerate CMRs” button.

Definitions:

TMS = TelePresence Management Suite

CMR = Collaboration Meeting Room (aka video bridge or jabber bridge)

CCA = Conductor Conference Alias

This is short because I have to go do this :)

This thing is going to kill me.

Today was a long day.

Our environment for Cisco TelePresence has a Telepresence Management Server with Provisioning Extension (TMSPE) and  a Conductor to manage the TelePresence Servers (Bridges) and multiple separate Active Directory Domains. TMS polls for accounts that should be allowed to use TelePresence resources and users can build a Collaboration Meeting Room (CMR (video bridge)) from there. We had 2004 CMR built through TMS.

Yeah. Had.

As best I can gather, a user profile is built by TMSPE. When certian parameters of their synched AD profile change TMSPE changes (?) the profile and if there is a CMR connected with that profile it is considered "out of sync".    Don't reconcile these out of sync CMR's because it deletes them and you won't sleep for a while because of that.

If a CMR is out of sync and you regenerate it they (at least in my case) get marked for deletion. We lost 50. And those 50 were not the ones you want to lose. They are gone however and I mourn their loss. I. Trying to bring them back the remaining 150 are now out of sync.

When you have a Conductor, you can build conference aliases manually. There is an API that TMSPE uses to build CMR's on the Conductor and the CMR is pretty much a conference aliases but it is held separate and is not in that list of conference aliases. There's a tool to search for the CMRs, but that's about it.

There is a magic goo that binds TMSPE and Conductor for those CMR's and they get held in a SQL database (tmspe I think was the name). I could restore that and fix everything. But that would make for a much shorter story and require that I have a backup.

Now I'm left with figuring out how to fix things. I am so super lucky that I exported the CMR's before regenerating everything. I know who had a CMR, but there is no way to use TMS to generate a replace ment CMR that has the same video number (which is what everyone uses instead of their video address).

I could manually build new aliases in Conductor and build a matching template to give them a pin.

I could tell everyone to build their CMR's again too. But with the remote possibility of an infrastructure overhaul in a few months I am reticent to cause that jumble only to have a do-over.

Should I leave you with something witty and positive?

Blogging, Tweeting, Linked Inning, Sparking and IFTTTing

Confession; I have never blogged before. 

Since joining Twitter 10 years ago I have tweeted 16.2k times. Twitter has always been more my style because brevity befits my balderdash (ooh i like that). Extending my posts may not be as much a problem as learning the practical mechanics of starting and maintaining something like this.

So this is how I'm proceeding:

1. Bought the NOSaturn.com domain via Domains.Google.com 
2. Tried to connect my new domain to a new Blogger blog, but had to figure out first how to delete some blog I made a dozen years ago about nothing (I only posted twice) (that doesn't really count as blogging does it?)
3.  OK, really setting up the Blogger blog and choose the URL http://blog.NOSaturn.com because I might someday want a real front page
4. Set Blogger to redirect http://NOSaturn.com to the blog because I don't have that real landing page 
5. Much Much playing and experimenting with Blogger and layouts and formats and discovering what holes I have in the configurations

That was a whole lot of fun and I see some neat features about the domain tools offered. The SRV tools could allow me to connect potential future lab to real world communication abilities. 😎  But I have to admit a real annoyance that Blogger does not allow HTTPS: redirects with custom domains. regular HTTP needs to die.

Now that I have a blog with a a couple of entries, I ought to connect it to some of the socials I use. I'm not going to connect to Facebook since that's entirely a personal social thing whereas I mix personal and professional in Twitter. You'll find me on LinkedIn too because I hear that I should be there.

My professional presence on social media is encouraged as I am a 2017 Cisco Champion for Collaboration. I'll talk about that another time.

Ah, yes; back to connecting this blog to social media.... IFTTT, or IF This Then That, is a super useful and pretty easy way to make a "trigger" in one thing do "something". In this case I setup an applet that would post to Twitter and LinkedIn whenever I made a blog entry. The post would include the hashtag #Collaboration because that is what hashtags are for. This was real neat right up to the point that I got way too smart and built an applet that would take any of my tweets with #Collab and post that as a blog entry. 

    Don't do that.

Thankfully I stopped all that nonsense because a blog post triggered a tweet which then triggered a blog post of the tweet and on and on. This is like aiming a video camera right at a screen showing the camera's feed. 

I still wanted some of that same functionality but figuring that Blogger should easily be able to tweet or LinkedIn for me I started exploring again. Blogger's Help forums pointed me to some tool that has shut down, then on to DLVR.it which seems to suite me right now. We will see...

Speaking of applets, the new hotness is of course BOTS! There really isn't much difference between applets, apps, bots or all these things except who is using whatever term at any one time. (right?) One of the collaboration tools I'm enjoying lately is Cisco's Spark. It's a mashup of messaging, chat, voice, video, email, file sharing and other general goodness but I will cover that later. Spark has bots and integrations that really enhance and extend it's functionality. I setup a connection in Spark to Twitter so I could Tweet directly from Spark. That worked. Of course if I included the #Collab hashtag the Twitter post then rolled on up into a blog post. NEAT. I cleaned it up even more with another IFTTT applet that would take something I say in a designated Spark room would post directly to my blog. EVEN NEATER.

This is all a very long winded explanation for today's previous posts and a couple I deleted last night from the recursive posting debacle. 

(Remember that "brevity befits my balderdash"? )

This blog really is an extension of my ongoing professional development. There are so many tools and communication modes available now. I really believe understanding their strengths and weaknesses is central to collaboration. 

The Lab (part 1)

I learn alot by exploring, breaking and of course by fixing things. This is completely impractical in a production environment so if you don't have a test or lab it's going to be slower learning for you.

I want to build a Cisco Collaboration focused lab here at home. Searching for "Cisco Collaboration Lab" hasn't been so productive for me. Everyone seems to build routing/switching labs but not collaboration. It isn't surprising because the R/S tract is core to everything but does collab need the same equipment.

The equipment I have already is:
- Dell Poweredge 2950 rack server
- Cisco 2960 24 port PoE switch
- Dell 6420 laptop
- RaspberryPi model b
- Netgear r6700 router and a cable modem

My initial thoughts were that the server would be great for VMware hosts (a Windows server for active directory and domain controller). I powered it on once when I got it and it was loud as hell so I spent a bunch of brain cycles scheming ways to run it in my garage. Then I look at eBay and find these things run for about $50-100.
           It might be smarter to recycle this thing instead.

A Cisco 2950 switch will work great; I won't need so many ports, but PoE will be great for phones, touch panels or even some WiFi access points if I want to play with that too.

The Dell laptop is running Windows 10 so I'll toss VMware workstation on it to start with. No big deal there.

A Raspberry Pi is wayore useful than just about everything else in the modern world. Just kidding! But for $35 it is an amazing learning tool. This RPi has been a platform for me to learn Asterix, Debian and Nagios. Monitoring a collaboration environment is going to be my next thing once my lab is running.

Ok, this is going to be a home lab so I can't really interrupt the normal production functions in at Home Corp. The CEO wife would not stand for major service (Netflix) interruptions!

So that's what I have to start with. I'll need more. What experiences have you had?

Let's get things started!

I have decided that some of my thoughts may exceed the 140 characters that Twitter allows so I find myself here wanting to collect thoughts, journal my activities and generally talk about the technology that I love and have built my career around.

Hello there!

Those two words are just one of the many ways we greet each other. But how often do you hear them in the workplace just as a meeting gets started? Probably not much. I find people start a meeting or a conversation with frustration - they do not want to be there, do not have a clear agenda, and might be frustrated actually getting the meeting started. 

There are so many things that make working together hard, and I find it to be my job to make working together easier. I have many years experience working on networks, with phone systems, video conferencing, instant messaging, chat, file sharing, email and oh so many other technologies, but I never loose sight of what it is like to actually do these things.

In the coming months I will share my quest to pass certifications, build a home lab, learn and expand my skills and share what I have learned.
Let's blend technology, psychology, philosophy and a little bit of reckless experimentation.
Are you in?