I contract with a small company that produces a contact management system and predictive dialer for contact centers. In testing for a regression, I found that my test dialer campaign could not reach my Skype number with a bogus caller ID.
I tried calling a land line and a mobile with the bogus caller ID successfully and was baffled why my Skype number wasn't receiving the call. My colleague noticed the bogus caller ID compelling me to determine an appropriate number to use instead which proved to work. I've been using the bogus caller IDs (1999 in this case) for years because laziness. So sometime between the last time I used the test system to call my Skype number and today, calls originated to my Skype number from the bogus caller ID no longer work. Logs of the backend PBX software looked good for all calls so the service provider isn't at issue here, it's Skype.
I'm sure it's nothing but it all seems too coincidental. If you're a governmental organization collecting "metadata" through an important provider, you're going to want to keep out the crap. Much ado?
I tried calling a land line and a mobile with the bogus caller ID successfully and was baffled why my Skype number wasn't receiving the call. My colleague noticed the bogus caller ID compelling me to determine an appropriate number to use instead which proved to work. I've been using the bogus caller IDs (1999 in this case) for years because laziness. So sometime between the last time I used the test system to call my Skype number and today, calls originated to my Skype number from the bogus caller ID no longer work. Logs of the backend PBX software looked good for all calls so the service provider isn't at issue here, it's Skype.
I'm sure it's nothing but it all seems too coincidental. If you're a governmental organization collecting "metadata" through an important provider, you're going to want to keep out the crap. Much ado?
Can anyone else corroborate this?