Incorrect inbound caller ID formatting/re-writing

[Lyndon]

Hi!

We have a trunk where the TO header is sent in E.164 format without +, (so 44aaaabbbbbb), which correctly matches against (0aaaa) bbbbbb in  DID Management, and formats the number in the logs etc nicely as (0aaaa) bbbbbb. All good.

The FROM/PAI header is not sent in E.164, but the UK "national" format, so 0aaaabbbbbb On the whole, this is fine as most FROM numbers in logs etc show as (0aaaa) bbbbbb - no problem. However, there are area codes in the UK starting 011, so calls received from, for example, 011aabbbbbb are being displayed in the logs and active call screen, handsets inbound caller ID presentation etc, as +aa bbbbbb, and NOT the usual and expected (0aaaa) bbbbbb format.

I assume this is a bug, as I'm guessing the PBX/trunk are treating the leading 011 as the international dialling code for North America, and is incorrectly replacing 011 with +.

Assuming this is what's happening, how can this be fixed?

Rewrite global numbers on the trunk is set to E.164 (without leading +). 

Running 68.0.30

Thanks

 

[Vodia PBX]

What trunk provider is this? Maybe it makes sense to add a template.

I would always set the country code in the trunk setting in case that it is being used from another country. Then the number presentation is helpful to understand inbound numbers and correctly convert them into the internal +-notation. For outbound there are many variables that can be put into the header settings (check the log for trunk on level 9 when you make an outbound call). 

Is this problem about inbound calls or outbound calls?