search for: mark_mcquiggan

While testing a problem with "spontaeously" and "occasionally" rebooting asterisk, I came upon this problem: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1210770512 (LWP 11346)] 0x002e3fe1 in pri_release_timeout (data=0x93a0478) at q931.c:2589 2589 q931.c: No such file or directory. in q931.c q931.c is in libpri, function

I am using a SIP softphone (X-lite, SIPPS or Firefly) connected to an Asterisk v 1.0.3 PBX. The PBX is also connected via a ISDN-PRI crossover cable to a Avaya Definity Generic 3 PBX via a TE405P card. All outside of the office calls go through the Definity. Here's the issue: Calls to internal SIP extensions, Definity extensions, other offices within our private network (through the

In the Avaya PBX, when a person calls a local extension within the PBX network, the caller is provided with the called person's name on his/her call display (I suppose that this could be called "Called ID"). For example, if I called Joe Blow from my extension 46480 by dialling 41234, I would see "Joe Blow - 41234" (the Called ID) on my call display after a pause, and Joe

The question below was asked before, and bounced back to me...trying again.... In the Avaya PBX, when a person calls a local extension within the PBX network, the caller is provided with the called person's name on his/her call display (I suppose that this could be called "Called ID"). For example, if I called Joe Blow from my extension 46480 by dialling 41234, I would see "Joe

Has anyone been able to successfully integrate the Avaya AUDIX voicemail system with Asterisk? I have been diligently investigating converting our small (Ontario, Canada) office to Asterisk, and ditching our Avaya PBX. However, our head office (New Jersey, USA) maintains our AUDIX system, and a) have no intentions of leaving it and b) some users rely upon AUDIX's ability to transfer

As a follow-up, I have traced the PRI connection and discovered that calls hung up by a local BCM voice station (analog, digital, whatever) send a disconnect with a clear cause of 1 (Number not assigned) instead of a normal clear cause of 16. Calls forwarded through the BCM disconnect with the normal clear cause. I have kludged up a fix to change all clear causes below 2 to 16 (I placed