1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. If you had a PIAF Forum account in the vBulletin days, log in with your old credentials. Otherwise, sign up again and we'll get you back in business as soon as we can.
  3. Please limit message subjects in new threads to 40 CHARACTERS or less! Otherwise, nobody can reply to your post! We're working on it. Suhosin sucks!

Rhino RCBFX trouble

Discussion in 'Help' started by keelingj, Apr 3, 2008.

  1. keelingj New Member

    My Rhino RCBFX cards haven't played nice with Trixbox since v2.2.12 and Rhino driver 2.2.1-beta2, so I thought I'd give PBXIAF a try.

    I followed the instructions here:

    http://pbxinaflash.com/forum/showthread.php?t=422

    The drivers (2.2.5.0) compile and install properly. The RCBFX module loads correctly as well. I can generate the configuration with genzaptelconf and configure the lines with ztcfg. If I run ZTTOOL, I can see 2 Rhino cards with OK status.

    However, if I try to place a call using the Rhino cards or dial a line connected to the Rhino cards, PBXIAF hardlocks and I have to power down the system manually.

    I have tried building older versions of the Rhino drivers (2.2.4, etc) with no success (typically results in a kernel panic on module load). I also tried switching system hardware from an Intel 865 board to an nVidia 6-series with no luck.

    Any suggestions?
  2. james Guru

    This is a platform issue. We are having a quite a few issues trixbox side. We are doing all of our debugging on pbx in a flash as it is source based.

    This has something to do with the way chan_zap calls EC with zaptel 1.4.9.2. You can drop your zaptel down to 1.4.8 you shouldn't need to rebuild the rhino Drivers.

    This issue only happens on Intel boards and on AMDx2 we don't know why but AMD single cores seem unaffected. We are doing a driver rewrite currently to see if we can compensate for the chan_zap issues... That all said our engineer has pbx in a flash up with all the latest updates at home and it works with an AMD x2 so it may be the chipset not the processor. We have full resources invested in a resolution.
  3. keelingj New Member

    James,

    I did some more testing with a fresh install on a Dell Dimension E521 (nForce 430 chipset and AMD Athlon 3200+ single core CPU). Same lockup problem as the Intel board.

    I suppose I could revert to Trixbox 2.4, but I'm having the following problem with the 2.4 branch: Rhino drivers (RPM or source) install and configure OK. However, system refuses to either answer the Rhino cards or use them to place outbound calls. System is pretty useless in that state!

    I could go back to 2.2.12, but that version's Asterisk borks itself when you save Zaptel extensions in FreePBX. Also, my Rhino cards stop responding (same as my Trixbox 2.4 issue) if drivers newer than (rhino-2.6.9-34.0.2.ELsmp-2.2.1beta2-1.i386.rpm) are used.
  4. euser4life Guru

    Since you already have PBX in a Flash loaded...

    You should just do the following:

    Go to this link:
    http://pbxinaflash.org/update_source.htm

    Follow the instructions there (pay attention to the bottom part - and edit the source14.conf file that you placed in the /usr/local/sbin to use zaptel 1.4.8)
    #ZAPTEL="zaptel-1.4-current"
    ZAPTEL="zaptel-1.4.8"

    Now you should be able to run update-source and it automagically recompile everything for you... It is relatively painless and hopefully will fix your problem. Let us know if this helps....

    Will
  5. keelingj New Member

    Followed those instructions, rebuilt my RCBFX modules for the new kernel, loaded them OK. However, system hardlocks when Amportal starts.

Share This Page