said by lmartin12:Any help in figuring this all out would be greatly appreciated.
I tried to do both flow charts and Venn diagrams and now I have a big headache.
Informally, doesn't it seem to you that the common factor in all of these cases (or at least most of them) is your VoIP provider?
More specifically, it may be related to the carrier(s) that they are using for outbound calls (sometimes called termination carriers).
Every anomaly, you should write down the phone numbers on both ends, the exact time, and send it to your VoIP provider without much delay so they can look into it.
said by lmartin12:Is there a common problem here that can be fixed or is this just the way the modern phone system in general is.
I would not blame the "system in general".
There is no doubt that beginning with the Bell System breakup (which is now 31 years ago!) things have gotten less orderly but OTOH it costs much less money.
Having said that, if you buy a suit at Walmart do you really expect the fabric and tailoring to be as good as that of Nordstrom?
We know for a fact that there are different quality levels of outbound routes....
That's why Voip.MS gave a choice between standard and premium, why FutureNine talks about different colours of routes, why CallWithUs offers multiple choices of routes.
And for that matter AnveoDirect offers choices of routing and carriers.
So it stands to reason that if you are using a very low price VoIP service, that's carrying on down the line.
For example (as in the old days with Voip.MS) the less expensive outbound route might not transmit the proper CID but rather show a trunk line number which is what that 331-481-xxxx probably is.
But I wouldn't blame the "system in general". That's like the speech in "Animal House" where Otter said the entire United States of America was responsible for the drunken debauchery of Delta House.