Author Topic: EBox 1.4 - Asterisk Module seems to be broken!!!!  (Read 6517 times)

jsalamero

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1419
  • Karma: +45/-1
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #15 on: March 18, 2010, 06:51:15 pm »
Just edit /etc/event.d/ebox.asterisk and remove the "-p" parameter. I hope will work now. If all of you confirm that this such small change fixes this problem, we will release new packages. This is an asterisk bug on the internal locking system it uses.

jsjc

  • Zen Apprentice
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #16 on: March 18, 2010, 07:39:40 pm »
No this change does not make any difference to me. Still has the problem.
I was pretty excited thinking all was goinng to be sweet hehe.

Cheers anyway!


Javi

bellson

  • Zen Apprentice
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #17 on: March 18, 2010, 08:23:44 pm »
Sorry Javi,

This did not fix the issues.  Snake Eyes!!!

jsalamero

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1419
  • Karma: +45/-1
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #18 on: March 19, 2010, 02:57:24 am »
Did you run /etc/init.d/ebox asterisk restart or stop ebox.asterisk ; start ebox.asterisk ? I can't reproduce this issue anymore here without -p.

bellson

  • Zen Apprentice
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #19 on: March 19, 2010, 03:39:24 pm »
I restarted the box.  I will re-check all, and report my findings....

bellson

  • Zen Apprentice
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #20 on: March 19, 2010, 05:11:36 pm »
I decided to start with a clean load.

Applied the changes you recommended, and now it works.

Great Job Javi!!!!!!!

I also removed and reinstalled asterisk, dahdi, and dahdi-modules-ebox on my VM, and that has worked as well.

I am continuing to test now.

Looks good so far.

jsalamero

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1419
  • Karma: +45/-1
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #21 on: March 19, 2010, 05:51:20 pm »
Great! Btw, I'm Jorge not Javi :) If nobody else complains during the weekend I'll upload the fix on monday.

bellson

  • Zen Apprentice
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #22 on: March 19, 2010, 07:13:51 pm »
My apologies....I am responding from my iPhone....Kind of difficult to see the names.  My Bad..

jsjc

  • Zen Apprentice
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #23 on: March 27, 2010, 04:32:18 am »
Bellson what you mean you started by a clean load??

Got all working then??

That is amazing!

Cheers,

bellson

  • Zen Apprentice
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: EBox 1.4 - Asterisk Module seems to be broken!!!!
« Reply #24 on: March 27, 2010, 04:56:38 am »
Hi,

Clean Load means that I first reloaded ebox from scratch on a server platform, performed the prescribed changes in the startup file, and then created the users and groups and other housekeeping.  Then I tested extensively.  I ran call loads that exceeded 100 calls per minute, I ran inbound dtmf routing checks as a part of that, and I forced a call recording to voicemail at the end of each call, after a ring sequence to each station.  I verified the sequence of events from the CDR and all was correct.

On a separate note, the "psuedo-real-time" issue exists with many Intel Chip-sets due to the method in which the metronome is provided.  Intel is right on this, but the majority of hardware manufacturers take their own path in order to allow for over-clocking and other such activities.

Bottom line is that between the "other fixes" that the ebox team implemented, and the change in the startup file to preclude the "psuedo-real-time" startup parameter, the issue is resolved.  Of that, I am convinced.  Great job to the ebox team!!!!