Freeside - User contributions [en]

Freeside:3:Documentation:Administration

2016-09-09T19:29:25Z

NathanK: /* Employees */

= Exports (provisioning) =

'''Exports''' allow you to provision services to remote machines, databases and APIs. Some exports, such as ''sqlradius'' and ''sqlradius_withdomain'', enable a feed for retrieving rating/usage data.

Exports can be added and edited under
: Configuration -> Provisioning, services and packages -> View/edit exports

Most exports place jobs in the job queue for new, modified or deleted services. Jobs are run by [[Freeside:3:Documentation:Developer/bin/freeside-queued|freeside-queued]]. This daemon needs to be running before exports are acted upon.

Some exports use SSH, SCP or SFTP to communicate with external machines. See the documentation on [[Freeside:3:Documentation:Administration:SSH_Keys|SSH keys]].

Click on ''Add a new export'' to create a new export. Select exports from the dropdown to show more information on each export, including available options, setup and usage.

Exports are activated by associating them with one or more '''service definitions'''.

Following is a list of which exports can be associated with each type of service.

==svc_acct==
* [[Freeside:3:Documentation:Administration:acct_plesk.pm|acct_plesk.pm]]: Real-time export to Plesk managed mail service
* acct_sql.pm: Real-time export of accounts to SQL databases .
* artera_turbo.pm:
* bsdshell.pm:
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* communigate_pro_singledomain.pm:
* cpanel.pm: Real-time export to Cpanel control panel.
* cp.pm: Real-time export to Critical Path Account Provisioning Protocol
* cyrus.pm: Real-time export to Cyrus IMAP server
* everyone_net.pm: Real-time export to Everyone.net outsourced mail service
* infostreet.pm: Real-time export to InfoStreet streetSmartAPI
* [[Freeside:3:Documentation:Administration:ldap.pm|ldap.pm]]: Real-time export to LDAP
* passwdfile.pm:
* radiator.pm: Real-time export to RADIATOR
* shellcommands.pm:
* shellcommands_withdomain.pm: Real-time export via remote SSH (vpopmail, ISPMan)
* sqlmail.pm: Real-time export to SQL-backed mail server
* sqlradius.pm: Real-time export to SQL-backed RADIUS (FreeRADIUS, ICRADIUS)
* sqlradius_withdomain.pm: Real-time export to SQL-backed RADIUS (FreeRADIUS, ICRADIUS) with realms
* sysvshell.pm:
* textradius.pm:
* vpopmail.pm: Real-time export to vpopmail text files

==svc_domain==
* bind.pm: Batch export to BIND named
* bind_slave.pm: Batch export to slave BIND named
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* domain_shellcommands.pm: Run remote commands via SSH, for domains (qmail, ISPMan).
* domain_sql.pm: Real time export of domains to SQL databases .
* http.pm: Send an HTTP or HTTPS GET or POST request
* [[Freeside:3:Documentation:Administration:opensrs.pm|opensrs.pm]]: OpenSRS integration
* sqlmail.pm: Real-time export to SQL-backed mail server

==svc_forward==
* artera_turbo.pm:
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* forward_shellcommands.pm: Run remote commands via SSH, for forwards
* postfix.pm: Postfix text files
* sqlmail.pm: Real-time export to SQL-backed mail server

==svc_www==
* apache.pm: Export an Apache httpd.conf file snippet.
* [[Freeside:3:Documentation:Administration:www_plesk.pm|www_plesk.pm]]: Real-time export to Plesk managed hosting service
* www_shellcommands.pm: Run remote commands via SSH, for virtual web sites (directory maintenance, FrontPage, ISPMan)

==svc_broadband==
* nas_wrapper.pm: A meta-export that triggers other svc_broadband exports.
* [[Freeside:3:Documentation:Administration:prizm.pm|prizm.pm]]: Real-time export to Northbound Interface
* router.pm: Send a command to a router.
* snmp.pm: Sends SNMP SETs to an SNMP agent.
* trango.pm: Sends SNMP SETs to a Trango AP.

