As we went through the journey of developing our new product, Netwrapper, I found it more and more important to work with good partners. Over the last couple years, I have had the pleasure of working with several partners. Today, I thought I would share a little bit about my journey through the development of our software, and one of our more relevant partners, Cisco.


Netwrapper is our new “network and service” management product, which uses what we know about how to run a collaboration network, and provides that knowledge to our customers. Netwrapper takes our intellectual property about how to run a network, and implements it in software.


Netwrapper is able to figure out what is going on in the network, in near real time, and then, based on our knowledge of what that means for voice and video, adjust the network and/or admission control policies to make collaboration services perform for an optimal customer experience.  To be specific, we are allowing smart allocation of network resources according to applications’ requirements, to ensure customer satisfaction with their voice and video calls. Speaking of video, here’s a little video where @coggerin interviewed me about Netwrapper.


It is here that I want to talk about Cisco. Netwrapper utilizes Cisco’s SDN controller software, which is called APIC-EM, and Cisco Unified Collaboration Manager, or CUCM. Those products provide a fair bit of our functionality, but more importantly, the APIs in APIC-EM provide us with what we needed to deliver our software.


We worked with some really great people at Cisco. Phil Casini, director, product management, is in the picture below. He has become a friend of mine during our journey. And, we have met several other people along the way, all of whom it was a pleasure to meet. If you become active in the Cisco developer community, I’m sure you will meet a bunch of people as well.





  In writing this story, I thought it would be nice to help other developers, who are trying to accomplish a similar journey. It is the first few steps that are hard. That is where Cisco DevNet can help. If your project involves a network, then you should look at Cisco’s APIs. We did. And, it turned out to be a good choice.


Mainly our customers already had Cisco networking. So, using their technology for our projects was a natural evolution. But, even if you did not have all Cisco in the network, they have networking APIs that are easy to use and very strong. I would recommend looking at what they have in software-defined networking to go along with their voice and video solutions.


For example, if you want to know about APIC-EM, you can go to DevNet and you will find learning labs, sandboxes, and even a community where you can get help. This is also true of the other APIs that Cisco offers.


When we started our journey, DevNet was new. Now, DevNet is more mature. The materials in their networking area are very robust and they are getting better all the time. Furthermore, if you find an area that isn’t giving you what you need, tell them. They will make it better.


The journey we have started is a very exciting one, since we are dealing with innovation and collaboration. Let’s go on, and enjoy it!