Ahmad,
I replied with an attachment with my configs, but it said that it's
awaiting moderation...
Meanwhile I just did some test with various FXO modes using dahdi_test
Kuwait Best: 99.980 -- Worst: 99.974 -- Average: 99.977131,
Difference: 99.977131
UK Best: 99.991 -- Worst: 99.985 -- Average: 99.988859, Difference: 99.988859
FCC Best: 99.992 -- Worst: 99.986 -- Average: 99.989719, Difference: 99.989719
GERMANY Best: 99.992 -- Worst: 99.987 -- Average: 99.989728,
Difference: 99.989728
I used to get much better numbers than these with trixbox 2.6. I don't
know which mode was used there...
On Sat, Aug 8, 2009 at 3:37 AM, Majed B.<majedb at gmail.com> wrote:
> I got it to change to UK mode! But that didn't fix the phone jack
> replugging thing :/
>
> The list of supported FXO modes is here:
> /usr/src/dahdi/linux/drivers/dahdi/xpp/init_fxo_modes
>
> before starting, stop asterisk then dahdi (in order):
> amportal stop
> service dahdi stop
>
> add this line to /etc/modprobe.conf or /etc/modprobe.d/dahdi
> options <card module name> opermode=UK
>
> (Country name has to be in capital, just as it is written in the FXO
> modes file above)
>
> You can find your card's name by typing:
> cat /proc/interrupts
>
> You'll find something like this:
> 217: 2026435 0 IO-APIC-level wctdm24xxp0
>
> (217 is the IRQ number).
>
> My card is: wctdm24xxp (notice: Remove the number at the end)
>
> If you notice that your card has the same IRQ number as something else
> in the list, change its PCI slot. If that doesn't work, disable
> whatever is using that IRQ from the BIOS (serial ports, USB, ...etc.).
>
> I changed it to both UK and KUWAIT modes but the phone jack replugging
> issue wasn't solved:
> root at pbx:~ $ dmesg | grep -i fx
> Port 1: Installed -- AUTO FXO (UK mode)
> Port 1: Installed -- AUTO FXO (KUWAIT mode)
>
> And I'm not sure if the values for Kuwait are correct, but I'm gonna
> keep it and try to find a solution for that replugging scam...
>
> I installed the backup & restore module through the GUI, ran a backup
> for system only and copied the file from: /var/lib/asterisk/backups/)
> -- I deleted some directories that enlarged the file size but where
> irrelevant to configs (modules, i18n, images, ..etc. from var/www)
>
> So you can now create your own backup schedule, then put my attached
> file and restore it, though I don't recommend you do that since your
> card is different than mine.
>
> On Sat, Aug 8, 2009 at 2:24 AM, Majed B.<majedb at gmail.com> wrote:
>> It appears that's not a timing issue. It works only after I unplug and
>> replug the phone jack!! o_O;;;
>>
>> I'll share my configs as soon as I fix this.
>>
>> As for the zone info, I've set them to UK, but the driver still loads
>> in us mode :/
>> root at pbx:~ $ dmesg | grep -i fx
>> Port 1: Installed -- AUTO FXO (FCC mode)
>>
>> I changed the parameters in /etc/dahdi/genconf_parameters:
>> lc_country uk
>>
>> That one sets the values of zones in system.conf when you run dahdi_genconf -Fv
>>
>> I'll keep digging till I get it to load the proper zone and see if
>> UK's settings work.
>>
>> On Fri, Aug 7, 2009 at 10:17 PM, Ahmad Al-Ibrahim<ahmad at koutbo6.com> wrote:
>>> Majed,
>>>
>>> What are the values you used for
>>> loadzone, defaultzone in /etc/dahdi/system.conf
>>> country in /etc/asterisk/indications.conf
>>>
>>> do you mind sharing chan-dahdi.conf and any other changed files?
>>>
>>> Regards,
>>>
>>> Ahmad Al-Ibrahim
>>>
>>> Majed B. wrote:
>>>> I can finally receive and make calls on the landline (PSTN)!
>>>>
>>>> I have no clue what made it work... Gonna take a backup of the current
>>>> configs and try to make it work again (and compare the config files to
>>>> a fresh installation).
>>>>
>>>> One post in a forum mentioned it was because asterisk was being
>>>> launched too soon...
>>>>
>>>> Ahmad,
>>>> Any progress on your end? Have you been able to work your card?
>>>>
>>>> On Fri, Aug 7, 2009 at 5:57 PM, Majed B.<majedb at gmail.com> wrote:
>>>>> Ahmad,
>>>>>
>>>>> If the card indicated a RED alarm when checking with the zap/dahdi
>>>>> tools, it means it's unable to detect the voltage on the line. That's
>>>>> when you try the cable trick.
>>>>>
>>>>> To check the alarm status:
>>>>> asterisk -rvvvvvvvvvv
>>>>> pbx*CLI> dahdi show status
>>>>> Description Alarms IRQ bpviol
>>>>> CRC4 Fra Codi Options LBO
>>>>> Wildcard TDM410P Board 1 OK 1 0 0
>>>>> CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)
>>>>>
>>>>> If you have zaptel, then type: zap show status
>>>>>
>>>>> I hope that makes it clearer a bit.
>>>>>
>>>>> As on my end, I was able to define the channels (FINALLY) for asterisk
>>>>> with dahdi! Seems like all I had to do is include dahdi-channels.conf
>>>>> into chan_dahdi.conf
>>>>>
>>>>> I can receive calls now, but I can't make any out, yet.
>>>
>>> _______________________________________________
>>> General mailing list
>>> General at oskw.org
>>> http://oskw.org/mailman/listinfo/general_oskw.org
>>>
>>
>>
>>
>> --
>> Majed B.
>>
>
>
>
> --
> Majed B.
>
--
Majed B.