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

    Yealink T4XG phones will not talk to FreePBX 14 over HTTPS

    IT Discussion
    yealink yealink t46g freepbx 14
    10
    61
    6.6k
    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.
    • DustinB3403D
      DustinB3403 @DustinB3403
      last edited by

      @dustinb3403 said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:

      @bnrstnr said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:

      Not sure if it makes any difference, but he says he's using G models and not S.

      Um he says he's using the G in the topic title, but the S in the body

      1 Reply Last reply Reply Quote 0
      • DashrenderD
        Dashrender
        last edited by

        Well I'm trying it this morning with a T46S and it's not working, as he said.. but I want to confirm his solution before I completely declare JB correct.

        1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender
          last edited by

          Well - I entered the information for the provisioning server, saved it... nothing.

          I rebooted the phone, and it's instantly registered.

          Of course the phones message light is now blinking.. since I copied someone else's config file, I might have missed something...

          1 Reply Last reply Reply Quote 0
          • brianlittlejohnB
            brianlittlejohn
            last edited by

            I just provisioned one of my phones from a factory state to my FreePBX 14 instance with https with success.

            1 Reply Last reply Reply Quote 0
            • DashrenderD
              Dashrender
              last edited by

              I just talked to JB. It's the G model he's having issues with.

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

                Right I want some one to provision one of their T4XS phones to my FreePBX 14 instance from a factory default state.

                brianlittlejohnB 1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender
                  last edited by

                  @JaredBusch is your phone on the latest firmware?

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

                    @dashrender said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:

                    @JaredBusch is your phone on the latest firmware?

                    Have tested the G models on various firmware versions, including current.

                    1 Reply Last reply Reply Quote 0
                    • brianlittlejohnB
                      brianlittlejohn @JaredBusch
                      last edited by

                      @jaredbusch said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:

                      Right I want some one to provision one of their T4XS phones to my FreePBX 14 instance from a factory default state.

                      I'm available to do that.

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

                        Just tested a T42S with @EddieJennings. It worked perfectly.

                        So the issue is 100% the G models and SSL.

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

                          looking for the logs, I cannot find anything. when a valid system hits, I can see it in access_log.

                          The ssl_error log is empty and has been since 2016.

                          The only thing I see in access_log is repeated timeouts when I tell the phone to provision with https

                          64.53.188.39 - - [06/Oct/2017:10:29:17 -0500] "-" 408 - "-" "-"
64.53.188.39 - - [06/Oct/2017:10:29:46 -0500] "-" 408 - "-" "-"
64.53.188.39 - - [06/Oct/2017:10:30:16 -0500] "-" 408 - "-" "-"
64.53.188.39 - - [06/Oct/2017:10:30:45 -0500] "-" 408 - "-" "-"
                          1 Reply Last reply Reply Quote 0
                          • JaredBuschJ
                            JaredBusch
                            last edited by 

                            [root@pbx ~]# ls -l /var/log/httpd
total 46104
-rw-r--r--  1 root root  6784013 Oct  6 10:31 access_log
-rw-r--r--  1 root root   101243 Sep 11 03:24 access_log-20170911
-rw-r--r--  1 root root   908614 Sep 17 03:23 access_log-20170917
-rw-r--r--  1 root root  1014085 Sep 25 09:25 access_log-20170925
-rw-r--r--  1 root root 38078761 Oct  1 03:37 access_log-20171001
-rw-r--r--  1 root root     2742 Oct  5 10:05 error_log
-rw-r--r--  1 root root    12883 Sep 11 03:47 error_log-20170911
-rw-r--r--  1 root root     8360 Sep 17 06:59 error_log-20170917
-rw-r--r--  1 root root     3305 Sep 25 09:29 error_log-20170925
-rw-r--r--  1 root root     1587 Oct  1 03:37 error_log-20171001
-rw-r--r--  1 root root        0 Oct 16  2016 ssl_access_log
-rw-r--r--. 1 root root    21393 Oct  2  2016 ssl_access_log-20161002
-rw-r--r--  1 root root    59064 Oct  9  2016 ssl_access_log-20161009
-rw-r--r--  1 root root     8669 Oct 10  2016 ssl_access_log-20161016
-rw-r--r--  1 root root        0 Oct 16  2016 ssl_error_log
-rw-r--r--. 1 root root    10997 Oct  2  2016 ssl_error_log-20161002
-rw-r--r--  1 root root    14011 Oct  9  2016 ssl_error_log-20161009
-rw-r--r--  1 root root     1947 Oct 10  2016 ssl_error_log-20161016
-rw-r--r--  1 root root        0 Oct 16  2016 ssl_request_log
-rw-r--r--. 1 root root    23391 Oct  2  2016 ssl_request_log-20161002
-rw-r--r--  1 root root    69536 Oct  9  2016 ssl_request_log-20161009
-rw-r--r--  1 root root     9621 Oct 10  2016 ssl_request_log-20161016
                            1 Reply Last reply Reply Quote 0
                            • JaredBuschJ
                              JaredBusch
                              last edited by

                              I change the autoprovision to http://pbx.domain.com:84

                              and boom.

                              64.53.188.39 - - [06/Oct/2017:10:40:56 -0500] "GET /001565649346.boot HTTP/1.1" 404 215 "-" "Yealink SIP-T46G 28.82.0.20 00:15:65:64:93:46"
