SIP trunk providers are sending CID's with new data in them... i.e. [V]+19735551212

[skycom10]

SIP trunk providers are sending CID's with new data in them...
i.e. [V]+19735551212
[V] = "Verified Number"

Can you give a quick inbound source pattern
to REMOVE the [V] please?

Currently using SOURCE PATTERN:+(1)(...)(.*)
with REPLACE PATTERN:\2\3
Thank you

Tom Kelly

 

[Alejandro_3CX]

Hi @skycom10 please note that the system will not reformat caller name.

Caller ID should be digits 0-9 or +. There is not any option to remove such characters [V] since source pattern will use . that means digits from 0-9 or fixed digits not letters...

More info here

 

[skycom10]

Okay, looks like SOURCE PATTERN is not the way...
So how do we remove this '[V]' in the SIP CID going forward?

Thanks,
Tom Kelly

 

[N_G]

Use a supported provider

 

[mcsphones]

This - the [V] - is not new, Vitelity has been using it for over a year now. Our folks happen to appreciate it, knowing a real person is on the other end. You can always add the calling party to your 3CX contacts with a custom name (caller ID) as desired to override the default.

 

[skycom10]

@Nick Galea
I do! It's Flowroute!!
Can we add this option to control this in SOURCE PATTERNS?


Regards,
Tom Kelly

 

[ltri37]

This should do the job:

SOURCE PATTERN ...(+1)(.*)
REPLACE PATTERN \2

This assumes there are no other valid CIDs with + in the third and 1 in the forth position.

CID rewriting has some really interesting, undocumented behaviors. Looks like you gotta consume (put into brackets) everything that is not at the very beginning. That is why you see so many examples that are not even using \1 or even \2.

source pattern will use . that means digits from 0-9 or fixed digits not letters...

The documentation specifically states that a dot matches everything:

A dot is a placeholder for any symbol.

And indeed my rule above will transform a CID of [V]+14567898788 into 4567898788 see the difference between the calls without and with this rule:

 

[N_G]

@Nick Galea
I do! It's Flowroute!!
Can we add this option to control this in SOURCE PATTERNS?


Regards,
Tom Kelly

Then we will check about it....

 

[SweetAction]

Flowroute has been doing this for a long time, like 2+ years. Like most other people here, I'd recommend you keep it and train the end user on why it's good.

It's added when the call is SHAKEN/STIR verified.

 

[ltri37]

Correct me if I'm wrong:

You cannot call those numbers back, right?
All CID based rules/configuration on the PBX will fail, right?

The user can still see the [V] even with CID rewriting. CID rewriting just fixes the above problems.

 

[YiannisH_3CX]

You cannot call those numbers back, right?
All CID based rules/configuration on the PBX will fail, right?

You can call these numbers and you can route via CID because the [V] is added in the From: DisplayName and both these things are based on the From:UserPart.
The caller ID does not contain the [V], the caller name does. 2 different things in 2 different SIP values.

 

[ltri37]

Ok, if it's not in the CID it's not a CID rewriting issue indeed, so this is a cosmetic issue in the Display Name.