Page History

...

1. The user logs in to the service (meetingtools in this case). In the login context we find the usual attributes but also an attribute that both sais that the users is permitted to use phone-bridge functions aswell as what costCenter is associated with this function for billing purposes. This part (costCenter) could be an option and if missing all the costs are sent to the default sequencenumber for that customer.
2. Meetingtools upon finding the "pgi" flag for the user provisions a PGIConnect account and stores the PGIConnect-id (which will turn up later in the CDR records) in the user-profile in meetingtools along with the departmentNumber. Later we'll see how this can be generalized a little bit. Now we know that the user is authorized for phone-bridge and what the costCenter for phone-bridge-costs for this user is.
3. User creates a meeting and the PGI system starts a CDR record for that meeting.
4. Each month (or some other periodicity) we receive a set of CDR records from PGI. Each record (a line in an excel-file) contains a PGIConnect-id for the user that incurred the cost. We use the mapping from user to costCenter to emit an aggregated record (for that user) to the SUNET billing system with the customerid, sequencenumber and total cost (i.e we sum over all phone bridge-meetings created by that user in PGI).

...