X100P No Worky?

[peterbata]

Hello. First time post. A little heads-up before I begin. I have spent the last week reading through posts here and elsewhere. I have tried to resolve my issue on my own, but alas I must turn to the experts. I apologize in advance if my post seems somewhat long-winded.

Here is my situation.

I am using what seems to have become the dreaded communication card of choice. The X100P Clone purchased from here approx 1 year ago:

http://www.x100p.com/products/FXO.php

I have installed the latest PIAF distro 32bit and taken in all of the module updates.

I had never been able to either dial out or receive calls until I read and followed this post 2 days ago.

freepbx.org/forum/freepbx/installation/x100p-clone-card-from-x100p-com-and-dahdi#comment-45838

Look for this instructional post: On January 13th, 2012 rkaczano (tadpole) said:

After countless frustrating hours/days I followed his steps to the letter. Lo and behold all was good in my PIAF world.

So what do I do next you ask? Courageous me decides to perform a fresh install of the distro again following the instructional steps one line at a time. I have never successfully made or received a call since. It is driving me absolutely insane. I should also mention that I have attempted miserably to repeat the same in Trixbox, Elastix, FreePBX, and AsterixNOW.

It appears to me that the card is being properly recognized. However, I am very new to all of this and know of no other was to diagnose my situation. I realize now, from what I have read, that the X100P is a low budget glorified modem. I cannot afford anything else at the moment but would like to learn. If it totally not compatible, I understand. But what bothers me the most is that I was able to have it function once, but am unable to do so again!

Thank you all in advance. Your patience and assistance would be greatly appreciated.

Here are some screenshots for what its worth.

http://i42.tinypic.com/whzdjq.jpg

http://i40.tinypic.com/fa3ckw.jpg

http://i42.tinypic.com/2ut2tk1.jpg

http://i43.tinypic.com/157rkn.jpg

http://i41.tinypic.com/kb99vo.jpg

http://i42.tinypic.com/zvsos1.jpg

 

[blanchae]

I was playing with the Dahdi config module last week and it wasn't updating the signaling from loop start (LS) to kewl start (KS). After trying for a while, we gave up and did a manual config. I think that the dahdi config module is broken.

 

[blanchae]

Here's a manual config that should work for you:

Configure /etc/dahdi/system.conf for

fxsks=1
echocanceller=mg2,1

loadzone = us         [I]<= or whatever is appropriate[/I]
defaultzone = us

Add the following line to the end of /etc/asterisk/chan_dahdi.conf for:

#include chan_dahdi_custom.conf

Create a new file /etc/asterisk/chan_dahdi_custom.conf with the following in it:

;;; This is the FXO port 1 using FXS signaling  [I]<= yes it's true![/I]
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
context=default

Now shut down asterisk from the Linux CLI: amportal stop
Restart dadhi: "service dahdi restart"
Start asterisk" "amportal start"

Run dahdi_tool, should see your card, nothing else to see here, move on.
Open the asterisk CLI> type "help dahdi", if dahdi is configured correctly, then there should be help if not then there's an error in the config of one of the above files. If it does work, type "dahdi show channels" and you should see your FXO port. Dahdi and Zaptel are house of cards, if one typo, nothing works.

Now the inbound and outbound routes should start to work.

 

[peterbata]

Thank you!

First, I would get rid of the DAHDI Config module. Tho they may well exist, I have yet to see a first hand account from anyone who has successfully configured an analog card using this module.

Second, pour a cup of coffee and read Blanchae's most excellent tutorial (in several parts) on how to set up an analog card.

Briankelly63 has a nice summary here.

 

[peterbata]

Good morning. My apologies for not getting back to you sooner. I understand why your membership status is "guru". Your mods definitely worked. I only wish that I understood why. I suppose that I have quite a bit of learning ahead of me.

After applying the mods I was able to both make and receive calls. Thank you immensely for getting me over this huge speed bump. Have a wonderful day / evening. Peter

Here's a manual config that should work for you:

Configure /etc/dahdi/system.conf for

fxsks=1
echocanceller=mg2,1

loadzone = us         [I]<= or whatever is appropriate[/I]
defaultzone = us

Add the following line to the end of /etc/asterisk/chan_dahdi.conf for:

#include chan_dahdi_custom.conf

