Solved Caller ID issue with Twilio

Status
Not open for further replies.

only1yoni

Free User
Joined
Feb 20, 2022
Messages
15
Reaction score
1
Hi All,

Hoping I can get some help here, I have configured Twilio as the trunk and got the caller ID in place (number that I purchased from Twilio). I have installed the 3cx app on my phone and created my user. I have set my Twilio number as the caller ID; the issue is when I make a call Twilio sees my personal cell phone number not my Twilio Caller ID number therefor the call fails.

I have verified the following: in the user setting (My ext) the caller ID is set as the twilio number (my main pbx number), in the Trunk setting caller ID is set as the twilio number.
 
Call(C:12): from Extn:101 to 3018905578 doesn't match any outbound rule. No outbound rule could be selected.
Both log posts had the same results, you have no outbound rules that match the numbers you dialed.
 
  • Like
Reactions: YiannisH_3CX
Both log posts had the same results, you have no outbound rules that match the numbers you dialed.
Do I need a rule for all other non matching ? Like a wild card ?
 
You have to have a rule that matches the digits dialed otherwise 3CX has no idea of what to do with the call.

In rules there are no wildcards as such. Rules can be made more specific by making the required leading digits longer (or not specifying any digits at all), and specifying, or not, the total number of digits dialed.

They are also read from the top down, so you'd put more specific rules above more "general" ones. First match will be taken.

Keep in mind that if you are dialing a number with a leading + and using E164 to convert to a dial-able number (add the correct prefix), then that (new) number is what the outbound rules will use.
 
Last edited:
You have to have a rule that matches the digits dialed otherwise 3CX has no idea of what to do with the call.

In rules there are no wildcards as such. Rules can be made more specific by making the required leading digits longer (or not specifying any digits at all), and specifying, or not, the total number of digits dialed.

They are also read from the top down, so you'd put more specific rules above more "general" ones. First match will be taken.

Keep in mind that if you are dialing a number with a leading + and using E164 to convert to a dial-able number (add the correct prefix), then that (new) number is what the outbound rules will use.
OMG I feel so dumb I put the prefix in the wrong area :-( fixed and now it works.
 
Thank you everyone for the help! its fixed.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,990
Messages
590,164
Members
164,927
Latest member
tohoken1