Forcing lookup in E.164 format

david.taylor

Gold Partner
Advanced Certified
Joined
Jan 25, 2022
Messages
22
Reaction score
11
The CRM we are using requires E.164 format for contact lookups.

Incoming works fine because I have enabled 'Switch on Caller ID to E164 Conversion' on the trunk.

However, for outgoing it seems it just looks up whatever digits the user dials, which will be in national format rather than E.164, and so the lookup fails.

Is there any way to force E.164 for lookups?
 
Our template does that.

It's the <Number> element. Check the docs.
 
Our template does that.

It's the <Number> element. Check the docs.
I'm not sure that's true.

I'm using:

XML:
    <Number Prefix="Plus" MaxLength="" />

But the lookup for outgoing calls is still done on the number as-dialled.
 
I'm not sure that's true.

I'm using:

XML:
    <Number Prefix="Plus" MaxLength="" />

But the lookup for outgoing calls is still done on the number as-dialled.
The number sent to the CRM integration is the final number formatted by outbound rules. Use those to format as E164. Also make sure to set a MaxLength. This will interfere with the phonebook matching config as well.
 
The number sent to the CRM integration is the final number formatted by outbound rules. Use those to format as E164. Also make sure to set a MaxLength. This will interfere with the phonebook matching config as well.
Thanks. I'll give it a try.