The call was hung up after entering conference

Ted

Joined
Sep 27, 2010
Messages
17
Likes
0
Points
0
#1
Hi,

I have recently noticed that I cannot get conference calls to work on my production box. Everything seems to be working up to the point of entering the PIN. If you enter the incorrect PIN, the system say to enter a correct PIN. If you enter the correct PIN, the call is dropped. I have confirmed that Asterisk recognizes the correct PIN but drops the number.

I am on Elastix 2 with all updates. I have also updated all freepbx modules to current releases.

I installed a fresh copy of Elastix on a test box and did the following tests:

1) Install Elastix 2.03 - setup one extension and one conference - and confirmed conferences worked

2) Yum Update - did a complete update. Confirmed that Conferences still worked. Rebooted system. Confirmed again that conferences worked.

3) Update FreePBX modules. I updated all module (did not upgrade to 2.8). Tested Conferences and they still worked. Rebooted the system and conferences did FAILED as above.


Does anyone have suggestions of where to look on this issue? The only reference I found similar to this was a "bug" listed in Elastix.

LINK TO BUG REPORT Hang up after entering conference
 

Ted

Joined
Sep 27, 2010
Messages
17
Likes
0
Points
0
#2

bucasia

Joined
Feb 15, 2009
Messages
36
Likes
0
Points
0
#3
Do you know what timing source you are using. Conference calls will not work if zaptel/dahdi timing source is not running.

Is this a physical server?
 

Ted

Joined
Sep 27, 2010
Messages
17
Likes
0
Points
0
#4
I am not using zaptel/dahdi, just VOIP. Conf Calls worked before Freepbx update but not after update/reboot.

Ted
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#5
Re: Re:The call was hung up after entering conference

but you have dahdi_dummy loaded as timing source?
 

Ted

Joined
Sep 27, 2010
Messages
17
Likes
0
Points
0
#6
Re: Re:The call was hung up after entering conference

Thanks for pointing me in the right direction.

The problem was created by doing the yum update and then rebooting. After rebooting I always got a lot errors on Dahdi and I ignored them because I did not have any Dahdi hardware.

To resolve this problem/re-install Dahdi is did the following:

1) Download the latest Dahdi http://www.asterisk.org/downloads to PC
2) Used WinSCP to transfer file to /usr/src

3) SSH to my Elastix Box
4) cd /usr/src
5) tar -zxvf dahdi-linux-complete-2.4.0+2.4.0.tar.gz
6) cd dahdi-linux-complete-2.4.0+2.4.0/linux
7) make clean
8) make
9) make install
10) cd ..
11) cd tools
12) ./configure
13) make
14) make install
15) make config


Then I ran:
16) /etc/init.d/dahdi restart

Ouput
Unloading DAHDI hardware modules: ERROR: Module dahdi is in use
error
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
opvxd115: FATAL: Module opvxd115 not found.
[FAILED]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]
opvxa1200: FATAL: Module opvxa1200 not found.
[FAILED]
ystdm8xx: FATAL: Module ystdm8xx not found.
[FAILED]
ystdm16xx: FATAL: Module ystdm16xx not found.
[FAILED]
ap400: FATAL: Module ap400 not found.
[FAILED]
dahdi_dynamic_eth: [ OK ]
dahdi_dynamic_ethmf: [ OK ]
ax1600p: FATAL: Module ax1600p not found.
[FAILED]
zaphfc: FATAL: Module zaphfc not found.
[FAILED]
wcopenpci: FATAL: Module wcopenpci not found.
[FAILED]
rxt1: FATAL: Module rxt1 not found.
[ OK ]
r1t1: FATAL: Module r1t1 not found.
[ OK ]
rcbfx: FATAL: Module rcbfx not found.
[ OK ]

No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: [ OK ]




The list line shows dahdi_dummy loading. Tested conferencing and it worked.


Does anyone know how to correct the other errors?
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#7
Re: Re:The call was hung up after entering conference

.
.
Unloading DAHDI hardware modules: ERROR: Module dahdi is in use
.
.
You normally can't successfully restart dahdi until asterisk is stopped.

service asterisk stop
service dahdi restart
service asterisk start

should suffice if you don't have redfone hardware and use the default dahdi init script.

you can edit the now bogus Elastix

/etc/dahdi/modules

to exclude the modules you don't have (i.e. all of them) the init script should then STFU :)


