[ASTPPCOM-513] Missing fields in trunks. v.4.0 Created: 05/Jun/19  Updated: 08/Jun/19  Resolved: 08/Jun/19

Status: Done
Project: ASTPP Community
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task
Reporter: tridcatij Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Hey, in v.3 there were number and callerId translation fields for trunks. I cannot find it in v.4. There are fields in the DB though.

ASTPP 3.6

ASTPP 4.0



 Comments   
Comment by hemdip [ 05/Jun/19 ]

You can do that in 4.0, We have introduce Localization concept
Switch > Localization here you have to set rules and Give it to your Provider from Accounts module, It will work same as 3.6

Comment by tridcatij [ 05/Jun/19 ]

Could you please give an example? In my case, I have 5 trunks for one account. For each of them I need different callerid number translations (need to add few digits in front of the original number). These prefixes are not related to the destinations in my case. We're splitting different price/quality strategies with it.

Comment by watoan [ 06/Jun/19 ]

Yup, I am having the similar issue with 4.0 for DNIS.
In case I have 2 trunks with 1 provider account, it's used to separate different level of routing/services (usually standard and premium), previously I can do it in "Trunks" - Number Translation for adding a tech prefix before send the call to the provider.
But in 4.0, seems I can have only 1 localization setting for 1 provider account, could you please advise how can I prepend tech prefix for 2 different trunks that belongs to the same provider account?
Should I do it in "termination rates" > "Prepend"? but it is not ideal way for me, tech prefix should always related to "Trunks" level.
Or should I create 2 provider account in this case? it is not ideal too....
Thanks.

Comment by hemdip [ 07/Jun/19 ]

Not sure about your scenario, But i have one suggestion for you,

In your provider's Rategroup you can select your those 2 trunk, might be it work for you.

Generated at Sat Feb 10 07:17:50 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.