3CX setup issues

Status
Not open for further replies.

James_K

Free User
Joined
Mar 10, 2020
Messages
16
Reaction score
4
Hi all,

Our current environment

We provide a whitelabelled service where we have inbound/outbound calls to/from the clients of our partners. We have a dedicated DID for each partner so their clients have a dedicated number to call and our outbound calls to those clients use the same number (as caller ID). We also communicate with our partners and have pseudo-extensions setup so we can call and/or transfer calls to the partner's main number.

Our current system is based on FreePBX/Asterisk. One of the main reasons for change is better support for home workers.

Our 3CX test environment

I have setup the following to try an mimic our existing PBX system functionality:
  • SIP Trunks for all the external DID's we use.
  • Extensions for all phones.
  • Extensions for all partners. These are set to autoforward to the partners main DID (not on our PBX). The purpose of these is to be able to dial our partner's main line as if it were an extension and also transfer calls.
  • Outbound rules to use different SIP trunks based on 3 digit prefix
  • Inbound rules to direct calls to Ring Groups

For 1 DID I require outbound calls to have No Caller ID, so I created another SIP trunk with outbound parameters set to make this work. This is used by one of the outbound rules.

Ideally I wouldn't need to create SIP trunks for all the DID's we use. The only reason I set them up is so I can specify the outbound DID to use for Outbound rules as you cannot specify a DID in the Outbound rule.

The main 3 outstanding issues/requirements I have are as follows:
  1. When calling a partner extension (which autoforwards to the partner main DID), I would like to specify the Caller ID to be used via either CallerID field or SIP Trunk to be used. At the moment it uses the default Trunk.
  2. I would like to be able to initiate a call externally. On our current PBX we use the Asterisk AMI to do this (our web app uses web sockets to send the AMI command to the Asterisk PBX). The Asterisk PBX calls the initiating extension (based on field in AMI Command) and once picked all calls the specified number (based on field in AMI Command).
  3. On the Dashboard I have a red ! next to Trunks with the issue text being "You are using Unsupported SIP trunk providers which may cause issues.". When I created the trunks I specified a supported provider. I did however rename the Trunk name as I need to differentiate between the multiple trunks I needed to create for the outbound rules mentioned above.

If anyone can provide some guidance on the outstanding issues/requirements or can recommened a better way to meet the functionality require it would be much appreciated.

Thanks,

James
 
Status
Not open for further replies.

Forum statistics

Threads
111,940
Messages
589,846
Members
164,830
Latest member
business@brightwaylogisti