Impact of trunks not being entered in e164 format?

[EscondidoAdmin]

3CX v20u4 Ent 128 SCs, self hosted on Linux.

Hi, I noticed something in our Admin Console while reviewing our trunk capacities. There's a bit about DIDs must be entered in e164 format. Our Telnyx trunks aren't entered using this format but our system seems to handle DIDs correctly. Screen shot from our production system below - Nxx and line numbers obscured.

Is there a reason for requiring e164 formatted DIDs and if so, what's the impact if not formatted this way?

Thanks,

 

[leejor]

If it is currently working, then the DID info being sent by your provider is being matched by your settings in 3CX, and the call routes correctly. The problem will occur when these two don't match as calls will then follow the trunks default route. Maybe you've just been lucky so far?

 

[YiannisH_3CX]

The warning is shown in trunks we know use numbers in E164 format. That means your provider will send the called number in the E164 number format. If your numbers do not match that format then call routing will not work correctly. If you only have 1 number and its sent to the default route then you will probably not have issues.