Showing SIP trunk number instead of caller ID/Choosing an outbound route

[ColinLiving]

Hi all,

I've got two questions; if someone is able to point me in the right direction with regard to them, it would be greatly appreciated.

I have a client with two businesses; each business has its own number. He has asked if it is possible that when he receives a call, he is able to see either the number that was called by the caller, or some other unique indicator that would allow him to know which business is being called. We have already tried to prepend the Rule name via Contacts > Options, but the rule name doesn't show up on his iPhone when a call comes through.

The next question is, is it possible to choose the outbound route by which the call exits on a per call basis? The client wants the appropriate caller ID to show to the callee, depending on who he is calling. As he could be calling anyone, I can't think of a specific outbound rule that would work for this scenario. Does anyone have any ideas?

Kind regards.

 

[leejor]

How does he get the calls on his iPhone? Are they sent to his iPhone provider number, or are the sent to the 3CX App on his phone? if it the former, then the only thing you will have control over is the caller ID sent. If it is the latter, then you can add names/numbers to calls (prefix/suffix to the original name sent), in 3CX, depending on the routing of the call within the PBX. Are these DID numbers?

You can change the outbound caller ID, on a per call basis (provider permitting), by creating a set of outbound rules. Each would have a different prefix to dial, and the desired caller ID added to the rule.

 

[ColinLiving]

How does he get the calls on his iPhone? Are they sent to his iPhone provider number, or are the sent to the 3CX App on his phone? if it the former, then the only thing you will have control over is the caller ID sent. If it is the latter, then you can add names/numbers to calls (prefix/suffix to the original name sent), in 3CX, depending on the routing of the call within the PBX. Are these DID numbers?

You can change the outbound caller ID, on a per call basis (provider permitting), by creating a set of outbound rules. Each would have a different prefix to dial, and the desired caller ID added to the rule.

Thanks for the reply, and sorry for the delay in getting back to you.

Calls are sent to the 3CX App on his phone. Can you link to documentation that shows how to do what you have described? I'll also search around and see if I can find anything.

The second idea is a good one; I'll see if I can implement it. Thanks!

 

[ColinLiving]

How does he get the calls on his iPhone? Are they sent to his iPhone provider number, or are the sent to the 3CX App on his phone? if it the former, then the only thing you will have control over is the caller ID sent. If it is the latter, then you can add names/numbers to calls (prefix/suffix to the original name sent), in 3CX, depending on the routing of the call within the PBX. Are these DID numbers?

You can change the outbound caller ID, on a per call basis (provider permitting), by creating a set of outbound rules. Each would have a different prefix to dial, and the desired caller ID added to the rule.

Hi Leejor,

I was able to implement the outbound call via prefix dialing, so that's all good. Also, I was able to use 3CX's Reformat Incoming Caller ID functionality to get that working perfectly on an Android phone. However, when calls come through to his iPhone, the lock screen still does not show the reformatted Caller ID, despite the fact that the Android does. Is there any mechanism available by which we can resolve this? Thanks!

 

[leejor]

If the Android phone is now showing the desired number , yet the Apple is not, then it indicates that 3CX is sending the correct format. It would appear that it is the iOS App that is not behaving the way you desire.

That, I'm assuming, will be something, 3CX would have to address, in how the App operates.

 

[ColinLiving]

If the Android phone is now showing the desired number , yet the Apple is not, then it indicates that 3CX is sending the correct format. It would appear that it is the iOS App that is not behaving the way you desire.

That, I'm assuming, will be something, 3CX would have to address, in how the App operates.

Hi leejor,

Thanks for your reply. I have opened a ticket with 3CX support to see if they are aware of this issue and if they know how to work around it. Thanks for your assistance.