64.53.188.39 - - [06/Oct/2017:10:40:56 -0500] "GET /y000000000000.boot HTTP/1.1" 404 216 "-" "Yealink SIP-T46G 28.82.0.20 00:15:65:64:93:46"
64.53.188.39 - - [06/Oct/2017:10:40:56 -0500] "GET /y000000000028.cfg HTTP/1.1" 200 10433 "-" "Yealink SIP-T46G 28.82.0.20 00:15:65:64:93:46"
64.53.188.39 - - [06/Oct/2017:10:40:58 -0500] "GET /T46-28.82.0.20.rom HTTP/1.1" 200 23234624 "-" "Yealink SIP-T46G 28.82.0.20 00:15:65:64:93:46"
64.53.188.39 - - [06/Oct/2017:10:41:02 -0500] "GET /001565649346.cfg HTTP/1.1" 200 4421 "-" "Yealink SIP-T46G 28.82.0.20 00:15:65:64:93:46"
                              syko24S 1 Reply Last reply Reply Quote 0
                              • syko24S
                                syko24 @JaredBusch
                                last edited by

                                @jaredbusch - Not sure if this is related but something I found interesting with my T46S phones are that when I autoprovision them using https they revert back to http. I am using option 66 and point to https://pbx.domain.com:1443. The phones provision fine but when I log into the phone the address under autoprovision is http://pbx.domain.com:83. I am using the endpoint manager module for configuration.

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

                                  @syko24 said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:

                                  @jaredbusch - Not sure if this is related but something I found interesting with my T46S phones are that when I autoprovision them using https they revert back to http. I am using option 66 and point to https://pbx.domain.com:1443. The phones provision fine but when I log into the phone the address under autoprovision is http://pbx.domain.com:83. I am using the endpoint manager module for configuration.

                                  You get that because that is what Enpoint Manager puts in the config file.

                                  You have to force it to not do that.

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

                                    @syko24
                                    The Endpoint Manager puts this in the basefile for Yealink phones.
                                    0_1507308604327_bea90b16-0c8e-4952-80a4-4d8bca56c173-image.png

                                    So you need to manually override that, or find where that variable gets set to make it use https instead.

                                    syko24S 1 Reply Last reply Reply Quote 0
                                    • syko24S
                                      syko24 @JaredBusch
                                      last edited by

                                      @jaredbusch said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:

                                      @syko24
                                      The Endpoint Manager puts this in the basefile for Yealink phones.
                                      0_1507308604327_bea90b16-0c8e-4952-80a4-4d8bca56c173-image.png

                                      So you need to manually override that, or find where that variable gets set to make it use https instead.

                                      So I would need to select custom under Provision Server Address and enter https://pbx.domain.com:1443 ?

                                      0_1507318682880_image13.png

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

                                        @syko24 said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:

                                        @jaredbusch said in Yealink T4XG phones will not talk to FreePBX 14 over HTTPS:

                                        @syko24
                                        The Endpoint Manager puts this in the basefile for Yealink phones.
                                        0_1507308604327_bea90b16-0c8e-4952-80a4-4d8bca56c173-image.png

                                        So you need to manually override that, or find where that variable gets set to make it use https instead.

                                        So I would need to select custom under Provision Server Address and enter https://pbx.domain.com:1443 ?

                                        0_1507318682880_image13.png

                                        Well you could probably do HTTP and disable http in SysAdmin -> port management.

                                        Then see what it puts in the file.

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

                                          @syko24 ah, here it is.. Assuming you have SysAdmin pro

                                          0_1507321373826_f8ebe664-a17a-4444-8dd2-ffaa477449cd-image.png

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

                                            No good answer from the FreePBX community.

                                            The COO tried to help, but another community member was less than helpful.

                                            I also posted on the Yealink community, but have no answer yet.
                                            http://forum.yealink.com/forum/showthread.php?tid=41194

                                            1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 1 / 4
                                            • First post
                                              Last post