Sangoma cards in Elastix 1.5 stable

vtofa

Joined
Oct 21, 2008
Messages
67
Likes
0
Points
0
#1
I just downloaded and installed Elastix 1.5

Sangoma card detection is grayed out in it.

It has something to do with messages relating to wanrouter during the startup. They point to /var/tmp
 

vtofa

Joined
Oct 21, 2008
Messages
67
Likes
0
Points
0
#2
When I run hardware detection from the command line, I get these messages. Maybe they are helpful for someone to be able to tell me what is going on:

Code:
[root@elastix ~]# /usr/sbin/hardware_detector -tv
Starting detection cards ...
Step 1: Stoping service asterisk ...



STOPPING ASTERISK
Asterisk Stopped

STOPPING FOP SERVER
FOP Server Stopped
Step 3: Unmounting modules mISDN ...
         Stoping service mISDN ...
-- Unloading mISDN modules --
Step 4: Detecting sangoma cards ...


########################################################################
#    		           Sangoma Wanpipe                              #
#        Dahdi/Zaptel/SMG/TDMAPI/BOOT Configuration Script             #
#                             v2.22                                    #
#                     Sangoma Technologies Inc.                        #
#                        Copyright(c) 2008.                            #
########################################################################

/usr/sbin/wanrouter: line 466: /var/tmp/wanpipe-3.3.15-1-root/etc/wanpipe/wanrouter.log: No such file or directory
---------------------------------------------
Configuring T1/E1 cards [A101/A102/A104/A108]
---------------------------------------------
------------------------------------
Configuring analog cards [A200/A400/B600]
------------------------------------
AFT-A200 configured on slot:7 bus:1 span:1

Analog card configuration complete


###################################################################
#                             SUMMARY                             #
###################################################################

  0 T1/E1 port(s) detected, 0 configured
  0 ISDN BRI port(s) detected, 0 configured
  1 analog card(s) detected, 1 configured

Configurator will create the following files:
	1. Wanpipe config files in /etc/wanpipe
	2. Dahdi config file /etc/dahdi/system.conf
	3. Chan-Dahdi config file /etc/asterisk/chan_dahdi.conf


Your original configuration files will be saved to:
	1. /etc/dahdi/system.conf.bak 
	2. /etc/asterisk/chan_dahdi.conf.bak 


Your configuration has been saved in /etc/wanpipe/debug-2009-03-25.tgz.
When requesting support, email this file to techdesk@sangoma.com


###################################################################


Asterisk is not running...

Stopping Wanpipe...

Warning: WAN_LOCK_DIR = /var/tmp/wanpipe-3.3.15-1-root/etc/wanpipe does not exist!
Please update the WAN_LOCK_DIR in /etc/wanpipe/wanrouter.rc



Unloading Dahdi modules...
FATAL: Module dahdi is in use.
Error executing command:
modprobe -r dahdi


Removing old configuration files...

Copying new Wanpipe configuration files...

Copying new Dahdi configuration file (/etc/dahdi/system.conf)...

Copying new Chan-Dahdi configuration files (/etc/asterisk/chan_dahdi.conf)...

Wanrouter start complete...
Current boot level is 3

Wanrouter boot scripts configuration...

Removing existing wanrouter boot scripts...OK
Verifying Dahdi boot scripts...Verifying Dahdi boot scripts...Enabled (level:26)
Verifying Dahdi shutdown scripts...Enabled (level:92)
Enabling wanrouter boot scripts ...(level:25)
Enabling wanrouter shutdown scripts ...(level:91)
Sangoma cards configuration complete, exiting...

Step 5: Detecting dahdi cards ...
Empty configuration -- no spans
Empty configuration -- no spans
Step 6: Mounting modules dahdi ...
        Starting service dahdi ...
Loading DAHDI hardware modules:
  wct4xxp:                                                 [  OK  ]
  wcte12xp:                                                [  OK  ]
  wct1xxp:                                                 [  OK  ]
  wcte11xp:                                                [  OK  ]
  wctdm24xxp:                                              [  OK  ]
  wcfxo:                                                   [  OK  ]
  wctdm:                                                   [  OK  ]
  wcb4xxp:                                                 [  OK  ]
  wctc4xxp:                                                [  OK  ]
  xpp_usb:                                                 [  OK  ]
  rxt1:                                                    [  OK  ]
  r1t1:                                                    [  OK  ]
  rcbfx:                                                   [  OK  ]

No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg:                                         [  OK  ]
Step 7: Mounting modules sangoma ...
        Restoring service wanrouter ...

Warning: WAN_LOCK_DIR = /var/tmp/wanpipe-3.3.15-1-root/etc/wanpipe does not exist!
Please update the WAN_LOCK_DIR in /etc/wanpipe/wanrouter.rc



Warning: WAN_LOCK_DIR = /var/tmp/wanpipe-3.3.15-1-root/etc/wanpipe does not exist!
Please update the WAN_LOCK_DIR in /etc/wanpipe/wanrouter.rc


Router is already stopped !


Warning: WAN_LOCK_DIR = /var/tmp/wanpipe-3.3.15-1-root/etc/wanpipe does not exist!
Please update the WAN_LOCK_DIR in /etc/wanpipe/wanrouter.rc


ERROR: Wanpipe configuration file not found:
               /var/tmp/wanpipe-3.3.15-1-root/etc/wanpipe/wanpipe1.conf

Step 12: Restoring service asterisk ...



STOPPING ASTERISK

STOPPING FOP SERVER
SETTING FILE PERMISSIONS
Permissions OK

