[Home]

Summary:ASTERISK-03718: [request]: PBX identification for handle multiple PBX with one CDR DB
Reporter:Fernando Romo (el_pop)Labels:
Date Opened:2005-03-20 00:51:06.000-0600Date Closed:2011-06-07 14:04:45
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/NewFeature
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:For centralize CDR information in one DB, i need to identify the PBX via a Unique identification in each Asterisk Server.

Set a new variable in cdr_xxxx.conf to label with a unique value each Asterisk server and identify easy each call and originator equipment, The "unique" identificator for each call is not enough for handle a "Asterisk Farm" (or cluster) and register the calls in high density deployments.

****** ADDITIONAL INFORMATION ******

The request is to modify the cdr sql layout to include the "pbx_id" value in each record in the DB (MySQL, Postgres, etc.) and generate a New Variable in cdr conf file or in asterisk.conf as well.

Example: A company than bring office infraestructure to many companys (vg HQ) has a 15 floor building and has 1 company in each floor with one Asterisk Server (In total 15 Asterisk Systems conected between IAX). But The company in floor 3 and 12 want the extensions 10XX, the Host company need to identify the calls from the companys and billing the calls right. The Host company has a good DB server and request to handle all the call registry in the available DB engine.

Maybe sound worthless, but the admin of calls and billing is more easy with this tiny change. Like a colateral effect, we can make a Universal_PB_ID number than simplify the creation of a "Asterisk Yellow Page" and help Dundi to know each equipment in the trusted voice network.

Your comments are welcome.
Comments:By: Olle Johansson (oej) 2005-03-20 02:00:14.000-0600

Please file feature requests in the "feature requests" category, thank you.
For now, I recommend that you use the cdr user field for this.

Long term, we need this kind of variable for the logging system, billing records as well as realtime databases.
By: Olle Johansson (oej) 2005-05-02 11:19:00

Closing this feature request - no programmer jumped on it and it will stay in the archives. If you want it done, post a bounty or contract a developer.