| 1 |
On Tue, 2006-12-12 at 17:04 -0700, Justin Findlay wrote: |
| 2 |
> On AD 2006 December 12 Tuesday 04:34:46 PM -0600, Michael Sullivan wrote: |
| 3 |
> > Can anyone give me a simple easy-to-understand place to start for |
| 4 |
> > setting up Asterisk? All I want it for is for Caller ID and to drop |
| 5 |
> > calls from certain phone numbers. I have a US Robots data/fax modem. |
| 6 |
> |
| 7 |
> Start here. |
| 8 |
> |
| 9 |
> http://voipspeak.net/images/stories/orielly/AsteriskTFOT.zip |
| 10 |
> |
| 11 |
> Read the first few chapters or so. Set aside having the answer Right |
| 12 |
> Now and devote some time to theory and concepts. The asterisk dialplan |
| 13 |
> configuration is a little difficult to understand at first, at least it |
| 14 |
> was for me. You can email me with any questions if you want or try |
| 15 |
> various means of the asterisk community. Both the official irc channel |
| 16 |
> |
| 17 |
> irc://irc.freenode.net/#asterisk |
| 18 |
> |
| 19 |
> and mailing list |
| 20 |
> |
| 21 |
> http://lists.digium.com/mailman/listinfo/asterisk-users |
| 22 |
> |
| 23 |
> are very active and usually helpful. |
| 24 |
|
| 25 |
I'm trying to follow the pdf in the link you sent me. On page 79 it |
| 26 |
lists some stuff to add to /etc/zaptel.conf (I emerged zaptel): |
| 27 |
|
| 28 |
"The zaptel.conf file located in /etc/ is used to configure your |
| 29 |
hardware. The following minimal configuration defines an FXO port with |
| 30 |
FXS signaling: |
| 31 |
|
| 32 |
fxsks=2 |
| 33 |
loadzone=us |
| 34 |
defaultzone=us |
| 35 |
|
| 36 |
After configuring zaptel.conf, you can load the drivers for the card. |
| 37 |
modprobe is used to load modules for use by the Linux kernel. For |
| 38 |
example, to load the wctdm driver, you would run: |
| 39 |
# modprobe wctdm |
| 40 |
|
| 41 |
If the drivers load without any output, they have loaded successfully.* |
| 42 |
You can verify that the hardware and ports were loaded and configured |
| 43 |
correctly with the use of the ztcfg program: |
| 44 |
# /sbin/ztcfg –vv |
| 45 |
The channels that are configured and the signaling method being used |
| 46 |
will be dis- |
| 47 |
played. For example, a TDM400P with one FXO module has the following |
| 48 |
output: |
| 49 |
Zaptel Configuration |
| 50 |
====================== |
| 51 |
Channel map: |
| 52 |
Channel 02: FXS Kewlstart (Default) (Slaves: 02) |
| 53 |
1 channels configured. |
| 54 |
If you receive the following error, you have configured the channel for |
| 55 |
the wrong sig-naling method: |
| 56 |
ZT_CHANCONFIG failed on channel 2: Invalid argument (22) |
| 57 |
Did you forget that FXS interfaces are configured with FXO |
| 58 |
signalling |
| 59 |
and that FXO interfaces use FXS signalling?" |
| 60 |
|
| 61 |
However, I get this: |
| 62 |
|
| 63 |
camille ~ # /sbin/ztcfg -vv |
| 64 |
|
| 65 |
Zaptel Configuration |
| 66 |
====================== |
| 67 |
|
| 68 |
|
| 69 |
Channel map: |
| 70 |
|
| 71 |
Channel 02: FXS Kewlstart (Default) (Slaves: 02) |
| 72 |
|
| 73 |
1 channels configured. |
| 74 |
|
| 75 |
ZT_CHANCONFIG failed on channel 2: No such device or address (6) |
| 76 |
|
| 77 |
I have no idea what it's talking about, or even what device or address |
| 78 |
it's trying to find... |
| 79 |
|
| 80 |
|
| 81 |
|
| 82 |
|
| 83 |
-- |
| 84 |
gentoo-user@g.o mailing list |
Archives