miércoles, 24 de abril de 2013
lunes, 22 de abril de 2013
Publicado por Ambiorix Rodriguez en 22:40
viernes, 19 de abril de 2013
If Asterisk loses internet connectivity or DNS, it stops responding to all SIP devices and trunks, and all extensions lose connectivity. This bug has apparently been around since Asterisk 1.4, persisted through 1.6, and remains in 1.8
Publicado por Ambiorix Rodriguez en 20:14
viernes, 12 de abril de 2013
you'll want to know the framing and the coding.?
The framing is one of "d4" or "esf" for T1 or "cas" or "ccs" for E1
Note: "d4" could be referred to as "sf" or "superframe"
The coding is one of "ami" or "b8zs" for T1 or "ami" or "hdb3" for E1
E1's may have the additional keyword "crc4" to enable CRC4 checking
You'll want to know the signaling type - is it a PRI, is it E&M?
You'll want to know how many voice channels you've got. If it's PRI where your d-channel is.
If it's PRI, what type of PRI signaling is it.
If it's E&M, you'll want to know whether it's immediate, wink, or Feature Group D.
You'll want to know how many digits you get on dialed numbers.
Publicado por Ambiorix Rodriguez en 6:09
martes, 9 de abril de 2013
El siguiente link tiene la configuracion de ejemplo de cada archivo relacionado con la configuracion de Asterisk.
Publicado por Ambiorix Rodriguez en 18:04
sábado, 6 de abril de 2013
Publicado por Ambiorix Rodriguez en 21:34
In Asterisk, Local channels are a method used to treat an extension in the dialplan as if it were an external device. In essense, Asterisk will send the call back into the dialplan as the destination of the call, versus sending the call to a device.
Two of the most common areas where Local channels are used include members configured for queues, and in use with callfiles. There are also other uses where you want to ring two destinations, but with different information, such as different callerID for each outgoing request.
Publicado por Ambiorix Rodriguez en 21:28