Q: 3cx v20 latest > Preserve original callerID when flow sends call to external# ?

[fortech]

Hi, am trying to figure out how to do this and hoping to get a bit of guidance / suggestion.
specific detail for my setup:

I am using latest 3cx - Version 20.0 Update 10 (Build 1694 Beta - AI 1.6.63)
I am working with Voip.MS for my sip trunk for inbound and outbound calling
I know already VoipMS easily allow me to do "Masquerade" outbound callerID if I have validated the masquerade number.

As I write this I realize maybe I have already answered my question. Sigh. I think the baseline security measures at VoipMS maybe will simply not allow me to pass "original caller ID" if that idffers from a validated CID# or a DID linked on my account.

digging into the support forum - I found people talking on this topic in the last few yeasr / older releases of 3cx / but no specific recent discussion
other than 'First be certain what your sip trunk provider allows, if they do not allow, then you are done"

So I think my next step after this 3cx forum post will be a query to tech support @ VoipMS.

anyhow ASSUMING it was possible to do this correctly with VoipMS. And not 'blocked'
I am hoping to confirm (precisely?) on how-where in 3cx to make config change.

The GoogleAI tells me when I asked,
"• Go to 3CX Admin Console > SIP Trunks > select your trunk > Outbound Parameters.
• Locate From: User Part and change its value to OriginatorCallerId"
this sounds pretty good, except that config place does not exist in 3cx currently
and when I dig in the forum with some searches <> I now find discussion on v20 requires to edit this parameter I must (export my template for SIP provider, edit the parameter, re-import the template" as the way to do this.
so any comment (ie "yes that is right" or "no, wrong, do this instead..." would be most welcome.

So. I will update my thread when I have a bit more info back from VoipMS team / in case this thread will be found by others in future and good-to-know reference

thank you,
Tim

 

[Alejandro_3CX]

I am using latest 3cx - Version 20.0 Update 10 (Build 1694 Beta - AI 1.6.63)

Hi @fortech latest one for Update 10 is the (Build 1716 Beta - AI 1.6.71).

Voip.MS does not support clip no screening, it means you can use as outbound caller id the numbers in your account, you can not send any number as caller id.




If by chance they allowed this to you, then you need to edit the sip trunk template in order to user the parameter originatorcallerid in the SIP Field used for the outbound caller id, normally the from user part.

By default they use these outbound parameters:

<!-- Gateway / Provider Outbound Parameters -->
<field name="ParameterOut" custom="" parameter="RequestLineURIUser">$CalledNum</field>
<field name="ParameterOut" custom="" parameter="RequestLineURIHost">$GWHostPort</field>
<field name="ParameterOut" custom="" parameter="ContactUser">$AuthID</field>
<field name="ParameterOut" custom="" parameter="ContactHost">$ContactURI</field>
<field name="ParameterOut" custom="" parameter="ToDisplayName">$CalledName</field>
<field name="ParameterOut" custom="" parameter="ToUserPart">$CalledNum</field>
<field name="ParameterOut" custom="" parameter="ToHostPart">$GWHostPort</field>
<field name="ParameterOut" custom="" parameter="FromDisplayName">$CustomField</field>
<field name="ParameterOut" custom="" parameter="FromUserPart">$AuthID</field>
<field name="ParameterOut" custom="" parameter="FromHostPart">$GWHostPort</field>
<field name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyDisplayName">$CustomField</field>
<field name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyUserPart">$OutboundCallerId</field>
<field name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyHostPart">$GWHostPort</field>

so you need to edit the sip field used for the caller id, ask your voip provider which field they want to use for the original caller id, for example if they say the RemotePartyIDCallingPartyUserPart then you should use lets say <field name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyUserPart">$OriginitorCallerId</field>

You can edit the template from the advanced menu ---- templates ---- voip provider templates. Please follow the documentation outlined in this link

Once you have edited your outbound parameters, go to the voice and chat menu ---- select the sip trunk and click on switch template, there you can select the new custom template.

 

[fortech]

Hi, wow that was fast. Thank you for the detailed reply (!)
- sorry to be off by my version 'current' assertion. Things move quickly with versions it seems! I will run update to latest ~soon.
- Thank you for clarify - that VoipMS will not do this. I think
- I guess then I realize, the next simple? question - is there a known 3cx-supported voip carrier who will do Canada service (or maybe just north america is fine) who will permit what I want / would allow "clip no screen" so that I can basically do the CID impersonation? It woud be in theory no drama to light up a new sip trunk to use with alternate carrier for outbound calling to support this call flow, if that was a "doh easy fix" solution.

but maybe asking that question is similar to asking "is there a recommended voip provider I can use that allows potentially illegal and risky-prone behaviour such as CID impersonation, thanks just asking for a friend, I promise to not abuse the service ha ha ha". (manicial laugh)

thank you!

Tim

 

[Alejandro_3CX]

You can check the list of supported voip providers here and validate the support for clip no screening

 

[fortech]

Thank you. That is very good/clear.
I also am going to test if it makes any difference to do my (ring group seek) at the VoipMS PBX layer instead of on the 3cx PBX side of things. In theory that might keep the call 'closer to origin' and allow me to (Ring answer group in 3cx if handset pickup happens) vs (push call out to external AI if no handset answer happens in 3cx side). We shall see. I will post reply-update to thread next week after kicking at this for a bit.

thank you again for assistance.
Tim