AX-100P single port FXO PCI interface card VoIP SIP IAX H.323 Asterisk
Product Description
Out of stock
AX-100P is a single port FXO PCI interface card for capturing a standard analog phone line into your Linux server with Asterisk PBX software. The AX-100P supports FXS Loopstart and "Kewlstart" (Loopstart with far end disconnection supervision).
It can detect ringing and remote hangup and fully supports Pseudo-TDM bridging through Zaptel. The device is fully supported by Asterisk PBX for both incoming and outgoing calls.
1. 100% identical to Digium's X100P card.
2. Be detected as "X100".
3. CallerID / BusyTone detection.
4. Suitable for SOHO PBX / VoiceMail / IVR.
5. Timming device for trunck / conference / MusicOnHold.
6. Starter device to study Zaptel / Asterisk.
7. Low cost channel for Fax server / Fax On Demand.
Specification:
>FXO
Loopstart
Kewlstart
>Interface:
1XFXO port
5.0V PCI interface
FAQ:
Q: What are the differences between FXS and FXO interfaces?
A.: FXS (Foreign eXchange Station) is an interface which drives a telephone. FXS interfaces get phones plugged into them, delivery battery, and provide ringing. FXS interfaces are signalled with FXO signalling. FXO (Foreign eXchange Office) is an interface that connect to a phone line. They supply your PBX with access to the public telephone network. FXO interfaces use FXS signalling. FXS interfaces are what allow you to hook telephones to your PBX, and FXO interfaces allow you to connect your PBX to real analog phone lines
Q: What is the difference between loopstart, groundstart, and kewlstart signalling?
A.: Loopstart signalling is used by virtually all analog phone lines. It allows a phone to indicate on hook/offhook, and the switch to indicate ring/no ring. Kewlstart is based on loopstart, but extends the protocol by allowing the switch to drop battery on the phone line to indicate to the phone that the other end of the party has disconnected the call. Most real phone switches, and almost no PBX's (except Asterisk, of course) support this feature. It is generally required for getting hangup notification. Groundstart signalling is sometimes used by PBX's. If you don't know what it is, don't worry, you won't need it.
Q: I'm using AX-100P and I have random call hangups. What can I do ?
A.: If you have busydetect=yes in zapata.conf then this is propably causing the problem. You might want to try to add busycount=5 or experiment a little bit with a busycount value. As a last resort you may just change busydetect to no: busydetect=no. Then asterisk won't try to detect the hangup on incoming calls. Notice that if "Loopstart with Remote Disconnection Supervision" (Kewlstart) is working for you than you don't need busydetect=yes at all. You can know if your current config is set
Q: How can I get start with AX-100P?
A.: Here is step by step guide:
a) Go into /usr/src directory on your linux box
> cd /usr/src
b) Download the latest CVS release of zapata,asterisk packages
> export
CVSROOT=:pserver:anoncvs@cvs.digium.com:/usr/cvsroot
> cvs login (password is anoncvs)
> cvs checkout zaptel asterisk
c) Compile all the packages in this order: zaptel/asterisk
> cd /usr/src/zaptel; make install
> cd ../asterisk; make install
> make samples
d) Edit configuration files and make sure they have at
least these lines:
/etc/zaptel.conf
fxsks=1 ;AX-100P
defaultzone=us
loadzone=us
/etc/asterisk/zapata.conf
[channels]
signalling=fxs_ks
context=incoming
channel=>1 ; AX-100P
/etc/asterisk/extensions.conf
[incoming]
exten => s,1,Echo ;for testing the connection
;exten => s,1,Playback,demo-thanks ;for playing a file
e) load the apropriate modules
> modprobe zaptel
> modprobe wcfxo
> ztcfg -vv
Note that you may run "make configs" in /usr/src/zaptel to install boot-up scripts so that you don't have to modprobe the drivers manually. That works well for RedHat 9.0.
f) everything is installed properly to run
> asterisk -vvvc
You may dial in now to the analog phone line connected to AX-100P and you should be able to hear yourself (with Echo application) or play a file (with Playback application).
AX-100P is a single port FXO PCI interface card for capturing a standard analog phone line into your Linux server with Asterisk PBX software. The AX-100P supports FXS Loopstart and "Kewlstart" (Loopstart with far end disconnection supervision).
It can detect ringing and remote hangup and fully supports Pseudo-TDM bridging through Zaptel. The device is fully supported by Asterisk PBX for both incoming and outgoing calls.
1. 100% identical to Digium's X100P card.
2. Be detected as "X100".
3. CallerID / BusyTone detection.
4. Suitable for SOHO PBX / VoiceMail / IVR.
5. Timming device for trunck / conference / MusicOnHold.
6. Starter device to study Zaptel / Asterisk.
7. Low cost channel for Fax server / Fax On Demand.
Specification:
>FXO
Loopstart
Kewlstart
>Interface:
1XFXO port
5.0V PCI interface
FAQ:
Q: What are the differences between FXS and FXO interfaces?
A.: FXS (Foreign eXchange Station) is an interface which drives a telephone. FXS interfaces get phones plugged into them, delivery battery, and provide ringing. FXS interfaces are signalled with FXO signalling. FXO (Foreign eXchange Office) is an interface that connect to a phone line. They supply your PBX with access to the public telephone network. FXO interfaces use FXS signalling. FXS interfaces are what allow you to hook telephones to your PBX, and FXO interfaces allow you to connect your PBX to real analog phone lines
Q: What is the difference between loopstart, groundstart, and kewlstart signalling?
A.: Loopstart signalling is used by virtually all analog phone lines. It allows a phone to indicate on hook/offhook, and the switch to indicate ring/no ring. Kewlstart is based on loopstart, but extends the protocol by allowing the switch to drop battery on the phone line to indicate to the phone that the other end of the party has disconnected the call. Most real phone switches, and almost no PBX's (except Asterisk, of course) support this feature. It is generally required for getting hangup notification. Groundstart signalling is sometimes used by PBX's. If you don't know what it is, don't worry, you won't need it.
Q: I'm using AX-100P and I have random call hangups. What can I do ?
A.: If you have busydetect=yes in zapata.conf then this is propably causing the problem. You might want to try to add busycount=5 or experiment a little bit with a busycount value. As a last resort you may just change busydetect to no: busydetect=no. Then asterisk won't try to detect the hangup on incoming calls. Notice that if "Loopstart with Remote Disconnection Supervision" (Kewlstart) is working for you than you don't need busydetect=yes at all. You can know if your current config is set
Q: How can I get start with AX-100P?
A.: Here is step by step guide:
a) Go into /usr/src directory on your linux box
> cd /usr/src
b) Download the latest CVS release of zapata,asterisk packages
> export
CVSROOT=:pserver:anoncvs@cvs.digium.com:/usr/cvsroot
> cvs login (password is anoncvs)
> cvs checkout zaptel asterisk
c) Compile all the packages in this order: zaptel/asterisk
> cd /usr/src/zaptel; make install
> cd ../asterisk; make install
> make samples
d) Edit configuration files and make sure they have at
least these lines:
/etc/zaptel.conf
fxsks=1 ;AX-100P
defaultzone=us
loadzone=us
/etc/asterisk/zapata.conf
[channels]
signalling=fxs_ks
context=incoming
channel=>1 ; AX-100P
/etc/asterisk/extensions.conf
[incoming]
exten => s,1,Echo ;for testing the connection
;exten => s,1,Playback,demo-thanks ;for playing a file
e) load the apropriate modules
> modprobe zaptel
> modprobe wcfxo
> ztcfg -vv
Note that you may run "make configs" in /usr/src/zaptel to install boot-up scripts so that you don't have to modprobe the drivers manually. That works well for RedHat 9.0.
f) everything is installed properly to run
> asterisk -vvvc
You may dial in now to the analog phone line connected to AX-100P and you should be able to hear yourself (with Echo application) or play a file (with Playback application).