Trunk Caller ID Reformat doesn't remove STIR/SHAKEN text

[JonathanH]

My SIP trunk provider puts the validation result into the "From:" header along with the caller ID:

From: "15555551212" <sip:15555551212;verstat=[email protected]:5060>;tag=113433738583093

I've tried using Caller ID Reformat in the trunk settings, using this regex, which validates in a tester:

([0-9]+) -> /1

But it doesn't appear to work. I have a custom CRM integration and I put a piece of debug code that emails me the number parameter that gets passed to it, and for any number that has this validation text in it, the integration never fires. I'm guessing the 3CX system doesn't trigger the integration because the "number" parameter isn't a number. If an incoming call doesn't have the validation text, the integration works fine. And the trunk regex rewrite is the only place I can find to manipulate the caller ID. There is no part of the original SIP message that just has the number, so I can't use the Inbound Parameters section of the trunk to change anything.

 

[leejor]

Caller ID, for North America, has traditionally consisted of two parts, a number, and alpha-numeric characters...the "name" part (normally 15 characters). The name is optional, in most cases, unless paid for. Reformatting caller ID will only work on the number portion, which is usually a separate entity...the portion in quotes...

It is possible that a change in the trunk, inbound parametes, could correct this, but, I would speak with your provider first.

Who is the provider? Others may also be using them.

 

[JonathanH]

Something else must be wrong, if that's the case about the number in quotes being what's operated on. Why would numbers with this text not ping my integration script at all?

My provider is 1Wire.