Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

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

fred.bloggs's Achievements


Rookie (2/14)

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

Recent Badges



  1. Thank you for clarification. I was not sure if there are some databases used that would end up corrupted in the backup file when not stopping the service. If it is only "flat" files - sure no problems to expect when scheduling the backup in a less busy time at night.
  2. Yes, you are right let me explain again: I set up an extension and assigned a mobile number to that extension. When I call the extension with the assigned mobile number, the personal assistant takes the call. -> the way it should be I now set up an ACD and assign that extension to the ACD. When I now use the very same mobile number to call that ACD, the call never gets routed. On the mobile you just hear music on hold but non of the assigned agents phones to the ACD rings. Infinite music. I do not think that this is the desired behavior as we have an ACD on our main line and when one employee tries to call via a mobile phone he never gets through.
  3. I switched back to 3.5.5 but mutli factor auth via Mail does still not work. It says the following without even asking for the 2nd factor: Error: Login credentials are incorrect. Please try again or contact your system administrator If I use the exact same login data on the web inteface it works perfectly with multi auth.
  4. Hi, we have enabled 2 factor auth. In our case via E-Mail. This is not supported by the windows app. Please add support. Thanks.
  5. Hi, on your manual pages you suggest coping the whole pbx folder for backup: https://doc.vodia.com/docs/how-to-backup-the-pbx /usr/local/pbx Is it required to stop the pbx service before backing up, to make sure we have consistent backups? Or is it supported to backup without stopping the service? At the moment we stop the service though before making a backup every night with: service pbx stop If it is recommended to stop the service, an update to the documentation would be good.
  6. Version: 67.0.6 (from 26.7.2021) Domain > General Setting > Trust Caller ID --> on Assign cell phone number to an account Assign account to agent group Log in to agent group with account call agent group from cell phone --> call gets never put through and stays in queue forever, non assigned extensions to the agent group rings Temporary solution: log out account from agent group or disable Trust Caller ID How it should be: when calling the extension directly via mobile, the virtual personal assistant should answer when calling the agent group via mobile, the call should be routed to the queue as any other call would
  7. Hi, I wanted to use service flags in dials plans, but this does not seem to work. I have a dial plan that allows the extensions to use a trunk, that supports clip no sreening and therefore using the extensions ANI. To this trunk I have added the service flag called "test". As a next trunk with higher pref, I added a second trunk that does not allow clip no screening and therefore setting the same outgoing number to all external calls: Main trunk = extension ANI 92.... = allways use the phone number with 92..... regardless of the extension ANI May expectation would be the following: When the service flag "test" is not active the extension ANI is set for outgoing calls, as the "main trunk" is used. When the service flag "test" is active the extension uses the second trunk and therefore the fixed number starting with 92... is used. But regardless of the state of the service flag "test", the first main trunk is always used and never set to disabled. It looks like the status of the service flag has no impact on the trunks. Maybe a bug?
  8. Yeah that would also be my expecation, but maybe I still get it wrong. So if I set an ACD on a BLF and have "Enable call pickup from extension BLF" active the BLF button should indicate an incomming call to that ACD and when I press the BLF button the call sould be transfered to that extension. But it does not work like this. The BLF button indicates the incomming call, but pressing the button does not pick the call but calling the ACD instead. Update: ok, when the extension is logged into the ACD, pressing the BFL button that is set to this specific ACD is indeed picking the call. I thought it was also possible, when the extension is not logged into the ACD. Obviously it is not. Is there a way to achive this?
  9. Yea. I do not want to touch templates, that is why I used the parameters "Advanced > Parameter > Yealink > Yealink General". I thought the settings in "Advanced > Parameter > Yealink > Yealink General" are of higher priority. But as I learned it is not. At least it may vary from parameter to parameter. So if this does not work and gets overwritten, your suggestion is to use the templates anyway? At least I want to prevent that Vodia resets manually changed settings with the next cycle of pushing configs to the phones. Otherwise I make manually changes to the phones to bypass Vodia defaults and after a day or so, they are gone due to Vodia regularly pushing standard configs out to the phones. The best way of cause would be one central place in Vodia where I can reliably overwrite default phone parameter settings.
  10. Ok, thank you. I got it working with the following settings 1. setting the trunk "regular ANI rule": 2. changing the easybell settings in the easybell web portal: https://login.easybell.de/phonesettings So as you suggested, I did not manipulate the from headers in the Vodia trunk settings: Important: for all that want to follow along, you need at least Vodia Version 66.0.7, buid date later than 5.2.2021 http://portal.vodia.com/downloads/pbx/version-66.0.7.xml Request: Form my point of view the Vodia easybell template needs the following minor updates in addition to the changes you already put in for version 66.0.7: add the "regualr ANI rule" as descibed above as default settings set the "rewrite global numbers" to E.164 as default settings add a comment somewhere, that on easybell web management portal the clip-no-screening options need to be changed to p-asserted-identity. That for sure would help others to get it working.
  11. Hi, I would like to have a BLF for an "agent group" that indicates callers in line and when pressing the BLF button, picking the next caller in line. What I could manage to do is the following: adding a BLF for the agent group -> it indicates when callers are in queue, but when pressing the button the callers are not picket; instead the extension calls the agent group adding a BLF that does a call pickup -> it picks up calls from queues but does not indicate via BLF when a caller is in queue. Our goal is to combine both settings. Within the agent group settings I found the option "Enable call pickup from extension BLF"; but I can not figure out how that works. Can you please tell me how to realize that? Thanks.
  12. This is also true for agents that are "allowed to add themselves". If they log in and out, they are added as "primary agents", which is of cause also not what you want
  13. Hi, as a follow up of this post, I think we need additional adjustments on Vodia side to the ones you already made in version 66.0.7, regarding the easybell trunk template: The inbound calls work perfectly and the numbers in Version 66.0.7 get presented in the correct way, but after your changes on the template, we lost the ability for clip-no-screening; that is using custom ANI set on the extensions. https://translate.google.com/translate?hl=&sl=de&tl=en&u=https%3A%2F%2Fwww.easybell.de%2Fhilfe%2Ftelefon-konfiguration%2Fip-telefonanlagen-fuer-unsere-sip-trunks%2Fantwort%2Fvodia-ip-pbx.html 1. In which field do you transmit the ANI? These are the settings I can choose form in the easybell trunk interface on easybell side; with the old Vodia trunk template "From-Display" was working fine. 2. Vodia easybell template settings Before the changes in Version 66.0.7 the following settings worked and enabled clip no screening; but no this does not work anymore: That is: "{ext-ani}" <sip:{trunk-account}@sip.easybell.de> and "{ext-ani}" <sip:{trunk-account}@secure.sip.easybell.de> for TLS If you need to hard code this to the template, please make both versions TLS and non TLS available (see different FQDNs) Thank you.
  14. Hi, I tried to change template paramters for yealink phones on domain level via Advanced > Paramer > Yealink > Yealink General. This does not work for all settings. For some it works, but especially the LDAP related settings are not applied correctly: ldap.tls_mode = 2 ldap.port = 2346 I guess the LDAP default settings from Vodia are applied at a later stage and therefore these settings get overwritten by the default ones. Update: parameters that also do not work local_time.date_format = 5 parameters that do work phone_setting.backlight_time = 60 phone_setting.inactive_backlight_level = 1 Why is this? Is it possible to prioritize all custom parameters over the default ones?
  15. Ok, thanks to your comment I got it working The trick is to set the "System management DNS address" on system level to the same name as the domain name. So you get two LE certificates. One for the domain using SNI and one for the system not unsing SNI. Because the DNS names are the same, it works. Hope this does not cause any side effects though
  • Create New...