<!-- 
RSS generated by JIRA (8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a) at Sat Feb 10 07:17:50 CET 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Jira</title>
    <link>https://jira.astppbilling.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.13.3</version>
        <build-number>813003</build-number>
        <build-date>14-01-2021</build-date>
    </build-info>


<item>
            <title>[ASTPPCOM-513] Missing fields in trunks. v.4.0</title>
                <link>https://jira.astppbilling.org/browse/ASTPPCOM-513</link>
                <project id="10608" key="ASTPPCOM">ASTPP Community</project>
                    <description>&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;ASTPP 3.6&lt;br/&gt;
&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://user-images.githubusercontent.com/4353590/58940494-4256e500-8782-11e9-8b4a-a8168c4d1dbc.png&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;ASTPP 4.0&lt;br/&gt;
&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://user-images.githubusercontent.com/4353590/58940458-2c492480-8782-11e9-824f-5901c887bd67.png&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="12333">ASTPPCOM-513</key>
            <summary>Missing fields in trunks. v.4.0</summary>
                <type id="10000" iconUrl="https://jira.astppbilling.org/secure/viewavatar?size=xsmall&amp;avatarId=10318&amp;avatarType=issuetype">Task</type>
                                                <status id="10001" iconUrl="https://jira.astppbilling.org/images/icons/status_generic.gif" description="">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="tridcatij">tridcatij</reporter>
                        <labels>
                    </labels>
                <created>Wed, 5 Jun 2019 13:37:41 +0530</created>
                <updated>Sat, 8 Jun 2019 15:45:24 +0530</updated>
                            <resolved>Sat, 8 Jun 2019 15:45:24 +0530</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                <comments>
                            <comment id="13582" author="hemdip" created="Wed, 5 Jun 2019 17:38:09 +0530"  >&lt;p&gt;You can do that in 4.0, We have introduce Localization concept &lt;br/&gt;
Switch &amp;gt; Localization here you have to set rules and Give it to your Provider from Accounts module, It will work same as 3.6&lt;/p&gt;</comment>
                            <comment id="13583" author="tridcatij" created="Wed, 5 Jun 2019 18:21:30 +0530"  >&lt;p&gt;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&apos;re splitting different price/quality strategies with it.&lt;/p&gt;</comment>
                            <comment id="13584" author="watoan" created="Thu, 6 Jun 2019 09:32:42 +0530"  >&lt;p&gt;Yup, I am having the similar issue with 4.0 for DNIS.&lt;br/&gt;
In case I have 2 trunks with 1 provider account, it&apos;s used to separate different level of routing/services (usually standard and premium), previously I can do it in &quot;Trunks&quot; - Number Translation for adding a tech prefix before send the call to the provider.&lt;br/&gt;
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?&lt;br/&gt;
Should I do it in &quot;termination rates&quot; &amp;gt; &quot;Prepend&quot;? but it is not ideal way for me, tech prefix should always related to &quot;Trunks&quot; level.&lt;br/&gt;
Or should I create 2 provider account in this case? it is not ideal too....&lt;br/&gt;
Thanks.&lt;/p&gt;</comment>
                            <comment id="13585" author="hemdip" created="Fri, 7 Jun 2019 12:12:11 +0530"  >&lt;p&gt;Not sure about your scenario, But i have one suggestion for you,&lt;/p&gt;

&lt;p&gt;In your provider&apos;s Rategroup you can select your those 2 trunk, might be it work for you.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10703" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>513</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10006" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i00bsv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>