Re: [Flash Operator Panel] FOP 0.26

[Nicolás Gudiño <nicolas@xxxxxxxxxxxx>]

Hi All,

On Aug 24, 2006, at 6:35 AM, Florian Schoppmeier wrote:

> gus@xxxxxxxxxxxx schrieb:
> > Hello,
> > I downloaded the latest version 0.26 and it seems that when 
> > transfering a call the ext number doesn't get passed and it will 
> > default to the s ext; ie; context,,1. For
> example, I have 5 extensions configured, if I try to drag ext 220 over 
> to ext 221, the phone will ring but as soon as I answer the call will 
> get disconnected, because the ext number is missing. I downgraded to 
> 0.25 and it works fine. I also tried the latest 0.27 snapshot but the 
> problem doesnt get fixed there either. Anyone else having this 
> problem? Appreciate any input.
> > Gus.
>
> hello
>
> i am having nearly the same problem with 0.26, didn't try any other 
> versions yet though.
>
> When i'm dragging a call from ext 50 over to 51, 51 will ring with 51 
> as caller ID; as soon as i than take the call on 51 i get disconnected 
> or i'm getting thrown in a different context.

This is a known issue that I fixed on my devel branch, but I haven't 
found the time to package a new snapshot. There is a workaround. But 
first we should understand the problem:

In 0.26 a new option was introduced: to transfer a call directly to 
voicemail. If you drop the icon over the MWI icon, then it will 
transfer to the extension defined in VoiceMailExt for that button. If 
you drop the phone icon anywhere else, then it will transfer as 
expected. The workaround would be to define VoiceMailExt to be the same 
extension and context as the button. The fix is to check if that value 
is empty and if so, transfer to the regular extension@xxxxxxxx

The new snapshot that I will be packaging includes also an attendant 
transfer implementation, but I have to sort some things out design wise 
before releasing it, because right now it is using the barge mechanics 
to perform the attendant transfer and you loose the ability to barge 
into calls. The fastest/easiest way would be to check for attendant 
transfers options in each panel_context, if there are attendant 
transfers definitions, then do that, if not, perform the regular barge 
ins.

The ultimate goal would be to have the option to perform attendant 
transfers and barges in in the same panel contexts. But I have to 
devise a way to do it with the current UI without cluttering buttons. 
Any ideas are appreciated.

About the attendant transfers, it is not a real attendant transfer but 
a hack using meetme, with the option to transfer to a defined extension 
(for example to voicemail) if the transfer destination is busy or fails 
to connect the call. It seems to work fine, although you will end up 
with lots of meetme rooms instead of real bridged calls.

I will try to implement this using the 'bridge' application/function 
when it is available. Any comments or ideas are welcome, I will try to 
package a new snapshot this week.

Regards,


--
Nicolas Gudino
Buenos Aires - Argentina