![]() ![]() Granted almost every system has their own small modifications to the protocol (usually additional information only relevant to their system within the SIP message) but the core methods are pretty standardised. Both Cisco, Microsoft and others conform to at least SIP RFC 3261 an internet standards based protocol. For instance Cisco and Microsoft are two very different VoIP ecosystems but they can quite easily talk to one another because under the bonnet there is a common set of protocols that define how they fundamentally work. I know I am never going to deploy or work on these other systems, but learning how the underlying protocols work gives you a firmer footing to deal with questions around it. I am Microsoft, why would I have this experience? But as a Skype consultant you’re expected to have knowledge of these systems to some degree if you are to integrate voice especially. I have never deployed or administered a Cisco or Avaya PBX system for instance because I just haven’t been in a situation where I have needed to. As a result, I often find it difficult to grasp some concepts on how things work outside of Lync / Skype for Business. There are still some areas where I feel I have gaps in my “data bank” as it were. Some might say this is the best way to learn, and while I agree to a point, there are times where I am in a room full of people and feel like the novice still. All of my knowledge has been a mixture of trial and error, death by fire and reading other people’s blogs. I have never been officially trained on Lync or Voice over IP. Coming from a traditional Microsoft background, when I started with Lync I had no conception of voice, or SIP and spent the best part of my early career actively avoiding anything to do with the subject. This blog is mainly for myself but it may serve anyone who needs a refresher or who is beginning to enter the world of SIP and Skype for Business. ![]()
0 Comments
Leave a Reply. |