Our 3CX instance is going to be operated across three sites that are merging individual phone systems so that each site can call the other. This brings with it a good chunk of number collisions.
Our solution is to have different starting digits for each site, 0 for one, 1 for the second, 2 for the third. That way site 1 can have e.g. 238 as 0238 and site 3 can have one as 2238.
Given that in the vast majority of instances a user will be dialling their own site, my hope was that I could use an outbound rule and user grouping to say 'if a user in the group for site 1 rings a 3 digit number, append a 0', 'if a user in the group for site 2 rings a 3 digit number, append a 1' etc (excluding 999, 101, etc), but this doesn't seem to be the case, since outbound rules require a SIP specifying. In my testing, the phone displays a Not found error.
Have I dun goof'd here, and it's going to be a case of retraining users to use 4 digit numbers, or is there a way to achieve what I'm after?
Thanks.
Our solution is to have different starting digits for each site, 0 for one, 1 for the second, 2 for the third. That way site 1 can have e.g. 238 as 0238 and site 3 can have one as 2238.
Given that in the vast majority of instances a user will be dialling their own site, my hope was that I could use an outbound rule and user grouping to say 'if a user in the group for site 1 rings a 3 digit number, append a 0', 'if a user in the group for site 2 rings a 3 digit number, append a 1' etc (excluding 999, 101, etc), but this doesn't seem to be the case, since outbound rules require a SIP specifying. In my testing, the phone displays a Not found error.
Have I dun goof'd here, and it's going to be a case of retraining users to use 4 digit numbers, or is there a way to achieve what I'm after?
Thanks.
