<!-- 
RSS generated by JIRA (8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a) at Sat Feb 10 07:16:33 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-374] DID - Orgination Rates not found.</title>
                <link>https://jira.astppbilling.org/browse/ASTPPCOM-374</link>
                <project id="10608" key="ASTPPCOM">ASTPP Community</project>
                    <description>&lt;p&gt;I understand that In order to use a DID. You have to set up the DID in the Origination Rates Table.&lt;/p&gt;

&lt;p&gt;I think the following changes would vastly improve the issues with Origination rates not found when dealing with DIDs.&lt;/p&gt;

&lt;p&gt;1. When a DID is assigned to a customer, make sure the system automatically creates the DID code in the origination rates table with the rate group of the customer that owns the DID.&lt;/p&gt;

&lt;p&gt;2. If you change the rate group on the customer account, automatically update the Origination Rates of all the customers DID to the new rate group.&lt;/p&gt;

&lt;p&gt;3. On the DID&apos;s section of a customer account - If the DID is not in the Origination Rates table at all or if there is not a record in the Origination Rates Table with the did AND the rate group of the customer - Show an Error Message on this screen, and maybe an auto fix button that will generate the rate.&lt;/p&gt;

&lt;p&gt;4. Optimized Call Routing - Also since ASTPP knows where the DID lives. It would be nice if you select force trunk option, the system would present a list of all the rate groups and allow you to select the rate groups you want an record inserted into with the force trunk. This would then make it so the system would not utilize a provider trunk to call out, but would keep the call on-net and there by reducing any costs that would be incurred by dialing out to the pstn and back in.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12194">ASTPPCOM-374</key>
            <summary>DID - Orgination Rates not found.</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="countrdd">countrdd</reporter>
                        <labels>
                    </labels>
                <created>Fri, 6 Apr 2018 18:54:37 +0530</created>
                <updated>Wed, 23 May 2018 11:20:28 +0530</updated>
                            <resolved>Wed, 23 May 2018 11:20:28 +0530</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                <comments>
                            <comment id="13266" author="kristapsdravnieks" created="Sun, 8 Apr 2018 18:01:54 +0530"  >&lt;p&gt;in file /var/lib/astpp/astpp.lua add line INB_FREE=&quot;TRUE&quot; and you will not need Origination rates for DID calls.  Unless you bill for inbound calls&lt;/p&gt;</comment>
                            <comment id="13267" author="countrdd" created="Sun, 8 Apr 2018 18:04:05 +0530"  >&lt;p&gt;Thanks. But we bill for certain inbound calls&#8230;.I.E. 800 inbound&lt;/p&gt;



&lt;p&gt;From: Kristaps Dravnieks &amp;lt;notifications@github.com&amp;gt;&lt;br/&gt;
Reply-To: iNextrix/ASTPP &amp;lt;reply@reply.github.com&amp;gt;&lt;br/&gt;
Date: Sunday, April 8, 2018 at 8:32 AM&lt;br/&gt;
To: iNextrix/ASTPP &amp;lt;ASTPP@noreply.github.com&amp;gt;&lt;br/&gt;
Cc: Dustian Countryman &amp;lt;countrdd@leillc.net&amp;gt;, Author &amp;lt;author@noreply.github.com&amp;gt;&lt;br/&gt;
Subject: Re: &lt;span class=&quot;error&quot;&gt;&amp;#91;iNextrix/ASTPP&amp;#93;&lt;/span&gt; DID - Orgination Rates not found. (&lt;a href=&quot;https://jira.astppbilling.org/browse/ASTPPCOM-374&quot; title=&quot;DID - Orgination Rates not found.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;ASTPPCOM-374&quot;&gt;&lt;del&gt;ASTPPCOM-374&lt;/del&gt;&lt;/a&gt;)&lt;/p&gt;


&lt;p&gt;in file /var/lib/astpp/astpp.lua add line INB_FREE=&quot;TRUE&quot; and you will not need Origination rates for DID calls. Unless you bill for inbound calls&lt;/p&gt;

&lt;p&gt;&#8212;&lt;br/&gt;
You are receiving this because you authored the thread.&lt;br/&gt;
Reply to this email directly, view it on GitHub&amp;lt;&lt;a href=&quot;https://github.com/iNextrix/ASTPP/issues/374#issuecomment-379546914&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/iNextrix/ASTPP/issues/374#issuecomment-379546914&lt;/a&gt;&amp;gt;, or mute the thread&amp;lt;&lt;a href=&quot;https://github.com/notifications/unsubscribe-auth/ADVyslabtFR0R6GVJnHYDxNN-Q1MViovks5tmgM7gaJpZM4TKDEx&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/notifications/unsubscribe-auth/ADVyslabtFR0R6GVJnHYDxNN-Q1MViovks5tmgM7gaJpZM4TKDEx&lt;/a&gt;&amp;gt;.&lt;/p&gt;</comment>
                            <comment id="13268" author="devangn" created="Mon, 9 Apr 2018 10:08:33 +0530"  >&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;~countrdd&amp;#93;&lt;/span&gt; &lt;br/&gt;
for 1,2,3&lt;br/&gt;
There may be chance that admin doesn&apos;t use rate as whole DID number as rate code instead they are having prefix same as outbound call and prefix length could be anything from 1 digit to whole DID number length&lt;br/&gt;
So as an open soure we need to provide the liberty to admin for different kind of usage scenarios.&lt;br/&gt;
The same thing applicable to 4&lt;br/&gt;
If you configure DID with correct call type and set correct destination then there is no chance of using other flow of other provider.&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>374</customfieldvalue>

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

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