Don't worry about the modules that didn't get built, you don't need them just dahdi_dummy they are not part of Dahdi for others who are mis-fortunate enough to own a clone need a lot more work, the support from rhino and sangoma will allow you to build or download compatible dahdi kernel modules. If you own a clone, well that's your problem, as they say, "penny wise pound foolish" wait for lisa or ranjid or ivan to help you :) :)

The bug however IMHO opinion remains, Elastix are responsible for these errors, yum update should do exactly that without destruction. Oh well go figure, it's only been eight months now.

dicko
 

Ted

Joined
Sep 27, 2010
Messages
17
Likes
0
Points
0
#8
Re: Re:The call was hung up after entering conference

OK, I ran what you said but get the same results on the DAHDI restart (see Below). I do not have any Dahdi hardware, just SIP Trunks. So from your message below (if i undstand correclty), since I am not using any of additional hardware, I do not need to worry about these errors???

Dicko is this the bug that caused the problem Bug report 665 or this one Bug report 595.


Service dahdi restart output below:
Unloading DAHDI hardware modules: done
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
opvxd115: FATAL: Module opvxd115 not found.[FAILED]
wcte12xp:[ OK ]
wct1xxp: [ OK ]
wcte11xp:[ OK ]
wctdm24xxp:[ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp:[ OK ]
xpp_usb: [ OK ]
opvxa1200: FATAL: Module opvxa1200 not found.[FAILED]
ystdm8xx: FATAL: Module ystdm8xx not found.[FAILED]
ystdm16xx: FATAL: Module ystdm16xx not found.[FAILED]
ap400: FATAL: Module ap400 not found.[FAILED]
dahdi_dynamic_eth: [ OK ]
dahdi_dynamic_ethmf:[ OK ]
ax1600p: FATAL: Module ax1600p not found.[FAILED]
zaphfc: FATAL: Module zaphfc not found.[FAILED]
wcopenpci: FATAL: Module wcopenpci not found.[FAILED]
rxt1: FATAL: Module rxt1 not found [ OK ]
r1t1: FATAL: Module r1t1 not found.[ OK ]
rcbfx: FATAL: Module rcbfx not found.[ OK ]

No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: [ OK ]
Bug report
 

bucasia

Joined
Feb 15, 2009
Messages
36
Likes
0
Points
0
#9
I'd say you don't need to worry about the errors, if conference calls are working now it's getting a timing source.

I'm not sure how well compiling dahdi from source over the top of the Elastix RPM dahdi stuff will work. You'll likely find that that Elastix updates in the future will break your system again - but at least you know how to fix it now :)
 

Ted

Joined
Sep 27, 2010
Messages
17
Likes
0
Points
0
#10
Is there a better way to fix this issue?

So far I have only tested this update on my test box. My production box is still running with this error.
 

bucasia

Joined
Feb 15, 2009
Messages
36
Likes
0
Points
0
#11
Ideally by figuring out what the issue was with the Elastix installed dahdi RPMs.

What does 'service dahdi restart' produce on your production box?

What does 'dahdi show status' show in the Asterisk console?

Also running 'dahdi_test' should give you some timing results.
 

Ted

Joined
Sep 27, 2010
Messages
17
Likes
0
Points
0
#12
This is from my test box with the fix above.

Service dahdi restart output below:
Unloading DAHDI hardware modules: done
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
opvxd115: FATAL: Module opvxd115 not found.[FAILED]
wcte12xp:[ OK ]
wct1xxp: [ OK ]
wcte11xp:[ OK ]
wctdm24xxp:[ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp:[ OK ]
xpp_usb: [ OK ]
opvxa1200: FATAL: Module opvxa1200 not found.[FAILED]
ystdm8xx: FATAL: Module ystdm8xx not found.[FAILED]
ystdm16xx: FATAL: Module ystdm16xx not found.[FAILED]
ap400: FATAL: Module ap400 not found.[FAILED]
dahdi_dynamic_eth: [ OK ]
dahdi_dynamic_ethmf:[ OK ]
ax1600p: FATAL: Module ax1600p not found.[FAILED]
zaphfc: FATAL: Module zaphfc not found.[FAILED]
wcopenpci: FATAL: Module wcopenpci not found.[FAILED]
rxt1: FATAL: Module rxt1 not found [ OK ]
r1t1: FATAL: Module r1t1 not found.[ OK ]
rcbfx: FATAL: Module rcbfx not found.[ OK ]

No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: [ OK ]

dahdi show status results below:
Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO

dahdi_test results
Opened pseudo dahdi interface, measuring accuracy...
99.975% 99.647% 99.977% 99.969% 99.970% 99.972% 99.972% 99.972%
99.970% 99.967% 99.972% 99.972% 99.973% 99.971% 99.972% 99.972%
--- Results after 16 passes ---
Best: 99.977 -- Worst: 99.647 -- Average: 99.951396, Difference: 99.995574
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#13
Please edit as suggested (or delete, in your case it's all crap for you ) /etc/dahdi/modules

you now have an acceptably functional timer.
.
.
dahdi_test results
Opened pseudo dahdi interface, measuring accuracy...
99.975% 99.647% 99.977% 99.969% 99.970% 99.972% 99.972% 99.972%
99.970% 99.967% 99.972% 99.972% 99.973% 99.971% 99.972% 99.972%
--- Results after 16 passes ---
Best: 99.977 -- Worst: 99.647 -- Average: 99.951396, Difference: 99.995574
.
.
 

Ted

Joined
Sep 27, 2010
Messages
17
Likes
0
Points
0
#14
Thanks, I got all the modules causing errors commented out.

Is there a better way to fix the duhdi_dummy not loading problem so that future yum updates do not break it again?
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#15
:):)

