ARADIAL TECHNOLOGIES. Aradial VOIP Converged Prepaid Billing for Windows 5.x. Administrator Guide

ARADIAL TECHNOLOGIES Aradial VOIP Converged Prepaid Billing for Windows 5.x Administrator Guide

A R A D I A L V O I P C O N V E R G E D Administrator Guide 2009 Aradial Technologies Ltd. Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without a prior express written permission from Aradial Technologies Ltd. All other products are trademarks or registered trademarks of their respective owners.

Table of Contents INTRODUCING ARADIAL... 2 ARADIAL COMPANY BACKGROUND... 2 BEFORE YOU BEGIN... 3 ARADIAL VOIP CONVERGED SYSTEM... 4 GENRAL OVERVIEW... 4 ARADIAL VOIP CONVERGED BENEFITS... 4 PREPAID CALLING CARD FEATURES... 5 VOIP BUSINESS PLANNING GUIDELINES... 7 THE BUSINESS PLANNING IMPLEMENTION BY STEPS... 7 ARADIAL VOIP USER MANAGER... 8 GROUPS... 8 SUB GROUPS... 17 GROUPS TIME PERIODS... 19 USERS... 21 IMPORTING USERS INTO ARADIAL... 28 VIEWING SESSION REPORTS... 31 PRINTABLE SESSION REPORT... 35 PERIOD SET... 36 PREFIX TABLE... 40 TARIFF PLAN... 45 IMPORT RATE TABLES... 47 EXPORT RATE TABLE... 48 EXPORT PERIOD SET TABLE... 49 IMPORT PERIOD SETS TABLE... 50 PREPAID CARDS / CALLING CARDS... 52 CARD TYPES... 53 GENERATE PREPAID CARDS / CALLING CARDS... 56 MANAGE PREPAID CARDS... 61 PREPAID CARDS REPORTS... 63 CARD SESSION SUMMARY... 66 ONLINE SESSIONS AND GRAPHS... 69 ONLINE SESSIONS... 69 GRAPHS... 72 SERVER CONFIGURATION... 73 BUSINESS PARTNERS... 74 ADMINISTRATOR ACTIVITIES... 75 BUSINESS PARTNER SELF-CARE ACTIVITIES... 80 WEB SELF CARE... 89 USER SUMMARY... 90 UPDATE USER... 91 CHANGE PASSWORD... 92 VIEW SESSIONS... 93 WIFI / HOTSPOT / ISP PORTAL... 95

Chapter 1 Introducing Aradial Welcome to the All-In-One Remote Access and Prepaid enforcment Solution, Aradial! Aradial is an All-In-One Remote Access solution, allowing you to maintain a common, centralized interface for all your Remote Access needs including: Management, Authentication, Authorization, and Accounting. If you are an Internet Service Provider (ISP) Aradial will prove an essential tool for all your Remote Access (RA) needs, providing extensive RADIUS and management features, allowing you to save time and resources when managing your business. As a Corporate IT professional who maintains the corporate remote access facilities, Aradial aids in maintaining a common, centralized administration kit which brings together all RADIUS, management, and analysis tools you will ever require. This manual will set you on the right track, whether you are a system administrator for an ISP or an IT professional in a corporation, to unleash the awesome power of Aradial and tailor it for your specific needs. Aradial company Background Aradial RADIUS solutions have been servicing large and small ISPs since 1997, with NASDAQ traded ISPs trusting their RADIUS needs with Aradial RADIUS infrastructure. Aradial RADIUS is high performing with Tier 1 levels of reliability and scalability. Aradial RADIUS supports the latest RFCs, vendor specific attributes, NAS templates and has a multitude of pre-configured settings that support most Access Servers in the market today. Aradial offers products that open a whole new set of possibilities for ISPs and Hot Spot (WiFi), ASPs, Wireless LAN and large corporations. Utilizing open standards such as RADIUS and SNMP and EAP, and innovative technologies such as VPN and LDAP, the Aradial product family offers unmatched features and performance at an affordable price. Aradial RADIUS solutions are installed in over 30 countries* supporting services such as: (* As a Radius server and as a part of billing solution). Wi-Fi hotspots and Wireless ISPs DSL, Cable, ISDN, Dialup

Voice services over IP PPPoE and VPN internet access (both terminating and distributor RADIUS server roles) Rented Infrastructure (such as the one provided by Quest, Verizon, BT) Content Subscriptions Internet Kiosk and Internet Café Aradial Ltd's premier product is the Aradial product family and, a state of the art, RADIUS server. The Aradial comes in few configurations: Small operators Medium operators Large scale operators (Tier 1) Before You Begin This manual is intended for both first time and experienced Aradial users and comes as an addition to the Aradial Manual document. If you are a first time user, please take time to read Aradial Manual (administrator guiide) before reading this document. This manual will aid you in understanding the logic of Aradial VOIP converged system in order to use its full potential. Not doing so might cause undoing and redoing some procedures just because you might find in each chapter better and faster ways of putting your thoughts and needs into practice. If you are an experienced Aradial user, you may use this manual as a reference guide when using your system. Please notice that a lot of work has been put into Aradial and this manual, yet in some cases the manual might prove outdated, just because it was printed or added to the distribution CD before some new features have been added to Aradial. If you encounter new features or changes in Aradial which are missing from this manual, please refer to Aradial s Internet web site at http://www.aradial.com which will always include all latest information regarding Aradial, whether it is new features, updates to the software, or new information regarding vendors supporting RADIUS (hence supported by Aradial). If you still have questions after reading this manual, and you are not able to find the information in our Internet web site. Please contact us by: Email: support@aradial.com

Chapter 2 Aradial VOIP Converged System Genral Overview Aradial VOIP Converged system gives operators the ability to provide real time IP sevices and end-to-end customer management, balance management and real time enforcment to their users with a fully controlled and flexible engine to support on-demand changes. Aradial VOIP converged system supports the following: IVR Calling Direct calling using ANI / Calling cards User name Peering Termination and origination The above features are supported in two charging methods: Single sessions method: all balance is allocated for the user during the session in order to enable maximum balance use and allow the user to use his whole balance. In that case only START and STOP sessions are sent to Aradial by the router. The sesion rate will be done based on the start time. Multi session method: the session is splitted into quotas of time and the balance is shared between multiple users using the same balance. Aradial will allocate initial quota (default quota size is 120 sec, configurable) and when the user has no balance for 120 quota's Aradial change dynamically the quota size to 10 seconds in order to use maximun available balance. The session will be rated by the LAST quota time (period). Aradial VOIP converged benefits This chapter will describe the benefits Aradial VOIP converged system will provide to the service providers. Centralize authentication and accounting for all the routers or gateways Converged services: VOIP, Dial-up, Wifi and ISP Broadband/DSL support on the same platform SSL secured HTML based administration

User and calling cards management Dealer/Business partner management. Dealers can manage their own users Extended HTML UI for user database and groups of users High-performance and reliable server Scalable to handle millions of users and concurrent sessions on a low-end hardware Support for most of VOIP gateways on the market User Self care module Calling card management, rating, importing and exporting (CSV files). Balance, Duration and Traffic enforcement User concurrency enforcement and viewing concurrent calls from the administration tool Support for multi-session calls using balance management (Quota management). HTTP API for external systems and customization External billing system interface using stored procedures or CORBA Support for multiple Admin types Admin activity tracking Prepaid Calling Card Features Authentication, authorization, accounting (AAA) and real time VOIP prepaid Convergent prepaid billing Dial-up, DSL, Wireless LAN, Mobile and VOIP Full prepaid system for Mailvision, Alcatel, Cisco, Quintum, NexGe, Mera, Telrad gatekeepers/sip gateways and many others. Calling Card based prepaid billing. Calling card generation importing and exporting. ANI based (caller id) VOIP prepaid billing.

Rating according to call destination. Different rounding intervals per tariff or per destination. Call Setup cost. Rating according to time of day, day of week. Replenishing API or voucher refilling (*) with Spotngo Payment module. Support multiple Tariffs and destination rating tables that can be assigning for a calling card. Session reports and summary reports per calling card, per system, per destinations and periods. Optional module :Termination billing including wholesale credit limit and fraud control

Chapter 3 VOIP business planning Guidelines The following chapter will describe the business flow and the guidelines to implemet Aradial VOIP converged in the right order with the explenations and links between the objects. The business planning Implemention by steps When you want to start implementing Voip services for your users you should follow the following steps: 1. Implement new period sets: As a preliminary step you should first define the period sets the system will work with. For detailed information please refer to the user manager chaper, period set section. Aradial also support rating with no period sets (rate will be done by default rate per min). 2. Implement prefix tables: As a default Aradial comes with 10 prefix tables. You should populate the table/tables with the relevant information (e.g. default rate, period set, rounding rules, etc). for detailed information please refer to the user manager chaper, prefix tables section. This activity can be done either manually or by using Aradial import/export functionality. 3. Implement tariff plans: Create tariff plans and associate them with specific prefix table. This is a mandatory step as the tariff plan will be associated with the user in the user registration. For detailed information please refer to user manager chapter, tariff plan section. 4. Generate users / Calling cards: generate users or calling cards and associate them with specific tariff plan. This is basically the user/calling card creation and price plan definition per user. Generation can be done one by one manually or by generate batch process. For detailed information please refer to user manager chapter, generate users section. 5. Run Sessions: at this point the users are ready for use and Voip calls can be made using the above implementation (rate per destination, using periods, based on tariff plan, etc). 6. View online / offline sessions: Operator will be able to view the online and offline sessions in Aradial GUI interface. For detailed information please refer to User manager and online sessions chapters. 7. Updates (Optional): updates can be done at any time to the above objects (e.g. period sets, tariff plans, prefix tables). For detailed information please refer to user manager chapter.

Chapter 4 Aradial VOIP User Manager Adding Users and Groups. Whether your network should satisfy one hundred customers all sharing the same service, or tens of thousands of users each with his own requirements and setting, Aradial user manager can handle the heat. The very simple, yet very powerful User Manager allows you to prepare yourself and Aradial for whatever needs you and your customers may require. Groups By using Groups, you will be able to apply a common connection model to sets of users. A Group allows you to define connection settings such as the type of service granted to each user within that Group, use sets of IP addresses, also known as IP Pools, limit the number of simultaneous users which may connect at one time, and apply NAS filters, which are access lists defined on the NAS and which may be applied to each user while logging in. To the ISP, Groups are of great importance, as they allow him to assign specific services to each user, and the ability to limit the maximum simultaneous user sessions. To the corporate administrator, Groups are essential in terms of QoS and resource management, as he is able to limit the number of simultaneous sessions for each group, and manage his IP address space better. To both, the Group s ability to assign a filter to the connecting user, will allows them to define which content the user may access. The Groups page may be reached from the Administrator interface by clicking User Manager > Add/Edit Group. The Edit page of Groups displays the following information, if any Groups have been set up:

