Redirect all outbound calls with original caller id

[ittesit]

Hi All,

I'm trying to setup a configuration where all outbound calls (no matter which number the dial) from extensions in a group are redirected to a ring group.
But added to this, time conditions are needed. So that after midnight a message is played with an IVR.

To get this working I created a generic sip trunk (to be used as a loopback), registerar on 127.0.0.1, with the main trunk number set to 1111.
I have setup the time conditions here and setup the routing to a ring group.

I also created an outbound rule applied to the specific group, to send calls to the loopback sip trunk.
With this configuration, any number the end users calls will be redirected to the loopback trunk, and send to 1111 which in turn redirects it to the desired ring group (ext 800)

The problem I'm having is that the phones in the ring group see incomming calls as comming from 1111, not the original caller.
I tried changing the parameters in the caller number/name field mapping on the inbound parameters on the sip trunk, but with no luck.

Does anybody know what the correct settings would be to get the original caller id to be shown?

 

[YiannisH_3CX]

Hi @ittesit

Not sure if this is possible but what number do you want to see? The extension number or the outbound caller ID of the extension?
Also why are you directing external calls back to a ring group of the system? What is the use case here?
I am asking because there may be an alternative solution we could propose.

 

[ittesit]

The use case is a hotel. We have 24 rooms who may only call to the reception. Even if they dial some external (or internal number) the call should go to the reception.

The reception are 2 static phones and 2 mobile 3CX app users.
And we need to check if its past midnight, a message should be played saying reception is closed, press 9 for emergency; which then redirects to a cellphone.

Both the extension number or the outbound caller id of the extension of the hotel room phone would be fine to see as the original caller id. At the moment we see '1111' .

 

[YiannisH_3CX]

What settings do you have under the outbound rules of the trunk you made for 127.0.0.1? Also I am guessing that you used an IP based trunk. Is that correct?

 

[ittesit]

Settings on the outbound rule:
Apply this rule to these calls -> Specific extention group (with all the hotel room extensions)
Make outbound calls on -> Loopback Trunk

Settings of the loopback Trunk:
Generic SIP TRUNK
Registrar 127.0.0.1
No Authentication
Main trunk number 1111
All other settings are default.

I have been playing with the inbound parameters, but with no result. In the end the ring group 800 still receives calls from 1111.

 

[YiannisH_3CX]

Under each extension you want this be applicable try adding an outbound caller ID in the outbound caller id field of the extension. Do not make it the same as the extension though as the PBX will think its an extension calling it and will try to authenticate. If your extension is 100 add the outbound caller id as 0100 and try again.

 

[ittesit]

Correct, if we set the outbound caller id on the extension to the same number as the extension itself, it does not work. The call won't be redirected to the reception.

If we change it to something like 'Room 100' or '0100', then the call does get redirected, but the reception still receives the call as comming from 1111.

 

[YiannisH_3CX]

Can you send us a screenshot of the outbound parameters of the trunk?

 

[ittesit]

Outbound settings for the generic sip trunk:

 

[ittesit]

I don't know if there is any better configuration/option to get what we need?

We are currently onsite to install the second site. But now we are having issues that 3CX is routing the outbound call to the wrong sip trunk.

 

[YiannisH_3CX]

I tested this on my system and I can see the correct caller ID on my extension.
Here are my outbound parameters

 

[YiannisH_3CX]

Now you are diving into uncharted waters. You will need to uncheck the source identification settings for all trunks and make sure that the trunks numbers of the trunks are unique. And if you planning to route the calls to a different destination for each site you will need to add the caller IDs as DIDs for each trunk and create inbound rules for each one.

What PBX version are you on btw?