Jump to content
Vodia PBX forum


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Matteo

  • Rank
  1. This is the same for me. WIth Snom phone when you dial a call during invite session or 100 or 180 answers, before the UDP session start, there's a loud white noise. This noise is introduced, in some way by PBX. It's not a confort noise function because this should be activated only after the session RTP start. Snom, in any case send only mute RTP packet in order to maintain up the UDP session. I Check in the phone settings of the provisioned phone and there are no option that ca be cause this behavior. I ask because the noise is very high and leads the user to think that there is a system malfunction. Obviously this noise completely disappears when the RTP audio session is started: at this point the audio is perfect. This is absolutely independent from the phone or the SIP trunk. Tx
  2. Thanks for the clarification.. if I understood the executable file well, it is "pbxctrl.exe" for windows or "pbxctrl" for other OS. This is therefore the only file that differentiates the installations on the different OS. The "pbxctrl.dat" file is always the same for all installations. Can I ask you what it contains? I imagine the configuration or version of the new system. In case of backup and subsequent restore how should this second file be treated? Suppose we have a backup of the v62 version. Reinstalling Vodia with v63 (for example) which files should be replaced? I ask you to understand what to do in case of manual recovery with the basic installation of a possible subsequent system. I would like to avoid making trouble. Based on your answer I will do tests to verify correct operation. A question comes to my mind. Since the purpose of any system is to make the operations as simple as possible, why not provide a button in the administration section that compresses the entire system folder and allows it to be downloaded? Another step coul be (as other systems do) an automatic backup procedure to a google drive writing the .zip file (or .tar). I think's not so difficult to implement using google API. This would obviously make things easier in the event of a fail. The new function may have the option to include the executable file (which is what distinguishes installations between operating systems) or not. This would make it very easy to move a single installation and complete system restore. Obviously the relative import function should also be included in the administrator panel. In the event of a crash it would be sufficient to reinstall vodia, enter the admin panel and restore the file. I think it would really be a big step forward. Thank You.
  3. Hi, thank you for your indication. About page (reg_pnpparm.htm) and the field "Snom General" What happens if these parameters are already present in the general parameters. I'll give you an example. I really don't like the call transfer method used in the vodia template. I prefer a more traditional method with simultaneous blind + attended transfer. This should also be the method most appreciated by users (judging by the requests). Using these parameters it is possible to obtain a completely automated transfer that allows you to transfer the call in blind mode (transferring and hanging up) or to transfer the call in attended mode, talk to the colleague and then complete the transfer by hanging up. There is no simpler way than this. To do this, just modify these parameters in all Snom: __________________________ <disable_blind_transfer perm = "RW"> on </disable_blind_transfer> <transfer_on_hangup perm = "RW"> on </transfer_on_hangup> <transfer_on_hangup_non_pots perm = "RW"> on </transfer_on_hangup_non_pots> ____________________________ Some of these parameters are already present in the template of course. By placing them on the page (do m_ext3.htm) in the "Snom general" field does this result in an override of any parameters present in the template? At the moment I have directly modified the template of the single phone but, since parameters are generalized for all snom models, it would be preferable to do it according to your advice. The doubt arises from the fact of not creating conflicts. Finally, I would like to ask you for clarification on the placement of template.xml files within the vodia folder structure. I am not referring to the files generated by the parser but to the original files. Where are the various .xml files related to the various templates placed? I couldn't find them in the folders. Are they present in the system database or cannot be modified? I am used to working intensively with other systems on the modification and customization of the templates. I've been dealing with it for many years and I'm very familiar with all the major brands. I was therefore wondering if it was possible to duplicate some templates and customize them or even insert the templates for the missing phones or adjust those that present problems or are not fully functional. I thank you in advance.
  4. HI, I need to know a couple of information about the backup and the possible restore in a failure case. I'am on vodia v63 on debian 9.9. I know the method to backup individual domains, export them and restore them My doubt arises in the event of a general hardware failure. How can I save the full pbx configuration and then be able to restore (manually too if the case)? By "full" I mean the entire administrator part including the various domains or the single instance (in the case of a single PBX domain). In the linux environment the position of the PBX is in / usr / local / pbx. This is clear. In the Windows environment it is even simpler and the structure is the same. Is it enough to copy the whole "pbx" folder, perform a new installation and overwrite the entire contents? I have not found other solutions. The available documentation only refers to backup of the single domain. But in the event of a total failure it is necessary to perform an integral restore quickly without the need to reconfigure the administrator part. I hope there is a solution for a total backup as it now happens for many other competing pbx solutions that allow you to restore an entire pbx in minutes. Thanks in advance
  5. Hi, I'm on vodia V63 with debian 9.9. I found a bug in the provisioning. If you change http or https port from standard port 80 or 443 provisioning stop to working correctly. In my case i provisioned a Snom 710 with standard port 80. Then i change http port to 8090. Deleted mac address bid to extension, reset the phone. This result in provisioning fault. Restoring port http 80 all start to working good. I think this is a possible bug. Then I install new clean PBX: i do same test changing http port to 8090 directly before provisioning: same result: provisioning fail. This is my fisrt problem. Second problem is that i need to modify standard provisioning template to change phone standard beahaviour for some parameters. Were are located in a linux debian environment .xml provisioning files ? I search in all folders under usr/local/pbx without result. Last question is about reprovisioning phones. I cannot find command to send reprovisioning command in case we need to change BLF or bottoms. Thank you in advance Matteo
  • Create New...