Caller ID displayed during Call Forwarding

[Kwang Mien]

Hi,

We have a requirement that when the call is forwarded, the caller ID displayed to the forwarded callee should show the DID of the extension.

Below is the configuration :

a. under Extension, the Outbound Caller ID is configured.

b. under SIP Trunk -> Outbound Parameters, the configuration is as below. This is to show the outbound caller ID of the extension.


c. For Call Forwarding, after 20 secs if no answer, forward to an external mobile phone

During call forwarding, instead of displaying the outbound caller ID of the extension, the number of the external caller is displayed on the forwarded callee's phone.


Can anyone advise how i can configure such that the outbound caller ID from the extension settings can be shown on the forwarded callee's phone ?

Thanks.


Regards,
Kwang Mien

 

[leejor]

There are other a number of fields, in the outbound trunk parameters, that can/will affect outbound caller ID, such as Remote Party ID-Calling Party-User Part. It may be a matter of changing these, one at a time, until it works the way you want. Each provider can have different requirements. If you list yours, someone else may have experience with them.

Keep in mind that changes to these parameters may have a detrimental affect on other outgoing calls, including the complete blockage of all calls. Proceed with caution.

 

[Kwang Mien]

In the Outbound Parameters of the SIP Trunk, I have set the FROM as "Outbound caller ID set in Extensions Settings"

a) For Unanswered Call forwarding , the caller ID shown on the receiver's phone is the Caller's Number.
b) For Busy or Not Registered Call Forwarding, the caller ID shown is the "Outbound Caller ID set in Extensions Settings"

b) is the correct result.

For a), it is not correct as it is showing the caller's number. Can anyone advise how for "Unaswered Call" forwarding to display the outbound caller ID of the extensions ?

 

[cobaltit]

Perhaps you didn't read the post from @leejor as he gave you suggestions on fields to change and test, as well as mentioning that since it's provider specific, perhaps if you mentioned the provider someone could provide more insight and haven't done so.

There are other a number of fields, in the outbound trunk parameters, that can/will affect outbound caller ID, such as Remote Party ID-Calling Party-User Part. It may be a matter of changing these, one at a time, until it works the way you want. Each provider can have different requirements. If you list yours, someone else may have experience with them.

 

[Kwang Mien]

Yes. I have tested the various options for "From : User Part" and "From : Display Name". But the caller ID of the extensions configured in the extensions settings was not sent out by 3CX. i have verified it using wireshark.

This issue is not of a Provider issue.

The caller ID is the outbound caller ID configured in the extension settings only in the "Busy or Not Registered" Caller Forwarding scenario.

When in "No Answer" call forwarding scenario, it is the caller's number which should not be the case.

 

[jed]

@Kwang Mien

As @leejor said, there are lots of settings to handle, but your SIP Provider has to support these.

If your SIP Provider support it, try to change the Outbound Parameter "From: Display Name to "Originator CallerID"
And you can play with P-Asserted Identity : Display NAme = "Originator CallerID"
And P-Asserted Identity : User Part = "Originator CallerID"

 

[leejor]

Have a read through this thread, in particular, the response from Yiannis.

When in "No Answer" call forwarding scenario, it is the caller's number which should not be the case.

Most users are more concerned with knowing who is calling, before they answer, rather than who is forwarding a call.

 

[cobaltit]

This issue is not of a Provider issue.

He didn't say it was a provider issue. He said if you listed the provider then someone who has gotten this working with the same provider might be able to help.

 

[ChrisC_3CX]

Just want to add that the OutboundCallerID parameter will not be populated with the extension's Caller ID when the call is forwarded outward due to a "No Answer" call forwarding scenario as @Kwang Mien called it. Rather, it will be populated with SIP Trunk's Caller ID or Main Trunk Number. That said, the fact that you are seeing the original caller's ID is weird.

@Kwang Mien
Are you using a 3CX Supported provider? Also, do you happen to have "OriginatorCallerID" set anywhere in your SIP Trunk's Outbound Parameters?

 

[Kwang Mien]

