I looked in sipXacccode/src/main/java/org/sipfoundry/authcode/AuthEnter.java and it does not appear to log the accepted auth code. Create an issue, i think creating a log would be useful i think. It should also log caller and destination so one could match their destination w/cdrs.
On Thu, Nov 11, 2010 at 10:36 AM, Kyle Haefner <[email protected]> wrote: > Regarding Authorization codes... does anyone know, when an auth code is used > does it show up in the database in any way? The end goal for us and auth > codes it to be able to bill based on auth code. > Thanks! > Kyle > > On Thu, Nov 11, 2010 at 2:57 AM, Hiranmayee Sahoo (JIRA) > <[email protected]> wrote: >> >> [ >> http://track.sipfoundry.org/browse/XX-8501?page=com.atlassian.jira.plugin.system.issuetabpanel:all-tabpanel >> ] >> >> Hiranmayee Sahoo resolved XX-8501. >> ---------------------------------- >> >> Assignee: Raymond Dans >> Fix Version/s: 4.3.1 >> (was: 4.3.2) >> Resolution: Fixed >> >> > Authorization Codes >> > -------------------- >> > >> > Key: XX-8501 >> > URL: http://track.sipfoundry.org/browse/XX-8501 >> > Project: sipXecs >> > Issue Type: New Feature >> > Reporter: Raymond Dans >> > Assignee: Raymond Dans >> > Fix For: 4.3.1 >> > >> > >> > Authorization codes provides the capability of a user to temporarily >> > (usually for the next call) gain a set of calling privileges/permissions >> > that the user does not normally have. These privileges only apply to the >> > call in question. Any other normally initiated call uses the regular >> > assigned permissions for that user. >> > An example of the use of Authorization code is in a school environment >> > where each classroom has a telephone. In order to prevent misuse of the >> > classroom phone (possibly by the students), the user that the phone is >> > registered with has very limited call permissions (say Emergency and >> > internal calls only). If the teacher has to make an external call that >> > possibly requires long distance permissions, they could dial the >> > Authorization code feature (say something like *81). The teacher would >> > then >> > be prompted for a valid authorization code and the destination dial string. >> > If the authorization code is validated the call would then proceed with >> > the >> > permissions assigned to this code. >> > Configuration of this feature will require the ability to: >> > 1. modify the Authorization code feature code (default possibly *81) >> > 2. add/delete a number of authorization codes. >> > 3. assign call permissions for each authorization code. >> > It is not necessary (at least in this iteration) to assign an >> > Authorization code to a user. In other words, any user can use any define >> > authorization code. >> > The feature should only accept the authorization feature code in the >> > original dialing as we do not want the redial or phone log capabilities to >> > record the actual authorization code entered as this would then be a >> > security hole. >> >> -- >> This message is automatically generated by JIRA. >> - >> If you think it was sent incorrectly contact one of the administrators: >> http://track.sipfoundry.org/secure/Administrators.jspa >> - >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> >> > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