Name Which displays the name of the Group. By clicking on the name of the appropriate Group, you may edit its properties. Service The type of service granted to users in this Group. IP Pools The IP Pools used by this Group, if any. Remote IP The IP address to which a user is connected if his service type is Telnet or RLogin. Filter The filter name, as stored in the NAS, to use for the Group, if any. Filters are access lists that are administered and maintained on the NAS, and may be assigned to the user when he logs in. Please review your NAS documentation in order to understand filters better, and how to create/administer them on your NAS notice that your NAS documentation may refer to filters as Access Lists or ACLs for short. Max Sessions The maximum number of simultaneous sessions allowed for this Group. A number of 0 (zero) means there is no limit. Max User Sessions The maximum number of simultaneous sessions each single user may conduct. A number of 0 (zero) means there is no limit. Action Where the possible actions are displayed. For Groups possible actions are: Delete By clicking on this link, if the Group is not in use by any user, it may be deleted. Sub Groups The two links under Sub Groups will allow you to manage Sub Groups under the specified Group. Possible actions for Sub Groups in this page are: View Which may be used to view all Sub Groups in the specified Group. New Which may be used to add a new Sub Group to the specified Group. Time Periods By clicking on the links in this column you can define Group settings based on the time of day and day of week. Time Periods are discussed thoroughly later in this chapter.

The Add page of Groups will allow you to add a Group, using the following parameters: Group Name Enter the name you wish to set for this Group. This name will be used to reference the Group. Service Type Select the type of service you wish to grant users in this Group. Password Source Select the Password Source for the users in this Group. By using this, the user password may be set to be acquired from ARADIAL (i.e. the user database), OS (i.e. Windows SAM), LDAP (i.e. your LDAP server), or SecurID (i.e. your ACE\Server). The default value for Password Source is <Users>, which tells ARADIAL to use the Password Source defined for each user (instead of using the one in Group). Active Which displays if users in this Group may access your network. IP Pools Enter the names of the IP Pools that should be used by this Group. Notice there are three reserved values for IP Pools: NAS Which tells the NAS to provide an IP address to the user. User Which tells the NAS that the user provides the IP address. DHCP Which tells Aradial to request and IP address from a DHCP server, and provide that IP address to the user. Notice that if no IP Pool is specified, Aradial defaults to NAS, meaning the IP address is to be set by the NAS.

You may specify a number of IP Pools by using a semicolon (;). For example an entry of Pool1;Pool2 will tell Aradial to use IP Pools Pool1 and Pool2. You may also define the same IP Pool in two different Groups. Aradial will automatically manage the specified address space. Notice that this is not possible when using one of the reserved type (i.e. NAS, User or DHCP) Notice that while the USER and NAS reserved types functionality are built in the basic Aradial, DHCP is not, so using it without the proper licensing will contribute nothing. Remote IP Use this field to specify the IP address to which a user using Telnet and RLogin services should login into. Filter If a filter (or an access list) has been created on your NAS (consult your NAS documentation), you may apply the filter to the Group by specifying its name here. Custom Attributes You may use this field to set custom RADIUS attributes to users in this Group. The format of attributes that may be entered here is Attr1=Val1,Attr2=Val2.Attrn=Valn where: Attr is the custom RADIUS attribute reference value you defined in the NasCfgDbs Services section. Val is a valid value that should be set for the RADIUS attribute. For example, if you have defined a an attribute named My-Attribute-1, with the value of $MyAttr1 (e.g. MyService:My-Attribute-1=$MyAttr1), you should set the following for the Custom Attributes field: $MyAttr1=value, where value is the value that attribute should receive. Multi Session as MultiLink Use this checkbox to tell ARADIAL that two or more simultaneous session by a user in this Group should be regarded as a MultiLink connection, so the ARADIAL handles this kind of requests correctly. Note that this option is used in connection with IP Pools to ensure that a MultiLink session will not be allocated a new IP. Maximum Simultaneous Group Sessions You may set here the number of simultaneous sessions that may be conducted by the Group. Notice that leaving this field empty, or specifying 0 (zero) will allow unlimited concurrent sessions. Maximum Simultaneous User Sessions You may set here the number of simultaneous sessions that may be conducted by each individual user. Notice that leaving this field empty, or specifying 0 (zero) will allow unlimited concurrent user sessions.

Notice that each User session is also counted as a Group session. For example: two Users from the same group conducting two sessions each are counted as four Group sessions. Session Timeout This time is a configuration to send to the NAS in Access response. This is a global session timeout for the group. The causes Aradial to send session-timeout attribute to the NAS. Every session from this group will be terminated according to the MAX time entered. If Session-timeout is defined for the group the Metering and time to Expiration will not work! Idle Timeout This time is a configuration to send to the NAS in Access response. NAS can detect that a user does not have any traffic in the network and after this time it will automatically terminate the session. The value is sent in Idle-Timeout (28) RADIUS attribute. Due to the fact there are daemons running on the client machine they might generate traffic and this Idle timeout will not be applied. However, if the user shuts down the client or machine the NAS will detect it. Business Entity You may set here the business entity that the group belong too. The group will be enforced from the Business Entity self care, not to allow other Business Entity to register users to this group. Auto Expire Policy and Auto Expire Time when a user loggins to the system the account expiration will be automatically set to the time defined. Note: The enforcement for the auto expiry happens from the second session. Meaning the initial time is not calculated and sent to the RADIUS. In the second session, the timeout for the session is calculated until the expiration time and sent to the NAS. Account Start Date the date and time from which the group will be activated. Account End Date the date and time the group expires. Empty means never.

Enable Callback Check this checkbox to allow callback to your users (notice the callback number is in the user add/edit page). Callback is common in corporate remote access, where the corporation pays for the connection, or for additional security by making Aradial call back only to a specified number. CallerID Template You may use this for higher security. If this field is not empty, only users whose CallerID matches this template will be able to log into your system. The CallerID may be either the users telephone number or the users IP address. The template may be composed from any digit 0-9, periods (.), and may include wildcards. The wildcards allowed are * (asterix) and? (question mark). The asterix matches any sequence of characters (zero or more). Event Scripting Aradial permits you to execute your own programs (or third party ones) based on accounting events. The currently supported events are: After Adding A User Execute Which executes the program specified in this field when a new User is added to this Group. After Removing A User Execute Which executes the program specified in this field when a User is removed from this Group. On Password Change Execute Which executes the program specified in this field when the password of a user in this Group is changed. After De-Activating A User Execute Which executes the program specified in this field when a user in this Group is deactivated (Active unchecked). After Re-Activating A User Execute Which executes the program specified in this field when a user in this Group is reactivated (Active rechecked). Notice that Event Scripting will not be applied to existing users that have been moved from one Group to another.

Event Scripting Parameters Event Scripting allows you, besides specifying a program to execute when an event occurs, to pass parameters to that program. The parameters you may use are any column in the Users and the UserDetails database tables, in the format of @db_tablename.column@: Table Name Column Format and Description Users UserIndex Number. The index number of the user in the database. Users UserID String. The User ID. Users Password String. The user password. Notice that this may be encrypted, thus unreadable by external programs. Users GroupName String. The name of the Group the user is in. Users UserService Number. The number represents the service this user is granted, in case of an override of the Group settings. The meaning of this number may be found in the NAS Configuration Database, described in Appendix D. Users UserIP Number. This is the override for the Group Remote IP parameter. Users FilterName String. The name of the filter applied to this user, as an override to the Group Filter value. Users UserExpiryDate Date. The expiration date of this user. Users UserActive Bit. This will return 1 or 1 if the user is active, or 0 if the user is not. Notice that the number returned for a true value (Active) is subject to the database interpretation of true (either 1 or 1). Users CallBackNumber String. The number to call if callback is enabled on your system. Users StartDate Date. The date in which the user account was (or will be) activated. Notice that dates may have special parameters, which are described later in this section. Users CallerID String. The CallerID template the user must match to login. UserDetails UserIndex Number. The index of the user in the database. UserDetails FirstName String. The first name of the user. UserDetails LastName String. The last name of the user. UserDetails Company String. The company name of the user. UserDetails Address1 String. The first address line. UserDetails Address2 String. The second address line. UserDetails City String. The user city. UserDetails State String. The user state. UserDetails Country String. The user country. UserDetails Zip String. The user Zip code. UserDetails PhoneHome String. The user home phone number. UserDetails PhoneWork String. The user work phone number. UserDetails PhoneFax String. The user fax number. UserDetails Email String. The user Email address. UserDetails CreateDate Date. The user creation date (i.e. the date in which the user was added to your database). Notice that dates may have special parameters, which are described later in this section. UserDetails LastModify Date. The date in which the user account was last modified. UserDetails CustomInfo1 String. Custom information field 1 value. UserDetails CustomInfo2 String. Custom information field 2 value. UserDetails CustomInfo3 String. Custom information field 3 value. UserDetails CustomInfo4 String. Custom information field 4 value. UserDetails Comments String. The comments entry. In addition, the following parameter are availible: @Password@ - An unencrypted password, availible only in case of creating a user or modifying his password @Param:xxx@ - Any input HTTP parameters sent from the Hts request. @ParamGet:xxx@ - Any input HTTP parameters with get format. @ServerParam:xxx@ - An HTTP server parameter. Event Scripting Guidelines When using Event Scripting, keep in mind that the scripting command is passed to Windows, thus is as limited as any command given to Windows. One obvious limitation is the

