Endpoint HTTP files 404

› VitalPBX Community Support › General Discussion › Endpoint HTTP files 404

  • Post
    • November 22, 2019 at 5:44 am
    huntay
    Participant
    Up
    -1
    Down
    ::

    Attempting to auto-provision a Yealink T42S as proof of concept and the phone doesn’t appear to be able to find the .cfg files (nor can I).

    Where does VitalPBX keep its .cfg files?

    Output of /var/log/httpd/access_log

    192.168.0.119 - - [22/Nov/2019:14:04:31 +1100] "GET /80xxxxxxxc91.boot HTTP/1.1" 404 215 "-" "Yealink SIP-T42S 66.84.0.15 80:xx:xx:xx:xc:91"
    192.168.0.119 - - [22/Nov/2019:14:04:31 +1100] "GET /y000000000000.boot HTTP/1.1" 404 216 "-" "Yealink SIP-T42S 66.84.0.15 80:xx:xx:xx:xc:91"
    192.168.0.119 - - [22/Nov/2019:14:04:31 +1100] "GET /y000000000067.cfg HTTP/1.1" 404 215 "-" "Yealink SIP-T42S 66.84.0.15 80:xx:xx:xx:xc:91"
    192.168.0.119 - - [22/Nov/2019:14:04:31 +1100] "GET /80xxxxxxxc91.cfg HTTP/1.1" 404 214 "-" "Yealink SIP-T42S 66.84.0.15 80:xx:xx:xx:xc:91"
    0
Viewing 4 replies - 1 through 4 (of 4 total)
  • Replies
    • November 22, 2019 at 9:29 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down
    ::

    What URL have you set on your phone?

    0
    • November 24, 2019 at 11:12 pm
    huntay
    Participant
    Up
    0
    Down
    ::

    @ing-joserivera26

    Just straight to ‘http://192.168.0.111’, and ‘http://192.168.0.111:80’ – both hit the server, but still same thing:

    192.168.234.119 - - [25/Nov/2019:09:43:35 +1100] "GET /80xxxxxxxx91.boot HTTP/1.1" 404 215 "-" "Yealink SIP-T42S 66.84.0.15 80:5e:xx:xx:xx:91"
    192.168.234.119 - - [25/Nov/2019:09:43:35 +1100] "GET /y000000000000.boot HTTP/1.1" 404 216 "-" "Yealink SIP-T42S 66.84.0.15 80:5e:xx:xx:xx:91"
    192.168.234.119 - - [25/Nov/2019:09:43:35 +1100] "GET /y000000000067.cfg HTTP/1.1" 404 215 "-" "Yealink SIP-T42S 66.84.0.15 80:5e:xx:xx:xx:91"
    192.168.234.119 - - [25/Nov/2019:09:43:35 +1100] "GET /80xxxxxxxx91.cfg HTTP/1.1" 404 214 "-" "Yealink SIP-T42S 66.84.0.15 80:5e:xx:xx:xx:91"
    192.168.234.119 - - [25/Nov/2019:09:44:50 +1100] "GET /80xxxxxxxx91.boot HTTP/1.1" 404 215 "-" "Yealink SIP-T42S 66.84.0.15 80:5e:xx:xx:xx:91"
    192.168.234.119 - - [25/Nov/2019:09:44:50 +1100] "GET /y000000000000.boot HTTP/1.1" 404 216 "-" "Yealink SIP-T42S 66.84.0.15 80:5e:xx:xx:xx:91"
    192.168.234.119 - - [25/Nov/2019:09:44:50 +1100] "GET /y000000000067.cfg HTTP/1.1" 404 215 "-" "Yealink SIP-T42S 66.84.0.15 80:5e:xx:xx:xx:91"
    192.168.234.119 - - [25/Nov/2019:09:44:50 +1100] "GET /80xxxxxxxx91.cfg HTTP/1.1" 404 214 "-" "Yealink SIP-T42S 66.84.0.15 80:5e:xx:xx:xx:91"

     

    0
    • November 25, 2019 at 8:29 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down
    ::
    0
    • December 8, 2019 at 1:37 am
    InTeleSync
    Participant
    Up
    0
    Down
    ::
    The server will not store a file of the provisioning rules, but rather generate output on-demand based on the User-Agent sent in the request from the phone, or as a URL get parameter.

    If this is what you meant by not being able to find the .cfg files.

    0
Viewing 4 replies - 1 through 4 (of 4 total)
  • The forum ‘General Discussion’ is closed to new topics and replies.