|
|
(9 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | [[Client]], [[Provider]], [[Destination]], [[Bilateral Agreements]], [[Rates]], [[Least Cost Routing]], [[Prepaid]], [[Custom Report]]
| |
− |
| |
− |
| |
| '''Minimum Requirements''' | | '''Minimum Requirements''' |
| | | |
− | BILLING runs on a customized Linux server. The hardware configuration has been designed to fit your specific needs. | + | Sky DANCE BILLING runs on a customized Linux server. The hardware configuration has been designed to fit your specific needs. |
| | | |
| | | |
− | Being a web application, BILLING runs on all the major browser:
| + | All the major browsers are supported: |
| Firefox | | Firefox |
| Google Chrome | | Google Chrome |
Line 36: |
Line 33: |
| Note: Your Username will be restricted after three unsuccessful login attempts. | | Note: Your Username will be restricted after three unsuccessful login attempts. |
| | | |
− | Once your username and password have been authenticated, you will see âWelcome, âyour usernameââ in the upper-right corner of the main menu bar, and the opening screen with the following graphs. | + | Once your username and password have been authenticated, you will see Welcome, your username in the upper-right corner of the main menu bar, and the opening screen with the following graphs. |
| | | |
| | | |
Line 47: |
Line 44: |
| These charts summarize the income and profit for the prior day, UTC±00:00. The currency used by default is USD. | | These charts summarize the income and profit for the prior day, UTC±00:00. The currency used by default is USD. |
| | | |
− | ⢠Income by Traffic Type
| + | * Income by Traffic Type |
| This is the first pie chart to the left. Scroll over the divisions of the pie and you will see a text box showing the income for that division of the chart compared to the total income for the day, i.e., 108,621.06 of 714,310.92. | | This is the first pie chart to the left. Scroll over the divisions of the pie and you will see a text box showing the income for that division of the chart compared to the total income for the day, i.e., 108,621.06 of 714,310.92. |
| | | |
− | ⢠Countries with Higher Profit
| + | * Countries with Higher Profit |
| This is pie chart to the right. Scroll over the divisions of the pie to see details of a specific country. The text box displays the profit of the country compared to the total profit for the day, i.e., 6,495.45 of 40,389.45. | | This is pie chart to the right. Scroll over the divisions of the pie to see details of a specific country. The text box displays the profit of the country compared to the total profit for the day, i.e., 6,495.45 of 40,389.45. |
| | | |
− | ⢠Evolution
| + | * Evolution |
| This is the bar chart located at the bottom of the screen. It summarizes the traffic volume (minutes) and profit behavior over the past 15 days. Scroll over a specific bar to display the exact value. | | This is the bar chart located at the bottom of the screen. It summarizes the traffic volume (minutes) and profit behavior over the past 15 days. Scroll over a specific bar to display the exact value. |
| | | |
Line 71: |
Line 68: |
| <center>''Figure 3. The Main Menu Bar.''</center> | | <center>''Figure 3. The Main Menu Bar.''</center> |
| | | |
| + | Click any of the following links to learn more about each menu item. |
| | | |
− | 1 SUMMARY
| + | '''[[Client]], [[Provider]], [[Destination]], [[Bilateral Agreements]], [[Rates]], [[Least Cost Routing]], [[Prepaid]], [[Custom Report]], [[Billing Mediation]], [[Billing Administration]]''' |
− | | |
− | The icon [[Image:Image011.gif]] will take you back to the Summary Charts that shows the income, profit and volumes of traffic for the prior day.
| |
| | | |
| | | |
− | 8 ROUTING
| + | '''Summary''' |
| | | |
− | This section explains the use of the automatic routing resources.
| + | The icon [[Image:Image011.gif]] will take you back to the Summary Charts that shows the income, profit and volumes of traffic for the prior day. |
− | 8.1 Automatic Routing
| |
− | | |
− | This option of the routing tab is used to enable or disable clients to route the traffic through the automatic routing resources of your network.
| |
− | | |
− | The Automatic Routing is software that reads the rates from the BILLING system and analyzes the quality of the providers to develop a custom routing table for the clients included in the Automatic Routing table (figure 28). All rates are read daily while the quality of calls and routes are computed every 15 minutes. The Automatic Routing software optimizes the routing routine resulting in a better financial performance. | |
− | | |
− | In the algorithm the ALOC is the key indicator parameter, and is given a weight of 3.
| |
− | | |
− | Figure 28 shows an example of the table to manage the clients that make use of the automatic routing.
| |
− | | |
− |
| |
− | | |
− | Figure 28. Automatic Routing Clients Management.
| |
− | | |
− | The fields of the table are:
| |
− | | |
− | ⢠Partition
| |
− | A partition is a common resource pool to a destination or carrier. A partition groups the common routing for one or more customers, i.e., the wholesale clients are often appointed to the same partition. This partition comprises all the routes they need to direct their traffic.
| |
− | | |
− | ⢠Description
| |
− | This is a brief description -sometimes the name of the carrier is enough- which refers to the client that is enabled to route the traffic in the automatic routing switch.
| |
− | | |
− | ⢠Subscription
| |
− | The subscription defines the type of product for example wholesale, and traffic, for example hubbing or direct, per carrier. A carrier can have more than one subscription, for example one as client and one as provider. In the case of the automatic routing, the subscriptions are client subscriptions. This field is updated by the system once the acronym is entered.
| |
− | | |
− | ⢠Acronym
| |
− | This is the abbreviated name of the client.
| |
− | | |
− | ⢠ASR, ALOC, Rate
| |
− | In these three indicators is defined the importance each one have when the traffic is routed automatically. In the example of figure 28, the ALOC is the key indicator (3) to perform the automatic routing, meaning that the route with the best ALOC will be selected to route the customerâs traffic. Then ASR and Rate are taken into consideration with the same importance (1).
| |
− | | |
− | ⢠Created
| |
− | This field denotes the date when the client was included in the automatic routing table. This field is filled automatically by the system.
| |
− | A custom search can be performed using the fields Subscription and/or Acronym and/or Description in the search window.
| |
− | | |
− | Click âAddâ to include a customer in the automatic routing table. A new row will appear in the table. Enter the Partition, Description and Acronym. ASR, ALOC and Rate have fixed values of 1, 3 and 1 respectively. Click âSaveâ to confirm the addition of âCancelâ to discard it.
| |
− | | |
− |
| |
− | | |
− | Figure 29. Client Addition in the Automatic Routing Table.
| |
− | | |
− | To disable one or more clients, mark the check box on the left of the table corresponding to the client you want to exclude from the automatic routing, and click âDeleteâ.
| |
− | 8.2 Black List
| |
− | | |
− | This option manages a list of providers that are not part of the automatic routing.
| |
− | | |
− |
| |
− | | |
− | Figure 30. Client Addition in the Automatic Routing Table.
| |
− | | |
− | The fields of the table are:
| |
− | | |
− | ⢠Subscription
| |
− | This is the subscription associated to the provider.
| |
− | | |
− | ⢠Acronym
| |
− | This is the abbreviated name of the provider.
| |
− | | |
− | ⢠Area Code
| |
− | This field corresponds to the area code that is not part of the automatic routing for that specific provider. In other words, traffic routed automatically will no be directed to this area code for this provider.
| |
− | | |
− | ⢠Destination
| |
− | This is the destination corresponding to the area code listed in the table.
| |
− | | |
− | ⢠Created
| |
− | This field denotes the date when the client was included in the black list. This field is filled automatically by the system.
| |
− | | |
− | A custom search can be performed using the fields Subscription and/or Acronym and/or Area Code and/or Destination, in the search window.
| |
− | | |
− | Click âAddâ to include a customer in the black list. A new row will appear in the table. As you type the Acronym, a drop down list of will appear. Select the Acronym from the list or finish typing.
| |
− | | |
− | As you type the Area Code, a drop down list of options will appear. Select the Area Code from the list. The Destination, Subscriptions and Created fields will be filled automatically. Click âSaveâ to confirm the addition of âCancelâ to discard it.
| |
− | | |
− | To exclude one or more providers form the black list, mark the check box on the left corresponding to the provider you want to delete from the table, and click âDeleteâ.
| |
− | | |
− | | |
− | | |
− | | |
− | | |
− | 9 PREPAID
| |
− | | |
− | With this option you retrieve information about your prepaid cards. Here the prepaid platform receives a call, the system sends the call to your network and from there it is routed to a provider.
| |
− | | |
− | The general topology of this option is as follows.
| |
− | | |
− |
| |
− | | |
− | Figure 31. Prepaid Customers Report.
| |
− | | |
− | The commands < and > are used to move your search one day back or forth separately while the commands << and >> are used to move the complete time frame back and forth.
| |
− | | |
− |
| |
− | | |
− | Figure 32. Prepaid Customers Report Example.
| |
− | | |
− | Figure 32 is an example of the customized report for eight days. Following is an explanation of this report:
| |
− | | |
− | ⢠Card
| |
− | This is the name of the prepaid calling card.
| |
− | | |
− | ⢠Evolution
| |
− | With the icon you will generate a graph and a report showing the performance of the customer in the timeframe specified at the beginning of your search. The graph will show, by default, the income in the bar chart, and the volume of calls in the line chart. These parameters are customizable as explained in section 2.2.5.
| |
− | | |
− | The table generated with the Evolution icon, represents all the destinations where the traffic of the calling card is terminated. It gives details about the area codes, connected calls, minutes, income and cost.
| |
− | | |
− | ⢠Calls
| |
− | Total amount of connected calls for that prepaid card.
| |
− | | |
− | ⢠Minutes
| |
− | Total amount of connected minutes for the prepaid card.
| |
− | | |
− | ⢠Retail Income
| |
− | This income reflects what the prepaid platform charges to the prepaid customers, according to the BILLING platform rates.
| |
− | | |
− | ⢠Income
| |
− | This income reflects what you charge per minute âusually at cost- to the prepaid platform traffic.
| |
− | | |
− | ⢠Cost
| |
− | This cost reflects the cost per minute you pay to your providers.
| |
− | | |
− | ⢠Profit
| |
− | You have two types of profit on this table, the prepaid platform profit and your profit as a carrier.
| |
− | | |
− | Going back to figure 32, click on the name of the card to retrieve a report of the traffic per destination.
| |
− | | |
− | | |
− | | |
− | | |
− | | |
− | 10 CUSTOM REPORT
| |
− | | |
− | This option is dedicated to the generation of custom reports. The customization window is illustrated in figure 33.
| |
− | | |
− |
| |
− | | |
− | Figure 33. Custom Report Generation.
| |
− | | |
− | The customization window is divided in three parts: Client, Provider, and the third part that includes the field Country. The field Display is used to enable or disable the deployment of the filter in the table. For example if you want to generate a report for a client where you want to see the traffic per area codes, check mark the box under Display for Dial Code.
| |
− | | |
− | The Client and Provider windows have the following fields:
| |
− | | |
− | ⢠Company
| |
− | This field is used when different companies, business units or subsidiaries carry on your business. You can generate the report for the entire group or select the company/business unit of your interest.
| |
− | | |
− | ⢠Traffic Type
| |
− | The traffic type depend on the type of service rendered: hubbing, retail, etc.
| |
− | | |
− | ⢠Carrier
| |
− | Type here the name of the customer or provider.
| |
− | | |
− | ⢠Destination
| |
− | Type here the name of the city or country. As you type a window with all the possible options will appear for you to select the destination.
| |
− | | |
− | ⢠Area Code
| |
− | You can customize the report by including a specific area code.
| |
− | | |
− | ⢠Manager
| |
− | You can generate a report to see the performance of the accounts of a particular Manager. Select the name of the Manager from the list.
| |
− | | |
− | ⢠Currency
| |
− | Here you decide whether or not to show this field in the report.
| |
− | | |
− | The third part of the customization window includes the following fields:
| |
− | | |
− | ⢠Country
| |
− | Type here the name of the country you want to retrieve data from.
| |
− | | |
− | ⢠Internal Destination
| |
− | Type here the name of the City or network (p. e. cellular Avantel) you want to retrieve information. Note that in this field your internal destination assignation is followed.
| |
− | | |
− | ⢠Internal Area Code
| |
− | Type the Area Code following your internal definition of area codes.
| |
− | | |
− | ⢠Internal/Client/Provider Date
| |
− | Depending on the internal time followed by your business, your customers or providers, you might have differences in the date. This field helps clarify these differences.
| |
− | | |
− | ⢠Output
| |
− | Select the format you want the report to be generated: html, csv, excel, xml.
| |
− | | |
− | ⢠Reset
| |
− | Click Reset to clear all fields and start a new customization.
| |
− | | |
− | ⢠Next
| |
− | Your customized report will be exported in the specified format.
| |
− | | |
− | Following is an example of a customized client report for the city of Armenia in Colombia, and for the 12/19/2012. Figure 34 shows the customization parameters.
| |
− |
| |
− | | |
− | Figure 34. Armenia â Colombia Customization Parameters.
| |
− | | |
− | The custom report generated in the example of figure 34 is shown in figure 35.
| |
− | | |
− |
| |
− | | |
− | Figure 35. Armenia â Colombia Custom Client Report.
| |
− | | |
− | This report lists the customers sending traffic to Armenia. The fields of the report are:
| |
− | | |
− | ⢠Client
| |
− | These are the customers sending traffic to Armenia.
| |
− | | |
− | ⢠Client Destination
| |
− | The destination your customers require the traffic to be terminated.
| |
− | | |
− | ⢠Client Currency
| |
− | The currency your customerâs billing is based.
| |
− | | |
− | ⢠Calls
| |
− | This is the total amount of calls in the time frame.
| |
− | | |
− | ⢠Internal Minutes
| |
− | You also have the Internal Minutes, which refers to your methods of billing in terms of minute rounding.
| |
− | | |
− | ⢠ALOC
| |
− | | |
− | ⢠Income
| |
− | As previously described.
| |
− | | |
− | ⢠Sell Rate
| |
− | As previously described.
| |
− | | |
− | ⢠Cost
| |
− | As previously described.
| |
− | | |
− | ⢠Cost Rate
| |
− | As previously described.
| |
− | | |
− | ⢠Profit
| |
− | As previously described.
| |
− | | |
− | ⢠% Profit / Income
| |
− | As previously described.
| |
− | | |
− | | |
− | | |
− | | |
− | | |
− | 11 MEDIATION
| |
− | | |
− | This window summarizes the activity of the switches, the distribution of calls by type, the routes with any billing trouble, and the detail of CDR files mediated between the switches and the BILLING module.
| |
− | | |
− | The displayed data corresponds, by default, to the information of the previous day. You can customize your search by date, using the field âFromâ of Figure 36. Or use the < and > to move one day forward and one day backward.
| |
− | | |
− |
| |
− | | |
− | Figure 36. Search by Date Window.
| |
− | | |
− | 11.1 Summary
| |
− | | |
− | The first table of the summary represents the number of files mediated between the BILLING module and the Switches.
| |
− | | |
− | The red cell denotes that the system has mediated fewer files than it should have.
| |
− | | |
− |
| |
− | | |
− | Figure 37. Summary.
| |
− | 11.2 Call Type
| |
− | | |
− | The second part of the table in the Summary window is Call Type. Following is a description of the fields of this table.
| |
− | | |
− | Table 1. Call Type Definition
| |
− | Call Type Description
| |
− | Mediated This field refers to the amount of calls in terms of sets of messages (2 or more) comprising a call.
| |
− | Connected A call is successfully connected when thereâs a ringing tone or the call is answered. A connected call is also a call that has to be billed
| |
− | Accepted A call that has been mediated successfully.
| |
− | Access
| |
− | Damaged The register has been corrupted and the call cannot be billed.
| |
− | Not Rated Calls that have not been rated by the BILLING module.
| |
− | Stuck These are calls which duration exceeds the configured length limit in the system.
| |
− | Errors
| |
− | Successfully Billed The number of accepted calls that have been billed by the platform minus the stuck calls.
| |
− | Billed Calls Should Be The number of connected calls that should be billed by the platform minus the stuck calls.
| |
− | | |
− | âSuccessfully Billedâ and âBilled calls Should Beâ numbers should match. A red cell denotes a problem if they donât.
| |
− | | |
− | The second table in the screen summarizes the billing problems for the prior day. First, you will find the billing codification (figure 38) and then the details of the events per route (figure 39).
| |
− | | |
− |
| |
− | | |
− | Figure 38. Billing Codes and Table of Events.
| |
− | | |
− | The following table explains the meaning of the billing codes.
| |
− | | |
− | Table 2. Billing Codes Description
| |
− | Billing Code Description
| |
− | Not Rated The call has not been rated due to some error in the processing.
| |
− | Rated The call is billed. If there are errors in the process, the other indicators will clarify.
| |
− | Default Rate Calls billed with a default configurable rate.
| |
− | Hourly The call is billed by the normal process that runs every hour after every mediation.
| |
− | No Clientâs Rate The clientâs rate does not exist in the rate registry. The system bills using the default rate.
| |
− | No Providerâs Rate The providerâs rate does not exist in the registry. The system bills using the default rate.
| |
− | Fixed This indicator denotes that there were damaged calls that were fixed and billed.
| |
− | Stuck Call These are calls which duration exceeds the configurable length limit. These calls are not billed.
| |
− | Not Billed Call Calls that could not be billed by the system.
| |
− | | |
− | The billing unusual events for the prior day are summarized in the following figure. It makes use of the billing codes to explain the nature of the event.
| |
− | | |
− |
| |
− | | |
− | Figure 39. Routes Presenting Billing Problems.
| |
− | | |
− | The following table describes the heading fields of the billing events summary.
| |
− | | |
− | Table 3. Billing Events - Parameters
| |
− | Field Description
| |
− | Code This is the internal code for the carrier.
| |
− | Client This is the actual customer sending traffic to a destination through your switches.
| |
− | Org_sub Clientâs identity that sends the call.
| |
− | Provider Providerâs identity that terminates the call.
| |
− | Dst_sub Destination providerâs identity that terminates the call.
| |
− | Tg_in This indicates the trunk group of the customer.
| |
− | Tg_out This indicates the trunk group of the provider.
| |
− | Cld Called_id. This is the called party number.
| |
− | | |
− | 11.3 Calls Without Subscription
| |
− | | |
− | These are the calls that cannot be associated to a customer or provider.
| |
− | | |
− |
| |
− | | |
− | Figure 40. Calls Without Subscription.
| |
− | | |
− | The field CIng refers to the calling party number.
| |
− | | |
− | 11.4 Detail by File
| |
− | | |
− | This table contains details of the CDR files collected by the Agents and mediated in the platform.
| |
− | | |
− |
| |
− | | |
− | Figure 41. Detail by File.
| |
− | | |
− | | |
− | The following table explains the fields of the Detail by File window.
| |
− | | |
− | Table 4. Details of the Mediated Files.
| |
− | Parameter Description
| |
− | Agent Switch where the CDR are collected.
| |
− | Description Name of the CDR file. The format contains the location, date and time.
| |
− | Mediated Files mediated by the BILLING module.
| |
− | Connected Connected calls.
| |
− | Accepted Accepted calls.
| |
− | Damaged The file has been corrupted and cannot be processed.
| |
− | Access
| |
− | Damaged
| |
− | | |
− | | |
− | | |
− | | |
− | | |
− | 12 ADMINISTRATION
| |
− | | |
− | This option provides administrative information about the carriers and the contracts, and rates and billing management tools.
| |
− | 12.1 Account Management
| |
− | | |
− | This tab is dedicated to classifying administrative information related to the customers, providers, and valid agreements with them.
| |
− | | |
− | Figure 43 shows the general structure of this option. The first screen that you will see is a list of contracts with the different carriers.
| |
− |
| |
− | | |
− | Figure 42. Account Management.
| |
− | | |
− | Following is an explanation of the fields of this table.
| |
− | | |
− | ⢠Company
| |
− | This field is useful to manage different companies of the same group that are interconnected with the carriers. You can see a specific company and its accounts by clicking on the right corner arrow of the header and then selecting âFiltersâ. This will display the list of companies that form the business conglomerate. Select the company or companies you want to see the accounts.
| |
− | | |
− | ⢠Account
| |
− | This is the internal Id given to the account.
| |
− | | |
− | ⢠Acronym
| |
− | This is the abbreviated name of the company with whom you have an agreement. You can see a specific account by clicking on the right corner arrow of the header and then selecting âFiltersâ. Type here the name of the carrier you want to find in the list.
| |
− | | |
− | ⢠Status
| |
− | You can select the status of the agreement by clicking on the right corner arrow of the cell and selecting âFiltersâ. You can define the status as âACTIVEâ when the agreement is operational, âBLOCKEDâ when the incoming trunk groups are blocked, and âCANCELLEDâ when the agreement is not valid anymore.
| |
− | | |
− | ⢠Credit Limit
| |
− | This field shows the maximum amount of credit that your company can extend to the carrier. You can use the filter on the header by defining a fixed amount or a range (see figure 43).
| |
− | | |
− |
| |
− | | |
− | Figure 43. Credit Limit.
| |
− | | |
− | ⢠Credit Currency
| |
− | This is the credit currency that is specified in the agreement.
| |
− | | |
− | ⢠Automatic Cut
| |
− | If the Automatic Cut is activated, the system will block the route once the Credit Limit value is reached. Use the filter to list the accounts with automatic cut or without it.
| |
− | | |
− | Now back to figure 42 the button Cash Flow Forecast takes you to a window dedicated to provide information about the expected consolidated incomings and outgoings of cash per account.
| |
− | | |
− |
| |
− | | |
− | Figure 44. Cash Flow Forecast.
| |
− | | |
− | This table compiles the cash flow forecast for the following 10 weeks. Make use of the field âFromâ to specify a different time frame you want to see the forecast. The table of figure 44 provides the following information:
| |
− | | |
− | ⢠Company
| |
− | This is the business unit or subsidiary under which manages the account.
| |
− | | |
− | ⢠Acronym
| |
− | This is the abbreviated name of the carrier.
| |
− | | |
− | ⢠Period
| |
− | This refers to the billing period.
| |
− | | |
− | ⢠Due Days
| |
− | The amount of days before the invoice has to be paid.
| |
− | | |
− | ⢠Week Number
| |
− | This refers to the week on which the forecast is being made.
| |
− | | |
− | The first line of the table shows the consolidated total forecasted per week. Click on to see the incomings and outgoings specific account. To see the incomings and outgoings of all the accounts click âExpand Allâ.
| |
− | | |
− | Now, back to the Account Management window (figure 42), the button Last Notes take you to the following window:
| |
− | | |
− | | |
− | | |
− |
| |
− | | |
− | Figure 45. Last Notes.
| |
− | | |
− | This window is useful to compile final notes regarding the performance of the agreement.
| |
− | | |
− | Again going back to figure 42, if you expand one of the companies, you will see the general address of the carrier and the financial contact information. If you click on one of the acronyms you will access detail information about the agreement: Account info, contact info, commercial info, financial info, special conditions, contact info, subscriptions, invoices, documents, and notes. Following is an explanation of these windows.
| |
− | | |
− | To add a new line in the Account Management table click on âNew Accountâ. The following window will appear:
| |
− | | |
− |
| |
− | | |
− | Figure 46. New Account window.
| |
− | | |
− | Fill in the information required and save the changes. Following is an explanation of the different tables of this window.
| |
− | | |
− | 12.1.1 Account Info
| |
− | | |
− | In this window you see general information about the account. Figure 47 shows an example for a specific carrier.
| |
− | | |
− |
| |
− | | |
− | Figure 47. Account Info.
| |
− | | |
− | The fields in this window are explained as follows:
| |
− | | |
− | ⢠Company
| |
− | This is the business unit or subsidiary, which manages the account.
| |
− | | |
− | ⢠Acronym
| |
− | This is the abbreviated name of the carrier.
| |
− | | |
− | ⢠Account Name
| |
− | This is the full name of the carrier.
| |
− | | |
− | ⢠TIN
| |
− | This is the Tax Identification Number of the carrier.
| |
− | | |
− | ⢠Status
| |
− | This field denotes whether the agreement is active, blocked or cancelled.
| |
− | | |
− | ⢠Manager
| |
− | This is the person in your company responsible for the relation with the carrier.
| |
− | | |
− | ⢠Time Zone
| |
− | This is the time zone that has been settled in the agreement.
| |
− | | |
− | ⢠Geographic Zone
| |
− | This is useful to define the geographic zone, such as Europe, Latin America, Asia, etc., to which the account belongs.
| |
− | | |
− | Note: To enable the edition of most of the fields of Account Info, Contact Info, and Financial info, use the button âEditâ located under the window of Special Conditions. After you make the changes, click âSaveâ to confirm the edition or âCancelâ to discard it.
| |
− | | |
− | 12.1.2 Contact Info
| |
− | | |
− | This window gives you specific information about the contact person or department, and the physical location of the carrier. Figure 48 shows an example for a specific carrier.
| |
− | | |
− |
| |
− | | |
− | Figure 48. Contact Info.
| |
− | | |
− | 12.1.3 Commercial Info
| |
− | | |
− | This window shows details about the rates notification.
| |
− | | |
− |
| |
− | | |
− | Figure 49. Commercial Info.
| |
− | | |
− | The fields in this window are explained as follows:
| |
− | | |
− | ⢠Rates Notification Period
| |
− | This period is specified in the agreement. It tells the days in advance required to enforce a rate or code change.
| |
− | | |
− | ⢠Rates Notification Subject
| |
− | Some customers accept rate changes through an email automatic upload module. This field specifies the subject of the email you must include to validate the reception of the amendments.
| |
− | | |
− | ⢠Rates Notification Sender
| |
− | This field specifies the email address from which you must send the rate notifications.
| |
− | | |
− | 12.1.4 Financial Info
| |
− | | |
− | This window provides general information about the financial status and the conditions agreed in the contract.
| |
− | | |
− |
| |
− | | |
− | Figure 50. Financial Info.
| |
− | | |
− | These conditions are:
| |
− | | |
− | ⢠Balance
| |
− | In case of a bilateral agreement, this field shows the difference between the traffic you receive and traffic you send to the carrier in terms of money.
| |
− | | |
− | ⢠Currency
| |
− | The currency is as agreed in the contract.
| |
− | | |
− | ⢠Bank
| |
− | This is the bank where all transactions are made.
| |
− | | |
− | ⢠Payment Terms
| |
− | This is the amount of days that the customer or your company has to pay an invoice.
| |
− | | |
− | ⢠Issue Invoice
| |
− | If this box is checked, it means that a physical invoice should be sent to the customer.
| |
− | | |
− | ⢠Invoice Model
| |
− | This field helps clarify the case where multiple business units emit different invoice models.
| |
− | | |
− | ⢠Invoice Subject This field specifies the subject of the email you must include to validate the reception of the invoice.
| |
− | | |
− | ⢠VAT
| |
− | This field indicates the Value Added Tax applied in the invoice.
| |
− | | |
− | ⢠Accounting ID
| |
− | This is the ID of the account.
| |
− | | |
− | ⢠Credit Limit
| |
− | A zero in this field means that the customer does not need a credit to send traffic. A one in this field means that the offset value canât be different to zero and further action should be taken. A different amount specified here represents the credit the customer has to send traffic.
| |
− | | |
− | ⢠Insured
| |
− | This is the insurance policy coverage in the event that your company is unable to collect on the accounts receivable.
| |
− | | |
− | ⢠Automatic Cut
| |
− | When this box is checked it means that the routes will be blocked once the credit reaches a zero value.
| |
− | | |
− | ⢠Balance Offset
| |
− | When this box is checked it means that traffic routing is allowed even when the offset value is not zero.
| |
− | | |
− | ⢠Alert
| |
− | The system sends an alert that indicates that the credit limit is reaching this value.
| |
− | | |
− | ⢠Prepaid Client/Provider
| |
− | This field indicates if this is a client or provider prepaid account.
| |
− | | |
− | Going back to Balance, Click on to see the daily movement of consolidated incoming and outgoing invoices, and the balance. The following window will appear:
| |
− | | |
− |
| |
− | | |
− | Figure 51. Detailed Balance window.
| |
− | | |
− | To create a bank transaction click âAdd Transactionâ:
| |
− | | |
− |
| |
− | | |
− | Figure 52. Transaction Addition.
| |
− | | |
− | Select the type of operation -Consolidate, Incoming Payment, or Output Payment. Select the date, the amount, the currency, and type a brief description if required. Then click âSaveâ or âCancelâ.
| |
− | | |
− | To edit a bank transaction click and make use of the Operation, Date, Amount , Currency and Description, to make the edition.
| |
− | | |
− | 12.1.5 Special Conditions
| |
− | | |
− | In this field you can document special financial conditions to be considered in the agreement.
| |
− | | |
− |
| |
− | | |
− | Figure 53. Special Conditions.
| |
− | | |
− | 12.1.6 Contact Info
| |
− | | |
− | This table summarizes the contact information of the different areas involved in the daily performance of the routes of the agreement You can add or delete contacts using the commands âAdd Contactâ, âSaveâ, âCancelâ.
| |
− | | |
− |
| |
− | | |
− | Figure 54. Contacts.
| |
− | | |
− | Following is an explanation of this table:
| |
− | | |
− | ⢠Delete
| |
− | To delete a contact, click on the x and then confirm the change by clicking on âSaveâ.
| |
− | | |
− | ⢠Name, Email, Phone
| |
− | These are editable fields that contain detail information of the recipient or contact person.
| |
− | | |
− | ⢠Rate, Balance, Automatic Cut, Alert, Invoice
| |
− | A checkmark on one of these columns indicates that the recipient or contact person is to receive the designated information.
| |
− | | |
− | 12.1.7 Subscriptions
| |
− | | |
− | This table provides information about the existing subscriptions with the carrier. In the example of figure 55 there are two subscriptions with this carrier, one as provider and one as client.
| |
− | | |
− |
| |
− | | |
− | Figure 55. Subscriptions.
| |
− | | |
− | Following is a description of the fields of the table:
| |
− | | |
− | ⢠Id
| |
− | This is the account ID.
| |
− | | |
− | ⢠Subscription
| |
− | This field describes the subscription.
| |
− | | |
− | ⢠Type
| |
− | Here you see the nature of the subscription: Client or Provider.
| |
− | | |
− | ⢠Traffic
| |
− | This field describes the type of traffic thatâs being routed.
| |
− | | |
− | ⢠Rate
| |
− | This identification takes you to the table of applicable rates for the subscription.
| |
− | | |
− | ⢠Custom Rating
| |
− | This field indicates that the rates change according to specific conditions agreed. These conditions could be for example volume of minutes, time of the day when the calls are placed, etc.
| |
− | | |
− | ⢠Billing Cycle
| |
− | These are the billing terms according to the agreement.
| |
− | | |
− | 12.1.8 Invoices
| |
− | | |
− | This table summarizes the recent invoices sent to the customer. The system saves up to two months of invoicing.
| |
− | | |
− |
| |
− | | |
− | Figure 56. Invoices.
| |
− | | |
− | ⢠Id
| |
− | XXXX.
| |
− | | |
− | ⢠Prefix
| |
− | This field gives an idea of what business unit in your company is invoicing the customer.
| |
− | | |
− | ⢠Invoice
| |
− | This is the number of the invoice. The actual file is accessible by clicking on the number.
| |
− | | |
− | ⢠Invoice Date
| |
− | This field is the date when the invoice was issued.
| |
− | | |
− | ⢠Minutes
| |
− | The volume of traffic billed.
| |
− | | |
− | ⢠Invoice Amount
| |
− | This is the amount due by the customer.
| |
− | | |
− | ⢠Due Date
| |
− | The last date to submit payment
| |
− | | |
− | ⢠Accounting Date
| |
− | | |
− | 12.1.9 Documents
| |
− | | |
− | In this field you will find contractual documents or any document supporting the agreement.
| |
− | | |
− |
| |
− | | |
− | Figure 57. Documents.
| |
− | 12.1.10 Notes
| |
− | | |
− | Here you will find information or comments of any nature that help clarify the spirit of the agreement.
| |
− | | |
− | | |
− |
| |
− | | |
− | Figure 58. Notes.
| |
− | | |
− | 12.2 Trunk Management
| |
− | | |
− | | |
− | | |
− |
| |
− | | |
− | Figure 59. Trunk Management Window.
| |
− | | |
− | [4/29/13 10:58:05 AM] jorge zeppenfeldt: el base on es la manera en que el billing identificara la llamada, en este caso dice incoming TG / Outgoing trunk, es decir que factura por TG ID
| |
− | [4/29/13 10:58:22 AM] jorge zeppenfeldt: hay otras opciones como DNI Prefix
| |
− | [4/29/13 10:58:55 AM] jorge zeppenfeldt: en esos casos va a una tabla predefinida donde pones prefijos de los DNI a los cuales asignas la subscripcion
| |
− | [4/29/13 10:59:01 AM] jorge zeppenfeldt: por ejemplo
| |
− | [4/29/13 10:59:46 AM] jorge zeppenfeldt: tu puedes poner que para todo lo que venga con el codigo 57 use una subscripcion y si viene con 1 otra y asi ......
| |
− | [4/29/13 11:00:12 AM] jorge zeppenfeldt: si le dices incoming tg , te pone la subscripcion a todo lo que venga con el TG x
| |
− | [4/29/13 11:00:48 AM] Pilar Saavedra: oook capto. Abajo en esa misma ventana se definen los casos de DNI y ANI
| |
− | [4/29/13 11:01:00 AM] jorge zeppenfeldt: recuedo que tambien habia ANI prefix
| |
− | [4/29/13 11:01:01 AM] jorge zeppenfeldt: si
| |
− | [4/29/13 11:01:27 AM] jorge zeppenfeldt: el ANI prefix es coo DNI prefix pero en base al ANI
| |
− | [4/29/13 11:01:47 AM] jorge zeppenfeldt: eso lo que te dice es como aplicar la subscripcion
| |
− | | |
− | 12.3 Users
| |
− | | |
− | This section explains the user access management to the platform functionalities.
| |
− | | |
− |
| |
− | | |
− | Figure 60. User Management.
| |
− | | |
− | The Users main screen gives you a complete list that you, as an Administrator, will need to manage the profile and permissions of every user. You have access to the following information:
| |
− | | |
− | ⢠Username
| |
− | This is user identification accessing the platform.
| |
− | | |
− | ⢠Group
| |
− | This field defines the group the username belongs to. The Administrator creates a group based on a role and responsibility matrix of users.
| |
− | | |
− | ⢠Phone, Cellular Phone Number, Email
| |
− | This is the contact information of the user.
| |
− | | |
− | ⢠Op
| |
− | Click to enable or disable a user.
| |
− | | |
− | To add a new user, click on âCreate New Userâ. The following window will open:
| |
− | | |
− |
| |
− | | |
− | Figure 61. User Creation.
| |
− | | |
− | Enter essential data âUsername, First Name, Last Name, Phone, Cellular, Email- and password. Select the Group the user will belong to from a drop-down list.
| |
− | | |
− | To access detailed information about the groups that are created in the system, click on User Groups. The following window will open:
| |
− | | |
− |
| |
− | | |
− | Figure 62. User Group Information Window
| |
− | | |
− | Click on a group to retrieve specific information of it. You can see the following fields:
| |
− | | |
− | ⢠Group Name.
| |
− | ⢠Group Description
| |
− | ⢠Security - Users Groups
| |
− | ⢠Reports â The access to the different features of the platform is described here. Each group has access to specific options of the menu depending on the user profile and permissions.
| |
− | | |
− | Now, if you want to edit data from an existing user, click on the username. The following window will open.
| |
− | | |
− |
| |
− | | |
− | Figure 63. User Edition.
| |
| | | |
− | In this window you can:
| |
| | | |
− | ⢠Edit contact information -Username, First Name, Phone, Cellular, Email.
| + | '''Logout''' |
− | ⢠Edit password.
| |
− | ⢠Edit group - Add or remove the user from a group.
| |
− | 13 LOGOUT
| |
| | | |
| Clicking on Logout will take you to the login window of figure 1. | | Clicking on Logout will take you to the login window of figure 1. |