STARTING ASTERISK
Asterisk Started

STARTING FOP SERVER
FOP Server Started
End detection cards ...
 

rafael

Joined
May 14, 2007
Messages
1,454
Likes
1
Points
0
#3
hi, can you please report this bug in http://bugs.elastix.org. Is the best place to solve this issue for you and everyone else that might have the same issue.
 

vtofa

Joined
Oct 21, 2008
Messages
67
Likes
0
Points
0
#4
I can't create an account on the bugs site.
I never receive the email from there.
Does someone needs to approve the account?
 

rafael

Joined
May 14, 2007
Messages
1,454
Likes
1
Points
0
#5
That is weird :( it should be automatic.

Can you please email me to rafael[at]elastix.org with your user for the bug tracker?

Thanks a lot for your help,

Rafael
 

a_villacis

Joined
Jun 2, 2008
Messages
36
Likes
0
Points
0
#6

a_villacis

Joined
Jun 2, 2008
Messages
36
Likes
0
Points
0
#7

onsite

Joined
Sep 10, 2007
Messages
35
Likes
0
Points
0
#8
I confirm that this particular bug is no more. Good news.
But... the "Detect Sangoma hardware" is still grayed out.

During my first tests:
1. run the command /usr/sbin/hardware_detector -tv (looks good)
2. run the command wancfg
setup hardware as detected "A200/A400-Analog"
Protocol -> TDM Voice
TDMV LAW -> ALaw (Europe)
TDMV Operation Mode -> Greece
Now I see at the Hardware Detection GUI that I have 2xFXO in use (a dual Sangoma module installed) This is promising.
FOP shows no trunks (like it didn't since "the old days")
If I try to reboot it awards me with a kernel panic (reminding me the blue screens of death during the Win95 days as installing a simple modem)
Then, reset the machine and the previous configuration is gone... (so long!)

Overall: pulling hair, smashing keyboard, way off target!

If anyone has an "good" experience with 1.5.2 and Sangoma A200, please share (along with the procedure! damnit!)

Regards,
George
 

gmichaud

Joined
Mar 19, 2009
Messages
4
Likes
0
Points
0
#9
Same problem here... kernel panic during reboot.

I was able however to configure wanpipe from the commande line, but I always get a kernel panic on reboot. May or may not be related to the Sangoma card...
 

haamed

Joined
Jul 23, 2007
Messages
251
Likes
0
Points
0
#10
Hi vtofa,
Did you found your answer ?
I still have this problem with sangoma and Ela1.5
 

a_villacis

Joined
Jun 2, 2008
Messages
36
Likes
0
Points
0
#11
You should open a new bug for this issue. Please include as much information about your setup as you can, especially if you are using 32-bit or 64-bit elastix. If you have a null-modem cable, you can try to boot with console=ttyS0 and attempt to capture the kernel panic through the serial port on another computer.
 

rafael

Joined
May 14, 2007
Messages
1,454
Likes
1
Points
0
#12

samix4u

Joined
Mar 31, 2008
Messages
20
Likes
0
Points
0
#13
how do i update this to my Elastix 1.5 stable server.
i tried yum
 

rafael

Joined
May 14, 2007
Messages
1,454
Likes
1
Points
0
#14
Hi samix4u, the yum update would take a while because we need a lot of testing and at the moment we are fixing some issues. Please read this email:

http://lists.elastix.org/pipermail/beta ... 00319.html

So for Friday we might the um update enable for the beta repositories. Then our beta testers would do some tests and when everything is ready they would be able as stable repos.

Regards,

Rafael
 

rafael

Joined
May 14, 2007
Messages
1,454
Likes
1
Points
0
#15
Elastix 1.5.2 stable is ready for downloads. This release should solve the issues with sangoma cards.

Regards,

Rafael
 

garcia.ronald.d

Joined
Sep 24, 2008
Messages
134
Likes
0
Points
0
#16
Hello rafael,

I used elastix 1.5.2 and the issue continues, to configure the sangoma card i have to unload the module wanpipe with the asterisk stop and dahdi with the respectives modules, and works fine but when i tried to init the system appear a kernel panic, I think its because unload wanpipe before stop asterisk.

Thanks.

PD.:Openr2 work fine with CANTV´s E1 (Telecomunications provider in Venezuela)
 

samix4u

Joined
Mar 31, 2008
Messages
20
Likes
0
Points
0
#17
What about FOP on my server fop doesn't show Sangoma card ports.
and is there any way to avoid this kernel panic problem yet
 

kspare

Joined
Mar 23, 2009
Messages
73
Likes
0
Points
0
#18
Whats the status of 1.5.2 and sangoma cards? they still don't work!
 

a_villacis

Joined
Jun 2, 2008
Messages
36
Likes
0
Points
0
#19
The kernel panic issue was solved with kernel-module-wanpipe version 3.3.15-4 (current version in repo should be 3.3.16). Do a yum update for the drivers. Please note that right after doing the update, the old driver is still in memory, and will crash your machine one last time before rebooting. After the machine reboots, the module should be unloadable without issues.
 

kspare

Joined
Mar 23, 2009
Messages
73
Likes
0
Points
0
#20
I saw that, but the issue i'm having is that elastix is not detecting the card at all.

I've tried upgrading a 1.3 testbox to 1.5.2 and a fresh install of 1.5.2 and after a yum update of the box, it does not pick up the card in the hardware detection.

Not sure whats going on.

I is aware of the card but thats about it. It actually shows all the boxes for the ports, but they all show unknown.
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,887
Members
17,565
Latest member
omarmenichetti
Top