At this point in time , and because yiou went "rogue",you could either disable the elastix repositories or you can wait for PaloSanto to supply a functional dahdi RPM that will actually load against all the other RPM's in their repository, including their kernel modules (which is the underlying problem by my guess) the wait continues . . . .

dicko
 

bucasia

Joined
Feb 15, 2009
Messages
36
Likes
0
Points
0
#16
That's a good idea. You could compile from source as you have and then add -

exclude=dahdi*

to /etc/yum.conf

That would stop dahdi updates being pulled down. The only issue that might cause is if a future Asterisk upgrade expects a more recent version of dahdi. In that case the Asterisk update would not get applied either.
 

bucasia

Joined
Feb 15, 2009
Messages
36
Likes
0
Points
0
#17
Maybe. Though compiling too much from source over the top of the RPMs is a slippery slope that there's no easy way back from :)
 

bucasia

Joined
Feb 15, 2009
Messages
36
Likes
0
Points
0
#18
Either way it's more hassle than it should be :)
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#19
Re: Re:The call was hung up after entering conference

my good friend dick, dont make a new rant ....but im with you always!!
 

basaran

Joined
Apr 9, 2011
Messages
12
Likes
0
Points
0
#20
Re: Re:The call was hung up after entering conference

Thanks for your instructions Ted. They worked great in getting the conferencing to work ;)


Ted said:
Thanks for pointing me in the right direction.

The problem was created by doing the yum update and then rebooting. After rebooting I always got a lot errors on Dahdi and I ignored them because I did not have any Dahdi hardware.

To resolve this problem/re-install Dahdi is did the following:

1) Download the latest Dahdi http://www.asterisk.org/downloads to PC
2) Used WinSCP to transfer file to /usr/src

3) SSH to my Elastix Box
4) cd /usr/src
5) tar -zxvf dahdi-linux-complete-2.4.0+2.4.0.tar.gz
6) cd dahdi-linux-complete-2.4.0+2.4.0/linux
7) make clean
8) make
9) make install
10) cd ..
11) cd tools
12) ./configure
13) make
14) make install
15) make config


Then I ran:
16) /etc/init.d/dahdi restart

Ouput
Unloading DAHDI hardware modules: ERROR: Module dahdi is in use
error
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
opvxd115: FATAL: Module opvxd115 not found.
[FAILED]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]
opvxa1200: FATAL: Module opvxa1200 not found.
[FAILED]
ystdm8xx: FATAL: Module ystdm8xx not found.
[FAILED]
ystdm16xx: FATAL: Module ystdm16xx not found.
[FAILED]
ap400: FATAL: Module ap400 not found.
[FAILED]
dahdi_dynamic_eth: [ OK ]
dahdi_dynamic_ethmf: [ OK ]
ax1600p: FATAL: Module ax1600p not found.
[FAILED]
zaphfc: FATAL: Module zaphfc not found.
[FAILED]
wcopenpci: FATAL: Module wcopenpci not found.
[FAILED]
rxt1: FATAL: Module rxt1 not found.
[ OK ]
r1t1: FATAL: Module r1t1 not found.
[ OK ]
rcbfx: FATAL: Module rcbfx not found.
[ OK ]

No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: [ OK ]




The list line shows dahdi_dummy loading. Tested conferencing and it worked.


Does anyone know how to correct the other errors?
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,887
Members
17,566
Latest member
Fpino
Top