Jump to content

Clint Berry

Members
  • Posts

    19
  • Joined

Posts posted by Clint Berry

  1. Agreed. But here is the sweet spot: It only benefits people on phones with 2-4 line keys and no side car. So while the receptionist at a dental office (our target market) has a 12 line key phone and a sidecar, when he/she puts a call into the park orbit, the crappy polycom 335 in the operatory room has access to that orbit now on its second line key. 

    If every phone is a VVX 410+, then no need for this feature.
  2. You can see how this would work on polycom on this doc, starting at the bottom of page 10: http://support.polycom.com/global/documents/support/technical/products/voice/Static_BLF_TB62475.pdf

    Also, I worked with a developer to patch FreeSWITCH to make the valet park presence work for this scenario. I don't know if that would help things since I believe you use Kamailio for presence, but let me know if I can be of assistance.
  3. The reason it shows an incoming call by default is in case you want to do a park orbit subscribe. Then the function key behaves as if multiple incoming calls are coming in, even though in reality they are parked. This allows you to press and hold the function key and it will list all calls on that orbit and allow you to pick one up. See this doc starting at the bottom of page 10: http://support.polycom.com/global/documents/support/technical/products/voice/Static_BLF_TB62475.pdf
  4. We second everything Karl said, in particular the device_id which is how we track what device is doing what.
    But we would also like to see channel_hold event for when a call gets put on hold.

    And if possible, a channel_park event for when a call gets parked, and what slot it was parked to.
×
×
  • Create New...