Stir/Shaken Issues

[TBWD]

Now that we are Stir/Shaken compliant I have discovered a new problem, when a call passes Validation the call log in 3cx will show XXXXXXXXXX;verstat=TN-Validation-Passed:Main (XXXXXXXXXX;verstat=TN-Validation-Passed), as the From, if you miss the call and attempt call back, the call will fail, the called number will be XXXXXXXXXXverstatTNValidationPassed
Is there a way to strip verstatTNValidationPassed from the back side of this?

 

[Kevin@voxtelesys]

We reached out to 3CX a while back asking about Stir/shaken and did't hear anything back on what their plan was. We will just be doing the verification at our switch for the time being or put in a custom prefix for the customer, then they can strip it on an outbound rule.

 

[TBWD]

We have turned off notifications at this point, but this is only a temporary fix but I think we need more of a permanent solution.

 

[VoIPTools]

If you still need notifications, I encourage you to take a look at our 3CX Emergency Notifier which can send notifications via phone (text-to-speech), email, SMS, and desktop alert. And you have granular control over who is notified based on location.

We also recently added a new feature where moving a phone from one location to another (change in registered IP address) automatically updates the extensions Caller ID.

 

[TBWD]

If you still need notifications, I encourage you to take a look at our 3CX Emergency Notifier which can send notifications via phone (text-to-speech), email, SMS, and desktop alert. And you have granular control over who is notified based on location.

3CX Emergency Notifier Will not do anything for this issue, this is about the new Stir/shaken and has absolutely no barring on 911 notifications. The notifications we had our CLEC turn off are XXXXXXXXXX;verstat=TN-Validation-Passed:Main (XXXXXXXXXX;verstat=TN-Validation-Passed), we have not nor will ever turnoff 911 notifications.

 

[YiannisH_3CX]

Now that we are Stir/Shaken compliant I have discovered a new problem, when a call passes Validation the call log in 3cx will show XXXXXXXXXX;verstat=TN-Validation-Passed:Main (XXXXXXXXXX;verstat=TN-Validation-Passed), as the From, if you miss the call and attempt call back, the call will fail, the called number will be XXXXXXXXXXverstatTNValidationPassed

We reached out to 3CX a while back asking about Stir/shaken and did't hear anything back on what their plan was. We will just be doing the verification at our switch for the time being or put in a custom prefix for the customer, then they can strip it on an outbound rule.

Can you send me an example in a p.m. of an Invite message of a validated call to see how it reaches the PBX?

 

[TBWD]

Can you send me an example in a p.m. of an Invite message of a validated call to see how it reaches the PBX?

I am working on it, as I stated we turned it off for most of out trunks. I will be setting up a test trunk today from that I will be able to send you that info.

 

[Kevin@voxtelesys]

Can you send me an example in a p.m. of an Invite message of a validated call to see how it reaches the PBX?

Hey Yiannis,
We sent an email to your about it last week, I will get our engineering to follow up on that thread with our S/S integration.

 

[TBWD]

Here is a sample of what the Validation looks like for those who have not yet seen it

P-Asserted-Identity: "Caller Name" <sip:XXXXXX9324;[email protected]:5060>