Create a new file /etc/asterisk/chan_dahdi_custom.conf with the following in it:

;;; This is the FXO port 1 using FXS signaling  [I]<= yes it's true![/I]
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
context=default

Now shut down asterisk from the Linux CLI: amportal stop
Restart dadhi: "service dahdi restart"
Start asterisk" "amportal start"

Run dahdi_tool, should see your card, nothing else to see here, move on.
Open the asterisk CLI> type "help dahdi", if dahdi is configured correctly, then there should be help if not then there's an error in the config of one of the above files. If it does work, type "dahdi show channels" and you should see your FXO port. Dahdi and Zaptel are house of cards, if one typo, nothing works.

Now the inbound and outbound routes should start to work.

 

[blanchae]

Dahdi (Zaptel v2) is different then VoIP. VoIP uses the existing network card (Ethernet or WiFI) so there's no hardware setup. With legacy interfaces, the Dahdi interface has to be setup. The kernel for PiaF is already aware of Dahdi so no kernel drivers need to be used. There are specific kernel modules that are loaded when the kernel detects them. All of the above is automatic, don't have to worry about them providing that the legacy card is working properly.

/etc/dahdi/system.conf

This file configs the legacy card driver as to how we are going to use it. In your case, it is a FXO card that is going to expect to connect to something providing dialtone (FXS line), is going to use kewlstart signaling (KS) and use the MG2 echo canceller. Lastly, we assign which voice channel it will be identifed by (channel 1).

 

[peterbata]

I will be going to bed a little smarter this evening. I appreciate it so much. Thanks again. Peter

Dahdi (Zaptel v2) is different then VoIP. VoIP uses the existing network card (Ethernet or WiFI) so there's no hardware setup. With legacy interfaces, the Dahdi interface has to be setup. The kernel for PiaF is already aware of Dahdi so no kernel drivers need to be used. There are specific kernel modules that are loaded when the kernel detects them. All of the above is automatic, don't have to worry about them providing that the legacy card is working properly.

/etc/dahdi/system.conf

This file configs the legacy card driver as to how we are going to use it. In your case, it is a FXO card that is going to expect to connect to something providing dialtone (FXS line), is going to use kewlstart signaling (KS) and use the MG2 echo canceller. Lastly, we assign which voice channel it will be identifed by (channel 1).

 

[blanchae]

Sorry, I'm writing the explanation on a break between classes that I'm teaching.

/etc/asterisk/chan_dahdi.conf

This is the main Asterisk config file for Dahdi. It points to other config files using the direction "#include". The "#" is part of the command not a comment. We add a custom config file call chan_dahdi_custom.conf and tell Asterisk to look at by using the #include command.

In the chan_dahdi_custom.conf, we tell asterisk how to find the FXO channel, what type of port, group, signaling, etc. And which context to use. This is for FXO trunks only. FXS sets are configured as extensions in FreePBX. FreePBX will add the appropriate info in /etc/asterisk/chan_dahdi_additional.conf

If we have more than one channel, we can group them together on a use the first channel available - these are called groups. You can select which channels belong to which groups. In FreePBX, you indicate a group using g0 or G0. g0 selects channels in an ascending order and G0 uses channels in descending order.

 

[peterbata]

Again I thank you for sacrificing your personal time to assist me. It really means a lot to me. What you have told me so far has really peaked my interest. I guess I will be investing more time and energy reading what I can on the subject. Have a wonderful day.

Sorry, I'm writing the explanation on a break between classes that I'm teaching.

/etc/asterisk/chan_dahdi.conf

This is the main Asterisk config file for Dahdi. It points to other config files using the direction "#include". The "#" is part of the command not a comment. We add a custom config file call chan_dahdi_custom.conf and tell Asterisk to look at by using the #include command.

In the chan_dahdi_custom.conf, we tell asterisk how to find the FXO channel, what type of port, group, signaling, etc. And which context to use. This is for FXO trunks only. FXS sets are configured as extensions in FreePBX. FreePBX will add the appropriate info in /etc/asterisk/chan_dahdi_additional.conf

If we have more than one channel, we can group them together on a use the first channel available - these are called groups. You can select which channels belong to which groups. In FreePBX, you indicate a group using g0 or G0. g0 selects channels in an ascending order and G0 uses channels in descending order.