Jump to content

Karl Stallknecht

Customers
  • Posts

    1,154
  • Joined

  • Days Won

    21

Posts posted by Karl Stallknecht

  1. Out of curiosity is this so that their employees can't stalk customers or something? haha

    Smart idea though, I like it. In Kazoo caller ID prepend works fine for us, as long as we are using SIP devices with it.

    2600hz: is there a way to disable incoming caller ID? I can see how this would be useful with certain customers. I know you can disable incoming CNAM dips, but I'm not sure about the number portion.
  2. A potential customer is currently using Ring Central and wanted to know if we have this ability: they said that Ring Central has the ability to prepend digits before or after the caller ID when a call is forwarded from their office to an external number.

    The idea is that a customer calls the office and presses the extension for employee A. Employee A has a call flow that rings their desk phone for 10 seconds and then rings their cell phone for 10 seconds. Employee A wants to know that it is a forwarded call though if they get it on their cell phone, so the cell phone shows "0(xxx)xxx-xxxx" and the employee can answer the phone differently.

    Currently the only two ways I know of right now to tell someone that it is a forwarded call are:

    a) Set the external device settings to not pass through caller ID, so the caller ID shows the office number - the problem with this is that the customer can't look at their cell phone call log to get the caller ID of the caller. Plus, then the employee might think another employee from the office is calling.

    or

    b) Set the external device settings to "press 1 to confirm pickup" - the problem with this is that you don't know until you have already answered and it also slows down the answer time, so you have to add more rings in order to allow time for the employee to listen to the prompt and then press 1.

    As for as I know, no other method exists. If it does though I'd love to know about it! And if it doesn't, are you able to add this caller ID prepend method? I tried setting up a call flow to prepend the caller ID before the call goes to an external landline type device, but it didn't work. The prepend feature only appears to work with SIP devices.
  3. We use Grandstream ATAs. They've been ROCK solid for us. The only thing we've noticed is that some of them seem to stop sending caller ID information through to the analog phone once and a while, and you have to reboot the ATA to fix the problem. Not sure whether that's a 2600hz problem or Grandstream.

    I would love auto provisioner though, as the Grandstreams require a lot of tweaking to the settings to get them to register and work well. We saved screenshots of all of the config pages so that we can go back and reference it, but auto provisioner would make our lives much easier.
  4. Aaron,

    We received a success message back, but the phone number we added still is able to dial DIDs on that account:

    {"page_size":0,"data":[],"revision":"undefined","request_id":"05769ba5bde5862240291107d2fbf0aa","status":"success","auth_token":"xxxxx"}* 

    We might be doing something incorrectly, but to us it appears that this is not working.
  5. Yes, it is available on hosted. Go into your call flows (or advanced call flows in Monster), create a new callflow, and then pick an extension...you can add a character like star in front if you want.

    Then, go to advanced on the right side and drag/drop the "group pickup" option into the callflow. Select what you want to pickup (whether it's a device, user, or ring group) and then save everything.

    If an endpoint that you selected is ringing, any phone can then pick it up by dialing that call flow. For customers who need this feature we usually just setup a call flow to match each device. It's a bit of manual labor to set up if they have a lot of users, but it works fine. In your case you could just do *8 and then add the extension number (i.e. *8101).

    To make it easier you can program BLF keys to work with this as well.
  6. I prefer Polycom (try the VVX series, or the SoundPoint IP series with a sidecar)

    Yealinks usually have a lot of BLF keys too though, I just think they're really cheap feeling so I don't like selling them.

    Yes, you can program the BLF keys with Advanced Provisioner. I don't know about others, but Polycom works other than using BLF keys for parking has issues with pickup. If you just want BLF for extensions though it works fine.
  7. Definitely a good point...we experience that with most of the SoundPoint IP models because while there may be enough line keys for BLF, then they don't have enough room for presence. This is why we've switched over 100% to the VVX series for new customers and we're even changing out some of our long time customers who are on the Polycom 430s (the 2 line non backlit ones).

    On a side note, the SP IP 335 is awful imho and we've refused to sell them as a result. Polycom has made it SO small that it is nearly impossible to use and navigate. 
  8. Hi Clint,

    Out of curiosity how would you be using channel_hold and channel_park? To track call statistics and see how long callers are being put on hold or parked?

    I'm also curious if channel_park would be redundant because the call is essentially on hold? Or maybe not and they're distinguishable?
×
×
  • Create New...