Well, just have them use a code like 7 + ext when they transfer to an
extension for fire and forget and then you could route that to your FS app.
 Just like transferring to voicemail is 8 + ext.

On Thu, Feb 16, 2012 at 6:46 AM, Михаил Родионов <ma...@siplabs.ru> wrote:

> Yep, Polycoms rule. But when entering Russian market with their ip phones
> they used high-end audiophilic audio gear price lists as a reference (which
> is ok if you think they provide vynil-like sound quality with warm
> tube-like middles :) ).
>
> IP 560 is $420 with big discount.
>
> Thanks for the reply!
>
> 2012/2/16 Michael Picher <mpic...@ezuce.com>
>
>> You might be able to use a Polycom Enhanced Feature Key (EFK) to do this.
>>
>>
>> On Wed, Feb 15, 2012 at 11:59 PM, Михаил Родионов <ma...@siplabs.ru>wrote:
>>
>>> The valet parking slot idea is what came to me first (the app can be
>>> easily implemented in FS+Lua morover there are actual examples that can be
>>> easily found on the Net).. but how to reach that app *in user-friendly way*
>>> is still a question..
>>> I've heard about phones that have settings for feature codes to be
>>> dialed on transfer though...
>>>
>>>
>>> 2012/2/16 Tony Graziano <tgrazi...@myitdepartment.net>
>>>
>>>> right, but i suspect a dialplan on the phone will transfer it to a
>>>> "valet" parking slot, which would have an app to ring the target UA
>>>> and bridge the call or if no answer then transfer on timeout... it was
>>>> just an idea.
>>>>
>>>> On Wed, Feb 15, 2012 at 8:27 PM, Joegen Baclor <jbac...@ezuce.com>
>>>> wrote:
>>>> > I think you missed the "Blind" in the subject line which makes call
>>>> parks a
>>>> > non issue.   In theory, If the transfer failed, the original dialog
>>>> should
>>>> > continue to exist.  I am not sure if there is any RFC about enforcing
>>>> a
>>>> > transfer timeout though.
>>>> >
>>>> >
>>>> >
>>>> > On 02/16/2012 04:01 AM, Tony Graziano wrote:
>>>> >
>>>> > A dial plan on the ua and a custom call park extension of freeswitch
>>>> would
>>>> > essentially address this is think.
>>>> >
>>>> > On Feb 15, 2012 2:34 PM, "Douglas Hubler" <dhub...@ezuce.com> wrote:
>>>> >>
>>>> >> On Wed, Feb 15, 2012 at 11:19 AM, Михаил Родионов <ma...@siplabs.ru>
>>>> >> wrote:
>>>> >> > Hello,
>>>> >> >
>>>> >> > One of our customers today asked for a feature he *loved* in his
>>>> old
>>>> >> > Panasonic PBX - return of calls being blindly transferred that got
>>>> no
>>>> >> > response after timeout.
>>>> >> >
>>>> >> > Panasonic PBX can act like this:
>>>> >> > when someone does a blind transfer of a call to a third party, that
>>>> >> > party
>>>> >> > rings for some time (while the call is on hold listening to the
>>>> MOH) and
>>>> >> > if
>>>> >> > not picked up, call returns to the original extension ("Let me TRY
>>>> to
>>>> >> > transfer your call to a manager"-like scenario). There are
>>>> actually two
>>>> >> > timers - after the first timeout the call is returned and rings
>>>> until
>>>> >> > second
>>>> >> > timeout (and then hanged up).
>>>> >>
>>>> >> Indeed a great feature.
>>>> >>
>>>> >> If you can find the ladder diagram for how the SIP RFC in general is
>>>> >> supposed to handle this, it might help getting some feedback.
>>>> >>
>>>> >> If SIP prescribes a SIPB2BUA, then I suggest rummage thru FreeSWITCH
>>>> >> mailing list and then come back w/how to integrate a FreeSWITCH
>>>> >> feature into sipx.
>>>> >>
>>>> >> > Any clues about the right place where should we dig? We are
>>>> relatively
>>>> >> > new
>>>> >> > to hacking sipX core parts (codewise) but are crazy and brave
>>>> enough to
>>>> >> > try
>>>> >> > :)
>>>> >>
>>>> >> love it!
>>>> >> _______________________________________________
>>>> >> sipx-users mailing list
>>>> >> sipx-users@list.sipfoundry.org
>>>> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>> >
>>>> >
>>>> > LAN/Telephony/Security and Control Systems Helpdesk:
>>>> > Telephone: 434.984.8426
>>>> > sip: helpd...@voice.myitdepartment.net
>>>> >
>>>> > Helpdesk Customers: http://myhelp.myitdepartment.net
>>>> > Blog: http://blog.myitdepartment.net
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > sipx-users mailing list
>>>> > sipx-users@list.sipfoundry.org
>>>> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> ~~~~~~~~~~~~~~~~~~
>>>> Tony Graziano, Manager
>>>> Telephone: 434.984.8430
>>>> sip: tgrazi...@voice.myitdepartment.net
>>>> Fax: 434.465.6833
>>>> ~~~~~~~~~~~~~~~~~~
>>>> Linked-In Profile:
>>>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>>>> Ask about our Internet Fax services!
>>>> ~~~~~~~~~~~~~~~~~~
>>>>
>>>> --
>>>> LAN/Telephony/Security and Control Systems Helpdesk:
>>>> Telephone: 434.984.8426
>>>> sip: helpd...@voice.myitdepartment.net
>>>>
>>>> Helpdesk Customers: http://myhelp.myitdepartment.net
>>>> Blog: http://blog.myitdepartment.net
>>>> _______________________________________________
>>>> sipx-users mailing list
>>>> sipx-users@list.sipfoundry.org
>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Михаил Родионов*
>>> Директор по развитию ЗАО "СибТелКом"
>>> E-mail: ma...@siplabs.ru
>>> Тел: +7(383)363-2111
>>> Моб: +7(913)985-5212
>>>
>>>
>>> _______________________________________________
>>> sipx-users mailing list
>>> sipx-users@list.sipfoundry.org
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>
>>
>>
>>
>> --
>> Michael Picher, Director of Technical Services
>> eZuce, Inc.
>>
>> 300 Brickstone Square****
>>
>> Suite 201****
>>
>> Andover, MA. 01810
>> O.978-296-1005 X2015
>> M.207-956-0262
>> @mpicher <http://twitter.com/mpicher>
>> www.ezuce.com
>>
>>
>> ------------------------------------------------------------------------------------------------------------
>> Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab
>> A gathering for - open source users, eZuce customers & eZuce partners
>> Get the inside track on 4.6 and a glimpse at the future of sipXecs!
>>
>>
>> _______________________________________________
>> sipx-users mailing list
>> sipx-users@list.sipfoundry.org
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
>
> --
>
> *Михаил Родионов*
> Директор по развитию ЗАО "СибТелКом"
> E-mail: ma...@siplabs.ru
> Тел: +7(383)363-2111
> Моб: +7(913)985-5212
>
>
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab
A gathering for - open source users, eZuce customers & eZuce partners
Get the inside track on 4.6 and a glimpse at the future of sipXecs!
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to