Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About GregV

  • Rank

Recent Profile Visitors

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

  1. Thank you. Even just an option to specify the delimiter or just leave out the spaces / hyphens would be ideal too.
  2. Thank you, I tried using CO-Lines but wasn't successful, and its good to know you are looking at retiring this option, as I don't want to build a setup around it if its going to disappear in future versions. The Domain level simultaneous call restriction is helpful when you wish to restrict a domain's total simultaneous calls, but not helpful if you want the Vodia PBX to move to the next option in the dial plan. It would be great to see an option to specify how many calls a trunk can handle at the trunk level in future releases of the product. In the meantime, might it be possible to ha
  3. Thank you for advising. Getting a carrier to change their ways is not easy, plus the ability to limit the number of calls in a trunk seems like a function that should be controllable at both the carrier and PBX level.
  4. To my understanding, on outgoing calls, the Vodia PBX waits for the carrier to either error the outgoing call or timeout before moving to the next dial plan option, if you have set Failover behavior to On all error codes. Some carriers play early media when call limits are reached on a trunk before sending the trunk an error code, thus the caller hears a message such as "All channels in use" before the PBX moves to the next option in the dial plan. This is confusing for the caller. It would be nice if we could set the number of concurrent calls that a trunk is allowed and thus if the maxim
  5. You can uncross your fingers Lyndon, I can advise that for me this worked ... its only just a little confusing that this Failover behavior option is located within Routing/Redirection section of the trunk which is predominantly to do with incoming call handling, though this is a routing thing so I guess it makes sense for it top be there Error codes from the carrier would generally be generated on outgoing calls which is what I wanted it for. i.e. when Vodia attempts to send a call out via a trunk and it cannot. Setting the parameter to "On all error codes" caused the system to move to t
  6. The display of the numbers via the Vodia Web Interface does appear to be a final stage presentation, as even if the number is 0400-999-777 you can still search in the search criteria for 977 as an example and the call / recording will show. This is great and as expected. How Vodia does this presentation appears to be driven by the country code you enter, in my case, 61. It also may allude to the fact that the storage of the numbers in Vodia's database is without localization, which is also good. Localization is an end step process as expected. I do like how the Vodia PBX will replace
  7. Hi Support, The main issue here is the user cannot disable the Hot Desking using the *70 star code (i.e. return the handset to its own extension) When you try, the system does states that Hot Desking is disabled, but the system doesn't actually disable it. The Extension remains Hot Desked. I'm asking if I'm following the correct procedure to return an extension to its own original extension number. I'm running Vodia 66.0.6 Below is where the user can see if their Extension is Hot Desked to another extension . This is found by logging into the Web Interface of the Vodia
  8. I'm running Vodia 66.0.6 I have an issue with disabling Hot Desking. To enable Hot Desking the user goes to another extension, calls *70, enters their extension number, enters their PIN, a confirmation is heard "Service is active" and the phone reboots. This works. Now the problem; To reverse the process, the user calls *70 from the same extention, enters the original extension number of the handset, confirmation is heard "Service is inactive", however the hot desking is still in place despite the confirmation. If the user logs into their extension using their web browser
  9. In Australia we rarely hyphenate numbers.. We generally space the numbers out or have no spaces at all. Most SIP carriers present calls with 11 digits including our country code (61). This is then followed by the area code (single digit) then the number (8 digits) Here is the chart; Starts with Replaced with Display format Use 614 04 04xx xxx xxx Mobiles 612 02 02 xxxx xxxx NSW 613 03 03 xxxx xxxx Victo
  10. Country code is 61 - Australia. I like how it replaces the +61 with 0. That does help the readability. But the dashes do not. Is there anyway to modify the way the system localises numbers based on country code?
  11. I'm running version 66.0.6 (Debian64) I'm finding the PBX is adding hypens to the CID of inbound calling numbers. e.g. 0291237744 is converted to 02-9123-7744 Hypehens are added to mobile numbers e.g. 0499999999 to 0499-999-999 The hypehs are not present in the SIP INVITE. Also when adding an entry to the Domain Address Book, hyphens are added to the numbers you add. Please advise how to remove this? Thank you. ----issued resolved... remove country code from domain general settings
  12. Service provider Vonex have advised that having this to work is a feature request and not a bug fix. I have directed them to the only manual where it states the feature exists. https://doc.vodia.com/serviceflags Calling a Service Flag "Both in automatic and manual mode, the state of the service flag can be changed from the phone (since version 5.4.2)." Can you please clarify if this is a bug or a feature request so I can inform Vonex to as they seem to be wanting to fob this off. Its a very simple feature, however its important for clients to be able to take their syste
  13. Ok, I'll advise the Service Provider Vonex in Australia to do this and will advise.
  14. Ok, thank you. Would also be nice if the software still completed the intended function, even if the audio files are missing. In this case the feature is broken over missing audio files which is annoying.
  15. Thank you, as I have several (approx 25) client's being effected by this, are you able to advise when the next release will be available so I can set their expectations.
  • Create New...