|
|
error(s) occurred, you should view the notification log on the dashboard or main screen to check for more details.
|
Medium |
|
|
|
|
|
|
'cp -rf' from src: '%s' to dst: '%s'...details follow
|
Medium |
|
|
|
|
|
|
A Dial Pattern is a unique set of digits that will select this route and send the call to the designated trunks. If a dialed pattern matches this route, no subsequent routes will be tried. If Time Groups are enabled, subsequent routes will be checked for matches outside of the designated time(s).
|
Medium |
|
|
|
|
|
|
A direct DID that is associated with this extension. The DID should be in the same format as provided by the provider (e.g. full number, 4 digits for 10x4, etc).<br><br>Format should be: <b>XXXXXXXXXX</b><br><br>.An optional CID can also be associated with this DID by setting the next box
|
Medium |
|
|
|
|
|
|
A user will enter this password when logging onto a device.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Asterisk may not be running.
|
Medium |
|
|
|
|
|
|
Authentication type to use for web admin. If type set to <b>database</b>, the primary AMP admin credentials will be the AMPDBUSER/AMPDBPASS above. When using database you can create users that are restricted to only certain module pages. When set to none, you should make sure you have provided security at the apache level. When set to webserver, FreePBX will expect authentication to happen at the apache level, but will take the user credentials and apply any restrictions as if it were in database mode.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Building Packaged Scripts...
|
Medium |
|
|
|
|
|
|
Callgroup(s) that this device is part of, can be one or more alpha/numeric callgroups, e.g. '1,3000-3005,sales,sales2'.
|
Medium |
|
|
|
|
|
|
Callgroup(s) that this device is part of, can be one or more alpha/numeric callgroups, e.g. '1,3000-3005,sales,sales2.'
|
Medium |
|
|
|
|
|
|
Cannot connect to Asterisk Manager with
|
Medium |
|
|
|
|
|
|
Cannot disable: The following modules depend on this one:
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Checking Online, Please Wait...
|
Medium |
|
|
|
|
|
|
Checking Signatures of Modules...
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Compressing Framework CSS...
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
DAHDI Channel DIDs allow you to assign a DID to specific DAHDI Channels. You can supply the same DID to multiple channels. This would be a common scenario if you have multiple POTS lines that are on a hunt group from your provider. You MUST assign the channel's context to from-analog for these settings to have effect. It will be a line that looks like:<br /><br />context = from-analog<br /><br />in your chan_dahdi.conf configuration effecting the specified channel(s). Once you have assigned DIDs you can use standard Inbound Routes with the specified DIDs to route your calls.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Default setting for (new Extension) SIP, DAHDi (and Zap) callgroup. Callgroup(s) that the device is part of, can be one or more callgroups, e.g. '1,3-5' would be in groups 1,3,4,5. See Asterisk documentation for details.
|
Medium |
|
|
|
|
|
|
Default setting for (new Extension) SIP, DAHDi (and Zap) pickupgroup. Pickupgroups(s) that the device can pickup calls from, can be one or more groups, e.g. '1,3-5' would be in groups 1,3,4,5. Device does not have to be in a group to be able to pickup calls from that group. See Asterisk documentation for details.
|
Medium |
|
|
|
|
|
|
Define the expected DID Number if your trunk passes DID on incoming calls. <br><br>Leave this blank to match calls with any or no DID info.<br><br>You can also use a pattern match (eg _2[345]X) to match a range of numbers
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Error fetching prefix list for:
|
Medium |
|
|
|
|
|
|
Error updating database. Command was: %s; error was: %s
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Error(s) have occured, the following is the retrieve_conf output:
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Forced downgrades and re-installs:
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Getting Data from Online Server...
|
Medium |
|
|
|
|
|
|
Getting Remote Repo list...
|
Medium |
|
|
|
|
|
|
If CallerID is supplied, the dialed number will only match the prefix + match pattern if the CallerID being transmitted matches this. When extensions make outbound calls, the CallerID will be their extension number and NOT their Outbound CID. The above special matching sequences can be used for CallerID matching similar to other number matches.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|