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 operation experiences: network, virtualization, security... but when I started working with voip and video, my heart was stolen.
VoIP, video and IMs (aka Unified Communication & Collaboraiton) had it all:
- you needed 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).
- 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 needed to know how protocols work (
h.323SIP is an entire world per se with STUN/TURN and STIR/SHAKEN). - you needed to know DNS and load balancing ('cause a service is useless if you don't know how to find/discover it)
- you needed 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 epithome 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.
(to be continued...)