text stringlengths 0 152 |
|---|
#loadzone=de |
#loadzone=uk |
#loadzone=fi |
#loadzone=jp |
#loadzone=sp |
#loadzone=no |
#loadzone=hu |
#loadzone=lt |
#loadzone=pl |
defaultzone=us |
# |
The /etc/dahdi/system.conf file uses the hash symbol (#) to indicate |
a comment instead of a semicolon (;) like the files in /etc/asterisk. |
PSTN Connectivity, DAHDI, Digium Cards, and Analog Phones |
| |
155 |
Although it is possible to load a number of different tone sets (you can see all the sets |
of tones in detail in zonedata.c) and to switch between them, in most practical situa‐ |
tions you will only need: |
loadzone=uk # to load the tone set |
defaultzone=uk # to default DAHDI to using that set |
…or whichever tones you need for your region. |
If you perform a dahdi_genconf to automatically (or should that be auto-magically?) |
configure your DAHDI adapters, you will notice that the newly generated /etc/dahdi/ |
system.conf will have defaulted both loadzone and defaultzone to being us. Despite |
the warnings not to hand-edit the file, it is fine to change these settings to what you |
need. |
In case you were wondering how we tell whether there are any voicemails in the mail‐ |
box associated with the channel an analog phone is plugged into, it is done with a |
stuttered dialtone. The format of this stuttered dialtone is decided by the loadzone/ |
defaultzone combination you have used. |
As a quick aside, analog phones that have a message-waiting indicator (e.g., an LED |
or lamp that flashes to indicate new voicemail) achieve this by automatically going |
off-hook periodically and listening for the stuttered dialtone. You can witness this by |
watching the Asterisk command line to see the DAHDI channel go active (if you have |
nothing better to do!). |
That’s it at the DAHDI level. We chose the protocol(s) for PRI or BRI connections, |
the type of signaling for the analog channels (all covered in Chapter 7), and the tones |
for the analog connections that have just been discussed. |
The relationship between Linux, DAHDI, and Asterisk (and therefore /etc/dahdi/ |
system.conf and /etc/asterisk/chan_dahdi.conf) is shown in Figure 9-5. |
Once you have completed your configuration at the DAHDI level |
(in /etc/dahdi/system.conf), you need to perform a dahdi_cfg -vvv to |
have DAHDI reread the configuration. This is also a good time to |
use dahdi_tool to check that everything appears to be in order at |
the Linux level. |
This way, if things do not work properly after you have configured |
Asterisk to work with the DAHDI adapters, you can be sure that |
the problem is confined to chan_dahdi.conf (or an #included dahdi- |
channels.conf if you are using this part of the dahdi_genconf |
output). |
156 |
| |
Chapter 9: Internationalization |
Figure 9-5. The relationship between Linux, DAHDI, and Asterisk |
Internationalization Within Asterisk |
With everything set at the Linux level, we now only need to configure Asterisk to |
make use of the channels we just enabled at the Linux level and to customize the way |
that Asterisk interprets and generates information that comes in from, or goes out |
over, these channels. This work is done in /etc/asterisk/chan_dahdi.conf. |
In this file we will not only tell Asterisk what sort of channels we have (these settings |
will fit with what we already did in DAHDI), but also configure a number of things |
that will ensure Asterisk is well suited to its new home. |
Caller ID |
A key component of this change is caller ID. While caller ID delivery methods are |
pretty much standard within the BRI and PRI world, they vary widely in the analog |
world; thus, if you plugged an American analog phone into the UK telephone net‐ |
work, it would actually work as a phone, but caller ID information would not be dis‐ |
played. This is because that information is transmitted in different ways in different |
places around the world, and an American phone would be looking for caller ID sig‐ |
naling in the US format, while the UK telephone network would be supplying it in |
the UK format (if it is enabled—caller ID is not standard in the UK; you have to ask |
for and sometimes even pay for, it!). |
Not only is the format different, but the method of telling a telephone (or Asterisk) to |
look out for the caller ID may vary from place to place, too. This is important, as we |
Internationalization Within Asterisk |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.