|
%s already used, please use a different description.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Allow creation of lists of PINs (numbers for passwords) that can be used by other modules (eg, trunks).
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Enter a list of one or more PINs. One PIN per line.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Optional: Select a PIN set to use. If using this option, leave the Route Password field blank.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
PIN Sets are used to manage lists of PINs that can be used to access restricted features such as Outbound Routes. The PIN can also be added to the CDR record's 'accountcode' field.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Please enter a description for this pinset
|
Medium |
|
|
|
|
Please enter a valid Description
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Select Yes, if you would like to record the PIN in the call detail records when used
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
checking if migration required..
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
unknown error fetching table data
|
Medium |
|
|
|