Search results

  1. DigitalDaz

    Sofia DNS resolution issue

    Interesting... @bcmike Why are you not just creating two gateways per outbound route eg sip1.blah, sip2.blah? Thie is exactly how I have my outbound routes configured and have done so for years, it works perfectly. @Adrian Fretwell Yealinks work perfectly for me with Route53 records set at...
  2. DigitalDaz

    Nginx 504 Gateway Time-out

    Why do you think starting out with an OS that goes EOL at the end of the year is the way to go?
  3. DigitalDaz

    Agent status is reset to "logged-out" at freeswitch restart, I want it to be preserved

    It wouldn't change, that file does not get loaded, this would be the relevant file: /usr/share/freeswitch/scripts/app/xml_handler/resources/scripts/configuration/callcenter.conf.lua
  4. DigitalDaz

    Agent status is reset to "logged-out" at freeswitch restart, I want it to be preserved

    This is on FusionPBX? I have never known this behaviour. We have queues that agents have NEVER logged into. They have always been logged in.
  5. DigitalDaz

    GATEWAY NOREG...

    There is nothing at all wrong with what you have shown. On your second screenshot, you have register: false. That causes the gateway not to register and so it displays NOREG. If you are having a problem with this trunk and are using authentication. put in a dummy username and password then stop...
  6. DigitalDaz

    Cannot log in with new user

    My mistake completely, there is nothing wrong with the code, I was using the wrong domain name. With regards to the missing salts, this is no more than the new way of authenticating, ie the salt is part of the password itself now, the new php way apparently.
  7. DigitalDaz

    Changing Default port 5060 for internal profile

    It must be communicating with the outside world somehow :)
  8. DigitalDaz

    Changing Default port 5060 for internal profile

    That really not the best way to deal with this. If you are using the recommended way of using FQDNs for domains then you can enable a couple of rules to block attempts at the IP address itself, look in /etc/fail2ban/jail.local, you will see a couple of rules disabled by default.
  9. DigitalDaz

    Freeswitch Wireshark RTP Audio Decoding

    Yes, unless you have messed with your port config
  10. DigitalDaz

    Cannot log in with new user

    Shed load of nulls in the check_auth.php, I'm not going crazy :) array(7) { ["plugin"]=> string(8) "database" ["domain_name"]=> string(21) "queue.mypbxdomain.com" ["username"]=> string(10) "digitaldaz" ["user_uuid"]=> NULL ["contact_uuid"]=> NULL ["domain_uuid"]=> NULL ["authorized"]=>...
  11. DigitalDaz

    Cannot log in with new user

    Hmm... Dunno if I'm on a wild goose chase but the salt column is empty. It is though too for superadmin and I can log in with that.
  12. DigitalDaz

    Cannot log in with new user

    I have just installed a fresh copy of the latest master, created a domain and a couple of users and made them members of the admin group and now I cannot log in. Anyone else experienced this? TIA
  13. DigitalDaz

    Docker - Initial Setup Postsql Credentials

    Just use debian, not docker, its a couple of lines to give you a rock solid installation usually.
  14. DigitalDaz

    Membership access to Multi-Master cluster documentation

    @itia I cannot quite understand the question you are asking regarding "how domains should be set up in multi master scenario"
  15. DigitalDaz

    Access Controls Defaults

    Most reasonable sized carrier will have more than one sip server that traffic comes from, I think my carrier has about 5 and then a whole bunch of separate media servers. Carriers should give you plenty of notice in advance if they are going to change the SIP ips. That is the question you should...
  16. DigitalDaz

    SOLVED 'internal' SIP profile assigning random port instead of 5060

    Just stop using stun, we'll work out the other problems from there, there should be no need to use stun.
  17. DigitalDaz

    SOLVED 'internal' SIP profile assigning random port instead of 5060

    FusionPBX changes settings perfectly, if someone says you need to change other pages to get things to save its probably some newbie without a clue who happened to think that way because cache expired or something. Flush your cache on the SIP status page. What many people do not realise is that...
  18. DigitalDaz

    SOLVED 'internal' SIP profile assigning random port instead of 5060

    Where are you making these changes and why would you want to have sip bind to some random port?
  19. DigitalDaz

    Fanvil

    Please do not try and hijack this thread, start your own.
  20. DigitalDaz

    ran update on 4.5.12 via web gui, no more web

    There has also been a sticky post explaining this in the FusionPBX News section since May29th