El Lunes, 8 de diciembre, 2014 12:51:42, Matthew Jordan
mjor...@digium.com escribió:
On Fri, Dec 5, 2014 at 3:23 PM, Rodrigo Montiel
guevara2...@yahoo.com.ar wrote:
Hi masters,
I’m not an expert on this my friends, but I’m trying to understand which the
expected behaviour
Hi masters,
I’m not an expert on this my friends, but I’m trying to understand which the
expected behaviour is from Asterisk side when you deal with the following
scenario:
Caller — GSM Gateway with SIM card A — Asterisk queue — extension 1000
GSM gateway with call waiting activated on SIM A
webinar every
Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Rodrigo Montiel
Ing. en Telecomunicaciones
GNU
which it doesn't make sense!
Is there a way to stop this behavior, let's say to run invalid
option if any other number was pressed doesn't belong to the current
menu level?
Thanks.
--
Rodrigo Montiel
Ing. en Telecomunicaciones
GNU/Linux VoIP System Support
Cel: +549 351 2581376
Hi all,
Recently I have raised up a bug (related to segmentation fault of
asterisk process) due to a core dump generated by Asterisk under the
following environment:
CentOS release 5.7 (Final)
Kernel 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:23:01 EDT 2011 i686 i686
i386 GNU/Linux
Asterisk
elastix-a2billing-1.9.4-5
Asterisk
asterisk-11.4.0-0
asterisk-perl-0.10-2
asterisk-addons-11.4.0-0
DRIVERS
dahdi-2.6.1-4
rhino-0.99.4-3.rc1
wanpipe-util-3.5.28-0
On Thu, 2013-09-05 at 10:19 -0500, Alex Villacís Lasso wrote:
El 05/09/13 07:02, Rodrigo Montiel escribió
