I am sure it is centos 6.7. That was we what we decided together to have the
Colo to use
Sent from my Verizon Wireless 4G LTE smartphone
Original message
From: Leandro Dardini
Date: 2/28/2016 3:49 PM (GMT-05:00)
To: Asterisk Users Mailing List - Non-Commercial Di
Which operating system are you using? I have experienced the same problem
on several OS except for CentOS 6. I suppose an ODBC problem on newer OS
version.
Leandro
Il 24/Feb/2016 05:30 PM, "Maxime" ha scritto:
> Dear list,
>
> i have a issue
>
> Asterisk crash (Module res_odbc exactly) after the
I do it via a group count:
main call handling:
exten => sub123,n,Set(GROUP()=11122345)
...
the main routine calls subroutine:
exten => general,1,GotoIf($["${busyonbusy}"="YES"]?100:200)
exten => general,100,GotoIf($[ ${GROUP_COUNT()} > 1 ]?110:200)
exten => general,110,Hangup(17) ; fehlercode 17
On Sun, 2016-02-28 at 01:43 +0100, Frank wrote:
> Question: How to give a "busy signal" back to the caller if one
> extension of a ring group is in use? Or redirect the call to voice mail?
Found a solution! :-)
exten => 7654321,1,GotoIf($["${DEVICE_STATE(SIP/111)}"="INUSE"]?Busy,1)
exten => 765
On Fri, Feb 19, 2016 at 10:52:34AM +1300, Daniel Harper wrote:
> What about leaving the old PBX in place and trunking it via ISDN to the
> asterisk server.
>
> We use rhino 24 channel bank but are 2U for rhino + 1U for patch panel.
> (RJ21 cable so might be able to use existing ones if they are RJ
Not sure if I can provide much help, however I have had problems with
Swift segmentation faults in the past. The problems I had were related
to the license server causing an Asterisk segmentation fault any time
security scans hit the server. That was with Asterisk 11.8. Cepstral has
been unable
On Wed, Feb 24, 2016 at 03:55:09PM -0600, Carlos Chavez wrote:
> I am having a problem trying to compile
> dahdi-linux-complete-2.11.0+2.11.0 on a CentOS 7.2 server. Version 2.10.2
> compiles fine. Is there a new dependency for 2.11.0 that was not required
> for previous versions? Here are s
