T44W Won't provision

Reporting an Issue VitalPBX 4
1

Not able to provision Yealink T44 with the provision link gave under PBX / Provision / provisionning

Did the template as usual but my phone won’t go online…

Yealink RPS saying that the phone has communicated with the RPS.

When loggin into the phone, nothing changed (default PW etc)

Trying go give the Server URL of provisionning … nothing more …

Had to configure it by hand …

The URL Link is good (other model that are working)

2

You can debug the provisioning by using the command below. This will allow you to see if the provisioning request is hitting the PBX.

tail -f -n 100 /var/log/apache2/access.log | grep "phoneprov"
1 Like
3

70.50.149.76 - - [21/Mar/2024:11:43:13 -0400] “GET /phoneprov/b3e84acba71cf4d7/249ad89916aa.boot HTTP/1.1” 200 842 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:11:43:13 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:11:43:13 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:11:51:24 -0400] “GET /phoneprov/b3e84acba71cf4d7/249ad89916aa.boot HTTP/1.1” 200 842 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:11:51:24 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:11:51:24 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:03:35 -0400] “GET /phoneprov/b3e84acba71cf4d7/249ad89916aa.boot HTTP/1.1” 200 842 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:03:35 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:03:35 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:06:47 -0400] “GET /phoneprov/b3e84acba71cf4d7/249ad89916aa.boot HTTP/1.1” 200 842 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:06:47 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:06:47 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:11:13 -0400] “GET /phoneprov/b3e84acba71cf4d7/249ad89916aa.boot HTTP/1.1” 200 842 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:11:13 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
70.50.149.76 - - [21/Mar/2024:12:11:13 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
24.225.186.71 - - [21/Mar/2024:13:24:06 -0400] “GET /phoneprov/b3e84acba71cf4d7/249ad89916aa.boot HTTP/1.1” 200 842 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
24.225.186.71 - - [21/Mar/2024:13:24:06 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
24.225.186.71 - - [21/Mar/2024:13:24:06 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
24.225.186.71 - - [21/Mar/2024:15:36:36 -0400] “GET /phoneprov/b3e84acba71cf4d7/249ad89916aa.boot HTTP/1.1” 200 842 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
24.225.186.71 - - [21/Mar/2024:15:36:36 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”
24.225.186.71 - - [21/Mar/2024:15:36:36 -0400] “GET /phoneprov/b3e84acba71cf4d7/xxx.cfg HTTP/1.1” 404 750 “-” “Yealink SIP-T44W 108.86.0.90 24:9a:d8:99:16:aa”

4

We will fix this in the next Provisioning update!