number of characters that may be passed, which is 256 for Windows 95/98 (DOS limitation), and 1024 for Windows, meaning that if the total command length you are running is longer then 256/1024, characters it will be truncated. In the base directory of Aradial, there is an example script named example.bat. This example script will output any number (as long as it does not exceed the 256/1024 character limitation) of variables to your Windows root hard disk, to a file named example.out. To test this script, just put in the appropriate field, specify the variable you would like to export. For example: using example.bat UserID:@db_Users.UserID@ FirstName:@db_UserDetails.FirstName@ LastName:@db_UserDetails.LastName@ will output the User ID, his first and last name as shown in Figure 3.1: This example shows what the output file, example.out, will contain after a user has been added, with a User ID of JohnDoe, first name John and last name Doe. example.bat UserID:@db_Users.UserID@ FirstName:@db_UserDetails.FirstName@ LastName:@db_UserDetails.LastName@ rbsexample.out file UserID:JohnDoe FirstName:John LastName:Doe Figure 3.1: Event Scripting Example Event Scripting Special Variable Denominators The following denominators, or tags, may be used to format Event Scripting variables: @[D{xyz}]db_TableName.Column@ - [D] is used for special date formatting, where x,y and z are used to define the date, month and year, in any order. Possible values for x, y and z, in no specific order (you may change the order and set which field, date, month and year is displayed first, then second and third): D The date, with no leading zeros. DD The date, with a leading zero (when needed). M The month number, with no leading zeros. MM The month number, with a leading zero (when needed) MMM{MMM} The first three letters of the month name. Any added m s will result in an additional letter of the month name. Y - The year, with no leading zeros. YY The year, with leading zeros (when needed, after the year 2000) YYY{Y} The last three digits of the year. Any additional y s will result in an additional digit of the year. You may use any character as a separator, except for the reserved D, M, and Y upper case letters.

Notice that all date tags must be upper case letters. Some examples of date tagging: @[D]db_TableName.Column@ - This is the most basic entry. The output is MMDDYY (e.g. February 22 nd, 1999 is 022299) @[DMMM-DD-YYYY]db_TableName.Column@ for August 7 th, 2001 is Aug-07-2001. @[DYY+D+MM]db_TableName.Column@ for June 3 rd, 2002 is 02+3+06. @[length]db_tablename.column@ - you may use any number before the db_ to enforce a maximum length on the outcome value. For example, @[4]db_TableName.Column@ will truncate the output to four characters. For example: A telephone number based Caller ID of 555*22 will accept users from any telephone number starting with 555 and ends with 22. An IP address based Caller ID of 192.110.*.* will accept users from any IP address starting with 192.110., any number, a period and another number. The question mark matches any single character. For example: A telephone number based Caller ID of 555555? will accept users from any telephone number between 555-5550 to 555-5559. An IP address based Caller ID of 192.110.100.10? will accept users from any IP address starting between 192.110.100.100 and 192.110.100.109. Notice that CallerID must be supported by your local telephony services (for telephone number CallerID) and by your NAS (for both telephone number and IP address CallerID). Example: Suppose your company wishes to provide two types of services - For the Development Team restricted access to PPP Services, by applying the Access List NoFTP stored on your NAS. For the Accounting Department up to 6 simultaneous Telnet sessions for the entire group, and up to 2 simultaneous sessions per user, to a computer with the IP address of 192.168.10.12. Create the Development Team Group first -You should:

Enter Aradial Administrator interface and click on User Manager>Add Group. When the Add Group page opens, you should enter the information as follows: For the Group Name field, pick a name that will help you later to identify the group, such as DevTeam. In the Service Type selection box, select PPP. In the Filter field, enter the name of the Access List you wish to use, in this case - NoFTP. Leave the Maximum Group Sessions and Maximum User Sessions empty, to allow unlimited sessions by this group and its users. Click the Submit button to create the new group. Now create the Accounting Department Group - you should: Enter Aradial Administrator interface and click on User Manager > Add Group. When the Add Group page opens, you should enter the information as follows: For the Group Name field, pick a name that will help you later to identify the group, such as AcctDept. In the Service Type selection box, select Telnet. In the Remote IP field, enter the name of the host computer for the Telnet service you specified in the Service Type Selection. In this case, enter 192.168.10.12. Set the Maximum Group Sessions to 6 and the Maximum User Sessions to 2. Click the Submit button to create the new Group. Sub Groups Sub Groups enable you to create an environment in which a user is granted service based on his location. Sub Groups require the presence of at least two NASes in your environment, as the user location is determined by the NAS he is calling. In a Sub Group setup, the user is checked not only by his User ID and password, but also by his location (or rather, by the NAS he is coming from). Based on the different NASes through which the user may be connecting through, he is assigned to a Sub Group, which may alter the parent Group settings, and apply new ones. As stated before, Sub Groups may be accessed from the main Group edit page, in which you may select to view or add new Sub Groups, by clicking on the links in the appropriate parent Group. The view Sub Group page, much like most hit pages, will display the existing Sub Groups information:

Name Which displays the name of the Sub Group. By clicking on the name of the appropriate Sub Group, you may edit its properties. Service The type of service granted to users in this Sub Group. IP Pools The IP Pools used by this Sub Group, if any. Remote IP The IP address to which a user is connected if his service type is Telnet or RLogin. Filter The filter name, as stored in the NAS, to use for the Sub Group, if any. Max Sessions The maximum number of simultaneous sessions allowed for this Sub Group. A number of 0 (zero) means there is no limitation. Max User Sessions The maximum number of simultaneous sessions each single user may conduct. A number of 0 (zero) means there is no limitation. Action Where the possible actions are displayed. For Sub Groups possible actions are: Delete By clicking on this link, the Sub Group may be deleted. The new Sub Group page, much like most add pages, will allow you to add new Sub Groups to the Group by specifying the following information: NAS Name - This selection box displays the NASes you have configured. Select the NAS for which this Sub-Group should be applied. Users in the parent Group, accessing through this NAS will use the properties set in this Sub Group.

The rest of the settings in Sub Groups are equivalent to Group settings, and may be used to override the parent Group settings. Groups Time Periods Group Time Periods enable you to set the Group environment based on the time of day and day in week. In a Group Time Periods setup, you can set what kind of access (if any) the user should be granted. Should you omit a time period, the default Group settings will be used. As stated before, Sub Groups may be accessed from the main Group edit page, in which you may select to edit the Group Time Periods. The edit Group Time Periods page is used to both view and edit the Group Time Periods table, if there are no Group Time Periods set, Aradial will report this, and you will have the option to add Group Time Periods. If any Group Time Periods were set, the following will be displayed: Day(s) The day(s) in week which the Group Time Period covers. By clicking on this value you may edit the Group Time Period values. Start Time The time in day(s) which the Group Time Period covers. End Time The time is day(s) after which the Group Time Period ends. Max Sessions The maximum number of simultaneous sessions allowed in this Group Time Period. A number of 0 (zero) means there is no limitation. Max User Sessions The maximum number of simultaneous sessions each single user may conduct in this Group Time Period. A number of 0 (zero) means there is no limitation. Disallow Access This field displays if users are allowed or denied access on the Group Time Period.

Action Where the possible actions are displayed. For Group Time Period possible actions are: Delete By clicking on this link, the Group Time Period may be deleted. Add Period By clicking on this button, you can add new Group Time Periods. After clicking on this button, you may set the following for the Group Time Period: Day checkboxes Use these to set which day(s) the Group Time Period covers. You may click the All or None buttons in order to check or clear all day checkboxes, respectively. Start Time Use this field to set the time in day(s) which the Group Time Period should cover. End Time Use this field to set the time is day(s) after which the Group Time Period ends. Disallow Access Check this check box in order to deny access at the set Day(s), between the Start Time and End Time. The rest of the settings in Group Time Periods are equivalent to Group settings, and may be used to override the parent Group settings.

Users A user, by definition, is a person you wish to grant access to, who, by connecting to a NAS, requires authentication from Aradial. If that person does not have a user record in your database, he will not be able to access your network. Notice that there is an exception to the previous statement. NT and LDAP users do not have users records in the Aradial database, yet, when using NT or LDAP as your primary or secondary database, they will be able to access your network. The Users page may be reached from the Administrator interface by clicking User Manager > Add/Edit User. The Query page for users displays the following search fields: User ID Use this field to search for users with a matching User ID. First Name Use this field to find users by their first name. Last Name Use this field to find users by their last name. Advanced Search By clicking on this link, you will access an advanced user search page, which will allow you to find your users by values other then available here. Historical Data Present data from history table for users that were deleted. Printable Report The result will be formated for printing and not as a regular table. Export to file export the search result to file.

If any users corresponding to your query were found, the following will be displayed in the Edit page: User ID The User ID is the handle with which the user connects to your system. First Name The users first name. Last Name The users last name. Group Name The Group applied to the user. Time Bank the left time for the users sessions (Metering). MB Bank the traffic left in MB. Balance the balance for calls that is left in the account. Expirtation Date the time the user will expire. Actions Email By tagging the appropriate checkboxes, and clicking the Email button, you may send an email to users. Delete By tagging the appropriate checkboxes, and clicking the Delete button, you may delete users.

Global Actions Allows to tag all the users presented on the screen or reverse the tagging. The Add page of users will allow you to add new Users, using the following parameters: User ID Use this field to set the user handle required for accessing the network. Password - This field holds the user password required for accessing the network. Active - Use this checkbox to activate or deactivate the user account. A deactivated user, although still in the user database, will not be able to access the network. Force Password Use this check box to allow the usage of a weak password. You may force a weak password only if it is higher then the Minimum Password Score set in the Advanced Configuration page.

Group Name - Use this selection box to select a Group for the user, setting his access parameters accordingly. CallerID - Use this field to add a security check based on a user's caller ID. The caller ID may be supplied by the NAS in the forms: Phone Number- if the NAS port is connected to a modem, it will inform Aradial of the dialing in phone number (where supported by both telephone company and the NAS). IP Number - if the NAS port is coming through a network, it will inform Aradial of the incoming IP number (where supported by the NAS). MAC Address the MAC address of the machine. Aradial will compare between the NAS supplied caller ID and this field, and if matching, it will allow the user to log in. You may use wildcards in the Caller ID field, thus allowing the user multiple points of origin. Wildcards supported are: * - Matches any sequence of characters (zero or more). For example: a Caller ID of 555*22 will accept users from any phone number starting with 555 and ending with 22.? - Matches any single character. For example: a Caller ID of 555555? accepts users from any phone number between 555-5550 to 555-5559. Callback Number - Use this field to specify the number which should be called back when the user logs in. Under some circumstances, you may wish the NAS will call back the user, thus the user will not have to pay for the phone bill. This may also be used as a security feature the user will only be able to access the system through the phone number specified here. Admin Type Use this checkbox to set the level of administrative rights the user has when accessing the Administrator Interface. The default value of <NONE> will disallow users from accessing the Administrator Interface. There are several admin types: <None> = regular user Co-Admin another admin user Tech Support enable to create / update users but not to configure the system Dealer Business entity has a special admin panel to manage users registered to it. API special user that is used to link between Aradial to external systems. Reviewer allowed seeing the online users. Business Entity - Use this selection box to select a Business entity for the user, setting his access parameters accordingly.