==svc_phone==
* globalpops_voip.pm:
* grandstream.pm: Grandstream phone and ATA provisioning. This [http://www.freeside.biz/blog/?p=11 blog article] is a start at documentation.
* indosoft.pm:
* internal_diddb.pm:
* netsapiens.pm:
* phone_shellcommands.pm:
* phone_sqlradius.pm:
* thirdlane.pm:
* [[Freeside:Documentation:Administration:vitelity.pm|vitelity.pm]]: Vitelity provisioning

==svc_external==
* artera_turbo.pm:

==svc_dsl==
* ikano.pm: see [[Freeside:3:Documentation:Administration:svc_dsl:ikano|Ikano DSL provisioning and qualifications]]

= Services =

== Generic ==

=== Accounts (svc_acct) ===

Accounts - anything with a username (mailbox, shell, RADIUS, etc.)

* [[Freeside:3:Documentation:Administration:svc_acct:_password_encoding|Password encoding]]

=== Hardware (svc_hardware) ===

Equipment supplied to customers

=== External (svc_external) ===

Externally-tracked service

== Access ==

=== DSL (svc_dsl) ===

* [[Freeside:3:Documentation:Administration:svc_dsl:ikano|Ikano DSL provisioning and qualifications]]

=== Broadband (svc_broadband) ===

Fixed wireless broadband

=== Cable (svc_cable) ===

=== DISH Network (svc_dish) ===

== Telephony ==

=== Customer phone number / DID (svc_phone) ===

* [[Freeside:Documentation:Administration:Phone devices|Phone devices]]

=== Customer PBX (svc_pbx) ===

=== Phone circuit (svc_circuit) ===

== Hosting ==

=== Domains (svc_domain) ===

=== Certificate (svc_cert) ===

=== Forwards (svc_forward) ===

=== Mailing list (svc_mailinglist) ===

=== Site hosting (svc_www) ===

== Colocation ==

=== Customer router/switch port (svc_port) ===

= Packages =

{{Freeside:3:Documentation:Administration:pkg_category}}

== Price Plans ==

=== Common price plans ===

* flat
* subscription
* prorate
* sqlradacct_hour
* [[voip_cdr]]
* prepaid

=== Wholesale price plans ===

* bulk

* [[Freeside:3:Documentation:Administration:Packages:Price_Plans:agent | agent]]
* [[Freeside:3:Documentation:Administration:Packages:Price_Plans:cdr_termination |
cdr_termination ]]

=== Other price plans ===

* flat_delayed
* flat_introrate
* prorate_delayed

* base_delayed
* base_rate

* sql_external
* sql_generic

=== Price plans of questionable functionality ===

* flat_comission_cust
* flat_comission_pkg
* flat_comission

* voip_sqlradacct

* sesmon_hour
* sesmon_minute

== Misc ==

* Some notes on [[Freeside:3:Documentation:Administration:Upselling | Upselling]]

= Resellers =

=== Wholesaler configuraiton ===
[[Freeside:3:Documentation:Administration:Wholesaler|Using agents for setting up Wholesalers]]

= Employees =

== Employees ==

Go to Configuration -> Employees -> Employees to view the existing employees and add new ones. It is highly recommended to add a separate account for each person rather than using role accounts.

* To add a new employee, click on "Add an employee"
* Or to edit an existing group, click on the employee number or name in the list of employees.
* Enter or edit the username, password and name. If editing an existing employee and no password change is desired, the password fields can be left blank.
* Check the "Disable employee" box to disable this employee.
* In the "Employee groups" section, mark or unmark checkboxes to indicate the access groups for this employee.

Go to Configuration -> Ticketing -> Ticketing users
* Click on the Create link in the upper right hand corner
* Enter the same username as the Employee name above
* Enter any other information (Real name, Email address, etc. )
* Check both boxes in the access control box
* Click the Create button
(Be sure to add the ticketing user to the appropriate ticketing groups)

== Employee groups and access control ==

To setup employee access control or agent/reseller virtualization, you need to setup employee groups. Go to Configuration -> Employees -> Employee groups to view the existing groups and add new ones. The system starts with a "Superuser" group which has access to all functionality for the first agent.

* To add a new group, click on "Add an employee group"
* Or to edit an existing group, click on the group number or name in the list of groups.
* Enter or edit the group name.
* In the "Group limited to these agent(s)" section, mark checkboxes next to the agents this employee group should be able to see. Employees in this group will only see customers of the selected agents in the system and reports.
* In the "Group access rights" section, mark or unmark checkboxes to indicate the access rights this employee group should have. Rights marked with an "*" are global rights which provide access to global data which is shared among all agents. Their use is not recommended for groups which are limited to a subset of agents.
* After adding a new group, don't forget to go back and add or edit employees to place them into the new group.

= Installers / Appointments =

== Installers ==

* Designate some employees as installers (Configuration -> Employees -> Employees)
* Edit their schedules (Configuration -> Employees -> Installer availability)

== Ticketing ==

* Setup a queue for appointments (installations, removals, etc.), or use existing per agent queues
* Make sure the installer employees can own / see / edit tickets in this
queue (add them to a ticketing group with OwnTicket / SeeQueue on that queue or global, etc.)
* not yet <strike>XXX future todo some sort of ill-defined thing with configuring a custom field to designate install / recall / service call / removal</strike>

== Packages ==

not yet; package(+location)-specific appointments are a future TODO
<strike>
* Setup a package category for packages that can schedule appointments
* In the package category, select a queue for appointments or pick "Agent-specific queue"
</strike>

== Employee rights ==

* Upgrade should do this / should be available in a default install, but may not be implemented yet
* Give one or more employee groups "View appointments" and "Make appointment" (in Customer package rights)

= Billing =

== Billing events ==
Billing events are the primary mechanism to implement your business rules. Rules such as resend invoices, retry cards, suspend or cancel accounts for non-payment, etc. are all handled by billing events.

At a high level, follow the following steps to create billing events:
* Add a new Billing Event (Configuration > Billing > Billing events)
* Name the event
* Choose the type of event:
** Package - Packages and associated dates (Including Commissions)
** Invoice - Invoice status and dates
** Customer - Customer Balances and Information
** Batch Payment - Batch payment results
** Statement - Send statement
* Choose whether to apply to one or all agents
* Choose the frequency for the system to check and see if the event should run.
* Choose appropriate filters.
* Choose appropriate actions.

The form is dynamic so changing the type of event will change the available filters and actions.

== Daily and Monthly Scripts ==
* The freeside-daily script should be run daily to bill customers and run invoice collection events.
** Typically, this is accomplished with an entry in the freeside user's crontab such as: <pre>0 0 * * * /usr/local/bin/freeside-daily</pre>
** If running freeside-daily manually, ensure the <code>TZ</code> variable is set to your timezone with a command such as: <pre>TZ="US/Pacific" freeside-daily fs_daily</pre>
* If any monthly events are enabled, the freeside-monthly script should be run monthly.
* Invoice events can also be used to implement agent-virtualized invoices. (add more info)
* Be sure to include the full path of freeside-daily in your cron job.

== Invoices ==

=== Typeset (LaTeX) invoice templates ===

==== Prerequisites ====

* Almost all distributions include the necessary prerequisites listed here, manual installation is practically never necessary.
* Install [http://www.ghostscript.com/ Ghostscript] (gs)
* Install [http://www.tug.org/tetex/ teTeX] or [http://www.tug.org/texlive/ TeX Live]
* Ensure that the <code>pslatex</code>, <code>dvips</code>, and <code>pdflatex</code> command line utilities were installed

==== Logo setup ====

The EPS logo is for PDF and printed invoices.

* For best results, save a '''vector format''' logo in EPS (Encapsulated PostScript) format.
** Your graphic artist can create vector image from a bitmap (tracing etc).
** Converting a bitmap such as a JPG can work (the bigger the better), but it may render in lower quality, blurry or with the "jaggies" (especially when actually printed, not just viewed as a PDF)
* Resize the logo to 90pt X 36pt: <code>epsffit -c 0 0 90 36 yourlogo.eps >logo.eps</code>
** ("no %%BoundingBox:" error? Fix with eps2eps)
* Upload the resized logo as the <code>logo.eps</code> configuration option.
* Problems? Try <code>bin/strip-eps <oldlogo.eps >trynewlogo.eps</code>

The PNG logo is for emailed and online invoices.

Freeside ships with a logo of 92 x 62. Any logo close to this size should work with the default HTML template.

{{Freeside:3:Documentation:Administration:invoice_layout}}

=== HTML invoice templates ===

* Convert your logo to PNG format and upload it as the <code>logo.png</code> configuration option.
{{Freeside:3:Documentation:Administration:invoice_templates|format=html}}

=== Plaintext invoice templates ===

* See the Text::Template documentation for details on the substitution language.
* You must call the invoice_lines() function at least once - pass it a number of lines, and it returns a list of array references, each of two elements: a service description column, and a price column. Alternatively, call invoice_lines() with no arguments, and pagination will be disabled - all invoice line items will print on one page, with no padding (recommended for email invoices).
* Descriptions of variables are available in [[Freeside:3:Documentation:Template:invoice_html|invoice_html]]

=== Misc ===

==== Manually setting next customer number sequence ====

* With PostgreSQL, to number customers starting at 5000: <pre>SELECT SETVAL(pg_get_serial_sequence('cust_main', 'custnum'), 4999);</pre>
* With MySQL, to number customers starting at 5000: <pre>ALTER TABLE cust_main AUTO_INCREMENT = 5000;</pre>

==== Manually setting next invoice number sequence ====

* With PostgreSQL, to number invoices starting at 5000: <pre>SELECT SETVAL(pg_get_serial_sequence('cust_bill', 'invnum'), 4999);</pre>
* With MySQL, to number invoices starting at 5000: <pre>ALTER TABLE cust_bill AUTO_INCREMENT = 5000;</pre>

== Taxes ==

[[Freeside:3:Documentation:Administration:Tax_Districts | District based taxes]]

== Payment Receipts ==

The [[Freeside:3:Documentation:Template:payment_receipt_email|payment_receipt_email]] template is used for manually applied payments.

== Credit cards and Electronic checks ==
* [[Freeside:3:Documentation:Administration:Real-time_Processing | Real-time credit card and electronic check processing]]
* [[Freeside:3:Documentation:Administration:Batch_Processing | Batch credit card and electronic check processing]]
* Credit card expiration alerts: Customize the ''alerter_template'' configuration option and run <code>freeside-expiration-alerter</code> daily.
* Credit card decline alerts: Customize the ''declinetemplate'' configuration option and set the ''emaildecline'' configuration option.

= Misc =

These things should probably find a home properly filed in a section above.

== Invoicing and Payments ==

* Setting up [[Freeside:3:Documentation:Administration:Encrypted Credit Cards | Encrypted Credit Cards]] (default in new installs, highly recommended for older installs upgrading)
* Setting up [[Freeside:3:Documentation:Administration:Texas Tax | Texas Tax]]
* Need to print to Windows printers, and the PDF spool is not for you? Follow steps 1-4 of [http://iharder.sourceforge.net/current/macosx/winmacprinter/ Share Your Windows Printer].

== Refunds for automatic payments ==

A refund to an automatic payment can be made within the time limitation set by the payment gateway by using the refund link next to the payment:

<pre>05/19/2015 Payment by fs_queue (Credit card #411111xxxxxx1111) applied to Invoice #228 (05/19/15) (view receipt) (refund) (void) (unapply) - $24.60 $0.00</pre>

On the refund page the Amount defaults to the amount of the payment. If only a partial refund is to be made then change this to the proper amount:

<pre>
Refund
Date 05/19/2015
Amount $10.00 by Credit card
Reason Package amount incorrect
</pre>

For this example we will only refund a part of the payment as illustrated above. It is usually a good idea to add a Reason that provides additional information for the refund.

Once you have the refund fields filled out click the Post refund button

This will unapply the payment from the invoice leaving the balance of the payment available for application to an invoice:

<pre>
05/19/2015 Open Invoice #228 (Balance 25.21) (void)
( View invoice events ) $25.21 $25.21
05/19/2015 Payment by nkennedy (Credit card #411111xxxxxx1111)
10.00 refunded on 05/19/2015
15.21 unapplied
(view receipt) (apply) (refund) (void) - $25.21 $0.00
05/19/2015 Refund by nkennedy (Credit card #411111xxxxxx1111) (view receipt) $10.00 $10.00
</pre>

Use the apply link to apply the remaining payment to the invoice. This will bring up the Apply Payment window where you can select the invoice to apply the payment to:

<pre>
Payment #77
Date: 05/19/2015
Amount: $25.21
Unapplied amount: $15.21

Apply to:
Invoice: #228 - 05/19/2015 - $25.21
Amount: $15.21
</pre>

After you click the Apply button you are left with the original invoice with a balance due from the refunded payment:

<pre>
05/19/2015 Open Invoice #228 (Balance 10.00) (void)
( View invoice events ) $25.21 $25.21
05/19/2015 Payment by nkennedy (Credit card #411111xxxxxx1111)
10.00 refunded on 05/19/2015
15.21 applied to Invoice #228 (05/19/15)
(view receipt) (refund) (void) (unapply) - $25.21 $0.00
05/19/2015 Refund by nkennedy (Credit card #411111xxxxxx1111) (view receipt) $10.00 $10.00
</pre>

To balance the invoice you can use the Enter Credit link to issue a credit that can be applied to the invoice:

<pre>
Enter Credit

Date 05/19/2015 10:03:26 AM
Amount $10.00
Reason Package Error
Additional info Credit for package error
Auto-apply to invoices yes
</pre>

When entering the credit you can select a credit reason that was previously defined at Configuration -> Billing -> Credit Reasons or you can create a reason on the fly.
You can also add a small note in the "Additional info" field which will print on the customers invoice. Please keept this short as long text will get truncated on PDF invoices to prevent formatting issues.

Once the credit is applied the customers account will be balanced out:

<pre>
05/19/2015 Invoice #228 (Balance 0.00) (void)
( View invoice events ) $25.21 $25.21
05/19/2015 Payment by nkennedy (Credit card #411111xxxxxx1111)
10.00 refunded on 05/19/2015
15.21 applied to Invoice #228 (05/19/15)
(view receipt) (refund) (void) (unapply) - $25.21 $0.00
05/19/2015 Refund by nkennedy (Credit card #411111xxxxxx1111) (view receipt) $10.00 $10.00
05/19/2015 Credit by nkennedy (Package Error Credit for package error) applied to Invoice #228 (05/19/15) (delete) (unapply) (void) - $10.00 $0.00
</pre>

If you need to have taxes calculated as part of the refund you can start with issuing a credit using the Credit line items link. This will allow you to select the line item on the invoice and enter the amount to credit that entry.
Follow the rest of the instructions for re-applying the payment to the invoice and the left over balance is the amount you need to use after following the refund link on the payment.

== Commissions ==


* Setting up [[Freeside:3:Documentation:Administration:Commission|Commissions and Referrals]]

== VoIP ==

* Setting up [[Freeside:3:Documentation:Administration:VoIP | VoIP]]
* [[Simple Bulk DID Orders]]
* [[Bulk DID Orders]]
* [[Freeside:3:Documentation:Administration:VoIP:e911|e911 Providers]]

== RADIUS ==

* Setting up [[Freeside:3.0:Documentation:Administration:FreeRadius | FreeRadius]]

== Torrus Network monitoring ==

* [[Freeside:3:Documentation:Torrus_Installation | Installation]]
* [[Freeside:3:Documentation:Torrus_Administration | Administration]]

== Old / uncommon ==

* Setting up [[Freeside:3:Documentation:Administration:Time billing | Time billing]]
* Using a non-standard [[Freeside:3:Documentation:Administration:PostgreSQL_Schema | PostgreSQL Schema]]
* Setting up [[Freeside:3:Documentation:Administration:Slony | Slony replication and failover]] (old - PostgreSQL native replication is a more current solution)

{{ContextSensitiveHelp}}

Freeside:3:Documentation:Administration

2015-12-29T17:51:36Z

NathanK:

= Exports (provisioning) =

'''Exports''' allow you to provision services to remote machines, databases and APIs. Some exports, such as ''sqlradius'' and ''sqlradius_withdomain'', enable a feed for retrieving rating/usage data.

Exports can be added and edited under
: Configuration -> Provisioning, services and packages -> View/edit exports

Most exports place jobs in the job queue for new, modified or deleted services. Jobs are run by [[Freeside:3:Documentation:Developer/bin/freeside-queued|freeside-queued]]. This daemon needs to be running before exports are acted upon.

Some exports use SSH, SCP or SFTP to communicate with external machines. See the documentation on [[Freeside:3:Documentation:Administration:SSH_Keys|SSH keys]].

Click on ''Add a new export'' to create a new export. Select exports from the dropdown to show more information on each export, including available options, setup and usage.

Exports are activated by associating them with one or more '''service definitions'''.

Following is a list of which exports can be associated with each type of service.

==svc_acct==
* [[Freeside:3:Documentation:Administration:acct_plesk.pm|acct_plesk.pm]]: Real-time export to Plesk managed mail service
* acct_sql.pm: Real-time export of accounts to SQL databases .
* artera_turbo.pm:
* bsdshell.pm:
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* communigate_pro_singledomain.pm:
* cpanel.pm: Real-time export to Cpanel control panel.
* cp.pm: Real-time export to Critical Path Account Provisioning Protocol
* cyrus.pm: Real-time export to Cyrus IMAP server
* everyone_net.pm: Real-time export to Everyone.net outsourced mail service
* infostreet.pm: Real-time export to InfoStreet streetSmartAPI
* [[Freeside:3:Documentation:Administration:ldap.pm|ldap.pm]]: Real-time export to LDAP
* passwdfile.pm:
* radiator.pm: Real-time export to RADIATOR
* shellcommands.pm:
* shellcommands_withdomain.pm: Real-time export via remote SSH (vpopmail, ISPMan)
* sqlmail.pm: Real-time export to SQL-backed mail server
* sqlradius.pm: Real-time export to SQL-backed RADIUS (FreeRADIUS, ICRADIUS)
* sqlradius_withdomain.pm: Real-time export to SQL-backed RADIUS (FreeRADIUS, ICRADIUS) with realms
* sysvshell.pm:
* textradius.pm:
* vpopmail.pm: Real-time export to vpopmail text files

==svc_domain==
* bind.pm: Batch export to BIND named
* bind_slave.pm: Batch export to slave BIND named
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* domain_shellcommands.pm: Run remote commands via SSH, for domains (qmail, ISPMan).
* domain_sql.pm: Real time export of domains to SQL databases .
* http.pm: Send an HTTP or HTTPS GET or POST request
* [[Freeside:3:Documentation:Administration:opensrs.pm|opensrs.pm]]: OpenSRS integration
* sqlmail.pm: Real-time export to SQL-backed mail server

==svc_forward==
* artera_turbo.pm:
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* forward_shellcommands.pm: Run remote commands via SSH, for forwards
* postfix.pm: Postfix text files
* sqlmail.pm: Real-time export to SQL-backed mail server

==svc_www==
* apache.pm: Export an Apache httpd.conf file snippet.
* [[Freeside:3:Documentation:Administration:www_plesk.pm|www_plesk.pm]]: Real-time export to Plesk managed hosting service
* www_shellcommands.pm: Run remote commands via SSH, for virtual web sites (directory maintenance, FrontPage, ISPMan)

==svc_broadband==
* nas_wrapper.pm: A meta-export that triggers other svc_broadband exports.
* [[Freeside:3:Documentation:Administration:prizm.pm|prizm.pm]]: Real-time export to Northbound Interface
* router.pm: Send a command to a router.
* snmp.pm: Sends SNMP SETs to an SNMP agent.
* trango.pm: Sends SNMP SETs to a Trango AP.

==svc_phone==
* globalpops_voip.pm:
* grandstream.pm: Grandstream phone and ATA provisioning. This [http://www.freeside.biz/blog/?p=11 blog article] is a start at documentation.
* indosoft.pm:
* internal_diddb.pm:
* netsapiens.pm:
* phone_shellcommands.pm:
* phone_sqlradius.pm:
* thirdlane.pm:
* [[Freeside:Documentation:Administration:vitelity.pm|vitelity.pm]]: Vitelity provisioning

==svc_external==
* artera_turbo.pm:

==svc_dsl==
* ikano.pm: see [[Freeside:3:Documentation:Administration:svc_dsl:ikano|Ikano DSL provisioning and qualifications]]

= Services =

== Generic ==

=== Accounts (svc_acct) ===

Accounts - anything with a username (mailbox, shell, RADIUS, etc.)

* [[Freeside:3:Documentation:Administration:svc_acct:_password_encoding|Password encoding]]

=== Hardware (svc_hardware) ===

Equipment supplied to customers

=== External (svc_external) ===

Externally-tracked service

== Access ==

=== DSL (svc_dsl) ===

* [[Freeside:3:Documentation:Administration:svc_dsl:ikano|Ikano DSL provisioning and qualifications]]

=== Broadband (svc_broadband) ===

Fixed wireless broadband

=== Cable (svc_cable) ===

=== DISH Network (svc_dish) ===

== Telephony ==

=== Customer phone number / DID (svc_phone) ===

* [[Freeside:Documentation:Administration:Phone devices|Phone devices]]

=== Customer PBX (svc_pbx) ===

=== Phone circuit (svc_circuit) ===

== Hosting ==

=== Domains (svc_domain) ===

=== Certificate (svc_cert) ===

=== Forwards (svc_forward) ===

=== Mailing list (svc_mailinglist) ===

=== Site hosting (svc_www) ===

== Colocation ==

=== Customer router/switch port (svc_port) ===

= Packages =

{{Freeside:3:Documentation:Administration:pkg_category}}

== Price Plans ==

=== Common price plans ===

* flat
* subscription
* prorate
* sqlradacct_hour
* [[voip_cdr]]
* prepaid

=== Wholesale price plans ===

* bulk

* [[Freeside:3:Documentation:Administration:Packages:Price_Plans:agent | agent]]
* [[Freeside:3:Documentation:Administration:Packages:Price_Plans:cdr_termination |
cdr_termination ]]

=== Other price plans ===

* flat_delayed
* flat_introrate
* prorate_delayed

* base_delayed
* base_rate

* sql_external
* sql_generic

=== Price plans of questionable functionality ===

* flat_comission_cust
* flat_comission_pkg
* flat_comission

* voip_sqlradacct

* sesmon_hour
* sesmon_minute

== Misc ==

* Some notes on [[Freeside:3:Documentation:Administration:Upselling | Upselling]]

= Resellers =

=== Wholesaler configuraiton ===
[[Freeside:3:Documentation:Administration:Wholesaler|Using agents for setting up Wholesalers]]

= Employees =

== Employees ==

Go to Configuration -> Employees -> Employees to view the existing employees and add new ones. It is highly recommended to add a separate account for each person rather than using role accounts.

* To add a new employee, click on "Add an employee"
* Or to edit an existing group, click on the employee number or name in the list of employees.
* Enter or edit the username, password and name. If editing an existing employee and no password change is desired, the password fields can be left blank.
* Check the "Disable employee" box to disable this employee.
* In the "Employee groups" section, mark or unmark checkboxes to indicate the access groups for this employee.

== Employee groups and access control ==

To setup employee access control or agent/reseller virtualization, you need to setup employee groups. Go to Configuration -> Employees -> Employee groups to view the existing groups and add new ones. The system starts with a "Superuser" group which has access to all functionality for the first agent.

* To add a new group, click on "Add an employee group"
* Or to edit an existing group, click on the group number or name in the list of groups.
* Enter or edit the group name.
* In the "Group limited to these agent(s)" section, mark checkboxes next to the agents this employee group should be able to see. Employees in this group will only see customers of the selected agents in the system and reports.
* In the "Group access rights" section, mark or unmark checkboxes to indicate the access rights this employee group should have. Rights marked with an "*" are global rights which provide access to global data which is shared among all agents. Their use is not recommended for groups which are limited to a subset of agents.
* After adding a new group, don't forget to go back and add or edit employees to place them into the new group.

= Installers / Appointments =

== Installers ==

* Designate some employees as installers (Configuration -> Employees -> Employees)
* Edit their schedules (Configuration -> Employees -> Installer availability)

== Ticketing ==

* Setup a queue for appointments (installations, removals, etc.), or use existing per agent queues
* Make sure the installer employees can own / see / edit tickets in this
queue (add them to a ticketing group with OwnTicket / SeeQueue on that queue or global, etc.)
* not yet <strike>XXX future todo some sort of ill-defined thing with configuring a custom field to designate install / recall / service call / removal</strike>

== Packages ==

not yet; package(+location)-specific appointments are a future TODO
<strike>
* Setup a package category for packages that can schedule appointments
* In the package category, select a queue for appointments or pick "Agent-specific queue"
</strike>

== Employee rights ==

* Upgrade should do this / should be available in a default install, but may not be implemented yet
* Give one or more employee groups "View appointments" and "Make appointment" (in Customer package rights)

= Billing =

== Billing events ==
Billing events are the primary mechanism to implement your business rules. Rules such as resend invoices, retry cards, suspend or cancel accounts for non-payment, etc. are all handled by billing events.

At a high level, follow the following steps to create billing events:
* Add a new Billing Event (Configuration > Billing > Billing events)
* Name the event
* Choose the type of event:
** Package - Packages and associated dates (Including Commissions)
** Invoice - Invoice status and dates
** Customer - Customer Balances and Information
** Batch Payment - Batch payment results
** Statement - Send statement
* Choose whether to apply to one or all agents
* Choose the frequency for the system to check and see if the event should run.
* Choose appropriate filters.
* Choose appropriate actions.

The form is dynamic so changing the type of event will change the available filters and actions.

== Daily and Monthly Scripts ==
* The freeside-daily script should be run daily to bill customers and run invoice collection events.
** Typically, this is accomplished with an entry in the freeside user's crontab such as: <pre>0 0 * * * /usr/local/bin/freeside-daily</pre>
** If running freeside-daily manually, ensure the <code>TZ</code> variable is set to your timezone with a command such as: <pre>TZ="US/Pacific" freeside-daily fs_daily</pre>
* If any monthly events are enabled, the freeside-monthly script should be run monthly.
* Invoice events can also be used to implement agent-virtualized invoices. (add more info)
* Be sure to include the full path of freeside-daily in your cron job.

== Invoices ==

=== Typeset (LaTeX) invoice templates ===

==== Prerequisites ====

* Almost all distributions include the necessary prerequisites listed here, manual installation is practically never necessary.
* Install [http://www.ghostscript.com/ Ghostscript] (gs)
* Install [http://www.tug.org/tetex/ teTeX] or [http://www.tug.org/texlive/ TeX Live]
* Ensure that the <code>pslatex</code>, <code>dvips</code>, and <code>pdflatex</code> command line utilities were installed

==== Logo setup ====

The EPS logo is for PDF and printed invoices.

* For best results, save a '''vector format''' logo in EPS (Encapsulated PostScript) format.
** Your graphic artist can create vector image from a bitmap (tracing etc).
** Converting a bitmap such as a JPG can work (the bigger the better), but it may render in lower quality, blurry or with the "jaggies" (especially when actually printed, not just viewed as a PDF)
* Resize the logo to 90pt X 36pt: <code>epsffit -c 0 0 90 36 yourlogo.eps >logo.eps</code>
** ("no %%BoundingBox:" error? Fix with eps2eps)
* Upload the resized logo as the <code>logo.eps</code> configuration option.
* Problems? Try <code>bin/strip-eps <oldlogo.eps >trynewlogo.eps</code>

The PNG logo is for emailed and online invoices.

Freeside ships with a logo of 92 x 62. Any logo close to this size should work with the default HTML template.

{{Freeside:3:Documentation:Administration:invoice_layout}}

=== HTML invoice templates ===

* Convert your logo to PNG format and upload it as the <code>logo.png</code> configuration option.
{{Freeside:3:Documentation:Administration:invoice_templates|format=html}}

=== Plaintext invoice templates ===

* See the Text::Template documentation for details on the substitution language.
* You must call the invoice_lines() function at least once - pass it a number of lines, and it returns a list of array references, each of two elements: a service description column, and a price column. Alternatively, call invoice_lines() with no arguments, and pagination will be disabled - all invoice line items will print on one page, with no padding (recommended for email invoices).
* Descriptions of variables are available in [[Freeside:3:Documentation:Template:invoice_html|invoice_html]]

=== Misc ===

==== Manually setting next customer number sequence ====

* With PostgreSQL, to number customers starting at 5000: <pre>SELECT SETVAL(pg_get_serial_sequence('cust_main', 'custnum'), 4999);</pre>
* With MySQL, to number customers starting at 5000: <pre>ALTER TABLE cust_main AUTO_INCREMENT = 5000;</pre>

==== Manually setting next invoice number sequence ====

* With PostgreSQL, to number invoices starting at 5000: <pre>SELECT SETVAL(pg_get_serial_sequence('cust_bill', 'invnum'), 4999);</pre>
* With MySQL, to number invoices starting at 5000: <pre>ALTER TABLE cust_bill AUTO_INCREMENT = 5000;</pre>

== Taxes ==

[[Freeside:3:Documentation:Administration:Tax_Districts | District based taxes]]

== Payment Receipts ==

The [[Freeside:3:Documentation:Template:payment_receipt_email|payment_receipt_email]] template is used for manually applied payments.

== Credit cards and Electronic checks ==
* [[Freeside:3:Documentation:Administration:Real-time_Processing | Real-time credit card and electronic check processing]]
* [[Freeside:3:Documentation:Administration:Batch_Processing | Batch credit card and electronic check processing]]
* Credit card expiration alerts: Customize the ''alerter_template'' configuration option and run <code>freeside-expiration-alerter</code> daily.
* Credit card decline alerts: Customize the ''declinetemplate'' configuration option and set the ''emaildecline'' configuration option.

= Misc =

These things should probably find a home properly filed in a section above.

== Invoicing and Payments ==

* Setting up [[Freeside:3:Documentation:Administration:Encrypted Credit Cards | Encrypted Credit Cards]] (default in new installs, highly recommended for older installs upgrading)
* Setting up [[Freeside:3:Documentation:Administration:Texas Tax | Texas Tax]]
* Need to print to Windows printers, and the PDF spool is not for you? Follow steps 1-4 of [http://iharder.sourceforge.net/current/macosx/winmacprinter/ Share Your Windows Printer].

== Refunds for automatic payments ==

A refund to an automatic payment can be made within the time limitation set by the payment gateway by using the refund link next to the payment:

<pre>05/19/2015 Payment by fs_queue (Credit card #411111xxxxxx1111) applied to Invoice #228 (05/19/15) (view receipt) (refund) (void) (unapply) - $24.60 $0.00</pre>

On the refund page the Amount defaults to the amount of the payment. If only a partial refund is to be made then change this to the proper amount:

<pre>
Refund
Date 05/19/2015
Amount $10.00 by Credit card
Reason Package amount incorrect
</pre>

For this example we will only refund a part of the payment as illustrated above. It is usually a good idea to add a Reason that provides additional information for the refund.

Once you have the refund fields filled out click the Post refund button

This will unapply the payment from the invoice leaving the balance of the payment available for application to an invoice:

<pre>
05/19/2015 Open Invoice #228 (Balance 25.21) (void)
( View invoice events ) $25.21 $25.21
05/19/2015 Payment by nkennedy (Credit card #411111xxxxxx1111)
10.00 refunded on 05/19/2015
15.21 unapplied
(view receipt) (apply) (refund) (void) - $25.21 $0.00
05/19/2015 Refund by nkennedy (Credit card #411111xxxxxx1111) (view receipt) $10.00 $10.00
</pre>

Use the apply link to apply the remaining payment to the invoice. This will bring up the Apply Payment window where you can select the invoice to apply the payment to:

<pre>
Payment #77
Date: 05/19/2015
Amount: $25.21
Unapplied amount: $15.21

Apply to:
Invoice: #228 - 05/19/2015 - $25.21
Amount: $15.21
</pre>

After you click the Apply button you are left with the original invoice with a balance due from the refunded payment:

<pre>
05/19/2015 Open Invoice #228 (Balance 10.00) (void)
( View invoice events ) $25.21 $25.21
05/19/2015 Payment by nkennedy (Credit card #411111xxxxxx1111)
10.00 refunded on 05/19/2015
15.21 applied to Invoice #228 (05/19/15)
(view receipt) (refund) (void) (unapply) - $25.21 $0.00
05/19/2015 Refund by nkennedy (Credit card #411111xxxxxx1111) (view receipt) $10.00 $10.00
</pre>

To balance the invoice you can use the Enter Credit link to issue a credit that can be applied to the invoice:

<pre>
Enter Credit

Date 05/19/2015 10:03:26 AM
Amount $10.00
Reason Package Error
Additional info Credit for package error
Auto-apply to invoices yes
</pre>

When entering the credit you can select a credit reason that was previously defined at Configuration -> Billing -> Credit Reasons or you can create a reason on the fly.
You can also add a small note in the "Additional info" field which will print on the customers invoice. Please keept this short as long text will get truncated on PDF invoices to prevent formatting issues.

Once the credit is applied the customers account will be balanced out:

<pre>
05/19/2015 Invoice #228 (Balance 0.00) (void)
( View invoice events ) $25.21 $25.21
05/19/2015 Payment by nkennedy (Credit card #411111xxxxxx1111)
10.00 refunded on 05/19/2015
15.21 applied to Invoice #228 (05/19/15)
(view receipt) (refund) (void) (unapply) - $25.21 $0.00
05/19/2015 Refund by nkennedy (Credit card #411111xxxxxx1111) (view receipt) $10.00 $10.00
05/19/2015 Credit by nkennedy (Package Error Credit for package error) applied to Invoice #228 (05/19/15) (delete) (unapply) (void) - $10.00 $0.00
</pre>

If you need to have taxes calculated as part of the refund you can start with issuing a credit using the Credit line items link. This will allow you to select the line item on the invoice and enter the amount to credit that entry.
Follow the rest of the instructions for re-applying the payment to the invoice and the left over balance is the amount you need to use after following the refund link on the payment.

== Commissions ==


* Setting up [[Freeside:3:Documentation:Administration:Commission|Commissions and Referrals]]

== VoIP ==

* Setting up [[Freeside:3:Documentation:Administration:VoIP | VoIP]]
* [[Simple Bulk DID Orders]]
* [[Bulk DID Orders]]
* [[Freeside:3:Documentation:Administration:VoIP:e911|e911 Providers]]

== RADIUS ==

* Setting up [[Freeside:3.0:Documentation:Administration:FreeRadius | FreeRadius]]

== Torrus Network monitoring ==

* [[Freeside:3:Documentation:Torrus_Installation | Installation]]
* [[Freeside:3:Documentation:Torrus_Administration | Administration]]

== Old / uncommon ==

* Setting up [[Freeside:3:Documentation:Administration:Time billing | Time billing]]
* Using a non-standard [[Freeside:3:Documentation:Administration:PostgreSQL_Schema | PostgreSQL Schema]]
* Setting up [[Freeside:3:Documentation:Administration:Slony | Slony replication and failover]] (old - PostgreSQL native replication is a more current solution)

{{ContextSensitiveHelp}}

Freeside:3:Documentation:Administration

2015-12-27T20:26:22Z

NathanK: /* Resellers */

= Exports (provisioning) =

'''Exports''' allow you to provision services to remote machines, databases and APIs. Some exports, such as ''sqlradius'' and ''sqlradius_withdomain'', enable a feed for retrieving rating/usage data.

Exports can be added and edited under
: Configuration -> Provisioning, services and packages -> View/edit exports

Most exports place jobs in the job queue for new, modified or deleted services. Jobs are run by [[Freeside:3:Documentation:Developer/bin/freeside-queued|freeside-queued]]. This daemon needs to be running before exports are acted upon.

Some exports use SSH, SCP or SFTP to communicate with external machines. See the documentation on [[Freeside:3:Documentation:Administration:SSH_Keys|SSH keys]].

Click on ''Add a new export'' to create a new export. Select exports from the dropdown to show more information on each export, including available options, setup and usage.

Exports are activated by associating them with one or more '''service definitions'''.

Following is a list of which exports can be associated with each type of service.

==svc_acct==
* [[Freeside:3:Documentation:Administration:acct_plesk.pm|acct_plesk.pm]]: Real-time export to Plesk managed mail service
* acct_sql.pm: Real-time export of accounts to SQL databases .
* artera_turbo.pm:
* bsdshell.pm:
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* communigate_pro_singledomain.pm:
* cpanel.pm: Real-time export to Cpanel control panel.
* cp.pm: Real-time export to Critical Path Account Provisioning Protocol
* cyrus.pm: Real-time export to Cyrus IMAP server
* everyone_net.pm: Real-time export to Everyone.net outsourced mail service
* infostreet.pm: Real-time export to InfoStreet streetSmartAPI
* [[Freeside:3:Documentation:Administration:ldap.pm|ldap.pm]]: Real-time export to LDAP
* passwdfile.pm:
* radiator.pm: Real-time export to RADIATOR
* shellcommands.pm:
* shellcommands_withdomain.pm: Real-time export via remote SSH (vpopmail, ISPMan)
* sqlmail.pm: Real-time export to SQL-backed mail server
* sqlradius.pm: Real-time export to SQL-backed RADIUS (FreeRADIUS, ICRADIUS)
* sqlradius_withdomain.pm: Real-time export to SQL-backed RADIUS (FreeRADIUS, ICRADIUS) with realms
* sysvshell.pm:
* textradius.pm:
* vpopmail.pm: Real-time export to vpopmail text files

==svc_domain==
* bind.pm: Batch export to BIND named
* bind_slave.pm: Batch export to slave BIND named
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* domain_shellcommands.pm: Run remote commands via SSH, for domains (qmail, ISPMan).
* domain_sql.pm: Real time export of domains to SQL databases .
* http.pm: Send an HTTP or HTTPS GET or POST request
* [[Freeside:3:Documentation:Administration:opensrs.pm|opensrs.pm]]: OpenSRS integration
* sqlmail.pm: Real-time export to SQL-backed mail server

==svc_forward==
* artera_turbo.pm:
* [[Freeside:3:Documentation:Administration:communigate_pro.pm|communigate_pro.pm]]: Real-time export to a CommuniGate Pro mail server
* forward_shellcommands.pm: Run remote commands via SSH, for forwards
* postfix.pm: Postfix text files
* sqlmail.pm: Real-time export to SQL-backed mail server

==svc_www==
* apache.pm: Export an Apache httpd.conf file snippet.
* [[Freeside:3:Documentation:Administration:www_plesk.pm|www_plesk.pm]]: Real-time export to Plesk managed hosting service
* www_shellcommands.pm: Run remote commands via SSH, for virtual web sites (directory maintenance, FrontPage, ISPMan)

==svc_broadband==
* nas_wrapper.pm: A meta-export that triggers other svc_broadband exports.
* [[Freeside:3:Documentation:Administration:prizm.pm|prizm.pm]]: Real-time export to Northbound Interface
* router.pm: Send a command to a router.
* snmp.pm: Sends SNMP SETs to an SNMP agent.
* trango.pm: Sends SNMP SETs to a Trango AP.

==svc_phone==
* globalpops_voip.pm:
* grandstream.pm: Grandstream phone and ATA provisioning. This [http://www.freeside.biz/blog/?p=11 blog article] is a start at documentation.
* indosoft.pm:
* internal_diddb.pm:
* netsapiens.pm:
* phone_shellcommands.pm:
* phone_sqlradius.pm:
* thirdlane.pm:
* [[Freeside:Documentation:Administration:vitelity.pm|vitelity.pm]]: Vitelity provisioning

==svc_external==
* artera_turbo.pm:

==svc_dsl==
* ikano.pm: see [[Freeside:3:Documentation:Administration:svc_dsl:ikano|Ikano DSL provisioning and qualifications]]

= Services =

== Generic ==

=== Accounts (svc_acct) ===

Accounts - anything with a username (mailbox, shell, RADIUS, etc.)

* [[Freeside:3:Documentation:Administration:svc_acct:_password_encoding|Password encoding]]

=== Hardware (svc_hardware) ===

Equipment supplied to customers

=== External (svc_external) ===

Externally-tracked service

== Access ==

=== DSL (svc_dsl) ===

* [[Freeside:3:Documentation:Administration:svc_dsl:ikano|Ikano DSL provisioning and qualifications]]

=== Broadband (svc_broadband) ===

Fixed wireless broadband

=== Cable (svc_cable) ===

=== DISH Network (svc_dish) ===

== Telephony ==

=== Customer phone number / DID (svc_phone) ===

* [[Freeside:Documentation:Administration:Phone devices|Phone devices]]

=== Customer PBX (svc_pbx) ===

=== Phone circuit (svc_circuit) ===

== Hosting ==

=== Domains (svc_domain) ===

=== Certificate (svc_cert) ===

=== Forwards (svc_forward) ===

=== Mailing list (svc_mailinglist) ===

=== Site hosting (svc_www) ===

== Colocation ==

=== Customer router/switch port (svc_port) ===

= Packages =

{{Freeside:3:Documentation:Administration:pkg_category}}

== Price Plans ==

=== Common price plans ===

* flat
* subscription
* prorate
* sqlradacct_hour
* [[voip_cdr]]
* prepaid

=== Wholesale price plans ===

* bulk

* [[Freeside:3:Documentation:Administration:Packages:Price_Plans:agent | agent]]
* [[Freeside:3:Documentation:Administration:Packages:Price_Plans:cdr_termination |
cdr_termination ]]

=== Other price plans ===

* flat_delayed
* flat_introrate
* prorate_delayed

* base_delayed
* base_rate

* sql_external
* sql_generic

=== Price plans of questionable functionality ===

* flat_comission_cust
* flat_comission_pkg
* flat_comission

* voip_sqlradacct

* sesmon_hour
* sesmon_minute

== Misc ==

* Some notes on [[Freeside:3:Documentation:Administration:Upselling | Upselling]]

= Resellers =

=== Wholesaler configuraiton ===
[[Freeside:3:Documentation:Administration:Wholesaler|Using agents for setting up Wholesalers]]

= Employees =

== Employees ==

Go to Configuration -> Employees -> Employees to view the existing employees and add new ones. It is highly recommended to add a separate account for each person rather than using role accounts.

* To add a new employee, click on "Add an employee"
* Or to edit an existing group, click on the employee number or name in the list of employees.
* Enter or edit the username, password and name. If editing an existing employee and no password change is desired, the password fields can be left blank.
* Check the "Disable employee" box to disable this employee.
* In the "Employee groups" section, mark or unmark checkboxes to indicate the access groups for this employee.

== Employee groups and access control ==

To setup employee access control or agent/reseller virtualization, you need to setup employee groups. Go to Configuration -> Employees -> Employee groups to view the existing groups and add new ones. The system starts with a "Superuser" group which has access to all functionality for the first agent.

* To add a new group, click on "Add an employee group"
* Or to edit an existing group, click on the group number or name in the list of groups.
* Enter or edit the group name.
* In the "Group limited to these agent(s)" section, mark checkboxes next to the agents this employee group should be able to see. Employees in this group will only see customers of the selected agents in the system and reports.
* In the "Group access rights" section, mark or unmark checkboxes to indicate the access rights this employee group should have. Rights marked with an "*" are global rights which provide access to global data which is shared among all agents. Their use is not recommended for groups which are limited to a subset of agents.
* After adding a new group, don't forget to go back and add or edit employees to place them into the new group.

= Installers / Appointments =

== Installers ==

* Designate some employees as installers (Configuration -> Employees -> Employees)
* Edit their schedules (Configuration -> Employees -> Installer availability)

== Ticketing ==

* Setup a queue for appointments (installations, removals, etc.), or use existing per agent queues
* Make sure the installer employees can own / see / edit tickets in this
queue (add them to a ticketing group with OwnTicket / SeeQueue on that queue or global, etc.)
* not yet <strike>XXX future todo some sort of ill-defined thing with configuring a custom field to designate install / recall / service call / removal</strike>

== Packages ==

not yet; package(+location)-specific appointments are a future TODO
<strike>
* Setup a package category for packages that can schedule appointments
* In the package category, select a queue for appointments or pick "Agent-specific queue"
</strike>

== Employee rights ==

* Upgrade should do this / should be available in a default install, but may not be implemented yet
* Give one or more employee groups "View appointments" and "Make appointment" (in Customer package rights)

= Billing =

== Billing events ==
Billing events are the primary mechanism to implement your business rules. Rules such as resend invoices, retry cards, suspend or cancel accounts for non-payment, etc. are all handled by billing events.

At a high level, follow the following steps to create billing events:
* Add a new Billing Event (Configuration > Billing > Billing events)
* Name the event
* Choose the type of event:
** Package - Packages and associated dates (Including Commissions)
** Invoice - Invoice status and dates
** Customer - Customer Balances and Information
** Batch Payment - Batch payment results
** Statement - Send statement
* Choose whether to apply to one or all agents
* Choose the frequency for the system to check and see if the event should run.
* Choose appropriate filters.
* Choose appropriate actions.

The form is dynamic so changing the type of event will change the available filters and actions.

== Daily and Monthly Scripts ==
* The freeside-daily script should be run daily to bill customers and run invoice collection events.
** Typically, this is accomplished with an entry in the freeside user's crontab such as: <pre>0 0 * * * /usr/local/bin/freeside-daily</pre>
** If running freeside-daily manually, ensure the <code>TZ</code> variable is set to your timezone with a command such as: <pre>TZ="US/Pacific" freeside-daily fs_daily</pre>
* If any monthly events are enabled, the freeside-monthly script should be run monthly.
* Invoice events can also be used to implement agent-virtualized invoices. (add more info)
* Be sure to include the full path of freeside-daily in your cron job.

== Invoices ==

=== Typeset (LaTeX) invoice templates ===

==== Prerequisites ====

* Almost all distributions include the necessary prerequisites listed here, manual installation is practically never necessary.
* Install [http://www.ghostscript.com/ Ghostscript] (gs)
* Install [http://www.tug.org/tetex/ teTeX] or [http://www.tug.org/texlive/ TeX Live]
* Ensure that the <code>pslatex</code>, <code>dvips</code>, and <code>pdflatex</code> command line utilities were installed

==== Logo setup ====

The EPS logo is for PDF and printed invoices.

* For best results, save a '''vector format''' logo in EPS (Encapsulated PostScript) format.
** Your graphic artist can create vector image from a bitmap (tracing etc).
** Converting a bitmap such as a JPG can work (the bigger the better), but it may render in lower quality, blurry or with the "jaggies" (especially when actually printed, not just viewed as a PDF)
* Resize the logo to 90pt X 36pt: <code>epsffit -c 0 0 90 36 yourlogo.eps >logo.eps</code>
** ("no %%BoundingBox:" error? Fix with eps2eps)
* Upload the resized logo as the <code>logo.eps</code> configuration option.
* Problems? Try <code>bin/strip-eps <oldlogo.eps >trynewlogo.eps</code>

The PNG logo is for emailed and online invoices.

Freeside ships with a logo of 92 x 62. Any logo close to this size should work with the default HTML template.

{{Freeside:3:Documentation:Administration:invoice_layout}}

=== HTML invoice templates ===

* Convert your logo to PNG format and upload it as the <code>logo.png</code> configuration option.
{{Freeside:3:Documentation:Administration:invoice_templates|format=html}}

=== Plaintext invoice templates ===

* See the Text::Template documentation for details on the substitution language.
* You must call the invoice_lines() function at least once - pass it a number of lines, and it returns a list of array references, each of two elements: a service description column, and a price column. Alternatively, call invoice_lines() with no arguments, and pagination will be disabled - all invoice line items will print on one page, with no padding (recommended for email invoices).
* Descriptions of variables are available in [[Freeside:3:Documentation:Template:invoice_html|invoice_html]]

=== Misc ===

==== Manually setting next customer number sequence ====

* With PostgreSQL, to number customers starting at 5000: <pre>SELECT SETVAL(pg_get_serial_sequence('cust_main', 'custnum'), 4999);</pre>
* With MySQL, to number customers starting at 5000: <pre>ALTER TABLE cust_main AUTO_INCREMENT = 5000;</pre>

==== Manually setting next invoice number sequence ====

* With PostgreSQL, to number invoices starting at 5000: <pre>SELECT SETVAL(pg_get_serial_sequence('cust_bill', 'invnum'), 4999);</pre>
* With MySQL, to number invoices starting at 5000: <pre>ALTER TABLE cust_bill AUTO_INCREMENT = 5000;</pre>

== Taxes ==

[[Freeside:3:Documentation:Administration:Tax_Districts | District based taxes]]

== Payment Receipts ==

The [[Freeside:3:Documentation:Template:payment_receipt_email|payment_receipt_email]] template is used for manually applied payments.

== Credit cards and Electronic checks ==
* [[Freeside:3:Documentation:Administration:Real-time_Processing | Real-time credit card and electronic check processing]]
* [[Freeside:3:Documentation:Administration:Batch_Processing | Batch credit card and electronic check processing]]
* Credit card expiration alerts: Customize the ''alerter_template'' configuration option and run <code>freeside-expiration-alerter</code> daily.
* Credit card decline alerts: Customize the ''declinetemplate'' configuration option and set the ''emaildecline'' configuration option.

= Misc =

These things should probably find a home properly filed in a section above.

== Invoicing and Payments ==

* Setting up [[Freeside:3:Documentation:Administration:Encrypted Credit Cards | Encrypted Credit Cards]] (default in new installs, highly recommended for older installs upgrading)
* Setting up [[Freeside:3:Documentation:Administration:Texas Tax | Texas Tax]]
* Need to print to Windows printers, and the PDF spool is not for you? Follow steps 1-4 of [http://iharder.sourceforge.net/current/macosx/winmacprinter/ Share Your Windows Printer].

== Commissions ==


* Setting up [[Freeside:3:Documentation:Administration:Commission|Commissions and Referrals]]

== VoIP ==

* Setting up [[Freeside:3:Documentation:Administration:VoIP | VoIP]]
* [[Simple Bulk DID Orders]]
* [[Bulk DID Orders]]
* [[Freeside:3:Documentation:Administration:VoIP:e911|e911 Providers]]

== RADIUS ==

* Setting up [[Freeside:3.0:Documentation:Administration:FreeRadius | FreeRadius]]

== Torrus Network monitoring ==

* [[Freeside:3:Documentation:Torrus_Installation | Installation]]
* [[Freeside:3:Documentation:Torrus_Administration | Administration]]

== Old / uncommon ==

* Setting up [[Freeside:3:Documentation:Administration:Time billing | Time billing]]
* Using a non-standard [[Freeside:3:Documentation:Administration:PostgreSQL_Schema | PostgreSQL Schema]]
* Setting up [[Freeside:3:Documentation:Administration:Slony | Slony replication and failover]] (old - PostgreSQL native replication is a more current solution)

{{ContextSensitiveHelp}}

Freeside:3:Documentation:Administration:Wholesaler

2015-12-27T20:23:19Z

NathanK: /* Using agents for setting up Wholesalers */

== Using agents for setting up Wholesalers ==

You can allow Wholesalers to manage their customers, resell your packages and perform all of their billing using your Freeside server. The following guide will help you setup your agents for this purpose. You will need to setup packages that use the wholesale price plans before you can bill your wholesalers.

*Create Master Customer:

#Follow the New customer link on the main menu bar
#Fill out the appropriate information for the customer and click the add customer button
#When the new customer is displayed follow the link for the Packages tab
#Order the appropriate Wholesale Billing packages for the customer (these packages are what
bills the Wholesaler for their customers packages).

*Create the Agent Type:

#Go to Configuration -> Companies -> Agent Types
#Follow the link labeled "Add a new agent type"
#Put the Agents name in the "Agent Type" field
#Select the packages that this Wholesaler will be allowed to order
#Click the Add agent type button

*Create the Wholesale Agent:

#Go to Configuration -> Companies -> Agents
#Follow the link labeled "Add a new agent"
#Enter the name for the Agent in the Agent Field
#Select the Agent type you created earlier
#Enter the customer number or name from the customer you created earlier in the Master Custoemr field
#Select the Superuser item from the Access Groups
#Click on the Add agent button

*Congigure the Agents settings:

#Go to Configuration -> Companies -> Agents
#Follow the link labeled (view/add/edit overrides) on the right hand side of the new agent
#Change the invoice_from, company_name, company_address, logo.eps, logo.png and any other
setting overrides to make sure everything is branded properly for your Wholesaler (to change
the value of a setting follow the link for the name of the setting and it will open a popup
window for you)

*Add Employee Group and Employee:

#Go to Configuration -> Employees -> Employee groups
#Follow the link labeled "Add an employee group"
#Enter the same name you used for the Agent name in the Group name field
#Select the new agent from the list of Agents (Do not select any other permissions)
#Click the Add Employee Group button
#Go to Configuration -> Employees -> Employees
#Follow the link labeled "Add an employee"
#Enter the Username, Password twice, Last name and First name
#Choose the Agent group created earlier and the Manager Group
#Click the Add Employee button

The username and password for this employee will be what the Wholesaler will use to log into
Freeside.

Freeside:3:Documentation:Administration:Wholesaler

2015-12-27T20:22:50Z

NathanK: Setting up agents as wholesalers

== Using agents for setting up Wholesalers ==

You can allow Wholesalers to manage their customers, resell your packages and perform all of their billing using your Freeside server. The following guide will help you setup your agents for this purpose. You will need to setup packages that use the wholesale price plans before you can bill your wholesalers.

*Create Master Customer:

#Follow the New customer link on the main menu bar
#Fill out the appropriate information for the customer and click the add customer button
#When the new customer is displayed follow the link for the Packages tab
#Order the appropriate Wholesale Billing packages for the customer (these packages are what
bills the Wholesaler for their customers packages).

*Create the Agent Type:

#Go to Configuration -> Companies -> Agent Types
#Follow the link labeled "Add a new agent type"
#Put the Agents name in the "Agent Type" field
#Select the packages that this Wholesaler will be allowed to order
#Click the Add agent type button

*Create the Wholesale Agent:

#Go to Configuration -> Companies -> Agents
#Follow the link labeled "Add a new agent"
#Enter the name for the Agent in the Agent Field
#Select the Agent type you created earlier
#Enter the customer number or name from the customer you created earlier in the Master Custoemr field
#Select the Superuser item from the Access Groups
#Click on the Add agent button

*Congigure the Agents settings:

#Go to Configuration -> Companies -> Agents
#Follow the link labeled (view/add/edit overrides) on the right hand side of the new agent
#Change the invoice_from, company_name, company_address, logo.eps, logo.png and any other
setting overrides to make sure everything is branded properly for your Wholesaler (to change
the value of a setting follow the link for the name of the setting and it will open a popup
window for you)

*Add Employee Group and Employee:

#Go to Configuration -> Employees -> Employee groups
#Follow the link labeled "Add an employee group"
#Enter the same name you used for the Agent name in the Group name field
#Select the new agent from the list of Agents
(Do not select any other permissions)
#Click the Add Employee Group button
#Go to Configuration -> Employees -> Employees
#Follow the link labeled "Add an employee"
#Enter the Username, Password twice, Last name and First name
#Choose the Agent group created earlier and the Manager Group
#Click the Add Employee button

The username and password for this employee will be what the Wholesaler will use to log into
Freeside.

Freeside:3:Documentation:Torrus Administration

2015-08-21T22:26:20Z

NathanK: /* References */

= Adding new routers =

== Web UI ==

* Go to Network Main -> Routers
* Click on "Add Router"

== Manually ==

Note: Execute these commands as the freeside user to retain correct permissions and allow the web UI to make changes.

cd /usr/local/etc/torrus/discovery
vi routers.ddx

Add a section like this at the bottom, just before the final </snmp-discovery>:

<host>
<param name="snmp-host" value="204.26.60.252"/>
</host>

Note: Execute these commands as the freeside user to retain correct permissions.

su - freeside
cd /usr/local/etc/torrus/discovery
torrus devdiscover --in=routers.ddx
torrus compile --tree=main --verbose

= Monitoring new interfaces =

== Torrus ==

=== Web UI ===

* Go to the "Interface traffic and error counters" page for an existing router.
* Click the "Monitor for Billing" link next to an interface.

=== Manually ===

cd /usr/local/etc/torrus/discovery
vi routers.ddx
<param name="RFC2863_IF_MIB::external-serviceid">
TESTING_1:TenGigabitEthernet2_1:Both:main,
TESTING_2:TenGigabitEthernet2_2:Both:main,
</param>

Note: Execute these commands as the freeside user to retain correct permissions.

su - freeside
cd /usr/local/etc/torrus/discovery
torrus devdiscover --in=routers.ddx
torrus compile --tree=main --verbose

If you add or change interfaces on a router you need to recompile the configuration database with the following commands:

cd /usr/local/etc/torrus/discovery
sudo -u freeside torrus devdiscover --in=routers.ddx
sudo -u freeside torrus compile --tree=main --verbose

== Freeside ==

* Setup an svc_port service definition, include it in a package definition with "Bandwidth (volume)" or "Bandwidth (95th percentile)" price plan.
* Order the package for a customer, and provision the Port service.
* The "Torrus serviceid" dropdown will have a list of the currently monitored serviceids.

= Virtual ports =

* Configuration -> Network Monitoring -> View/Edit virtual ports
* The freeside-torrus-srvderive daemon combines virtual port data from component ports.
* The following delays apply:
** If the virtual port combines existing ports _that are already being monitored for billing_, you will be able to view bandwidth graphs within 1 hour of adding the virtual port
** OR, if the virtual port combines NEW ports that have not yet been monitored for billing until the current day, it will take until the next morning for bandwidth graphs to appear.

= Trouble shooting =

* If Networking main displays the text "Error:Error initialzing Renderer" this typically means that the BerkeleyDB backend for Torrus has become corrupted
The database can be repaired with the following procedure:
/etc/init.d/freeside stop
db_recover -h /var/torrus/db
torrus compilexml --verbose --all
/etc/init.d/freeside start

= References =

* [http://torrus.org/install.pod.html Torrus install]
* [http://torrus.org/userguide.pod.html Torrus userguide]
* [http://torrus.org/reporting_setup.pod.html Torrus reporting setup]
* [http://torrus.org/userguide.pod.html#database_lock_troubleshooting Database troubleshooting]

Freeside:3:Documentation:Torrus Administration

2015-08-21T22:25:22Z

NathanK:

Freeside:3:Documentation:Torrus Administration

2015-06-30T00:09:18Z

NathanK: /* Manually */

= Adding new routers =

== Web UI ==

* Go to Network Main -> Routers
* Click on "Add Router"

== Manually ==

Note: Execute these commands as the freeside user to retain correct permissions and allow the web UI to make changes.

cd /usr/local/etc/torrus/discovery
vi routers.ddx

Add a section like this at the bottom, just before the final </snmp-discovery>:

<host>
<param name="snmp-host" value="204.26.60.252"/>
</host>

Note: Execute these commands as the freeside user to retain correct permissions.

su - freeside
cd /usr/local/etc/torrus/discovery
torrus devdiscover --in=routers.ddx
torrus compile --tree=main --verbose

= Monitoring new interfaces =

== Torrus ==

=== Web UI ===

* Go to the "Interface traffic and error counters" page for an existing router.
* Click the "Monitor for Billing" link next to an interface.

=== Manually ===

cd /usr/local/etc/torrus/discovery
vi routers.ddx
<param name="RFC2863_IF_MIB::external-serviceid">
TESTING_1:TenGigabitEthernet2_1:Both:main,
TESTING_2:TenGigabitEthernet2_2:Both:main,
</param>

Note: Execute these commands as the freeside user to retain correct permissions.

su - freeside
cd /usr/local/etc/torrus/discovery
torrus devdiscover --in=routers.ddx
torrus compile --tree=main --verbose

If you add or change interfaces on a router you need to recompile the configuration database with the following commands:

cd /usr/local/etc/torrus/discovery
sudo -u freeside torrus devdiscover --in=routers.ddx
sudo -u freeside torrus compile --tree=main --verbose

== Freeside ==

* Setup an svc_port service definition, include it in a package definition with "Bandwidth (volume)" or "Bandwidth (95th percentile)" price plan.
* Order the package for a customer, and provision the Port service.
* The "Torrus serviceid" dropdown will have a list of the currently monitored serviceids.

= Virtual ports =

* Configuration -> Network Monitoring -> View/Edit virtual ports
* The freeside-torrus-srvderive daemon combines virtual port data from component ports.
* The following delays apply:
** If the virtual port combines existing ports _that are already being monitored for billing_, you will be able to view bandwidth graphs within 1 hour of adding the virtual port
** OR, if the virtual port combines NEW ports that have not yet been monitored for billing until the current day, it will take until the next morning for bandwidth graphs to appear.

= References =

* [http://torrus.org/install.pod.html Torrus install]
* [http://torrus.org/userguide.pod.html Torrus userguide]
* [http://torrus.org/reporting_setup.pod.html Torrus reporting setup]