call transfer to outside with original CALLER ID ...is it possible with 3cx ?

BABALUCHA

Silver Partner
Advanced Certified
Joined
Jan 9, 2021
Messages
217
Reaction score
42
Hello Everyone,
Hope everyone is doing well, and thanks for stopping and having a look at it.
i m trying to send the original caller ID when the call is transferred to an outside phone number, this is for after-hours service. So basically right now they get the compnay's phone number when call is trasnfered to them, so in case the after hours guys on duty miss that call than they can not call back becaus it shows the office;s own phone number, but instead i would liek to PRESERVE the Originoal Caller ID and send out that same number where the caller called from.
To troubleshoot this i have done these:
1 Spoke to SIP TRUNK provider and they said they are not prohibiting it so it should preserve the original Caller ID as long as i have set it upo in SIP TRUNK filed to PRESEEVE(rebound) it.
2 I tested with Panasonic PBX, and it works fine. So this proves that my SIP Trunk provider is not overriding.

I do not see these options in 3cx where I could change/enable to preserve CALLER ID.
Thanks a lot :)
 
Hi @BABALUCHA what is the voip provider that you using in the 3CX? they must support clip no screening for sending the original caller id, then for the outbound parameters, the sip field used for sending the caller id must be using the value ORIGINATOR CALLER ID, original caller id will be sent.

Example below

<!-- Gateway / Provider Outbound Parameters -->
<field status="readonly" name="ParameterOut" custom="" parameter="RequestLineURIUser">$CalledNum</field>
<field status="readonly" name="ParameterOut" custom="" parameter="RequestLineURIHost">$GWHostPort</field>
<field status="readonly" name="ParameterOut" custom="" parameter="ContactUser">$AuthID</field>
<field status="readonly" name="ParameterOut" custom="" parameter="ContactHost">$ContactURI</field>
<field status="readonly" name="ParameterOut" custom="" parameter="ToDisplayName">$CalledName</field>
<field status="readonly" name="ParameterOut" custom="" parameter="ToUserPart">$CalledNum</field>
<field status="readonly" name="ParameterOut" custom="" parameter="ToHostPart">$GWHostPort</field>
<field status="readonly" name="ParameterOut" custom="" parameter="FromDisplayName">$OriginatorCallerId</field>
<field status="readonly" name="ParameterOut" custom="" parameter="FromUserPart">$OriginatorCallerId</field>

<field status="readonly" name="ParameterOut" custom="" parameter="FromHostPart">$GWHostPort</field>
<field status="readonly" name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyDisplayName">$OriginatorCallerId</field>
<field status="readonly" name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyUserPart">$OriginatorCallerId</field>

<field status="readonly" name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyHostPart">$GWHostPort</field>
 
Hello Alejandro
Thank you for your quick reply to this. I'm using a 3rd-party Generic SIP Trunk provider.
 
Hello Alejandro
Thank you for your quick reply to this. I'm using a 3rd-party Generic SIP Trunk provider.
Please check with them to see if they support CLIP no screening (which allows you to send any outbound Caller ID). If they do not support it, you will only be able to use the numbers registered in your account as the Caller ID.

If they do support this feature, you will need to update your outbound parameters by setting the SIP field used for the outbound Caller ID to originatorcallerid, as detailed in my previous reply.

Find further details in this document https://www.3cx.com/docs/voip-provider-template-builder/
 
  • Like
Reactions: Evolute IT
Hi Alejandro
Yes they do support that feature, i ll do more R&D over the weekend and see how it goes, but thanks a lot for guiding me to the right direction. thanks
 
  • Like
Reactions: Alejandro_3CX
Hi Alejandro
Yes they do support that feature, i ll do more R&D over the weekend and see how it goes, but thanks a lot for guiding me to the right direction. thanks
No problem, just check with them, which are the sip fields they need to get with the caller id, in that way you just edit those fields with value originatorcallerid. Once done, sync the template in the sip trunk that you already have.
 
This thread goes over a number of scenarios involving caller ID when using different types of call forwarding. I'm not certain if it has changed, in recent 3CX updates, but depending on the call forwarding used, different Caller Id will be sent.

 
  • Like
Reactions: BABALUCHA
This thread goes over a number of scenarios involving caller ID when using different types of call forwarding. I'm not certain if it has changed, in recent 3CX updates, but depending on the call forwarding used, different Caller Id will be sent.

thanks a lot for your time and help :)
 

Forum statistics

Threads
111,818
Messages
589,166
Members
164,642
Latest member
davids86