Notice that business entity user, used for Business entity self care must be selected to the business entity and also the Admin Type for the user should be Dealer User Creation Date - This field displays the date in which the user has been created. Last Modified - This field displays the date in which the user was last modified. User Activation Date - This field displays the date from which the User is (or will be) allowed to access your network. You may change the value of this field, so a user, although in the user database, will be able to connect only after the set date. User Expiration Date - This field displays the date in which the User has (or will) expire. Service Type - This selection box allows you to override the Service Type defined for the Group this user is a member of. Password Source This selection box allows you to override the Password Source defined for the Group this user is a member of. When using this override, the user password may be set to be acquired from ARADIAL (i.e. the user database), OS (i.e. Windows SAM), LDAP (i.e. your LDAP server), or SecurID (i.e. your ACE\Server). The default value for Password Source is <Group>, thus telling ARADIAL to retrieve this setting from this user s Group. Remote IP If the service type of the user, or his Group, is Telnet or RLogin, use this field to override the host to which the user should connect. When using a framed service such as SLIP, CSLIP or PPP, you may use this field to set a static address for the user (i.e. each time the user connects, he will have the same IP address). Filter - You may use this field to specify the use of an access list or filter which is stored on the NAS. In case the user Group already contains a Filter value, the Filter value here will allow you to override it. Custom Attributes You may use this field to set custom RADIUS attributes to users in this Group. The format of attributes that may be entered here is Attr1=Val1,Attr2=Val2.Attrn=Valn where: Attr is the custom RADIUS attribute reference value you defined in the NasCfgDbs Services section. Val is a valid value that should be set for the RADIUS attribute. For example, if you have defined a an attribute named My-Attribute-1, with the value of $MyAttr1 (e.g. MyService:My-Attribute-1=$MyAttr1), you should set the following for the Custom Attributes field: $MyAttr1=value, where value is the value that attribute should receive. First Name - The user's first name. Last Name - The user's last name.

Company - The user's company name. Email - The user's Email address. This address will be used to override the default Email address when sending reports and invoices to the User. The default Email address for a user on your system is UserID@Mail.Server, where Mail.Server is defined by the SMTP Host setting in the Server Configuration>Adv. Configuration page. Address, City, State, Country, Zip Code, Home Phone, Work Phone, Fax - The user's contact information. Metering Money This field can be used to give the user a starter amount in the registration process. Actually, this is the customer balance and the available money he has in his account. The field can also be updated by the CSR in order to update the customer balance and/or refill his account. Credit Limit The field is used for balance enforcment. As part of the registration the CSR is requested to fill in the credit limit value. Aradial will enforce the credit limit in the user real time sessions. Example: The customer has a 10$ balance. His credit limit is 0. meaning the user will be able to use his 10$ before Aradial engine will reject his sessions. The credit limit can also allow the customer to enter into debit. The CSR is able to update the user credit limit at any given time. Tariff ID The tariff ID is a combo box presenting the available tariff IDs in Aradial system. As part of the registration the CSR is requested to fill in the Tariff ID. The selected value is actually linking to specific tariff which will be rated based on the selected tariff ID. By this field Aradial support flexible and multiple tariff rates and enable the operators to provide different sets of rates per users / Groups. ISP / Hotspot metered Bank Time this field holds the maximum time the user would be allowed to surf. When this time is depleated the user will not be able to login again.

Traffic - this field holds the maximum traffic for upload and download the user would be allowed to surf. When this bank is depleated the user will not be able to login again. Enforce Time and Traffic check boxes if to enforce the banks. Note: certain routers support traffic limit within a session, like Mikrotik, Chillispot, Nomadix, Colubris and others. In such cases Aradial will send the traffic limit to the router that would disconnect the users close to the breaching of the traffic limit. The configuration/script is in the Metering.tcl script. Custom Information - These fields may be used to store any custom information you wish to keep about the user. Comments - Use this text box to store general information regarding your user. Note that although only the User ID, Password, and Group Name are required fields, it is a good management strategy to store as much information as possible regarding your user.

Importing Users into Aradial Aradial allows you, as discussed previously, to create new user accounts either by using the Administrator interface, through the Add/Edit User page, or by the New User interface, by filling the New User form. Aradial also allows you to import users from existing sources such as Windows and various types of text files, including UNIX passwd/shadow files, Livingston RADIUS for UNIX user files and comma separated variable (CSV) files. Importing OS / Windows users By using Aradial to import Windows users, you may achieve two tasks. One is a common security model, achieved by the fact that Aradial not only imports Windows users, but also maintains the link to the source Windows user, by using Windows passwords as the user password under Aradial. This means that if the user password is changed on Windows, the change will be maintained in Aradial, and vice versa (i.e. a Windows user password changed from Aradial will also update Windows). The second is time saving, as you will not need to add existing users manually into Aradial. Aradial refers to Windows users as OS users, and this term will be used now on. The Windows Import page may be reached from the Administrator interface by clicking Server Configuration > Data Management > Import OS Users. Notice that this page, although related directly to Accounting, is placed under the Server Configuration button. This derives from the fact that importing users is not a routine operation and is more of a system management nature. The Import OS Users page requires the following information: Computer from which to import This selection box will list all Windows machines in your Windows domain. Usually you will import the users from your Primary Domain Controller (PDC)/Backup Domain Controller (BDC), as these are usually the machines that are used to store user accounts in a Windows domain. NT Group to import This selection box will list all available global (i.e. available in your NT domain) NT groups from which you may import users. By selecting a specific group, instead of All, you may import OS users from the specified group.

Group to assign This selection box will list all Groups you have configured, and you may select which Group should be assigned to the imported users. Perform Event Script after adding a user Check this checkbox in order to perform the script for adding new users (if defined), as set in the Group to which you are importing the users. When importing OS users, Aradial does the following: The Windows username field is used as the OS user User ID. The Windows Full Name field is broken down at the first space character and used as the OS user First Name and Last Name. The Windows Description field is used as the OS user Comments. The Windows Password is not copied to Aradial as it is encrypted, instead, Aradial maintains a link to that password by placing the letters OS in the OS user password field. Note that currently, if you break the password link (i.e. change the password from OS to anything else), Aradial will no longer check with Windows the user password. After the import is done, Aradial will inform you if the import was successful: n users were successfully added: The number of OS users successfully added to Aradial by the import process. n users were already in the database: The number of OS users that were already in Aradial database prior to the last import, thus were not added. n users were not added due to errors: The number of OS users that were not added due to unknown problems. A name list of all users that were not added to Aradial database will be listed under Users not added due to errors. Importing Text File Users Importing users from text files to Aradial may prove to be a great time-saver. As most ISPs and corporate administrators keep, in one way or another, their users database on UNIX or a database that can create a CSV file, this will prove to be a fast and easy way to add those users to Aradial without consuming the time it takes to add users manually. The text file User Import page may be reached from the Administrator interface by clicking Server Configuration > Data Management > Import Users. Notice that this page, although related directly to Accounting, is placed under the Server Configuration button. This derives from the fact that importing users is not a routine operation and is more of a system management nature.

The Import Users page requires the following information: Local File Name Enter the full path and file name of the file from which the users should be imported. You may use UNC (i.e. \\machine\sharedname\path\filename) or local path (i.e. drive:\path\filename). Notice that the path and filename are relative to the machine running Aradial. A local path/name will be stored on that machine. File Type Select the file type from which the users should be imported. Importable file types are: UNIX Passwd file A file, common on UNIX machines, which usually resides in the root etc directory and contains User IDs, encrypted passwords and full name of the user. UNIX Shadow file Another common user/password file on UNIX systems. Livingston RADIUS file The legacy users file used by Livingston s RADIUS for UNIX. Comma Separated Variables file Any text file in a format of user ID,password,full name,comment. Group to Assign This selection box will list all the Groups that were configured, and you may select to which Group should the imported users should be assigned. Perform Event Script after adding a user Check this checkbox in order to perform the script for adding new users (if defined), as set in the Group to which you are importing the users. After the import is done, Aradial will inform you if the import was successful: n users were successfully added: The number of text file users successfully added to Aradial by the import.

n users were already in the database: The number of text file users that were already in Aradial database prior to the last import, thus were not added. n users were not added due to errors: The number of text users that were not added due to unknown problems. A name list of all users that were not added to Aradial database will be listed under Users not added due to errors. Viewing Session Reports View Sessions page may be reached from the Administrator interface by clicking User Manager > View Sessions. The Query page of View Sessions displays the following information: Report Type Select the type of Sessions Report you wish to see: Individual Sessions or Sessions Summary. The Individual Sessions report will display the user(s) sessions sorted by time

of login. The Sessions Summary report will display a cumulative report for the time and bandwidth the user consumed throughout the sessions he conducted. Subtype select if the summary report would display all the users or just users that have sessions. User ID - Enter the User ID, whose sessions you wish to see, in this field. If the Start Date and End Date fields are left empty, Aradial will list all sessions for the User ID specified. From Date - Enter the starting date from which to look for User Sessions. The date format is DD-MM-YYYY or MM-DD-YYYY, depending on your regional settings. If the User ID field is left empty, all the users sessions between the From Date and To Date will be displayed. To Date - Enter the end date up to which the sessions should be searched for. The date format is DD-MM-YYYY or MM-DD-YYYY, depending on your regional settings. If the User ID field is left empty, all the users sessions between the From Date and To Date will be displayed. Business Entity List only users that belong to the Business Entity selected. Destination The prefix of the location / country the call was placed. MAC Address/Caller ID based on the Caller-Station-Id attribute or the Caller ID Defined In User list only user s sessions that the CallerID that contains the value (MAC, Phone). Defined In Session list only sessions that the CallerID that contains the value (MAC, Phone). List only users that have thbelong to the Business Entity selected. Ascending - sort the report retults accending by date. The default is dscending. Historical Data show only users that are achived. Printable Report show the report a long formatted HTML to enable printing it to printer. Export To File - send the results to CSV file. After clicking on the Search button, a list of sessions, in case there are any, will be displayed, along with the dates in which the session took place. The Individual Sessions page will display the following information:

User / Card This field displays the User ID or the calling card number which was used for the session. By clicking on the User / Card, you will display the user / card information page. Client IP display the client IP address information for the specified session. NAS Port This field displays to which NAS port the user connected when the session took place. Notice that not all NASes provide this information. In case your NAS does not, this field will be blank. Local start time the field specify the session start time (for both single and multi sessions method). Connect time - specify the time the connection was done. Duration this field specify the session accumulated duration. Caller ID the caller ID for the session can be MAC address or phone. Destination the call DINS for VOIP session.

