Skip to content
View bbird81's full-sized avatar

Block or report bbird81

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
bbird81/README.md

I'm not a developer.

Well not exactly... I'm more of an infra guy doing dev stuff.

Started more than 10 years ago at the lowest level of the IT ladder, helpdesk & support, and climbed my way up to the architect level.

Done and practiced several technologies during my operations experiences: network, virtualization, security... but when I started working with voip and video, my heart was stolen.

VoIP, video and IMs (aka Unified Communication & Collaboration) had it all:

  • you need to know networks (because how traffic is routed and how the phones interacted with switches with lldp&cdp and how trasport affects quality of real time traffic, so QoS as well, are topics of prime importance).
  • you needed to know security and firewalls (because you need to secure negotiation & real time traffic, understand very well NAT and its implications in protocols like SIP, not to mention the importance of PKIs).
  • you need to know how protocols work (h.323 SIP is an entire world per se with STUN/TURN and STIR/SHAKEN).
  • you need to know DNS and load balancing ('cause a service is useless if you don't know how to find/discover it)
  • you need to understand virtualization ('cause -you know- you don't waste a physical machine for just making audio/video calls, right...? Even though things like transcoding have dedicated HW technology, known as DSP, which suddenly has to be emulated in software... easy stuff, right?)
  • you needed to understand databases (when you deal with a lot of phone devices/phone numbers aka dial plan, being able to directly read or manipulate your data in SQL makes a difference).
  • you needed to be able to script (doing stuff in bulk really saves a lot of efforts and spares you from the misery of human fallacy, God bless the inventor of APIs).

Cisco Call Manager in particular was the epitome of this: the most powerful communication solution existing to date, able to do it all, with all sort of technology crammed in. If you think you cannot do something with the Call Manager (well, UC related obviously) it means you don't know it enough.

So, while becoming a UCC specialist, I was in fact becoming a jack of all trades of IT.

More recently, having developed almost every useful skill in UCC, I'm tinkering with DevOps stuff: some scripting, some containers, some git, some Jenkins... that's a whole lot of new interesting stuff to learn. You'll find here some of my experiments in this new journey!

Popular repositories Loading

  1. Netbox-ipscanner Netbox-ipscanner Public

    ip scan script for populating IPAM module in Netbox

    Python 24 9

  2. webex-skill-gpt webex-skill-gpt Public

    Simple integration between Cisco's Webex Skill SDK and ChatGPT Library.

    Shell 2

  3. feedback-meeting feedback-meeting Public

    Forked from tloyau/feedback-meeting

    Feedback Meeting

    Vue

  4. cisco-phone-controller cisco-phone-controller Public

    Forked from avholloway/cisco-phone-controller

    Embeds a Remote Phone Control App on the Phone's Web Page

    JavaScript

  5. xapi-cisco-tasmota xapi-cisco-tasmota Public

    A simple macro for managing Sonoff switch device with Tasmota firmware

    JavaScript

  6. bbird.github.io bbird.github.io Public