Tipos de modulos en Asterisk.

• Added by malcolmd, last edited by Malcolm Davenport on Sep 23, 2010  (view change)

There are many different types of modules, many of which are shown in the diagram above.

PHPAGI para Autenticar la claves de acceso desde una base de datos MYSQL

Este agi lo que hace es que valida la clave de acceso de  aplicación Authenticate() desde una  base de datos mysql.

Usando el chan_mobile en Asterisk

Using chan_mobile

• Added by Malcolm Davenport, last edited by Malcolm Davenport on Aug 31, 2010

chan_mobile.so must be loaded either by loading it using the Asterisk CLI, or by adding it to /etc/asterisk/modules.conf
Search for your bluetooth devices using the CLI command 'mobile search'. Be patient with this command as it will take 8 - 10 seconds to do the discovery. This requires a free adapter.
Headsets will generally have to be put into 'pairing' mode before they will show up here.
This will return something like the following :-

*CLI> mobile search
Address Name Usable Type Port
00:12:56:90:6E:00 LG TU500 Yes Phone 4
00:80:C8:35:52:78 Toaster No Headset 0
00:0B:9E:11:74:A5 Hello II Plus Yes Headset 1
00:0F:86:0E:AE:42 Daves Blackberry Yes Phone 7 

Buscando errores en los Logs de Asterisk.

Estos dos comando nos pueden ayudar a encontrar errores que causan un funcionamiento inesperado en nuestra central Asterisk.

grep -i  error /var/log/asterisk/messages | less

root@Asterisk-PBX:~# cat /var/log/asterisk/messages | grep -i error | less

root@Asterisk-PBX:~# cat /var/log/asterisk/messages | grep -i warning | less



root@Asterisk-PBX:~# cat /var/log/asterisk/messages | grep -i notice | less

grep -i  error /var/log/asterisk/messages > error.txt

Los dos primeros comandos nos muestran la informacion de  forma paginada en la consola de shell .

El tercero envía  el resultado del comando a un archivo de texto llamado error.txt

Si lo que queremos es leer en tiempo real los logs podríamos ejecutar el comando :

tail -f /var/log/asterisk/messages

Lista de de códigos de Respuesta SIP.

Lista de Codigos de Respuesta SIP.

100 Trying

Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response

180 Ringing

Destination user agent received INVITE, and is alerting user of call.^[1]

181 Call is Being Forwarded

Servers can optionally send this response to indicate a call is being forwarded.^[1]

182 Queued

Indicates that the destination was temporarily unavailable, so the server has queued the call until the destination is available. A server may send multiple 182 responses to update progress of the queue.^[1]

183 Session in Progress

This response may be used to send extra information for a call which is still being set up.^[1]

199 Early Dialog Terminated

Can used by User Agent Server to indicate to upstream SIP entities (including the User Agent Client (UAC)) that an early dialog has been terminated.^[2]

Commandos Útiles Asterisk

root@Asterisk-PBX:~# asterisk  -x  " core show help " | less


 ! Execute a shell command
                    ael reload Reload AEL configuration
ael set debug {read|tokens|mac Enable AEL debugging flags
                  agent logoff Sets an agent offline
                    agent show Show status of agents
             agent show online Show all online agents
                 agi dump html Dumps a list of AGI commands in HTML format
                      agi exec Add AGI command to a channel in Async AGI
        agi set debug [on|off] Enable/Disable AGI debugging
     agi show commands [topic] List AGI commands or specific help
                 aoc set debug enable cli debugging of AOC messages

:q

Configurancion de una linea T1 en Dahdi

Configuring a Dahdi T1 Line

This webpage is about configuring a T1 line for Asterisk - it should work equally well for E1 cards. If you haven't at this time, read the pages on this website about Testing Dahdi Hardware. It'll give you an introduction into how the Dahdi cards integrate with Linux and Asterisk - probably too much information!

The script "dahdi_genconf" creates a generic configuration for both the FXS/FXO and E1/T1 Dahdi cards. In most cases, /etc/dahdi/system.conf will have to be manually tweaked to your requirements.

Make sure that your cards are blacklisted as per the instructions at Testing Dahdi Hardware and that the card modules are being loaded at /etc/Dahdi/modules as per the instructions at Dahdi Drivers Once that is verified than you are ready to perform the configuration of the first file: /etc/dahdi/system.conf. At this point you will need to know your service provider's T1 settings or if you are connecting to a channel bank, its T1 configuration.

This webpage is divided into two sections:

1. Configuring the T1 Line Parameters (this page)
2. Configuring the T1 Channel Parameters