Pass original caller id to "On Call" phone

[gbrown100]

Hi all,

I think this has been discussed a few times but I can seem to find a definitive answer for the UK now that we must all present a valid callerid on outbound. I have a client that want's their "on-call" calls to go to a mobile when they are out of hours but now they want to see the original caller id when they receive the call. They know the Gamma Horizon system can do this (which it can, I believe they actually divert the call at the network level not system level). Having had to just change our servers to ensure that we correctly present the caller id in the right format lest we get fined I don't think we can mess with the outbound id at all without risking a fine.

Right now, their on call goes to an extension that's always diverted to a mobile but as such shows the callerid of the trunk. The only way I thought this might work was if the call is also sent to the mobile number using the "also ring my mobile" feature (although maybe this has the same issue) but the issue is that as a virtual extension it's not signed in so we never get the twinned call.

The answer of "Please use the 3CX client" is just not good enough as mobile coverage for calls is still better than mobile coverage for data! How do other UK people do this? Do we need to find a different trunk provider that allows us to do the diversion at the network level?

Thanks

Graham

 

[ChrisC_3CX]

Right now, their on call goes to an extension that's always diverted to a mobile but as such shows the callerid of the trunk. The only way I thought this might work was if the call is also sent to the mobile number using the "also ring my mobile" feature (although maybe this has the same issue) but the issue is that as a virtual extension it's not signed in so we never get the twinned call.

First off, since you just need to forward the call out again, I think it would be better to just route the call outward on the DID/CID rule directly:



That way you'll have a much cleaner setup. You can of course keep the forwarding on the extension level if you need the user to be able to change the destination number from their forwarding rules.

In any case, you will have to make sure that the SIP Trunk routing the call outwards uses the OriginatorCallerID parameter in it's Outbound Parameters. The default 3CX template for Gamma has OriginatorCallerID set as the "From: User Part" and the "From: Display Name" fields. First confirm that this is in fact the case by going to "SIP Trunks >> Edit the SIP Trunk >> Go to the Outbound Parameters" tab. If they are, I recommend then performing a packet capture while making such a call (inbound call that is routed out again) so that you can then check the capture and determine whether the "From: User Part" and "From: Display Name" fields do actually carry the original caller's Caller ID in the SIP INVITE message set to Gamma for the Outbound call. If they do, it means that the information is correctly sent to Gamma by the 3CX PBX, in which case, you might need to contact them if it still does not work as it would be out of 3CX's control at this point.

 

[gbrown100]

That way you'll have a much cleaner setup. You can of course keep the forwarding on the extension level if you need the user to be able to change the destination number from their forwarding rules.

That's exactly what they want to be able to do, and change the number on the fly. Don't fancy giving them that level of access!

The trunk isn't gamma, the provider (T4COM) are very specific as to how they want it formatted. So the question really is does anyone know of either a trunk provider that gives you the ability to divert at the network level (for the end user) or a 3rd party intermediary service that does this without changing the originator callerid?

 

[ChrisC_3CX]

That's exactly what they want to be able to do, and change the number on the fly. Don't fancy giving them that level of access!

In that case, you should indeed leave this forwarding on the extension level so that they can change the number whenever they want by editing their forwarding rules from within the 3CX Client.

The trunk isn't gamma, the provider (T4COM) are very specific as to how they want it formatted.

Ah sorry, I had misunderstood who the SIP Provider was. As I can see in our UK supported providers list, T4COM supports "Clip No Screening" meaning they should allow showing other numbers as your caller ID other than the ones associated with your SIP Trunk.

What is the format they require?

So the question really is does anyone know of either a trunk provider that gives you the ability to divert at the network level (for the end user) or a 3rd party intermediary service that does this without changing the originator callerid?

I'm not sure what you're trying to achieve exactly. Could you provide an example?

Example:

• Incoming call from 123456
• Call forwarded out again via SIP Trunk with number 987654
• Caller ID sent stays as 123456

If this is what you're trying to do, then it should just work as I have checked T4COM's default template and it also has OriginatorCallerID set in the mentioned SIP Fields. just make sure that your Outbound Rule has not "Outbound Caller ID" set to it as that will be enforced if you do.

 

[gbrown100]

In that case, you should indeed leave this forwarding on the extension level so that they can change the number whenever they want by editing their forwarding rules from within the 3CX Client.


Ah sorry, I had misunderstood who the SIP Provider was. As I can see in our UK supported providers list, T4COM supports "Clip No Screening" meaning they should allow showing other numbers as your caller ID other than the ones associated with your SIP Trunk.

What is the format they require?


I'm not sure what you're trying to achieve exactly. Could you provide an example?

Example:

• Incoming call from 123456
• Call forwarded out again via SIP Trunk with number 987654
• Caller ID sent stays as 123456

If this is what you're trying to do, then it should just work as I have checked T4COM's default template and it also has OriginatorCallerID set in the mentioned SIP Fields. just make sure that your Outbound Rule has not "Outbound Caller ID" set to it as that will be enforced if you do.

Hi Chris,

Exactly as your example. Let me speak to T4COM, maybe I am getting confused with the recent changes made to CallerID, they're a great bunch and am sure will assist.

Thanks

Graham

 

[ChrisC_3CX]

Understood! Do let us know how it goes and if there is anything else we can help with!