Configure Outbound Paramaters

[gcq1]

Hi,

Is there an other way

whitout creating a new trunk​

or

without restoring a back-up​

to change the following outbound parameters

• ContactUser
• FromDisplayName
• FromUserPart
• RemotePartyIDCallingPartyUserPart

?

 

[bitn2]

Export import or via API.

 

[gcq1]

- import does create a new trunk (or am I missing something)
- api doc ?

 

[bitn2]

No, thats correct. You need to delete your trunk after export and change what you want and import it again. Its some work todo...

https://www.3cx.com/docs/configuration-rest-api/

 

[gcq1]

I am using v20 on two pilot locations. I noticed that after upgrading to U4 the outbound parameters of the configured generic trunk are overwritten/changed.
Is this going to be like that after every upgrade or is there a way to prevent ?

 

[bitn2]

I am using v20 on two pilot locations. I noticed that after upgrading to U4 the outbound parameters of the configured generic trunk are overwritten/changed.
Is this going to be like that after every upgrade or is there a way to prevent ?

I have no pbx where a already configured trunk changed anything after upgrade.

 

[gcq1]

In the template :

      <field name="ParameterOut" custom="" parameter="RequestLineURIUser">$CalledNum</field>
      <field name="ParameterOut" custom="" parameter="RequestLineURIHost">$GWHostPort</field>
      <field name="ParameterOut" custom="" parameter="ContactUser">$OutboundCallerId</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">$OutboundCallerId</field>
      <field name="ParameterOut" custom="" parameter="FromHostPart">$GWHostPort</field>
      <field name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyDisplayName">$OutboundCallerId</field>
      <field name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyUserPart">$OutboundCallerId</field>
      <field name="ParameterOut" custom="" parameter="RemotePartyIDCallingPartyHostPart">$GWHostPort</field>

after upgrade to U4 in the back-up :

<OutboundParam ParamName="RequestLineURIUser" ValueName="$CalledNum"/>
<OutboundParam ParamName="RequestLineURIHost" ValueName="$GWHostPort"/>
<OutboundParam ParamName="ContactUser" ValueName="$AuthID"/>
<OutboundParam ParamName="ContactHost" ValueName="$ContactUri"/>
<OutboundParam ParamName="ToDisplayName" ValueName="$CalledName"/>
<OutboundParam ParamName="ToUserPart" ValueName="$CalledNum"/>
<OutboundParam ParamName="ToHostPart" ValueName="$GWHostPort"/>
<OutboundParam ParamName="FromDisplayName" ValueName="$OriginatorCallerId"/>
<OutboundParam ParamName="FromUserPart" ValueName="$OriginatorCallerId"/>
<OutboundParam ParamName="FromHostPart" ValueName="$GWHostPort"/>
<OutboundParam ParamName="RemotePartyIDCallingPartyDisplayName" ValueName="$OutboundCallerId"/>
<OutboundParam ParamName="RemotePartyIDCallingPartyUserPart" ValueName="$OriginatorCallerId"/>
<OutboundParam ParamName="RemotePartyIDCallingPartyHostPart" ValueName="$GWHostPort"/>

I have no pbx where a already configured trunk changed anything after upgrade.

Generic trunks ?

 

[bitn2]

Yes generic.

 

[fxbastler]

@gcq1
you may use this script and google translate with the explanation above:
https://www.3cx.de/forum/threads/si...edata-ausgehende-rufnummer.119683/post-445951

 

[gcq1]

@gcq1
you may use this script and google translate with the explanation above:
https://www.3cx.de/forum/threads/si...edata-ausgehende-rufnummer.119683/post-445951

Excellent info. I will definitly look into it.
Thanks !

 

[gcq1]

I have been reading the documentation (https://www.3cx.com/docs/configuration-rest-api/) : Please note: You must have a 3CX Enterprise license to use 3CX Configuration API.

*sigh*