V20 Outbound Caller ID

[sandyhardi]

We have a main line which is 63226333.
We have several DIDS, one is 63226346. In v18, we configure the Outbound caller id per extension and when it calls out, it displays the configured outbound caller ID.

however, in v20, we configured the same, but the outbound caller id shows the main line which is 63226333.
Please help.

 

[leejor]

There are/were several parameters in the trunk Outbound Parameters, that tell 3CX from where Caller ID should be taken, perhaps that changed.

Thread 'V20 SIP Trunk Outbound Parameters'

Nov 24, 2023

Where did V20 move the SIP Outbound Parameters? I'm trying to change the outgoing caller ID, and I cannot find it.

In version 18 this was easy to find, but I cannot figure this out in Version 20.

If anyone could point me in the right direction it would be appreciated.

I've attached a picture from V18 and V20

please help.

• TRAVISCC
• Replies: 11
• Forum: Phone System / PBX

Thread 'SIP-trunk - access to inbound parameters in V20'

Jan 23, 2024

I need to change some default field mappings for incoming calls on a V20 3CX SIP-trunk.
WithV18, these parameters used to be located under the SIP-trunk settings / Inbound parameters (see attachment). I cannot find them under the current V20 release. Is that feature not yet available or where has it been moved to?

• Dominique_CH
• field mapping v20 sip-trunk
• Replies: 5
• Forum: Other

Post in thread 'sip trunk can't fix it. After Updates to V.20'

Jun 11, 2024

I can't export data.
But I captured the old setup.

• areeya

 

[sandyhardi]

Ah so in V20, it is not as straight cut as v18. we should be editing the xml of the sip trunk?

 

[sandyhardi]

any other way to change this?

 

[leejor]

Have not yet had to do it myself, but, as far as I can gather, until they bring back the parameter options in the PBX settings, you'll have to edit the Template file.

If your provider is supported, and a default Template, for them, is available, you might consider re-installing the trunk using that.

 

[sandyhardi]

We have already tried to do several things:

1. changed from gateway config to trunk config but it doesnt register our sip trunk
2. changed it back to gateway and it is able to register to the gateway.
We also changed xml file to this.
</codecs>

<field name="ParameterIn" custom="" parameter="ToUserPart">$CalledNum</field>

<field name="ParameterIn" custom="" parameter="FromDisplayName">$CallerName</field>

<field name="ParameterIn" custom="" parameter="FromUserPart">$CallerNum</field>

<field name="ParameterOut" custom="" parameter="RequestLineURIUser">$CalledNum</field>

<field name="ParameterOut" custom="" parameter="RequestLineURIHost">$GWHostPort</field>

<field name="ParameterOut" custom="" parameter="ContactUser">$CallerNum</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">$OutboundCallerId</field>

<field name="ParameterOut" custom="" parameter="FromUserPart">$CallerNum</field>

<field name="ParameterOut" custom="" parameter="FromHostPart">$ContactUri</field>

<field name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyDisplayName">$OutboundCallerId</field>

</device>


all of these are all in vain. anyone can suggest another way?

 

[sandyhardi]

this is our XML file for our trunk.

 

[leejor]

Don't know if this will be of any help. These are the parameters that I've used on a VoIP trunk for many years. It allows any caller ID set against an extension to be sent, as well as incoming caller ID from one trunk to be sent back out, on a forwarded call. Of course, providers, and devices may take caller ID from different fields.