Good news! I finally got them to take me seriously. It took a bit of effort on my end, though.
I turned on debug logging on my Grandstream ATA, and then used the Voip.ms softphone app to call one of my numbers from the other. I examined the captured SIP messages from the call, and found the incoming Identity header. Using the info in the rraptor-dot-org debugging tool mentioned above, I decoded the header to show that calls were indeed being signed with level B, even when it’s only Voip.ms talking to itself, no third parties involved.
I shared those findings with the Voip.ms support agent late yesterday, and today it’s all fixed! I don’t know what they did, but I’ve asked. “We made some changes to the outgoing calls on your account” is the only explanation I’ve gotten so far.
They’re now citing “security reasons” for why they can’t share details about the changes they made to make this work.
My working theory is that their systems just automatically sign all calls with level B. If an any particular customer complains enough, they’ll add a rule to sign all of their calls with level A.
Out of curiosity, who did you all end up working with at VoIP.ms? I was talking with Grace about my attestation problem, and she was the one who helped get it corrected.
I have invalid caller id hung up on, no toll free numbers, have that service that hangs up on known spam phone calls. I get at least 5-6 calls a days to sign me up for Medicare, sell my house, register my business to google, etc.. all fake callerID #’s Stir/shaken is being shoved down our throat and is not helping any of us. I have over 300 senior citizen customers, we have to create whitelists for some of them because the amount of calls that should have been blocked by stir/shaken.
Can yhou post your message again by starting a new topic?
I can provide some detailed information regarding the issue you describe, and other forum users will likely have information, as well, so this topic deserves its own thread.