Code this is the termination code of the session. 10 means session terminated nornally. Please review the VOIP gatway specific termination codes. Call prefix the field specify the call prefix was dialed by the user. The prefix is found by Aradial by a best match mechanism and fetched from the prefix tables. Rounded The field specify the rounded session duration based on the rating rules. Rate per minute the field specify the rate per minute as fetched from the prefix table. Charge the field specify the total cost of the session. The Sessions Summary page will display the following information: User / card This field displays the User or calling card number for the session. By clicking on the User / card, you will display the user/card information page. Total calls the field will display the total count of calls per user or calling card. Total Hours - This field displays the overall duration of all included sessions. ACD Avrage call duration. ASR the ratio between succesful / completed calls, with duration, out of all the calls. Cost the field disply the total cost of all sessions per user or calling card based on the search criteria. Group Name This field displays to which Group the user or calling card belongs to.

Example: From Date The date from which sessions has been included in the summary report. No Start Date value means all sessions until the End Date were included. To Date The date to which sessions has been included in the summary report. No End Date value means all sessions from Start Date until now were included. Suppose you wish to look up all sessions that took place between June 15 th, 1997, and June 16 th, 1998 by your user, JohnDoe: Enter Aradial Administrator interface and click on User Manager>View Sessions. When the View Sessions page opens: Select the type of report you wish to see, either Sessions Summary or Individual Sessions. Enter the User ID in the User ID field, in this case, enter JohnDoe. Enter the Start Date and End Date to set the range of time in which Sessions should be searched for. In this case, enter 06-15-1997 and 06-16-1998, respectively. Printable Session Report Session report can also been presented in printable mode. Once marking the 'printable report' flag the following session report will be presented and available to be printed.

Period Set A period set divides the time of day and the days of the year into segments, for example, Peak, Off Peak, Night, Holiday, Weekday, Christmas, New Year, and so forth. After configurating the period sets, Aradial can base the decision for the rating plans based on specified period set. A cross period session (session started in period1 and ended in period2) will be rated based on the following algorithm: Single session method: Aradial is configured by default to work in a single session method, nonmultisessionvoipmetering.tcl (please refer to rate methods in chapter 1 ), then the session time for Period set will be rated based on the session start time. Multi session method: If Aradial confugre to work in a multi session method, using Multi Session TCL (please refer to rate methods in chapter 1), then the session time for Period set will be rated based on the last quota beginning time. The period set page can be found under the Aradial Voip converged main screen User manager Period set. Two optionas are available: Edit will allow the user to view the existing period sets and also enable editing the period set details. For more details please refer to the below screen shot and explanation. Add - will allow the user to add new period sets. For more details please refer to the below screen shot and explanation.

Add option: The Add period set screen allow the user to add new period sets. The following fields are available: Period set name: This field indicate the period set name. free text field which allow the user to set the name. If spliting specific period set to more than one period, then all entities must have the same period set name. This Period name will be used later when configuring the rates in the Prefix Table for the period name. From day: allow the user to divide the weeks into days and split specific period set for certain days and/or the whole week. The user will be requested to choose day from a drop down list. The from date field will indicate the day the period set is starting from. Please note: The week starts on Sunday 00:00 and end on Saturday 23:59 One can not set a period to Start Monday and end Sunday. This should be split to two periods. Money -> Saturday Saturday -> Sunday To day: allow the user to divide the weeks into days and split specific period set for certain days and/or the whole week. The user will be requested to choose day from a drop down list. The to date field will indicate the day the period set is ended. From time: allow the user to split the day into hours and minutes. The user will be requested to insert start time where the specific period set is starting from. Please note: the start time date format is: hhmm with no (':') between them. To time: allow the user to split the day into hours and minutes. The user will be requested to insert end time where the specific period set is ended.

Please note: the start time date format is: hhmm with no (':') between them. Please note: Time can not be split between days: e.g. 18:00 -> 02:00 illegal. Need to do: 18:00 -> 00:00 00:00 -> 02:00 Period ID: This field is assosicate specific period (e.g. Peak, off peak, etc) with the created period set. One period set can have more then one period. This Period will be used later when configuring the rate in the Prefix Table for the period. Edit option: The Edit option will allow the user to view all exisitng period set and enable editing them. The following fields are available in the opened screen: Name: display the period set name as inserted in the period set creation. When the screen show more than one period set with same name it means that the specific paerid set is using more than one period. Days range: the field specify the date range used in the soecific period set. The 'from date' and 'to date' value in the period set creation. Time range: the field specify the time range used in the soecific period set. The 'from time' and 'to time' value in the period set creation.

Period ID: the field show the used period (e.g. peak, off peat, etc) for the specific period set. Action: the action field enable the user to delete existing period set. Pressing on the delete link will pop up warning massage and ask for the user confirmation. Once approving the massage the period set will be deleted from and will no longer be used. When the user would like to edit existing period set, he should press on the Name field and the following page will be opened: The opened screen will present the existing data for the period set and will allow the user to add / change details and save them.

Prefix Table Prefix tables reference tables which define the rates and other important information which can be used by Aradial as part of the rating process. The rates are used in Authentication to calculate the session timeout (when to stop the session by the VOIP gateway) and in STOP session to charge the user. The prefix table also hold a default entity for non-exist prefixes which allow Aradial to rate the calls by default rates. There is a special entery in the prefix table where the prefix is Default. If a call comes with an unknown destination (the best match did not find an entry) the Default entry is used. It contains the cost, round1, round2 and rate per minutes that will used as default. If the default entity doesn t exist in the prefix table such session will be rejected in the call authentication. The prefix table page can be found under the Aradial Voip converged main screen User manager Prefix table option. Please note: Aradial VOIP converged system comes with 10 prefix tables as a default in order to support VOIP rating based on the criteria will follow in the below chapter. However, more tables can be added by demand without coding. Edit page: The edit page will present the existing prefixes tables and will allow the user to add or edit information in the specified tables. The following fields are available: Name: specify the prefix table name. The name can be changed in a table in the database called: RateNames.

Action: as mention above, allow the user to add or edit information in the prefix table: Add: the following screen will be opened and allow the user to add one new single entity to the table: Access Number: the access number field allows to qualify rates by access number (in addition to destination prefix). Prefix: The holds the call prefix for specific destination. The prefix table is used as part of the rating process to best match which destination was called. The prefix will give the ability to support with different charges for each destination and allow 'rate by destination' functionality. Example: 1 means USA, 1212 means USA/New York. When one is calling 1212, New York rate will be chosen for the rating. Destination name: the field is holding the destination name. With this information Aradial will be able to view the sessions with the destination details. Default rate per minutes: The field holds the default rate per minute for specific destination. Although the default rate is per minutes Aradial can rate sessions by seconds. Please note that this is a default rate which might be overiden by periods rate. Round1: This field specify the first rounding interval in the session. By this field you can decide the minimum rate per session. Example: if the round1 is 30 seconds, that means that the user will be charged for 30 seconds minimum regardless of the session duration is less than that. Example: 12 call duration would be rounded to 30 seconds. Round2: This field specify the next rounding interval in the session. By this field you can decide the quotas for rating after the first interval. Example: if the round1 is 30 seconds and round2 is 12

seconds, that means that the user will be charged for 30 seconds minimum regardless of the session duration. After the first 30 seconds of the session the customer will be charged in 12 seconds. Example: 39 call duration would be rounded to 30+12=42 seconds. Period set name: Allows the user to choose one of the existing period sets and associate it with specific destination in the prefix table. Rate for period 1: This filed is holding the rate per minutes for specific period name. Please note that specific destination can support few rates for different periods. In addition, the rate for period is overiding the default rate. Rate for period 2: This filed is holding the rate per minutes for specific period name. Rate for period 3: This filed is holding the rate per minutes for specific period name. Edit: the following screen will be opened once pressing on the Edit button and allow the user to search specific entity based on the prefix and access number in the table: If inserting a prefix and/or access number then the search will be done based on the inserted value. Aradial supports adding % to select by wild card. E.g. 33% all numbers beginning with 33% (detinations to France). Pressing on the search without inserting prefix will present all entities in the prefix tables.

The following fields and activities will be available: Prefix: presenting the prefix per entity. Clicking on the prefix itself will open the entity screen and will allow edit / change the record. Access Number: presenting the access number per entity. Destination: The field will present the destination per entity. Rate per minute: the field will present the default rate per minute for specific entity. The default rate can be overiden by rate1-3 fields if defined. Round1: This field specify the first interval in the session as inserted in the entry registration. This value overide the interval value in the tariff level. Round2: This field specify the next interval in the session as inserted in the entry registration. This value overide the interval value in the tariff level. Period set name: the field specify the period set the entity is using. Rate for period 1-3: The period rates in the entity level as were inserted in the period set registration. These rates will overide the default rate. Action: this link allow the user to delete specific entity (specific prefix) from the prefix table. Please note: Aradial supports also rating for SIP usernames. When the VOIP session, Called- Station-Id will be populated with domain/user or domain@user a best match will be done by Aradial and run the rating. The domain will be used same as a prefix. Please note: IP addresses can also be used for Aradial rating same as prefixes.

Partial IP addresses can also be used. For example: Initial IP address 192.168 can be defined as a prefix. When Aradial get Called- Station-Id start with the above prefix it will be rated.

Tariff plan The tariff plan is the price plan that the customer associated with. When creating user in Aradial the Admin or Generate users/calling cards, will be requested to associate the customer with specific tariff plan. The tariff plan is linked to specific prefix table (reference table) which is storing the rate and rating rules per destination (please refer to the prefix table section) as well as other rating rules which will be described in the below sub-chapter. The tariff plan page defining can be found under the Aradial Voip converged main screen User manager Tariff plan option The tariff plan has the following options: Add will allow the user to define a new tariff plan, associate the tariff with specific prefix table and define the rating rules. The following fields are available in the 'add tariff' page: Tariff plan name: free text field to define the tariff plan name. the tariff name will be used once creating new user in order to associate the tariff with the user. Tariff table name: This field is a drop down field which will present the available prefix tables and will point for the rates per destination. Tariff plan can be linked with one prefix table. Setup cost: This field enable the operator to define a setup cost ( Toll ) per call for users who will use the mentioned tariff plan. This is a fixed setup cost which will be added to the cost rate. Interval round 1: The field is used to define the first rounding interval for the call. The interval is a unit which the customer will be rated based on it. This parameter can be overriden at the prefix table.

