The called number is not a valid E.164 number.

[LOG.JEST]

I use twillio for my sip trunk. They record the above error, "The called number is not a valid E.164 number." So I can Receive calls just fine, but I can not place calls without getting the 3CX message, " 3CX can not reach the number you called. The number may be incorrect or currently unavailable." Combining the two errors, it seem 3CX is not sending the right number format (E.164) to twillio. So my question is, is this something that I take care of on the 3CX side or the twillio side? If it is the 3 CX side, how do I do that?

 

[KyriacosS_3CX]

Hi,

You have set up the trunk using the build in template and guide? How are your outbound rules set up?

 

[LOG.JEST]

Hi,

You have set up the trunk using the build in template and guide? How are your outbound rules set up?

Thanks for your response.

I set up twilio using the “Auto Setup” option.

Outbound rule for My3CXSystem

Any

Any

The Land Of Green

My3CXSystem

Blocked

Blocked

Blocked

Blocked

In "Outbound rule for My3CXSystem" the only fields populated are "Rule Name*": Outrbound rule for my3CXSystem. & "Rout 1": My3CXSystem; "Strip digits": Strip no digits. Oh, it also lists "Select which Departments can use this outbound rule and lists my only department.

Does this help with solving the issue?

 

[KyriacosS_3CX]

Are you dialing the number as e.164?

 

[LOG.JEST]

Are you dialing the number as e.164?

Thank you. I did not notice there was a way to type the "+" on the keypad. Since all my calls are "+1" numbers, I added that as a "prepend" on the outbound rules, and all is working now.