Hi,

1. How can I use the Whisper option? When i try to do this it only spies the conversation, however i cannot whisper anything to the selected party. How does this option work?

It passes the "w" option to chanspy, you can modify the options to pass by modifying whisper_options in fop2.cfg

There are many versions of asterisk where chanspy is broken in different parts, on some versions whisper does not work reliably or at all. I cannot tell if your version is broken or not. It is always advisable to run the latest asterisk version.

2. I cannot manage to monitor the DAHDI trunks correctly on 3 of the PBXs (one running Elastix 2.3 and the other 2 running 1.6). I have used the FreePBX admin module to setup the buttons with the correct channels on all three machines as suggested on other posts, however the monitoring is not correct and they display the same behaviour as follows:

- The buttons for the DAHDI trunks are displayed in the FOP2 as ZAP/1, ZAP/2, ZAP/3 and ZAP/4.

- When I use the analog trunks, the only button that works is ZAP/4. Even if I use several trunks at the same time only ZAP/4 works and it lists all the lines in use as DAHDI/1, DAHDI/2, etc..

- The buttons ZAP/1, ZAP/2, ZAP/3 never display anything.

The only particular configuration for the trunks is that I have assigned ZAP DIDs to them so I can redirect incoming calls depending on which line they are coming from. See dahdi settings below...

What can I do to display each DAHDI trunk on their respective button correctly? Thank you in Advance.

Juan

FOP2 does not care *at all* about your DAHDI configuration. It only cares about device/channel names. It monitors status based on those names only. To figure things out, you will have to first see what names are configured for trunk buttons in FOP2 (taken from the FreePBX autoconfiguration), you can do so by running:

/usr/local/fop2/autoconfig-buttons-freepbx.sh

or in Elastix 2.3:

/etc/asterisk/fop2/autoconfig-buttons-freepbx.sh

Inspect the output, look for the trunk definitions, specially the name in Brackets, something like

[ZAP/1]
type=trunk
label=Zap 1
channel=DAHDI/1
...
etc,

notice that you have the name in brackets, and also the channel fields. FOP2 will match if there is an active channel name in asterisk that matches either, to know the channel names as seen by Asterisk:

asterisk -rx "core show channels"

FreePBX has an odd naming convention for trunks, not really odd but that makes it a little bit more involved or difficult than extensions, they use the group modifiers in the name. So You will probably see [ZAP/g0] in the fop2 button definition. That will never match, as the g is a modified, not part of the channel name, that is why you have those extra channel fields in the button definition, to add new or different channels to monitor.

If in "core show channels" you see DAHDI/2, then be sure your trunk button in fop2 has also DAHDI/2 on the channel field. You can set those by specifying the correct range in the fop2 buttons page in fop2admin, if its only one channel, try to specify 2-2 (for example).

Best regards,

And what is the output from "core show channels"?

Perhaps you have DAHDI/iX/1234 instead of DAHDI/X as channel names. In that case, please look at this post:

View Post 1243

Ok, you do not have the i, but you do have an error in the fop2 buttons config, if you have individual dadhi channels, then you do not need to specify any range?

Go to fop2 buttons and leave the channels field empty for ZAP 1,2,3 and 4

Also, your core show channels shows a DAHDI/5, but you pasted only 1,2,3,4 ?

FOP2 logic is *dead* simple

if Channel name matches, it will work, if not, it won't.

If you have in your button configuration:

[DAHDI/1]

or

[ZAP/1]
channel=DADHI/1

And core show channels displays:

DAHDI/5

Then it won't work! You want to monitor A but you are getting B. So, fix your button configuration so you see A and it will work. Upadte fop2 buttons until the output from autoconfig-buttons-freepbx.sh matches the channel name you see in core show channels. You should also avoid having the same channel monitored in multiple buttons, that will generate issues. Do not add 1-4 in all four dahdi channels, only one of them will work in that case.

Best regards,

Hola Nicolás,
Realmente nos ha parecido muy bueno el producto y con excelente presentación. Sin embargo la existencia de ciertos errores tiene un poco descontentos a nuestros clientes ya que ellos necesitan poder usar correctamente todas las funciones que se ofrecen y están "disponibles" para ellos poder usar en el programa.

Permiteme discrepar. Ninguno de los temas que mencionas son ERRORES de FOP2, sino problemas de configuración o problemas con Asterisk mismo.

Agradeceríamos enormemente que por favor nos ayudaras a corregirlas. Si es posible sería excelente si pudieras concretar algun momento en el que nos puedas colaborar remotamente y yo poder simular las llamadas si es necesario.

No hay ningún problema, pero ten en cuenta que el soporte remoto tiene un costo, las tarifas están en http://www.fop2.com/buy.php. Si me encuentras en la ayuda en línea es posible que te ayude por chat sin necesidad de ingresar a tu sistema, y de paso aprenderás a configurar correctamente el producto. Ahora, si prefieres que ingresemos de forma remota para configurar tus equipos, puedes comprar las horas que creas necesarias para hacerlo.

Los 3 problemas que tenemos son:
1. No poder usar el whisper mode en una maquina de nuestra oficina.

FOP2 es un "centro de comandos". Cuando quieres hacer whisper, le envía a Asterisk la instrucción para iniciar chanspy con la opción "w". Esta es TODA su responsabilidad. Si a partir de entonces, Asterisk explota, entonces el error es de Asterisk, no de FOP2. Ahora bien, si FOP2 envía una instrucción equivocada, entonces si es problema de FOP2 que se puede corregir o bien derivado de una mala configuración.

2. No poder mostrar los dahdi trunks correctamente en botones independientes. Elastix 1.6 y 2.3.

Este es un problema de configuración, ya he mencionado infinidad de veces como configurar correctamente, o bien como modificar el script de autoconfiguración para incluir los DAHDI/i. Esto último si podría decirse que es un problema del FOP2 que es facilmente solucionable agregando UNA linea a un script, sin embargo no es tu problema por lo que me comentas.

3. Cuando se parquean llamadas, es posible hacerlo solo en 2.3 y no en 1.6. En 2.3 luego de parquear la llamada no es posible volverla a contestar.

Podría ser un problema de configuración o bien de versionado de Asterisk. Asegurate de crear los contextos override que requiere el fop2:

/usr/local/fop2/generate_override_contexts.pl -w

Esto es importante porque crea el contexto especial para poder parquear desde FOP2. Lamentablemente PARK y AMI (la interfaz que usa el FOP2) no se llevan bien, por una sencilla razón, cuando se hace desde AMI *no existe* un canal de origen (al cual poder devolver el llamado).

Si el foro no te sirve, te repito que está la ayuda en línea disponible.

Saludos,