Advice using Twilio and 3CX

[rjamesm2884]

Hello,

We are in the process of porting our numbers into Twilio everything seems to be working fine except for a few cosmetics things.

1.) How can we remove from our outbound calls the area code +1 on all calls? It seems like E164 needs to be disabled in the settings according to the 3CX documentation and added manually in the outbound rules.

2.) When forwarding calls to outside numbers the routing fails to connect. Not sure why if we are able to dial out with no problems.

Any help is much appreciated.

 

[nub]

Hi.

Issue 1:
from what I understand you want to dial 10 and 7 digit number.

7 digit number:
Outbound rules > new rule > name the rule > rule path just like the outbound rule you have now > prepend 1555 (replace 555 with your areacode)

10 digit number:
Outbound rules > new rule > name the rule > rule path just like the outbound rule you have now > prepend 1

Second issue, lets see changing the outbound rules helps with this.

 

[cobaltit]

1) Did you read the guide? It's all covered in

How to set up Twilio Elastic SIP Trunking with 3CX V15.5

2) Are your outbound rules restricted to extensions or groups? Forwarding comes from the system, not an extension or group. Looking at the logs would show why calls are not going out.

 

[rjamesm2884]

1) Did you read the guide? It's all covered in

How to set up Twilio Elastic SIP Trunking with 3CX V15.5

2) Are your outbound rules restricted to extensions or groups? Forwarding comes from the system, not an extension or group. Looking at the logs would show why calls are not going out.

Yes, I did follow that guide and like I said it works however the outbound numbers show +1********** when you dial out. We don’t need to notify everyone local the area code.

 

[rjamesm2884]

1) Did you read the guide? It's all covered in

How to set up Twilio Elastic SIP Trunking with 3CX V15.5

2) Are your outbound rules restricted to extensions or groups? Forwarding comes from the system, not an extension or group. Looking at the logs would show why calls are not going out.

And by the way, line 3 is WRONG, why would you instruct to strip 1 digit then prepend +1 Twillo then gets the first number taken off. Unless we get 3CX support to pitch in here we can't configure Twilio correctly.

 

[cobaltit]

I guess I'm confused if calls are working what are you trying to accomplish? You don't want the E164 showing in the call log or where is it it 'showing' that you are trying to remove?

And by the way, line 3 is WRONG, why would you instruct to strip 1 digit then prepend +1 Twillo then gets the first number taken off. Unless we get 3CX support to pitch in here we can't configure Twilio correctly.

I'm also confused by this statement. Your first post says things are working except for some cosmetic things. Here you seem to imply that unless you get help from 3CX support you can't configure Twilio correctly. But really, you should be getting the support from Twilio. At the end of the day, 3CX can send calls in a variety of formats but it's the provider that accepts or rejects it so ultimately they should be the ones telling you how to format things. This seems to be the part folks don't understand, the hidden cost of support. Twilio is great when it works but if you've ever tried to work with their support when it doesn't then you start to understand the true cost of Twilio when compared to other providers.