Jump to content

DanielA

Members
  • Posts

    23
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

DanielA's Achievements

Rookie

Rookie (2/14)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

0

Reputation

  1. Hi Team, As previously mentioned, the keys available from newrelic do not validate in the license key field. Over-riding the pattern match on the field to add any of the available license keys from new relic also does not work. Any update/feedback on how to get this to work?
  2. @Vodia support Any update on this? Would really like to start monitoring our servers.
  3. Even tried to remove the pattern match on the field to add the licence key. Still no good.
  4. @Vodia support I have tried every key that new relic has to offer from the portal and none validate in that field. I have setup keys using all key types (User, Ingest - License, Ingest - Browser) and none work.
  5. Nope - I've even tested with the reminder timer set to 5 seconds with voicemail default.
  6. Hi Team, We've run into a few issues and are wanting to setup external monitoring on our Vodia servers. I can see that there is a section to input a new relic license key? Can you provide some further information on how to setup the new relic integration?
  7. Probably a poor choice of words on my behalf. Transferring a call to another extension. If they start an attended transfer via a BLF key and hang up before speaking to the other extension, it gives the appearance of a blind/cold transfer. In this case, the transfer reminder doesn't function and the call would hit the receiving extensions voicemail. In some cases, users would want the called returned to the extension that transferred the call instead of an extensions voicemail. Currently, the transfer reminder will work on the yealink handsets if you specifically use the B.Trans key - but trying to explain to a user that they have to press 3-4 extra keys to transfer the call blind rather than pressing the BLF key doesn't get received well.
  8. Have another customer that has raised this same request. With the default config, the handsets (Yealink T54W) will complete a BLF transfer as an attended transfer. They want to be able to press a BLF key to initiate the transfer then hang up. Is there anyway this can ringback to the reception handset should they not pick up the transferred call? This customer previously had an iPecs which worked in this manner.
  9. You cannot CSV upload the category field - which is a bit of a pain. I'm unsure of how you would utilise this? Doesn't look like it would help. We have a customer that owns multiple unrelated businesses. Each has their own address book. Perfect world - it would be great to be able to create multiple address books per tenant. Set one as default, then add others and have the ability to select the relevant address book on a per extension basis. Or even add a relationship to a department or building - and if an extension is in that dept or build, have an option to display dept/building address book entries.
  10. Hi Team, Wondering if it would be possible to have an address book based on a department? We have a couple of clients that have multiple sites and their address books are not the same across all sites. Thought is would be a good option to be able to specify a Department and/or Building to specify an address book? Or a way to add multiple domain address books and select which one the user sees from the admin portal?
  11. The problem I have is users completing a blind transfer by pressing the BLF key and hanging up. Asking them to press transfer and b.trans would be an issue.
  12. At the moment, we have chosen not to display the DID management section to users. Which is a shame - I'd prefer to have them see DID management and use it - just restricted to their own numbers. If you could work on having the option to link a DID to a domain to achieve this - it would be greatly appreciated. Linking a did to a trunk makes sense if you are running individual trunks per tenancy - but we are running a call termination service as a global trunk. We have a few customers that have a 10 or 100 number ranges - I'd love to be able to assign all their DIDs to their tenancy and let them self manage.
  13. Hi Team, I have set the "Transfer Reminder After" on a tenancy, which works fine when completing a blind transfer from a yealink handset (actually pressing the blind trans button). However, When you begin with an Attended transfer, then hang up, turning it into a blind transfer, the call does not call back with the transfer reminder. Is this something that can be achieved?
  14. Hi Team, Just wondering if the DID management can be expanded on? Currently, it would seem that you can add a DID to any tenancy. It would be great if we can allocate DID's to a particular tenancy, then the end user can route the DIDs within their tenancy. Essentially giving us as the provider the ability to allocate the DIDs to only work with a single tenancy. Hopefully this makes sense.
  15. That sounds like it wouldn't be a bad idea. Could I suggest that rather than "guessing" the locale, that it is a configurable option. You could "guess" a locale initially, but if its guessed incorrectly, it needs to be easily changed/corrected. Is it possible to include a time in the service flag? i.e business closes at 5pm on 19/03/2021 and re-opens at 9am 22/03/2021. so you could input a range something like "19/03/2021 17:00 - 22/03/2021 09:00" ? It would also be good if there was a way to set a holiday in a format like "the first Tuesday in November." We have a few holidays where the actual date varies each year in this kind of manner (as I'm sure other countries would also.) Don't know if something like that could be included in a future build?
×
×
  • Create New...