ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Building Elastix 4 via RPM Repo

    IT Discussion
    asterisk centos centos 7 elastix elastix 4 linux pbx voip
    15
    184
    126.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dom @scottalanmiller
      last edited by

      Something in the installation is incorrect...If i need to change the server name or ip address which file do I do that in? hostfile?

      scottalanmillerS 1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @dom
        last edited by

        @dom said:

        Something in the installation is incorrect...If i need to change the server name or ip address which file do I do that in? hostfile?

        Hostname is...

        vi /etc/hostname
        

        IP Address is changed easiest using a TUI:

        nmtui
        
        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller
          last edited by

          What is the output of...

          netstat -tulpn
          
          1 Reply Last reply Reply Quote 0
          • D
            dom
            last edited by

            said:

            netstat -tulpn

            Active Internet connections (only servers)
            Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
            tcp 0 0 127.0.0.1:20004 0.0.0.0:* LISTEN 2553/php
            tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 1841/mysqld
            tcp 0 0 0.0.0.0:5038 0.0.0.0:* LISTEN 2519/asterisk
            tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 2496/cyrus-master
            tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 2496/cyrus-master
            tcp 0 0 0.0.0.0:4559 0.0.0.0:* LISTEN 2547/hfaxd
            tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 1295/dnsmasq
            tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1290/sshd
            tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 2057/master
            tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 2496/cyrus-master
            tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 2496/cyrus-master
            tcp 0 0 100.78.250.75:16001 0.0.0.0:* LISTEN 1298/python
            tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 2496/cyrus-master
            tcp6 0 0 :::110 :::* LISTEN 2496/cyrus-master
            tcp6 0 0 :::143 :::* LISTEN 2496/cyrus-master
            tcp6 0 0 :::80 :::* LISTEN 3853/httpd
            tcp6 0 0 :::53 :::* LISTEN 1295/dnsmasq
            tcp6 0 0 :::22 :::* LISTEN 1290/sshd
            tcp6 0 0 :::25 :::* LISTEN 2057/master
            tcp6 0 0 :::443 :::* LISTEN 3853/httpd
            tcp6 0 0 :::4190 :::* LISTEN 2496/cyrus-master
            tcp6 0 0 :::993 :::* LISTEN 2496/cyrus-master
            tcp6 0 0 :::995 :::* LISTEN 2496/cyrus-master
            udp 0 0 0.0.0.0:53 0.0.0.0:* 1295/dnsmasq
            udp 0 0 0.0.0.0:68 0.0.0.0:* 3800/dhclient
            udp 0 0 0.0.0.0:69 0.0.0.0:* 1303/xinetd
            udp 0 0 127.0.0.1:323 0.0.0.0:* 647/chronyd
            udp 0 0 0.0.0.0:4520 0.0.0.0:* 2519/asterisk
            udp 0 0 0.0.0.0:2727 0.0.0.0:* 2519/asterisk
            udp 0 0 0.0.0.0:50631 0.0.0.0:* 3800/dhclient
            udp6 0 0 :::53 :::* 1295/dnsmasq
            udp6 0 0 ::1:323 :::* 647/chronyd
            udp6 0 0 :::53939 :::* 3800/dhclient

            1 Reply Last reply Reply Quote 0
            • D
              dom
              last edited by

              said:

              nmtui

              BTW should mention that Im using dynamic ip address

              internal ip is 100.78.250.75
              public dynamic is 40.121.19.1

              1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller
                last edited by

                So https://100.78.250.75/ is bringing up the 500 error?

                1 Reply Last reply Reply Quote 0
                • D
                  dom
                  last edited by

                  Tried both and yes 500 error

                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    Do a telnet on the local box and see if it connects.

                    telnet localhost 80
                    

                    You might need telnet...

                    yum -y install telnet
                    
                    1 Reply Last reply Reply Quote 0
                    • D
                      dom
                      last edited by

                      yep it connects

                      JaredBuschJ 1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch @dom
                        last edited by

                        @dom said:

                        yep it connects

                        Webserver is definitely up. Chrome loaded your IP and complained about the certificate. I then got this result after accepting the certificate

                        0_1457649571937_upload-a39e48f2-a4f2-4e4c-bb0c-64c7fea23611

                        1 Reply Last reply Reply Quote 0
                        • JaredBuschJ
                          JaredBusch
                          last edited by

                          Also http://40.121.19.1 redirects to https://40.121.19.1

                          1 Reply Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller
                            last edited by

                            Did you add an HTTP to HTTPS redirect before getting things working?

                            JaredBuschJ 1 Reply Last reply Reply Quote 0
                            • JaredBuschJ
                              JaredBusch @scottalanmiller
                              last edited by

                              @scottalanmiller said:

                              Did you add an HTTP to HTTPS redirect before getting things working?

                              Elastix does that by default. Always has.

                              scottalanmillerS 1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @JaredBusch
                                last edited by

                                @JaredBusch said:

                                @scottalanmiller said:

                                Did you add an HTTP to HTTPS redirect before getting things working?

                                Elastix does that by default. Always has.

                                Doh. That's right.

                                1 Reply Last reply Reply Quote 0
                                • D
                                  dom
                                  last edited by

                                  Azure provides the following:
                                  DNS NAME
                                  pbx77.cloudapp.net
                                  HOST NAME
                                  pbx77
                                  PUBLIC VIRTUAL IP (VIP) ADDRESS
                                  40.121.19.1
                                  INTERNAL IP ADDRESS
                                  100.78.254.76
                                  I access the site and I ssh in using the public vip. When Elastix setup it says:
                                  To access your Elastix System, using a separate workstation (PC/MAC/Linux)
                                  Open the Internet Browser using the following URL:
                                  http://100.78.254.76

                                  After the install I did'nt change anything - which files (conf? host?) can I look at to trouble shoot this?

                                  1 Reply Last reply Reply Quote 0
                                  • scottalanmillerS
                                    scottalanmiller
                                    last edited by

                                    Viewing the page source shows your site returning blank.

                                    As this is connecting the ports must be open. But just double check that you've opened the right ports on Azure for this as you have two separate firewalls to deal with here. Azure's firewall is unrelated to the VM's firewall.

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      dom
                                      last edited by

                                      I opened up the standard ports on azure 80 443 and 22 and the same on centos
                                      firewall-cmd --zone=public --query-port=443/tcp
                                      yes
                                      firewall-cmd --zone=public --query-port=80/tcp
                                      yes

                                      1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller
                                        last edited by

                                        Okay, just wanted to be sure. I assumed from the error, but better safe than sorry.

                                        1 Reply Last reply Reply Quote 0
                                        • D
                                          dom
                                          last edited by

                                          said:

                                          Open the Internet Browser using the following URL:
                                          http://100.78.254.76

                                          Correct me if Im wrong but shouldnt Elastix be configured to use the public vip instead of internal ip - (for example I setup a lamp stack on pbx66.cloudapp.net - no issues.
                                          To access your Elastix System, using a separate workstation (PC/MAC/Linux)
                                          Open the Internet Browser using the following URL:
                                          http://40.121.19.1

                                          Do you know which file I can modify to change and test this theory? don't you just hate noobs lol!

                                          scottalanmillerS 2 Replies Last reply Reply Quote 0
                                          • scottalanmillerS
                                            scottalanmiller @dom
                                            last edited by

                                            @dom said:

                                            said:

                                            Open the Internet Browser using the following URL:
                                            http://100.78.254.76

                                            Correct me if Im wrong but shouldnt Elastix be configured to use the public vip instead of internal ip - (for example I setup a lamp stack on pbx66.cloudapp.net - no issues.
                                            To access your Elastix System, using a separate workstation (PC/MAC/Linux)
                                            Open the Internet Browser using the following URL:
                                            http://40.121.19.1

                                            Do you know which file I can modify to change and test this theory? don't you just hate noobs lol!

                                            No, it should not. Or it is already, depending on how you look at it. Elastix' public IP is the 100.x.x.x number. Then there is another firewall that it knows nothing about and has no interaction with that has the 40.x.x.x. Elastix has nothing to do with that extra router. It doesn't know about it, it can't find out about it and it should not.

                                            Under normal circumstances (normally meaning nothing more than more often than not) you don't expose your PBX to the world, only to your LAN. That's what Elastix is doing. It's telling you how to access it from itself or another machine on your LAN, which could easily be another Azure box.

                                            So it IS configured to use either IP address and it is using its public one. The 100.x.x.x isn't private, like it seems. You are thinking of this like NAT, but that's not what it is.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 9
                                            • 10
                                            • 1 / 10
                                            • First post
                                              Last post