- Joined
- Mar 26, 2019
- Messages
- 150
- Reaction score
- 20
I noticed that 3CX is not able to import outbound rules, If someone needs to configure for over 1000 users they have to do it manually, its tiresome.
Maybe you can tell us what you want to archive with this configuration. Maybe we can show you some other options.Apparently, I have no other option, when I contact 3CX I don't get help, I have to figure out how to accomplish that.
Let me share a screenshot of how my outbound rules areCan you the outbound rules for one user? This scenario isn't supported at all, but maybe we will find a solution to use less outbound rules.
If I add them on the extension side it won't work, the only option I seem to have is the long route... I even tried manipulating on the SIP outbound parameters.So the configuration is mostly regarding the outbound caller id correct?
Why not add them to a Group, assign the outbound rule for the Group and take the caller id from each extension?
If you change each extension's outbound caller ID as its own extension number:This is how my setup is:
I have 3 SIP trunks
1. Integrated with Cisco Voice Gateway and users can call extension to extension internally
- Calls from 3CX to Cisco display the 3CX Caller Extension number
- Same calls from Cisco to 3CX display the Cisco Caller Extension number
2. Bridged with a remote 3CX PBX
- Users can call each other
3. SIP for our VoIP provider carrier for our outbound calls whereby each user has a number from the providers that allows inbound
- I have configured inbound rules for each user, their respective DID will route calls to their extensions
- Outbound when users call out their DID issued by the VoIP provider is what displays
I have achieved the above by configuring Outbound rules for each user and adding routes for the 3 SIP trunks above.
However, 1000 users are too many, so I wanted to know if there is an easy way of doing it.


Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.