# T44W Won't provision **URL:** \ **Category:** VitalPBX 4\ **Created:** [March 21, 2024, 5:18pm UTC](https://forums.vitalpbx.org/t/t44w-wont-provision/3862 "2024-03-21T17:18:46Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Corposolution](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/c/74df32/32.png) [@Corposolution](https://forums.vitalpbx.org/u/Corposolution)\ **Post date:** [March 21, 2024, 5:18pm UTC](https://forums.vitalpbx.org/t/t44w-wont-provision/3862/1 "2024-03-21T17:18:47Z")
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) ---
**Author:** ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)\ **Post date:** [March 21, 2024, 6:36pm UTC](https://forums.vitalpbx.org/t/t44w-wont-provision/3862/2 "2024-03-21T18:36:44Z")
You can debug the provisioning by using the command below. This will allow you to see if the provisioning request is hitting the PBX. ```bash tail -f -n 100 /var/log/apache2/access.log | grep "phoneprov" ``` ---
**Author:** ![Corposolution](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/c/74df32/32.png) [@Corposolution](https://forums.vitalpbx.org/u/Corposolution)\ **Post date:** [March 22, 2024, 12:31pm UTC](https://forums.vitalpbx.org/t/t44w-wont-provision/3862/3 "2024-03-22T12:31:20Z")
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” ---
**Author:** ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)\ **Post date:** [March 22, 2024, 5:42pm UTC](https://forums.vitalpbx.org/t/t44w-wont-provision/3862/4 "2024-03-22T17:42:28Z")
We will fix this in the next Provisioning update!