Feature request: Correct phone number display on the cell phone when the "Signal calls to cell phone simultaneously" option is active

[patrickb_de]

Hello community,

Unfortunately, I have discovered that there seems to be no way to configure the caller ID display correctly on a mobile phone when call forwarding is enabled. I have tried various trunks and all the outgoing parameters that can be configured, but it appears to be an either-or situation.

Example A: In the trunk, the OriginatorCallerID is set for the "From: Display Name" or "P-Preferred Identity: Display Name" field.
When an external call comes in to an available extension with the aforementioned option enabled, both the desk phone and the mobile phone ring, and the original caller's number is displayed. Everything works perfectly. However, if an internal extension calls in this configuration, and the internal extension's direct line rings on both the desk phone and the mobile phone, the mobile phone only displays the trunk's main number, not the external or internal extension number of the caller. This is unfortunate because the employee using the mobile phone cannot see which colleague is calling.

Example B: In the trunk, "Outbound caller ID taken from Extension settings in management console" is set for the "From: Display Name" or "P-Preferred Identity: Display Name" field.
When an external call comes in to an available extension with this option enabled, both the desk phone and the mobile phone ring. In this scenario, the desk phone correctly displays the caller's number, but the mobile phone displays the external number of the called extension. Again, this is unfortunate because the employee using the mobile phone cannot see which external number is calling. However, when an internal extension calls in this configuration, and the internal extension's direct line rings on both the desk phone and the mobile phone, everything is displayed correctly.

Using the APP would be an option. Unfortunately not in Germany or other countries that dont have a stable mobile network. In my opinion, it would be appropriate to make an adjustment to the OriginatorCallerID parameter, which would populate it with the corresponding data depending on the origin (internal or external). It could either be filled with the external number of the internal extension being forwarded to the mobile phone, or with the number of the external caller being forwarded.

This would allow for better integration of mobile phones, especially in regions where the data network for using the app is really poor. Can anyone relate to this and consider such an adjustment useful? Or does anyone have an idea of how to implement this? It seems to me that even with a second trunk, this would be impossible.

 

[Evolute IT]

This always depend on your provider and their ability to do ClipNoScreening.

If they can't, then the originator CID will never show.

Otherwise, the outbound parameter to set will also depend on the provider.

 

[patrickb_de]

This always depend on your provider and their ability to do ClipNoScreening.

If they can't, then the originator CID will never show.

Otherwise, the outbound parameter to set will also depend on the provider.

Yes of course. But thats not a problem caused by the providers or clip-no-screening. its an 3cx issue that there is no possibility to send out the right number in just one option. Clip no screening works correctly. The issue is that the OriginatorCallerID in szenario b dont set the number of the internal extension as OriginatorCallerId and transfered it to the provider. The OriginatorCallerID always sets if the call comes from external but not from internal. so at the moment there is no way to send the right external number from an internal extension to the provider. only if you send the "Outbound caller ID taken from Extension settings in management console" to the provider it will work, but in this case the external calls dont send out the right number.

 

[patrickb_de]

Hi Community,

I've figured out why this issue is occurring and found a temporary solution for it. The root cause of the problem is that when the option "Simultaneously ring on mobile phone" is active, a second call is being established that, instead of using the entered external DID, sets the extension number of the internal extension as the DID.

However, since this number is usually not recognized by the provider, it gets discarded, and subsequently, the main trunk number is used.

As a temporary solution, I have currently tested an outbound reformatting that rewrites each individual 3-digit number upon leaving the system. This way, when simultaneous ringing occurs, the internal number is displayed correctly on the mobile phone, and for external callers, the external number is shown.

Source Pattern: 100Replace Pattern: external DID, e.g., +49123412345100

However, this whole process only works if the numbers are explicitly recognized. Unfortunately, the typical regex source pattern (XXX) replace pattern +49123412345\1 doesn't work.

 

[patrickb_de]

Simultaneously, a module can be developed that allows connecting to the system via GSM call and initiating calls from there using one's own DID (provided one is authorized for it) WITHOUT the need to go through the cumbersome mailbox menu.

If anyone identifies a way, possibly through C#, to access the "Outbound Reformatting" section in the SIP trunk settings and input something there, the entire expansion and scaling can be accomplished relatively easily and with minimal effort.

 

[SweetAction]

Simultaneously, a module can be developed that allows connecting to the system via GSM call and initiating calls from there using one's own DID (provided one is authorized for it) WITHOUT the need to go through the cumbersome mailbox menu.

If anyone identifies a way, possibly through C#, to access the "Outbound Reformatting" section in the SIP trunk settings and input something there, the entire expansion and scaling can be accomplished relatively easily and with minimal effort.

https://www.3cx.com/community/threads/cellular-dialing.53518/

 

[patrickb_de]

https://www.3cx.com/community/threads/cellular-dialing.53518/

Main Problem is that you also need internet to initiate the call. In my solution you dont need that internet connection

 

[patrickb_de]

Hi Community,

I've figured out why this issue is occurring and found a temporary solution for it. The root cause of the problem is that when the option "Simultaneously ring on mobile phone" is active, a second call is being established that, instead of using the entered external DID, sets the extension number of the internal extension as the DID.

However, since this number is usually not recognized by the provider, it gets discarded, and subsequently, the main trunk number is used.

As a temporary solution, I have currently tested an outbound reformatting that rewrites each individual 3-digit number upon leaving the system. This way, when simultaneous ringing occurs, the internal number is displayed correctly on the mobile phone, and for external callers, the external number is shown.

Source Pattern: 100Replace Pattern: external DID, e.g., +49123412345100

However, this whole process only works if the numbers are explicitly recognized. Unfortunately, the typical regex source pattern (XXX) replace pattern +49123412345\1 doesn't work.

I have found a way to achieve this without having to individually input each number...) = 1 dot represents a position in the extension length.

 

[SweetAction]

Main Problem is that you also need internet to initiate the call. In my solution you dont need that internet connection

My post in that thread (https://www.3cx.com/community/threads/cellular-dialing.53518/post-304437) addresses that.