Solved Problem regarding "Ring mobile simultaneously"

[SirPcsvA]

Scenario: Making an internal call to an extension that has "ring my mobile simultaneously" enabled.
Problem: Main-trunk-no is is shown on the mobile
Goal: Outbound callerID as configured should be used instead of main-trunk-no.
Info: Calling the Extension from external, works as expected.
Info:disabling "Ring mobile simultaneously" and enabling "forward to mobile after timeout" also works as expected.

So this problem only occurs when calling the ext from internal.

Any Ideas? Thank you very much

 

[YiannisH_3CX]

Hello @SirPcsvA

Do you want to show the outbound caller ID of the calling or called extension?

 

[SirPcsvA]

I want to show the set outbound ID of the callee, nothing special.

 

[YiannisH_3CX]

Please note that you can forward the callers Outbound caller ID to the provider but not the outbound caller ID of the called extension when calling internally. This is because there are 2 extensions involved in the call and the callers Outbound caller ID is the one used. If one is not present then the Caller ID of the trunk is used.

 

[leejor]

So, on an internal call, if the calling extension has it's DID number in the Outbound Caller ID field (rather than it being left blank), does that DID number show, rather than the main trunk number, on the mobile. If so, then it is working as intended.

 

[SirPcsvA]

@YiannisH_3CX I did not quite understand the first sentence of your last post. Could you please explain? I guess the first "not" should be removed?
@leejor I had a different Outbound Caller ID number than its DID configured on the calling extension, but changed it to its DID now for this test. Its showing the main trunk no on the mobile. Not working as expected.

Thank you so much

 

[leejor]

If external calls are passing on the callers outside number, then your provider obviously allows this and that is not the issue. It may be one of the outbound options, that deal with caller ID, in the trunk settings for the route that call is using. If working correctly, it will still show the originators number, not the extension that has the Ring My mobile number enabled.

 

[SirPcsvA]

I want to show the originators number, not the number of the extension that has "ring my mobile" enabled. just to make sure.

So, as I have a straight forward setup with a single trunk provider from the supported providers list, followed the manuals and did not change any outbound options except adding the single, simple outbound rule for all calls,

I guess I can suppose a problem with the trunk template?

 

[leejor]

Sorry, misunderstood your issue. There are a number of outbound trunk options that deal with "Outbound Caller ID", look through and you will find them. You may have to make some changes, and do some test calls, to find something that works with your provider. However, before changing anything, make note of (print out) the current settings as changes with these settings can cause all outgoing calls to fail over that trunk group.

 

[SirPcsvA]

Thank you! I will try.
I think I am responsible for the misunderstanding because I wrote "callee" in my second post, which is wrong.

Thank you

 

[YiannisH_3CX]

I did not quite understand the first sentence of your last post. Could you please explain? I guess the first "not" should be removed?

Apologies for the mistake. Yes the first "not" is a mistake. I will fix it to avoid further confusion .

want to show the originators number, not the number of the extension that has "ring my mobile" enabled. just to make sure.

This is possible if the outbound parameters of the trunk are configured correctly and the provider allows it. You should check what SIP field the provider uses to read the caller ID and change that to "OriginatorCallerID".
Be careful with changes you apply in the outbound rules as any miss-configuration could break outbound calling completely.

 

[SirPcsvA]

Yes I found a solution:
changing the trunks outbound parameter "From : Display Name".
from "OriginatorCallerID"
to "OutboundCallerID"

Thank you all

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.