New trixbox 2.4.1 machine with HFC card
Submitted by ACSS-001 on Tue, 01/08/2008 - 2:14pm.
I have just installed a clean machine with trixbox 2.4.1. This is the 13th installation of trixbox (from back to 2.0.0) with all the intermediate versions (2.1, 2.2, etc.). I have manage to have one good working (with a few problems) 2.0.0 with HFC Card on it and install-zaphfc script.
I have tried to install the script on a 2.2.x but with no luck
I have read almost all the topics about the HFC cards installation (install-zaphfc, mISDN, vISDN, etc) and I can say I am very confused on what is most apropriate to install so that to have a smooth working machine.
Can anyone help on my decision which is best to install? Is there any pros & cons on every installation? Any fully documented file (like the one from Suretec - thanks alot; you opened my eyes and helped me alot) on every installation?
And last, is there any way to make an image of the installed hard disk, so that when we reach apoint on to have to make all the configurations from the beginning?
Thanks alot for every answer I will receive.
I already used all methods
Tue, 01/08/2008 - 4:37pm
I already used all methods you mention and I got stick with mISDN. If you would like to install please use the wiki we created recently (see bellow). There is a new method getting the mISDN packages available at Trixbox beta repos which make it more simple and fast:
http://www.trixbox.org/wiki/chan-misdn
Regarding to install-ZAPHFC I'll let to W1zz to reply since he is the author of the script and he's being active in the forum.
I've not much to add. There
Tue, 01/08/2008 - 4:47pm
I've not much to add. There are pro's and con's to each approach.
If you want tighter integration with TB then it is best to install the card in a way which impacts the TB rpm's as little as possible.
install-ZAPHFC builds asterisk, zaptel, libpri and the HFC driver from scratch. So it will not include any extensions that may be in the rpm's.
W1zz, I have seen this on my
Tue, 01/08/2008 - 4:55pm
W1zz, I have seen this on my working 2.0.0. Doesn't do anything else (i.e. upgrade) only the ones I have put it to do, accept and make calls to 3 different trunks. B.T.W. I am trying to call (with the working one) via ZAP International numbers (starting with 00) and it acts crazy. It doesn't dials the 00 and starts dialing from the third digit. Any ideas Alan?
Thx alot, Alex - SV2ATD
Well that's why I said that
Tue, 01/08/2008 - 5:00pm
Well that's why I said that I didn't tested along with RPM versions. You have to configure differently when working with single or multiple port cards. If there isn't one please use the following:
single port (my own configuration, never messed with it):
[general] debug = 0 method=standard bridging=no stop_tone_after_first_digit=yes append_digits2exten=yes dynamic_crypt=no crypt_prefix=** crypt_keys=test,muh [default] context=misdn language=en musicclass=default senddtmf=yes far_alerting=no allowed_bearers=all nationalprefix=0 internationalprefix=00 rxgain=0 txgain=0 te_choose_channel=no pmp_l1_check=no reject_cause=16 need_more_infos=no nttimeout=no method=standard dialplan=0 localdialplan=0 cpndialplan=0 early_bconnect=yes incoming_early_audio=no nodialtone=no callgroup=1 pickupgroup=1 presentation=-1 screen=-1 echocancel=yes jitterbuffer=4000 jitterbuffer_upper_threshold=0 hdlc=no [isdn] ports=1 context=from-pstn msns=*
multiple port (got it from http://www.becyber.be/Thomas/Trixbox_BN4S0_guide_v2.html):
[general] misdn_init = /etc/misdn-init.conf debug = 0 bridging = yes stop_tone_after_first_digit = yes append_digits2exten = yes dynamic_crypt = no crypt_prefix = crypt_keys = [default] language = en [belgacom] ports = 1,2,3,4 context = from-trunk msns = * echocancel = no overlapdial = no senddtmf = yes far_alerting = yes te_choose_channel = no dialplan = 0 localdialplan = 0 cpndialplan = 0 nationalprefix = 0 internationalprefix = 00 rxgain = 0 txgain = 0
Compare both versions and you will noticed the main differences.
Unfortunately no luck.
Tue, 01/08/2008 - 5:31pm
Unfortunately no luck. Doesn't do anything. I tried to see if it's working as step:
11. Check if misdn is working at asterisk:
asterisk -r
misdn show stacks
You should see something like this:
BEGIN STACK_LIST:
* Port 1 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0
But got:
trixbox1*CLI> misdn show stacks
No such command 'misdn show' (type 'help' for help)
Can't understand what did I do wrong.
I will try the yum -y --enablerepo=trixboxbeta install mISDNuser mISDN-modules mISDN now to test this also.
Nope, nothing like that. No
Wed, 01/09/2008 - 7:27am
Nope, nothing like that. No error at compilation, and no chan_misdn.so. I am thinking that I will do a clean install and do everything from the begining. I will be online about 7.45pm GMT. Hope to meet online. I saw your PM and did what you asked me, also send you PM. See you later.
See my post to you
Wed, 01/09/2008 - 7:35am
See my post to you here:
http://www.trixbox.org/forums/trixbox-forums/trunks/trixbox-2-4-c...
Let's continue this subject in the post related to the wiki page. Download the lasted version of Trixbox 1.4.0.2 and follow the instruction mentioned on that same post.
Member Since:
2007-01-12