Interval round 2: The field is used to define the first rounding interval for the call. The interval is a unit which the customer will be rated based on it. This parameter can be overriden at the prefix table. Description: free text field to indicate the tariff description. Edit - will allow the user to view and edit existing tariff plans. the following fields are available in the edit tariff page: Name: specify the tariff plan name as insetered in the tariff creation. The tariff name is also use as a link to edit the tariff plan details. Pressing on the tariff name will open the tariff in edit mode and allow the user to change the tariff plan details (see above screenshot). Setup cost: this field display the setup cost per tariff plan as registered in the tariff creation. Round1-2: this field display the round (intervals) date per tariff plan as registered in the tariff creation. Tariff table: this field display the associated prefix table as registered in the tariff creation. Description: this field display the tariff plan description as registered in the tariff creation. Action: allow the Admin to delete a tariff plan. Clicking on the delete will pop up a warning massage to confirm deletion. Warning: there is no check if users have this tariff prior to deleting.

Import Rate tables Aradial VOIP converged allows the operator to easily maintain and load data into the reference tables (prefix table). Aradial support 'Import Tariff table' for prefix tables connected with tariff plans in the system. For the prefix tables connected with tariff plans the operator can load new reference data and backup the previous data via GUI interface. Aradial is also able to restore the backup table in case a rollback is needed. The changes are effective immidiatlly and the user rating plan is reflected on the action time. The 'import tariff table' page can be found under the Aradial Voip converged main screen Price Plans Import Rate table option. The following options are available in Aradial GUI interface: Local file name: This field should get the full path for the input file to import. The import file should be a CSV file containig all 9 prefix table fields (excluding the Action field which is not holding a value). Here is an example from a csv file with data to import: Default,,All others,0,30,60,set1,0.01,0.03,0.05 Default,1,All others,0,30,60,set1,0.01,0.03,0.05 9370,1,Afghanistan Cellular,0.18,30,60,Set2,0.01,0.03,0.05 9379,1,"Afghanistan,Cellular",0.18,30,60,Set1,0.01,0.03,0.05 9371,2,"Afghanistan,Cellular-Others",1,30,60,Set2,0.01,0.03,0.05 9372,2,"Afghanistan,Cellular-Others",1,30,60,Set1,0.01,0.03,0.05 9373,2,"Afghanistan,Cellular-Others",1,30,60,Set2,0.01,0.03,0.05 9374,,"Afghanistan,Cellular-Others",1,30,60,Set1,0.01,0.03,0.05 9375,,"Afghanistan,Cellular-Others",1,30,60,Set2,0.01,0.03,0.05

9376,,"Afghanistan,Cellular-Others",1,30,60,Set1,0.01,0.03,0.05 9377,,"Afghanistan,Cellular-Others",1,30,60,Set2,0.01,0.03,0.05 9378,,"Afghanistan,Cellular-Others",1,30,60,Set1,0.01,0.03,0.05. The fields are in the same order as appear in the prefix tables GUI (e.g. Prefix, AccessNumber, Destination, Rate per min, round1, round2, PS name, rate1, rate2, rate3). Table name: This field will present the available reference tables (prefix table) the user can load. The drop down will present only prefix tables connceted with tariff plans. Prefix table which are not connected with any tariff plan will not be presented in the GUI drop down. Backup table name: Aradial will automatically create backup for the replaced prefix tables. When the user is loading (importing) new data into specific prefix table, Aradial will backup first the old data. This field will automatically get the prefix table name and will add "_BAK" extention to the file name. this is saved for history needs and also to restore in case of rollback is needed (see below restore option). Import: The Import button will start the import process to load the new data into the prefix table after populating all needed information. Restore: As mentioned above, Aradial support for restore process in case a rollback is needed. Backup is always saved for the previous version. Meaning 1 history version is saved. This button will start the restore process after populating the relevant fields. Export Rate Table Aradial VOIP converged allows the operator to easily maintain and export data from a reference tables (prefix table). Aradial support 'Export Tariff table' for prefix tables connected with tariff plans in the system. For the prefix tables connected with tariff plans the operator can export the reference data and backup the previous data via GUI interface. The 'Export tariff table' page can be found under the Aradial Voip converged main screen Price Plans Export Rate table option.

The following options are available in Aradial GUI interface: Output file name: This created file should get the full path for the input file after export is endded succesfully. The oprtation generate CSV file containig all 9 prefix table fields (excluding the Action field which is not holding a value). Here is an example from a csv file with exported data: 1 1800228846366 USA / Canada 0.0071 0 0 0 1242 Bahamas 0.1541 0 0 0 1246 Barbados 0.2248 0 0 0 1264 Anguilla 0.3441 0 0 0 1268 1212777899934 Antigua & Barbuda 0.3441 0 0 0 1268464 Antigua & Barbuda Mobile 0.3441 0 0 0 126872 Antigua & Barbuda Mobile 0.3441 0 0 0 126877 Antigua & Barbuda Mobile 0.3441 0 0 0 1284 Virgin Islands (UK) 0.7148 0 0 0 1340 Virgin Islands (US) 0.6966 0 0 0 1345 Cayman Islands 0.1911 0 0 0 The fields are in the same order as appear in the prefix tables GUI (e.g. Prefix, AccessNumber, Destination, Rate per min, round1, round2, PS name, rate1, rate2, rate3). Export period set table Aradial VOIP converged allow the operator to easily maintain the period sets as well as importing and exporting data into csv files. The 'Export Period Set Tables' page can be found under the Aradial Voip converged main screen User manager Export Period Set Tables option

The following fields / activities are available: Output file name: By default this field will get the Periodset.csv file name however the user can change it. This is the output name to save the period sets. Export: Once pressing on the Export button the export activity will start and ask the user for the path to save the file. The output csv file will contain header with the column title and the period sets information as appear in Aradial database. This is en example from periodset.csv file: "SJO",1,7,0,1800,1 "SJO",1,7,1800,2400,2 "Set1",1,7,0,1800,1 "Set1",1,7,1800,2400,2 "Set1",1,7,0,1800,1 "Set2",1,7,1800,2400,2 "SAL",2,6,1800,2300,1 "SAL",2,6,700,1800,2 "SAL",2,6,2300,700,3 Reset: The reset button will allow the user to reset the output file name in case he changed it. Import period sets table Aradial VOIP converged allow the operator to easily maintain the period sets as well as importing and exporting data into csv files. The 'Import Period Set Tables' page can be found under the Aradial Voip converged main screen User manager Import Period Set Tables option

The following fields / activities are available: Local file name: this field should get the full path for the input file to import. The import file should be a csv file containig all period sets fields. Backup table name: Aradial will automatically create backup for the replaced Period sets table. When the user is loading (importing) new data, Aradial will backup first the old data. This field will automatically get the name of "Period_Set_Bak". this is saved for history needs and also to restore in case of rollback is needed (see below restore option). Import: The Import button will start the import process to load the new data into the period set table after populating all needed information. Note when exporting a period set the header if exported. Before importing make sure to remove this header or delete it after the import. Restore: Aradial supports restoring the last period set table in case a rollback is needed. Backup is always saved for the previous version. This button will start the restore process after populating only the Backup Table Name, without the file name, effective immediatly.

Chapter 5 Prepaid Cards / Calling Cards Aradial supports unlimited card / user types and allows operators to generate massive bulks of prepaid cards or users. The following features are supported by Aradial prepaid cards: Unlimited numbers of card types Card types management (add, edit, remove) Generate prepaid card batches Full batches life cycle management Manage prepaid card batches Prepaid cards summary and detailed reports Card sessions summary Support and view historical data

Card Types The Card type page can be found under Aradial main page Prepaid Cards Card Types option. The card types allows the operator to define a set of prepaid card templates, which allow easy batch generation later on. The card type entity supports a set of definitions at the card level. Adding Card Type page: Card Type: a free text field which allows to set the card type name. The card type will be used once generating batches of prepaid cards and actually provides a segmentation capability for prepaid cards. Time Bank: holds the number of seconds at the card type level. When generating prepaid cards batch using a specific card type, the related value in the time bank will be used for the generated cards and will be enforced by Aradial. Predefined values can be selected from the drop down, however, you are allowed to fill any free value by choosing the "other" option. Traffic Bank: holds the number of MB at the card type level. When generating prepaid cards batch using a specific card type, the related value in the traffic bank will be used for the generated cards and will be enforced by Aradial. Predefined values can be selected from the drop down however, you are allowed to fill any free value by choosing the "other" option. Card Length: specifies the card ID length.

Password Length: specifies the card password length. Password Symbols Set: a combo box which allows the user to set the password symbols. The possible values are: Alpha numeric, digits only, capital and numbers, alpha numeric readable and custom which allows the user to define and customize rules in Aradial configuration. Enable Password: selects whether the generated cards will have a password (Yes) or will not have a password (No). In case of no password, the cards will have a password source of No Password. User Name Type: decides whether to create the user names / card ID in sequential order or random order. Card Price: Set the card price. When generating the prepaid cards, the user will be able to choose a price from a predefined list or set his own price by choosing the 'other' option. Group Name: defines the group name to be associated with the created users at the card type level. Business entity: allows a business entity association. Choosing a business entity means that all created cards will be registered under the chosen business entity. Edit Card Type page: The edit page displays all existing card types and allows opening and editting certain details. Card Type: the card type name. Clicking on the card type will open the selected card type in edit mode and allow changes.

Time Bank: the value for the time bank Card Length: the value for the card length Password Length: the value for the password length Price: the value to print on the card. It is not, nessasary the balance that the card contains. Default Group Name: the value for the selected group name Tarrif ID: the card type Tariff ID. Business Entity: the value for the card business entity (or None if no business entity was selected)

Generate Prepaid Cards / Calling Cards The Generate prepaid cards page allows the user to generate batch of prepaid cards or adding prepaid cards to an existing batch using predefined card types or by creating new prepaid cards. The user has full control over the batch parameters and input values which allows high flexibility.

Generate calling cards from card type: Card Type: allows creating a batch of prepaid card using predefined card types. The combo box will present the avaialble card types. When selecting a specific card type, the related attributes will automatically be populated. The Card type is not mandatory and the user may generate a batch using his own parameters and not using the predefined card type. For such cases, the user will be requested to fill in all input parameters for the prepaid card generation. Number of Prepaid Cards to Generate: specifies the number of cards to be created. Enable Password: selects whether the generated cards will have a password (Yes) or will not have a password (No). In case of no password, the cards will have a password source of No Password. Batch Prefix: selects the prefix to be used for the generated cards. The same prefix will be used for all created cards. Cards Batch: specifies the batch to which the cards will be assigned. You have an option to generate prepaid cards with an existing batch by selecting a batch from the combo box field, which presents the available batches in the system. For a new batch you should use the 'None' value and fill in a new batch name.

