|
Telecom Billing System
Q. How do I populate the Employee Directory in the Telecom Billing System module with the name and extension numbers from the PBX so I can run TBS reports?
A. Please refer to the 03/07 article TM CND and TBS Billing Synchronizations in Keeping Connected with ISI
Q. I have the TBS module for call accounting. With OTM I could access the Employee Hierarchy from the Station Administration module. Where do I build/maintain my Employee Hierarchy?
A. With TM the Station Administration module has been upgraded to an all new Web installment which is called Telephone Manager. The Organizational Hierarchy Editor and the Employee Selector are not available in Telephone Manager. They are exclusively accessed via the TBS Edit menu.
Q. I restored call data from an archived file back into the TBS module to run some reports on past data. I configured the filter for the report correctly but when I run the report, it states that there is no data found. What is wrong?
A. The reason may be that you restored a large portion of data in excess of 25K worth of calls. The TBS call database is comprised of two separate sections: A Collected database and a Costed database. The reports are run from the Costed database where the calls are labeled with the correct City, State or International country information as well as pricing. With larger volumes of data the system will only restore the Collected portion of the database. Simply run a manual re-cost of the restored archived data, and then run your reports. From the main TBS menu, perform the following:
- Select the Tools menu.
- Choose Costing → Start.
- Choose the FILTERED option in the Costing Mode box.
- Click on the More button to create a new filter or modify an existing one.
- Click the Start button to begin re-costing.
| Figure 8 - Select Filtered option for Costing |
 |
| Figure 9 - Re-cost Filter |
 |
Q. What information do I need from the PBX to program the TM Telecom Billing System module?
A. You will need a listing of each route in the PBX, plus the number of members and the Access code of each route. This information can be printed from Load 21. For the routes and access codes, print out the full Route Data Block. For the number of members in each route, process a List Trunks & Members (LTM).
LD 21
> REQ: PRT
TYPE: RDB
CUS: 0
ROUT: (enter)
ACOD: (enter)
> REQ: LTM
CUS: 0
ROUT: (enter)
ACOD: (enter)
Q. I am getting an error message when polling that the "Database is Full". What is the problem?
A. The TBS Microsoft Access database can hold a maximum of approximately 2.5 million call records. This figure can vary from system to system however the main item to know is that the database has a maximum file size limit of just over one gigabyte. This is a Microsoft Access limitation. When this limit is reached, regardless of the number of call records, call processing will cease. It is important to monitor this database and use the Archive/Purge utility to keep the file size well below this limit. Additionally, the database should be Compacted using the Compact utility found under the Utilities menu of the System window. Archiving/Purging of the database will not reduce the actual file "size" that is recorded by the Windows Operating System. The database file (CDRD001.mdb) must be compacted to record its true value. As an example, all call records could be purged from the database but the OS may still think the file size is at the maximum. It is not until the database is compacted that the OS will correct the designation of the file size. For monitoring purposes, the CDRD001.mdb file can be located via My Computer or Explorer in the Site/System folder.
Return to questions
|
