SIP-trunk - access to inbound parameters in V20

Status
Not open for further replies.

Dominique_CH

SMB User
Advanced Certified
Joined
Mar 20, 2020
Messages
84
Reaction score
15
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?
 

Attachments

  • 3cx SIP Field Mapping.jpg
    3cx SIP Field Mapping.jpg
    154.5 KB · Views: 131
It is removed in v20. CID naming will be coming as a feature but not the rest.
 
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?
You may export the provider, edit the template and import it again. Please note that using supported voip provider these parameters are configured by default.
 
  • Like
Reactions: StanleyS and bitn2
You may export the provider, edit the template and import it again. Please note that using supported voip provider these parameters are configured by default.
Thanks for this tip (which indeed works :)) but it's strange that this useful edit-feature was removed: some supported providers use alternate fields to pass additional useful information such as the name of the calling party based on public directories.
 
Agreed: the old scenario was just fine - the Generic template could be loaded and very easily customised if needed for the specific provider.

The change makes it much harder to customise settings as well as FAR less transparent as there's no easy way to see what settings are in place. Previoously it was easy enough to undertake initial quick troubleshooting in checking all the SIP fields were being correctly populated - which was very useful in scenarios where for example some outbound CIDs were sourced from handsets and others from extension settings - but now it's far harder.

I don't believe any users would actually have requested that change - it seems completely unecessary.
 
  • Like
Reactions: SteveITS
Thanks for this tip (which indeed works :)) but it's strange that this useful edit-feature was removed: some supported providers use alternate fields to pass additional useful information such as the name of the calling party based on public directories.
Hello,
I'm trying to follow this tip as I'm facing the same issue. but when importing the template again I notice that the changes are not applied.

is there any procedure I should follow to export the provider template, edit it, and then import it again?
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,993
Members
164,867
Latest member
swegner