Number of Seconds: number of seconds to be included in the cards time bank. You can select a value from a predefined combo box and also specify any other value by selecting the 'other' option and specifying the value. Number of MegaBytes: number of MB to be included in the cards traffic bank. You can select a value from a predefined combo box and also specify any other value by selecting the 'other' option and specifying the value. Card Number Size: the size of the generated card. This is also the user ID which will be used for the user authentication. Expiration Date: allows setting an expiration date for the cards. Blank value means no expiration date. Create Active: weather to create the cards as active (and ready for use) or not. Active cards are ready for use while non-active cards require manual activation (please refer to the Manage section). Password Symbols Set: a combo box which enables to set the password symbols. The possible values are: Alpha numeric, digits only, capital and numbers, alpha numeric readable and custom which allows the you to define and customize rules in Aradial configuration. User Name Type: decides weather to create the card ID in a sequential order or a random order. Start Number in Range to Generate: the field specifies the start number to be used after the batch prefix. For example: batch prefix A with start number 10000 and card length 6 will generate the following cards: A10000, A10001, etc Card Price: specifies the card price. Will be filled automatically when using a predefined card type. This price will be the selling price for the card. Balance: The balance for calls to generate for the calling card. This balance can be diffrenct than the selling price. Password Size: specifies the password size to created for the cards. Tarrif ID: the Tarriff ID to put on the card. Selecting None means the card is not for calls but for Data. Group to Assign: specifies the group the cards will be created under. Business Entity: specifies the business entity the cards will be created under. Return Detailed Results: checking this flag means that the generated prepaid cards will be presented on the screen after the operation is completed. Export to File: checking this flag means that the generated prepaid cards will be exported into a CSV file after the operation is completed.

The following screenshot present a batch using a predefined card type where part of the fields are automatically set and disabled: Once populating the cadrs details and pressing on the 'Generate' button, the process will be executed and a batch of prepaid cards will be created based on the input parameters. Detailed result page: Card ID: the created card ID which is also the user ID based on the input parameters (batch prefix and start numbers based on card length)

Password: created password based on the input parameters (digits only) Card Batch: the card s batch Card Type: the card type saved for querying. Time Bank: the time bank value MB Bank: the MB bank value Card Price: the card price value Balance: the card balance to be used for calls. Expiration Date: the expiration date if exist. Empty field means no expiration date Group Name: the associated card / user group Action: allows deletion of prepaid cards. Deleted cards will be kept in the historical repository.

Manage Prepaid Cards The manage prepaid cards menu provides the user with full control over the batches and prepaid cards and supports status changes in various cases. Perform Operation: the field is a combo box which allows several options to be executed at the batch or card level. The following options are available: Activate allows activation of batches / cards. The option is available for batches / cards which were created as non-active. Deactivate - allows deactivation of batches / cards. The option is available for batches / cards which are in active status only. Delete - allows deletion of batches / cards. The option will be available for batches / cards which are in active or deactive status. The deleted cards will be kept in the history repository. Batch: allows filtering based on a spefic batch. The list presents the available batches in the system. Card ID: allows to operate on a single card. You need to populate the card ID. Business Entity: allows filtering based on a business entity. Card Type: the combo box presents the available card types and allow filtering based on it. For example, when multiple batches are using the same card type.

Active: allows filtering based on the card status. Card price: allows filtering based on the card price. Create date: allows filtering based on creation date. Available values are: is after, is before or is (equal). Start date: allows filtering based on start date. Expiration date: allows filtering based on expiration date. Available values are: is after, is before or is (equal). The following page presents an example for deactivating cards belonging to a specific batch: The list of cards that will be impacted by the operation is presented and you should press on the Confirm button to approve the operation to perform. Once pressing on the confirm button an approval massage will be displayed.

Prepaid Cards Reports The prepaid cards reports page allows to to generate detailed or summary reports for your prepaid cards. The following page allows you to define the criteria's for the reports: Report Type: allows selecting between a summary report and a detailed report. Summary report will present summaries at the batch level Detailed report will present details at the card level. Batch: allows filtering based on a specific batch. For example: when you want summary report for a single batch you need to choose the batch name from the combo box. Card ID: allows filtering based on a card ID. Business Entity: allows filtering based on a business entity. Card Type: allows filtering based on a card type. Active: allows filtering based on the card status. Card Price: allows filtering based on card price.

Create Date: allows filtering based on card creation date. Available values are: is after, is before or is (equal). Start Date: allows filtering based on card start date. Available values are: is after, is before or is (equal). Expiration date: allows filtering based on card expiration date. Available values are: is after, is before or is (equal). Export to File: when marking this flag you will be able to export the report details into a CSV file. Printable Report: when marking this flag you will be able to view the report in an output screen in printable format. Print option will be available for you. Summary report output page: Batch: the batch name. In case no batch name was used in the batch generation, the field will remain empty. The summary report displays a single line per batch. Business Entity: the business entity the cards were created under. When no business entity was selected in the cards generation, the field will remain empty. Total Cards: total cards in the batch (all statuses). Active cards: total of active cards in the batch. Non Active Cards: total of non active cards in the batch. Total Price: total price for all cards under the selected batch (cards in all statuses). Active Price: total price for all Active cards in the batch.

Detailed report output page: Batch: the batch the prepaid card belongs to. Card ID: the card ID. Price: the price for the single prepaid card. Action: allows marking the prepaid card for deletion. Deleted cards will be kept in the history repository.

Card Session Summary The card session summary page allows you to gather statistic and view detailed or summary reports for prepaid card sessions. The following page allows you to define and set the input parameters for your reports: Report Type: the report type field is a combo box presenting the available batches in the system. The field allows you to retrieve results for a specific batch. Report Subtype: the field specifies weather to present session lookup report for cards with sessions only, cards without sessions or both. Card ID: the field allows you to specify single card ID and hence present session details for a single user. Date: the from and to fields allows you to filter your sessions based on a range of dates. Business Entity: allows you to filter sessions for a specific business entity. The combo box will present the available business entities in Aradial. Ascending: when marking this flag, the output results will be presented in ascending order. Historical data: when marking this flag, the output results will present also historical data (for deleted prepaid cards). Printable Report: when marking this flag, the output results will be presented in prinable format. Print button will be available on the screen

Export to File: when marking this flag, the output results will be exported into a CSV file. The following screenshot presents an output for cards related to a specific batch which have sessions: Card ID: the card ID the line is refering to. Clicking on the card ID hyperlink will connect you to the related user page. Total Sessions: the number of total sessions the card has. Group name: the group the card is associuated with. Total Hours: the total hours used for the selected card in all sessions. Total in MB: the total in MB used for the selected card in all sessions. Total out MB: the total out MB used for the selected card in all sessions. From Date: the date of the first session for the selected card. To Date: the date of the last session for the selected card. Action: allows you to drill down for a detailed report for selected card. The following is a detailed report for selected card:

Online Sessions and Graphs Chapter 6 Understanding Aradial Online Sessions and Graphs. Aradial, by manipulating extensive amounts of data, is able to display, in real time, information about your server such as online users, maximum sessions, logins, online time and more. This information is available through three different pages: Online Sessions This page, available by clicking on the Online Sessions button in the Administrator interface, displays users online information such as the User ID, the originating NAS and port, and online time. Graphs These pages, available by clicking on the Statistics button in the Administrator interface and selecting the required graph, displays information such as maximum sessions, logins, online time and revenues on a daily, weekly, monthly and yearly basis. Online Sessions You may configure the way in which the information is displayed: Poll Every - The Poll Every selection box allows you to set the update time for the Online Sessions page. The default value for Poll Every is Manual, meaning you have to click the Update Now button (described below) in order to update the page. Other values are in seconds, so if you select 10 Seconds, the Online Sessions page will automatically update itself every 10 seconds.

Sort By - The Sort By selection box allows you to alter the way in which the information is sorted. The default value for Sort By is NAS Name, meaning all information will be sorted by NAS Name. You may change this value to Online Since, which shows at what time a user connected, Time Online, which shows how long a user has been connected or User ID. Ascending - Use this check box to set the direction in which the information is sorted by - lower to higher value fashion (a-z, 0-9) or a higher to lower fashion (Z-a, 9-0). Lookup User(s) Use this text box to specify a user name. By using this checkbox, you can narrow down the list of online users, and see if a specific user is currently connected. You may also use in this field the % wildcard for user lookup, for example: looking up the user A% will narrow the online users list to just the User Id that begin with A. Update Now - Click the Update Now button to update all information on the page, sorting it by the values you have set in the Sort By selection box and the Ascending check box. The following are the information fields displayed in the Online Sessions page: User ID - This is the User ID of the user connected to the system. Click on the User ID in order to access User Edit page, which allows you to view and edit the user information. NAS Name - This is the name of the NAS to which the user is connected to. Click on the NAS Name in order to access the Edit NAS page, which allows you to view and edit the NAS information. NAS Port - This is the port number on the NAS the user connected to. This number is supplied by the NAS. As not all NASes support this feature, this field may be blank. Online Since - This field displays when the user initiated his connection to your network.

Time Online - This field displays for how long has the User been connected to your network. Service - This field displays the type of service the granted to the User and optionally, based on the type of the service, which IP address has been assigned to the user, or which IP was he telnted/rlogin into. Caller ID: the field displays the user caller ID which might use as a security check based on a user's caller ID. The caller ID may be supplied by the NAS. Destination: displays the call DINS for VOIP Action Available actions for the Online Sessions page are: Passive Disc. By clicking on this link, you are able to passively disconnect a user. A passive disconnect means that the user will be reported to Aradial as disconnected, even if still connected to the NAS. You should use this option only in cases where your NAS has shutdown before issuing an Account-Stop packet to Aradial, thus Aradial still regards the user as online (in which case, the user may not be able to login again).

Graphs You may select which graph to display after clicking on the Statistics button: Max Sessions This graph displays the number of maximum concurrent sessions established by your users on a daily, weekly, monthly, and yearly basis. You may choose to generate the graph by All, which displays the overall sessions, regardless of the user groups or NAS of origin. By Group, which displays the amount of sessions established by each user group, or by NAS, which displays the information based on the origin NAS. Logins This graph displays the number of concurrent logins by your users on a daily, weekly, monthly, and yearly basis. You may choose to generate the graph by All, which displays the overall number of logins, regardless of the user groups or NAS of origin. By Group, which displays the amount of logins by each user group, or by NAS, which displays the information based on the origin NAS. Online Time This graph displays the overall amount of time spent online by your users on a daily, weekly, monthly, and yearly basis. You may choose to generate the graph by All, which displays the overall amount of time online, regardless of the user groups, or by Group, which displays the amount of time online used by each user group.

