1. FreePBX
2. dahdiconfig
3. source strings
4. review

Wanrouter Failed: %s

Wanrouter Started

Wanrouter Stopped

Whether or not to enable call waiting on internal extensions. With this set to "yes", busy extensions will hear the call-waiting tone, and can use hook-flash to switch between callers. The Dial() app will not return the "BUSY" result for extensions.

Whether or not to support Call Return (*69, if your dialplan doesn't catch this first)

Whether or not to use caller ID

Whether or not to use the caller ID presentation for the outgoing call that the calling switch is sending

Writing out default Sangoma conf

Yemen

Yes

You have new hardware! Please configure your new hardware using the edit button(s)

You most likely dont need this feature. Default is yes. <br />When this is set to yes, all calls that are offered (incoming calls) for which DNIS is valid (exists in extensions.conf) and also pass collect call validation will be accepted with a Group B tone (either call with charge or not, depending on mfcr2_charge_calls).<br />With this set to 'no' then the call will NOT be accepted on offered and the call will start its execution in extensions.conf without being accepted until the channel is answered (either with Answer() or any other application resulting in the channel being answered). <br />This can be set to 'no' if your telco or PBX needs the hangup cause to be set accurately. <br />When this option is set to 'no' you must explicitly accept the call with DAHDIAcceptR2Call or implicitly through the Answer() application.<br /> <strong>Default:</strong>yes

add additional column

alaw

collect_call

dahdi_scan exists but can not be run as this user!

fcc

gsm

international_priority_subscriber

international_subscriber

national_priority_subscriber

national_subscriber

none - Performs no detection

none - Performs no detection

software EC to use in system.conf

ulaw