Difference between revisions of "Authorization by ANI"
| Line 38: | Line 38: | ||
= If the system asks for a PIN to be entered = | = If the system asks for a PIN to be entered = | ||
This occurs if the CallerID comes in a different format | This occurs if the CallerID comes in a different format from that which is entered in the Device CID. Use [[Last Calls]] to check it and [[Number Manipulation]] to fix it. | ||
= See also = | = See also = | ||
* [[Dial Plans]] | * [[Dial Plans]] | ||
Revision as of 05:36, 16 May 2010
Authorization by Automatic Number Identification (ANI) is a variant of the [[Authorization by PIN | Auth. by PIN method] that makes the system act in a different way. If you check the Use ANI? field in the Dial Plan creation window, the user's CallerID will be checked automatically when he dials in, and he will only be asked to enter his PIN if his CallerID is not found.
CallerIDs are entered for every device in Device Settings using the 
icon.
ANI - Automatic Number Identification
ANI is used to authenticate who is calling, by CallerID.
When a call comes into MOR, the CallerID is checked with all available CLI's in the database. If a match is found, the call is authorized and assigned to the device which CLI has matched against the CallerID of the call:
All other details are the same as for Authorization by PIN dial plan, and the dial plan is created in the same way. Just check Use ANI?:
In main Dial Plan window, we have:
Note the difference between Auth. by PIN and Auth. by ANI dial plans.
Assigning a DID is similar to Auth. by PIN method.
ATTENTION! Be careful because it is very easy to fake a CallerID.
Troubleshooting
If the system asks for a PIN to be entered
This occurs if the CallerID comes in a different format from that which is entered in the Device CID. Use Last Calls to check it and Number Manipulation to fix it.