Chapter 7 Server Configuration Please referer to the generic Aradial RADIUS Maunal guide.

Chapter 8 Business Partners Using Business Partners in Aradial. A Business partner is an individual or organization that registers customers and sells the company s products in exchange for a commission. Aradial supports the following Business partner functionality: Administrator activities: Registration of Business partner View/Edit/Delete business partner entities View/maintain business partners list Add users under specific business partner Register Admin dealer user (Dealer admin user) Dealer self-care activities: Login as pre-defined business partner Specific main screen and user manager for business partner login Register single user by business partner Generate bulk of users by business partner Dealer portal to view/maintain and manage their own customers. Search sessions for specific business partner View online sessions for specific business partner

Administrator Activities Registration of Business partner The Add/Edit Business entity page can be accessed from Aradial main screen User Manager Business Entity screen. The page will allow registering new business partner or editing existing business partner. The Add/Edit page of Business partner displays the following information,: Business Entity Name Contain the name of the Business partner. This is a mandatory field and requiered as part of the business partner registration. Type Specify the type of the business partner (e.g. Dealer). Company Informational text field to indicate the company name for the business partner. Contact First Name Informational text field to indicate the business partner contact first name. this is an optional field.. Contact Last Name - Informational text field to indicate the business partner contact last name. this is an optional field.. Address Informational text field to indicate the business partner address details. this is an optional field.. City Informational text field to indicate the business partner City details. this is an optional field..

State - Informational text field to indicate the business partner State. this is an optional field and need to be choosen from drop down list. Country Informational text field to indicate the business partner Country. this is an optional field and need to be choosen from drop down list. Zip - Informational text field to indicate the business partner Zip. this is an optional field. Phone Informational field to indicate the business partner phone number. this is an optional field. Email - Informational field to indicate the business partner Email address. this is an optional field. View/Edit/Delete Business partner entities The View/Edit/Delete Business partner entity page can be accessed from Aradial main screen User Manager Business Entity Edit button. The page will allow to view the currentl registered business partners in a summary view, delete business partner and view specific business partner details. The View/Edit/Delete page of Business partner displays the following information,: Business Entity List: Name Display the business entity name as was inseerted in the business partner registration. Type Display the business entity type as was inseerted in the business partner registration

Company Display the business entity Company name as was inseerted in the business partner registration Created Display the sysdate the business partner was registered to the data base. Last Modified Display the sysdate for the last change was done on the business entity details (any field on the business partner entity). Action Allow do delete specific business partner. Please note: Only non-used business partner will be allowed for deletion. Business partners with active users / sessions will be forbidden from this activity. Aradial will block the option to delete used business partner.

Add users under specific business partner (from the administrator portal): The Add/Edit user page can be accessed from Aradial main screen User Manager Business Entity Add button. The page will allow to register user as described in chapter 2 (User Manager chapter). Aradial support registration of user related to a pre-defined business partner. Aradial distinguish between two type of registration under the business partner:

Registering Dealer Admin user under business entity: The ascription to the business partner will be done using the 'Business Entity' field. The ' Business Entity' field will display the list of registered business partner and will allow connecting the user under specific business partner. The ' Administrative Rights' field will set the user as an Admin user and will allow access to the business partner self-care module. Registering regular user under business entity: The ascription to the business partner will be done using the 'Business Entity' field as described above. The ' Administrative Rights' field should not be used for regular users.

Business Partner Self-Care Activities Login as pre-defined business partner Once a business partner will access Aradial portal page he will be requested to enter his user name and password. User Name Should be identical to the User Id' registered in the Admin user under the business partner. The user name is case sensitve. Password - Should be identical to the 'Password' registered in the Admin user under business partner. The password is case sensitve. Aradial will validate the user name and password details and authenticate or reject the admin user login to the system.

Admin Dealer main screen The Admin Dealer main screen page can be accessed from Aradial access portal Using the Admin dealer user name and password. In the Admin main screen you may find the following links: User Manager The user manager will be detailed described in the next figure. This is limited user manager that will allow specific activities related to the loged-in business partner only. Online sessions - The Online sessions option will be detailed described in the next figures. This is limited Online sessions that will allow viewing sessions related to the loged-in business partner only. Prepaid Card managment managing prepaid cards that only belong to the dealer. User Lookup

The User Lookup screen will allow the logged-in Admin dealer user to view/maintain and manage his own customers (e.g. users regsited under his business partner entity). The search screen is identical to the generic User Manager search screen as described in chapter 2 however, the Dealer self-care screen will limit the admin dealer user to search his own users only. Dealer Options under the User Manager menu The Admin Dealer main screen page can be accessed from Aradial access portal Using the Admin dealer user name and password User Manager. the opened screen will present the available options / activities allowed for the admin dealer user and not the full list of options as appear in system admin user. User Add/Edit Allow the admin dealer user to Add / search / view / update his own users. The 'Business Entity' field will not presented in the registration form and will be populated by default with the log-in admin user details. View Sessions The view sessions option will allow the admin dealer user to view / Search the sessions related to his business partner. The view sessions will be details described in the next figures. Back to Main Will return the admin delaer user to the main screen. Online help The Online help button will follow the admin dealer user to an online web Aradial help menu.

User list under the Business Partner The User List page can be accessed from Aradial access portal Using the Admin dealer user name and password User Manager Edit. The Users screen will present the list of users under the looged-in business partner and based on the search criteria. The screen and the presented output fields are details described in chapter 2 under the User Manager chapter. The Users page allow the business partner to view / edit / search / maintain his own customers as well as to send emails or do specific actions (e.g. reserve, delete, etc) as described in chapter 2 under the User Manager chapter.

Add single user under the business partner The Add/Edit User page can be accessed from Aradial access portal Using the Admin dealer user name and password User Manager Add. The opened screen is the same as described in charpter 2 under the User Manager chapter with the following exception: 'Business entity' field is not presented. The value for the business entity is set automatically to the looged-in business partner and there is no need to set it manually. 'Administrative Rights' field is not presented. This field is not relevant for regular user and therefore is not presented when user is registered by Admin dealer user.

Generate Calling Cards and Prepaid Cards under the business partner

View sessions for business partner Search screen The Session Lookup page can be accessed from Aradial access portal Using the Admin dealer user name and password User Manager View Sessions. The opened screen is the same as described in charpter 2 under the User Manager chapter with one exception: The screen will present the sessions related to the logged-in business partner only and will not present sessions related to other business partner in the system.

View sessions for business partner Results screen The Session Result page can be accessed from Aradial access portal Using the Admin dealer user name and password User Manager View Sessions. The opened screen is the same as described in charpter 2 under the User Manager View Sessions chapter and will present the sessions for the logged-in business partner only.

View Online sessions for business partner screen The Online Sessions page can be accessed from Aradial access portal Using the Admin dealer user name and password Online Sessions. The opened screen is the same as described in charpter 2 under the Online Sessions chapter and will present the sessions for the logged-in business partner only. The filters, sort orders, refreshing methods and presented values are the same as described in charpter 2 under the Online Sessions chapter

Chapter 9 Web Self Care Using Aradial s User s Web-Self-Care. Aradial provides a Wifi portal which is a web-based application that enables customers and users to browse and manage their own accounts. The portal can be customized to suit any provider's look and feel. With Aradial self care application, authorized users will have the following activities: View the user summary View user balances Update user details Change user password View and search the user sessions Login to Aradial user self care: When a pre-defined user want to access to Aradial portal and view / manage his account he should access the Aradial portal URL (http://localhost:8001/wsc).

The Aradial portal port is configurable and can be changed from the main admin Aradial screen Server Configuration Advanced Configuration HTTP Server WSC Interface Setting section, WSC Interface port parameter. Once Aradial authenticate and validate the user name and passoword, the Aradial User Self Care will present the User Summary Page: User Summary The following sections will be presented in the User Summary tab: Personal Information: Aradial user self portal will present the user personal information with the registered data in 'read only' mode. Access Information: Aradial user self portal will present the user access information with the registered data in 'read only' mode. Additional access information: Aradial user self portal will present the user additional access information with the registered data in 'read only' mode. Dates: Aradial user self portal will present the dates information with the following details in 'read only' mode: User Creation date: The date the user was created in Aradial.

User expiration date: the user expiration date. In case the user has no expiration date, the field will be empty. User activation date: The user activation date as inserted in the user registration. In case no activation date was inserted, the user creation date will be presented. Last login on: the last login date for the specific user. This field is updated automatically by aradial and will present the most updated date. Metering information: User metering information will be presented. The data is automatically updated by Aradial based on the user' sessions. Data is presented in 'read only' mode. In Aradial VOIP Converged plantform the user balance bank will also be presented. Update User The Update User page in the Aradial self care interface will allow the users to manage their own accounts and allow self update. Aradial will allow changing any of the user personal information but will not allow changing Metering info and / or any other system data information (e.g. user activation date, expiration date, tariff details, etc). The user will be able to change his personal information by changing the appropriate field and then pressing 'Update' button. The change will be reflected immdiatlly.

Change Password Aradial self care portal is enabling the users to maintain and change their password information. Aradial will first authenticate and validate the old password and then allow changing to new password. The flow to change the user password is as follows: - The user login to the change password tab in the user self care - User type in the old password, new password and re-entering the new password - Aradial will authenticate the old password - If validation pass, the password will be replaced and appropriate massage will be displayed. - In case of validation error, password will not be changed and appropriate massage will be displayed.

View Sessions Aradial user self care interface is allowing the users to view their own sessions by login to the View sessions tab. Once login, the page will be dispalyed in search mode and will ask for data range criteria's for the search. Leaving the date fields empty means to range criteria's and Aradial self care will present all user sessions. Reset Will enable the user to reset the search criteria's and will remove the old values from the search fields. The search button will search the user sessions based on the input parameters, or all sessions if no parameters will be entered. The sessions screen will present the following information: Last update: the field will present the last login date and time when the user was connected. Local Start Time: Aradial local Start time for the specified session. Clent IP: The Client IP as specified in the VOIP session. Connect time: Session local start time as specifed in the VOIP session. Duration: Total session duration. Caller ID: Session caller ID (from the session).

Called ID: Session called ID (from the session). Code: This is the termination code of the session. 10 means session terminated nornally. Please review the VOIP gatway specific termination codes Cost: Total cost for the session as calculated by Aradial.

Chapter 10 10 Wifi / Hotspot / ISP Portal Please referer to the generic Aradial RADIUS Maunal guide.