Recent content by pbxgeek

  1. P

    Fax Client Invalid Caller ID

    Fixed has been pushed. Please update and let me know if you experience any further issues. It had to do with the Australian numbers, as I suspected.
  2. P

    Fax | Delete a sent fax | warning internal error

    I pushed a fix for this. Please, update and try again
  3. P

    Preventing extensions to make outside calls

    I'm sure we can add something like this in the future.
  4. P

    Fax Client Invalid Caller ID

    They are stored in /var/www/fspbx/resources/views/emails
  5. P

    Fax Client Invalid Caller ID

    Yes right now it seems to be this way. We will need to make it more centralized in future updates.
  6. P

    Fax Client Invalid Caller ID

    This might be due to the same issue on a different page. Let me look into this and push another update.
  7. P

    Provisioning a yealink

    This is a very old phone. But I've seen it working. Call our suuport and we'll try to help you get it up an runnning
  8. P

    Fax Client Invalid Caller ID

    I pushed an update. Please update and try again. Let me know if it's all good.
  9. P

    FSPBX <-> FreePBX

    I believe your concern was resolved on our Discord channel.
  10. P

    Setting up inbound routing

    I would have to circle back and add new voices if they are supported. We added all the options they had at the time we were coding the first version. Rebuilding of an old recordings page is on the roadmap. When we do, you will be able to generate recordings on one page and use them elsewhere...
  11. P

    Some advice on set up

    I have many clients, small and large, that go with a primary-backup pair of servers. This way, both servers and databases are geographically redundant. You can always spin up new servers, add them to the cluster, and remove the old ones. I like your idea of manually moving clients. Believe it...
  12. P

    Deleting a domain

    https://www.pbxforums.com/threads/remove-a-domain.8958/
  13. P

    Fax Client Invalid Caller ID

    Let me push a quick update to allow this type of number. Stand by
  14. P

    domains are case sensitive - but caps are not honoured when creating a domain

    We simplified things in FS PBX. You register against your main domain and pass the tenant domain in the header. It's a unified way of doing things. If you must, you can still make tenant domains routable, but it's not a hard requirement, and it makes things a lot easier in the long run. For...
  15. P

    domains are case sensitive - but caps are not honoured when creating a domain

    If your plan is to export the data and import it to FS PBX, why do you need to keep the domain name the same? This is a perfect time to adopt the unified name convention that uses only lowercase.