Everyone hates learning SIP
The only reason I even learned about phones and telephony to begin with was because my boss hated it. So, naturally, he made me deal with it.
Skipping over the part where I actually ended up loving phones, the fact of the matter is that whether you're working on firewalls, network gear, load balancers, hypervisors, or phone systems, you'll need to learn SIP.
(This is a real GIF of me giggling like a schoolgirl making my first phone ring in a home lab when i was just a kid):
…the real reason why learning SIP sucks is because every vendor has developed their own “flavor” of how it functions in their equipment. Microsoft has their standard in Skype for Business. Cisco has their standard in Communications Manager. Avaya has Session Manager. Sonus, and Audiocodes has their own standard operation. The list goes on.
What ends up happening is people enter this line of business (either by choice or by force) and they end up reading out of one of these vendors manuals. Then, the inevitability comes:
You have to touch some other vendor with SIP
Whether it's setting up a SIP trunk to a provider, connecting two systems together, or something else, the WHOLE POINT OF SIP is to connect systems together with a vendor-neutral protocol. But you end up with the Cisco Engineer telling you their stuff is right, and the service provider telling you that your stuff is wrong, and the constant finger pointing begins because both people are reading out of their own vendor-focused rule-book.
The Truth is: SIP is designed to be flexible
If you really want to be able to stay on top of all these moving pieces, you need to step away from the Vendor-Guide for a bit and actually learn how SIP works. There's an RFC for it. Don't worry it's only 230 pages long (I type sarcastically).
I've been able to bounce between all of those systems, get them all to talk to each other and various service providers even in the most technically frustrating situations because I understood SIP. I may not have known exactly what button to push in each system, but I knew what needed to change in order to get SIP to function. It's easy to google where the button is. It's nearly impossible to google SIP issues because you only get answers on specific vendor forums.
So I created a course called Introduction to SIP. It's designed to give students a working knowledge of the SIP protocol, no matter what vendor you're working with. So that way you can speak competently when troubleshooting and implementing new SIP services. It's normally $20, but I've included the 50% off coupon code LEARNSIPA1 as a thank you for reading the end of my rant. The bottom line: If you want to stop being frustrated with SIP, you've got to learn it properly.
You Wont Regret It