Calling the Clearly IP attestation check number at 920-666-1392 as well as the testnumber.org attestation check number at 737-727-3232 both return the correct caller ID number I use (the voip.ms account DiD), but the STIR/SHAKEN attestation level reported is B (Partial attestation, Identity known, authorization to use the number: Unknown. In other words “This is my customer. This call originated on my network; however, I did not give them this telephone number”). The call is certified 91715573 Quebec Inc (voip.ms parent company) Service Provider 161K
I called from my voip.ms account using as the caller ID the DiD number I ported into voip.ms, So it is perhaps because the DiD was ported, not originally acquired from voip.ms, but in nay case it is now with voip.ms, so the attestation level should be A (Full attestation, In other words “This is my customer. I gave them this telephone number. This call originated on my network.” .
The fact that the attestation level is B risks the calls from voip.ms being flagged as robocalls or spam calls.
I am curious to know if I am the only one with this issue, or if it is a widespread voip.ms issue. I know that the company I work with has the same problem and has submitted a support ticket, but so far no solution.
If this is a general voip.ms issue, I think it is pretty serious.
Interesting … my work cell phone has a call masking feature where it sends a caller ID number I submitted instead of the real number of the cell phone. (I use it to display my desk phone number instead of my cell phone when making calls.) That number dialed from my cell phone is given an attestation level of “A”. When I call the check number from my actual desk phone (through the local telephone company) I get an attestation level of “B”.
In other words, I am getting a higher attestation level using a carrier that the number is not assigned to than when using the carrier where that number is actively assigned.
It sounds like STIR/SHAKEN needs more work. And I agree, when placing a call through the voip,ms servers using a voip.ms DID I would expect an attestation level “A”.
Thanks for your feedback. My understanding is that if the carrier has verified that you are authorized to use the number as your caller id, they should attest at the A level. The verification could be, as voip.ms or google voice do, via phone call or SMS sending with a confirmation code that must be entered.
So if your cell phone carrier did the verification, attesting at level A is the way it should be. If the did not do a verification, then they are doing it wrong and should attests at B. Your local phone company on the other end seems to be doing it wrong.
I agree with you, STIR/SHAKEN as well as SMS regulations appear to be a total mess, forcing people and companies to spend tons of time and money.
My numbers are US. But it should not matter, because they do attest, but at level B rather then A, which makes the call show up as “unverified” instead of “verified” or “verified Number” on many cell phones, or it might get blocked by some spam/robocall filters (ooma used to have such a thing when I was with them). I believe it will be even more of a problem in the future as call attestation gets more used to filter calls. This is not good.
BTW, I also tried from the main account instead of sub-accounts with the same results.
My voip.ms number, which I have had for 30+ years, have ported at least 5 times through that period, and is US based, reports a level A from your test numbers.
So it’s not a general problem
But a bit concerning is that the 737 number (testnumber.org) says “scout” rates my number as a “possible” robo call risk. I guess because it knows it’s a VoIP number? Or that voip.ms mostly has corporate customers?
My other number, with a simular porting history, but which currently resides with Tello (a T-Mobile reseller) gets an “A” and “unlikely “.
My 3rd number, recently ported to Sonic (an internet provider) and which is VoIP, reports as “A” and “unlikely”.
So that implies it’s probably a voip.ms reputation problem, not a general VoIP concern.
I have an open trouble ticket regarding this exact issue.
My telephone number consistently received Attestation A when I was with my previous VoIP provider, voipo.com. After they went out of business, I ported the number to voip.ms, and since then, it has been assigned Attestation B. Voip.ms has attributed this to the downstream carrier, Bandwidth.com—however, Bandwidth.com was also the downstream carrier when I was with voipo.com, and I still had Attestation A at that time.
What’s puzzling is that the certificate for my calls is now signed by voip.ms, not Bandwidth.com. I understand that in the past, certificates were sometimes signed by the downstream provider, but that’s not the case here. The signing authority is clearly listed as 91715573 Quebec Inc, which is voip.ms’s parent company.
To further illustrate the inconsistency, I tested two free numbers from Textfree and Google Voice, and both returned Attestation A. Yet my paid DID through voip.ms is flagged with Attestation B, and recipients are seeing “Potential SPAM” on their caller ID displays.