Just want to add that the OutboundCallerID parameter will not be populated with the extension's Caller ID when the call is forwarded outward due to a "No Answer" call forwarding scenario as @Kwang Mien called it. Rather, it will be populated with SIP Trunk's Caller ID or Main Trunk Number. That said, the fact that you are seeing the original caller's ID is weird.

@Kwang Mien
Are you using a 3CX Supported provider? Also, do you happen to have "OriginatorCallerID" set anywhere in your SIP Trunk's Outbound Parameters?

I am using Netpluz as the provider, one of the 3CX supported provider from Singapore.

i did more tests and found that for call forwarding when set to "No Answer", the caller ID is the SIP Trunk main number (if the FROM is set to "Outbound Caller ID set in Extensions Settings"), as you have mentioned.

I also did test for Call forwarding when set to "Busy or Not Registered", the caller ID is SIP Trunk main number as well.

Is there anyway to display the Outbound caller ID of the Extension , instead of the SIP Trunk Main number for call forwarding ?

Thanks.

 

[Kwang Mien]

He didn't say it was a provider issue. He said if you listed the provider then someone who has gotten this working with the same provider might be able to help.

Hi, I am using Netpluz provider, one of the 3CX supported provider.

 

[ChrisC_3CX]

i did more tests and found that for call forwarding when set to "No Answer", the caller ID is the SIP Trunk main number (if the FROM is set to "Outbound Caller ID set in Extensions Settings"), as you have mentioned.

This is expected and cannot be changed.

I also did test for Call forwarding when set to "Busy or Not Registered", the caller ID is SIP Trunk main number as well.

Provided that the extension has a set Outbound Caller ID this should not happen. If the extension is busy or unregistered while in the available status, the call will carry the extension's Outbound Caller ID.

Is there anyway to display the Outbound caller ID of the Extension , instead of the SIP Trunk Main number for call forwarding ?

First you will have to make sure that the extension in question actually has a set Outbound Caller ID. If yes, you can then use the Away, DND or Custom 2 Profile status forwarding rules. Using these will have the OutboundCallerID parameter populated with the extension's caller ID. In the available status this will only happen if the "Busy or Unregistered" condition has been satisfied, otherwise, if the call rings and times out ("No Answer" scenario) the OutboundCallerID will be populated with the SIP Trunk's Outbound Caller ID or Main Trunk number.

 

[Kwang Mien]

This is expected and cannot be changed.


Provided that the extension has a set Outbound Caller ID this should not happen. If the extension is busy or unregistered while in the available status, the call will carry the extension's Outbound Caller ID.


First you will have to make sure that the extension in question actually has a set Outbound Caller ID. If yes, you can then use the Away, DND or Custom 2 Profile status forwarding rules. Using these will have the OutboundCallerID parameter populated with the extension's caller ID. In the available status this will only happen if the "Busy or Unregistered" condition has been satisfied, otherwise, if the call rings and times out ("No Answer" scenario) the OutboundCallerID will be populated with the SIP Trunk's Outbound Caller ID or Main Trunk number.

Thanks Chris for your reply.

Our intention is to have the caller ID as the Outbound Caller ID set in the Extension settings for "No Answer" call forwarding.

Looks like the caller ID cannot be the Outbound Caller ID.

 

[ChrisC_3CX]

I'm afraid that in the "No Answer" scenario, you cannot have the OutboundCallerID be populated with the extension's OutboundCallerID value, but you could potentially use Outbound Rules to achieve the desired behavior. You could for instance set the extension's forwarding rule to send the call to the external number 123456 but on the forwarding rule add a prefix to the number such as 333123456. Then, create an Outbound Rule that only matches calls with prefix 333 and calls made from that extension. Have that Outbound Rule strip all 3 digits and use the same Outbound Caller ID as the one set on the Extension level. Move this Outbound Rule to the top so it is checked first.

Note: If you require this to be applied for all or a large number of extension it may not be a suitable solution for you as you would need a separate Outbound Rule for every extension (each with a unique prefix). This would most probably be time consuming both to configure and manage.