Jump to content
Vodia PBX forum

Vodia PBX

Administrators
  • Content Count

    9,503
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vodia PBX

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

191,973 profile views
  1. You can use e.g. truecnam.com to tell the PBX what numbers are suspected SPAM and which ones are not (in reg_recording.htm). First you need to get an account with them.
  2. It seems that you have a license with the Fax-to-mail feature enabled. Do you hear the FAX CNG tone when you call the mailbox? The gateway that you are using must support the T.38 protocol. If that all does not help, please generate a PCAP for this extension and open a trouble ticket.
  3. Ehhh 63.0.4 is not out yet... what OS are you on? If you can give us HTTP(S) access to your server we can handle that for you - for that just open a ticket with the description (or a link to this topic) and login credentials.
  4. The next version will be 63.0.4 - hopefully tomorrow. The topic with the certificates is a little bit longer (maybe worth another discussion thread). In a nutshell - if you are on public IP turn the ACME certificate generation on ("letsencrypt") and the PBX will generate a valid certificate for you. Otherwise the phone has to turn the certificate validation off.
  5. Chiming in... The call log timezone depends on the browser - the PBX sends it in GMT and then the browsers job is to show this in the local time zone. It is actually easy and browsers are good in calculating the local time.
  6. So maybe your problem is not so much the PBX itself - it might be the VoIP phone. You can check if the PBX has the time right by leaving a dummy mailbox message and then listen to it - maybe pressing "4" to hear the time when it was received. If that time is correct, the PBX itself has the time correct. If the time on the VoIP phone is incorrect, then this might be a problem with the timezone for that specific vendor and model. Unfortunately there is absolutely no standard for the different VoIP phones and we are trying to keep up. If the the VoIP phone gets it wrong let us know what model and vendor you are using and we'll take a look if it can be corrected.
  7. Every VoIP phone has to make a decision weather a configuration change requires a reboot. Most of them "whitelist" some settings that don't require it, and for everything else (keep in mind the are millions of settings LoL) it will be careful and perform a reboot cycle. I guess the name is not on that whitelist.
  8. Well - did you try "Atlantic Time Zone (No DST)" and did it solve the problem?
  9. Whops looks like that went under - next version will have that fixed again.
  10. I think "Atlantic Time Zone (No DST)" should be your time zone. There is no daylight savings in Puerto Rico right?
  11. I would just whitelist the pbxctrl.exe with the Windows firewall. Then you don't have to list each separate port. While you are on it, I would delete the FTP port (unless you want to use Polycom phones in the LAN) and possible also delete the TFTP port unless you want to use option 66 in the LAN.
  12. We'll include the update of the name in 63.0.4 - no need to switch phones. Send a private message if you want to get a preview build.
  13. The Yealinks work differently there - for many Grandstream models the "private" line buttons are sort of hard coded while they are just regular buttons on the Yealinks.
  14. No those screens are not the point - the PBX provisions the "Programmable Keys". I have just checked here a GXP 1628 where the display comes from the "Account Name", which does not change with the hot desking. Looks like it would be worth changing that as well with the hot desking, there should be no negative side effect with other devices.
×
×
  • Create New...