Jump to content
Vodia PBX forum

Support

Administrators
  • Content count

    198
  • Joined

  • Last visited

Everything posted by Support

  1. Support

    Restore Backup

    Hi, Can you send that backup zip file to us in a private message and we will try to reproduce that issue here.
  2. Support

    Large DECT Installations

    Hi, We do support a Yealink W52P DECT phone. And also we can also manually register Snom M700, but the Yealink should be recommended.
  3. Support

    can't set conference password v.58

    Hi, We tested this on our latest 60.0 version and everything seemed to work fine. Please picture attached. Make sure you are not using the password codes that you have used previously anywhere (no matter if it's a new ad-hoc conference, it's just a security measure). If that still doesn't go through, then try upgrading to 60.0 and the issue might disappear. P.S: Do make sure you give us a call before upgrading to 60.0.
  4. Support

    Snom M9 cannot make outgoing calls

    Hi, Did you check your dial plans and trunks if they are working as they were previously?
  5. Support

    API to transfer an active call

    Hi, Unfortunately this would be a little out of our reach to develop an API at this point. After discussion with our team, we have concluded that going with only CSTA will be the best option for you.
  6. Support

    Delayed ringing

    Hi, It will be released on 60.0.3. If you want to upgrade to this version before the official version is released then you can follow these steps: 1) Download the 'pbxctrl' from this link http://vodia.com/downloads/pbx/centos64/pbxctrl-centos64-60.0.3 2) replace the 'pbxctrl' in the /usr/local/pbx folder with the 'pbxctrl' from the downloaded file. 3) Reboot.
  7. Support

    BLF - NW BUTTONS V60.00

    Hi Norris, Yes for now those are the only buttons that we have on the latest build for now. As we spoke earlier, they may have to get new extensions for the phones. For buttons, we will create an updated page shortly.
  8. Support

    Paging Problem on Cisco 8851 Phones

    Hi, But please give us a call before you upgrade to 60.0.
  9. Support

    API to transfer an active call

    Hi, Did you check out this link https://vodia.com/documentation/csta_api_example ?
  10. Support

    API to transfer an active call

    Hi, So you are looking for a Blind call to be transferred? Did you try our REST API yet https://vodia.com/pbxapi/index.php? If you dont find what you are looking for, then give us a call or maybe describe here what you are looking for and we can try to add it if it's possible (scenario wise).
  11. Hi, Which phone is 41bis? Also, BLIND transfer should work fine. If it had been just one phone in picture here then you can try that the Blind transfer works fine. If you try to blind transfer from 41bis first (and if it doesn't work) and if you try again from 41 does it give you the same issue again? If yes, then the cancel is not being sent from both the phones at the same time (because they aren't in sync with each other) and hence yes double registration might be the issue.
  12. Support

    Cell No Longer Showing Extension, but CID

    Yes. But before that, try turning the DISA feature off on that domain's settings page and give it a try. We don't know your use case but if it works then well and good.
  13. Support

    Cell No Longer Showing Extension, but CID

    Hi, Use either of these (choice depends on how your trunk takes it) settings to NOT show the original caller ID and just show from where the call have generated.
  14. Support

    Getting extension password via REST api

    Hi, Give us a call and we can discuss this further. +1-617-446-1399
  15. Support

    Getting extension password via REST api

    Slightly, not much. But we gave you the exact one you need.
  16. Support

    Getting extension password via REST api

    Hi, The procedure we provided above is from the latest version 60.0.1. Did you follow the steps 2 and 3 exactly as it's shown? We also tried to "append" the outputs of the pbx.xml before and after restart and can clearly see the difference ( password visible) in the latter part of the file. Please test the API command above again, it has been edited to suit you better.
  17. Hi, The settings at the bottom of the page mentions that restart is required if you change any of those settings on the page reg_settings.htm There is one more build from March 12th, but we don't see how that will make a difference.
  18. Hi, We just tried this out on the 60.0.1 version build date March 12th and we do not see this issue. The domain admin can view all the Extensions, Auto attendants and Hunt Groups. Even the call logs are visible. Did you restart the system after you changed the dial plan to false?
  19. Support

    Getting extension password via REST api

    Hi, You have to follow the same steps: 1) Setting called "rest_show_passwords" in the pbx.xml if you set it to "true". 2) Restart the PBX. 3) Use this REST API command 'sudo curl -u admin:password GET -D - http://127.0.0.1/rest/domain/<domain>/user_settings/<account>'
  20. Hi, Yes the REST API would be easier. Please check out this page https://vodia.com/pbxapi/extensions_api If you need strictly only the list of extensions then you can use this command we just made: curl -ku admin:password GET -D - https://<PBX_DOMAIN_NAME_OR_IP>/rest/domain/<DOMAIN_NAME/extensions
  21. Support

    Snom D315 IO provisioning not working

    Hi, Yes, that can be simulated by using the software called "Postman" Or you can get chrome extension https://chrome.google.com/webstore/detail/user-agent-switcher-for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg?utm_source=gmail
  22. Support

    Snom D315 IO provisioning not working

    Hi, Well, we don't have that exact model in the lab as it's not used much so we tested on the closest one. Which would you like us to test it on, closest to that one?
  23. Support

    Snom D315 IO provisioning not working

    Hi, We tested it on snom300-SIP 8.7.3.25.9
  24. Support

    Snom D315 IO provisioning not working

    Hi, Looks like it worked on our 60.0 over here. Here are the admin level logs: [5] 16:08:30.889 PROV: Identified prov/snom300.htm by pattern snom???.htm [9] 16:08:30.889 PROV: Provision for User-Agent Mozilla/4.0 (compatible; snom300-SIP 8.7.3.25.9 1.1.3-u) [8] 16:08:30.889 PROV: HTTP: Received request for file snom300.htm from 192.168.123.26 [8] 16:08:30.890 PROV: PnP: Extracted MAC for file snom300.htm [9] 16:08:30.890 PROV: Filter configuration file snom_redirect.xml auth: false body: content-type: text/xml filename: snom300.htm host: 192.168.0.144 http: true https: false ip: ({ mac: macauth: false match: 300 resource: /snom300.htm user-agent: Mozilla/4.0 (compatible; snom300-SIP 8.7.3.25.9 1.1.3-u) [7] 16:08:30.890 PROV: File snom_redirect.xml was rendered without a user [8] 16:08:30.891 PROV: HTTP: file snom300.htm based on template snom_redirect.xml is sent to 192.168.123.26 [9] 16:08:30.967 PROV: Provision for User-Agent Mozilla/4.0 (compatible; snom300-SIP 8.7.3.25.9 1.1.3-u) [8] 16:08:30.967 PROV: HTTP: Received request for file snom300-000413280753.htm from 192.168.123.26 [8] 16:08:30.968 PROV: PnP: Extracted MAC 000413280753 for file snom300-000413280753.htm [8] 16:08:30.968 PROV: Provisioning file snom300-000413280753.htm looking for MAC 000413280753 [8] 16:08:30.970 PROV: PnP: Using the credentials of 448@vodia for file snom_300.xml [9] 16:08:30.971 PROV: Filter configuration file snom_300.xml auth: true body: content-type: text/xml filename: snom300-000413280753.htm host: 192.168.0.144 http: true https: false ip: ({ mac: 000413280753 macauth: false match: 0 model: 300 resource: /prov/snom300-000413280753.htm user-agent: Mozilla/4.0 (compatible; snom300-SIP 8.7.3.25.9 1.1.3-u) [8] 16:08:30.974 PROV: HTTP: file snom300-000413280753.htm based on template snom_300.xml is sent to 192.168.123.26 [9] 16:08:31.065 PROV: Provision for User-Agent Mozilla/4.0 (compatible; snom300-SIP 8.7.3.25.9 1.1.3-u) [8] 16:08:31.065 PROV: HTTP: Received request for file snom_cert-000413280753.xml from 192.168.123.26 [8] 16:08:31.065 PROV: PnP: Extracted MAC for file snom_cert-000413280753.xml [9] 16:08:31.066 PROV: Filter configuration file snom_cert.xml auth: false body: content-type: text/xml filename: snom_cert-000413280753.xml host: 192.168.0.144 http: true https: false ip: ({ mac: macauth: false match: resource: /prov/snom_cert-000413280753.xml user-agent: Mozilla/4.0 (compatible; snom300-SIP 8.7.3.25.9 1.1.3-u) [7] 16:08:31.066 PROV: File snom_cert.xml was rendered without a user [8] 16:08:31.067 PROV: HTTP: file snom_cert-000413280753.xml based on template snom_cert.xml is sent to 192.168.123.26 And this is the setting from the web GUI of the phone. Maybe you can switch the firmware on the phone and try it again? Flash the phone, switch the PBX into the incognito mode, reboot the phone and then it should show up in the LAN devices.
  25. Support

    MOH files visible across domains

    Hi, Yes, thanks for bringing that to our attention. We will look into this.
×