Congrats on the OSCP, that's quite an accomplishment! Based on the subject alone, I initially thought this thread would be someone whining about the OSCP being too difficult, so I was pleasantly surprised when I actually read your post.
If you haven't already done so, write a penetration tester version of your resume. Highlight all the security responsibilities in the role(s) you've had, and emphasize everything that's as close to penetration testing as you possibly can (network scanning, vulnerability analysis, patching, system hardening, password auditing, etc.). If you haven't done those things, get permission to do them, and then do them. See if you can even get some exploitation approved, so you can also add internal penetration testing activities.
The CEH is a multiple-choice marketing cert, so no, it's not going to hold a candle to the OSCP. It may open some doors with HR or recruiters, and it will satisfy a DOD checkbox if you're trying to go that route (but others can be used for that). Aside from potentially helping you get your foot in the door somewhere, it's really not well-respected by technical professionals. It's not going to hurt you, but you already have the one that matters to those people.
What's your official title? You first said you've been an IT professional for ~5 years, but your second post makes it sound like you've been in a support position that entire time. If so, that's getting to be a long time in a support role, and the lack of advancement may be viewed negatively by some people.
What other certifications do you have? Everything we do revolves around general IT, so certifications like the CCNA will definitely lend you more credibility. As great as the OSCP is, it doesn't encompass everything. I've met OSCPs who haven't been able to do basic network troubleshooting. A large component of penetration testing is explaining why the current configuration is vulnerable, how to remediate it, and what the potential repercussions of remediation may be. It's unlikely that someone who lacks those core skills and knowledge would be able to do those tasks well.
If you don't have a blog, start one. Put your OSCP review and other things you learn/are working on there. That will demonstrate your knowledge and writing skills (writing reports is a big piece of the equation, so make sure the message you're sending is that you're a competent writer). Unrelated, but the same is true for the quality of your resume. If there are errors and your thoughts are jumbled on such an important document, one can only imagine what the quality of your reports would look like. I'm not implying that your resume is in poor shape; I'm just emphasizing the important of making sure it's polished.
What are you doing for networking (the kind that doesn't involve bits and bytes)? Are there DC[Area Code], OWASP, ISSA, ISACA, etc. meetings in your area? BSides? Do you attend any larger conferences? DefCon will likely be overwhelming if you aren't yet acclimated to cons, but if nothing else, you should definitely head out to DerbyCon later this year. That should be a relatively short trip for you too. Snag your ticket quickly though; it's a smaller con that will sell out.
Are you open to relocating and/or traveling? You're not in a great area for InfoSec, or even IT in general, so being able to broaden your horizons will significantly increase your likelihood of success.
The day you stop learning is the day you start becoming obsolete.