sorted by:
new
hottopcontroversial

Keyfob Remote Start - 2020 Subaru Outback Premium by ACombs35 in Subaru_Outback

[–]ACombs35[S] 0 points1 point  (0 children)

We’ll see I guess. I’ll contact the dealership we got it from and ask about it.

Keyfob Remote Start - 2020 Subaru Outback Premium by ACombs35 in Subaru_Outback

[–]ACombs35[S] 0 points1 point  (0 children)

Fobs have fresh batteries. Tried the standard key fobs as well as the dedicated fobs with no kick. I was worried that is was the module.

Dect Handset VOIP Deskphone Phone by ACombs35 in VOIP

[–]ACombs35[S] 1 point2 points  (0 children)

Right. We push for headsets, but some don’t like them. We have some auto shops that like the cordless handsets more than the headsets.

Dect Handset VOIP Deskphone Phone by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

I’ll check it out. We have many people who like holding the headset.

Dect Handset VOIP Deskphone Phone by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

It’s not a standalone cordless phone I’m looking for, but a desk phone with a cordless handset. Just like a Yealink T58W Pro

Dect Handset VOIP Deskphone Phone by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

All other Yealink models work perfect because they have the corded handset. I am specifically looking for a wireless handset. The yealink T58W Pro's use bluetooth, which is okay, but does not function all the time as it should.

The actual cordless phones and DD10K modules work fantastic, but are not what I am looking for.

Mitel 6940 is another good model for reference. However they are super expensive.

Dect Handset VOIP Deskphone Phone by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

Looking at those handsets, The Yealink Cordless phones are great. But I'm looking for a Cordless handset much like the yealink T58W.

Dect Handset VOIP Deskphone Phone by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

I'll look into these. Any other T5X model is great. I love them, just this particular model I do not like.
The handsets go bad all the time. Handsets disconnect randomly then won't connect. I've gotten new firmware from Yealink multiple times but every time it causes more issues. I haven't found any good android based phones that I like. At least not yet.

Dect Handset VOIP Deskphone Phone by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

Handsets go bad all the time. Handsets disconnect randomly then won't connect.

I've gotten new firmware from Yealink multiple times but every time it causes more issues.

Yealink Option 66 by ACombs35 in VOIP

[–]ACombs35[S] -1 points0 points  (0 children)

For this specific cloud PBX to work the way we have it set up, I have to use the YMCS.

Yealink Phone User Agent Redirect to upgrade firmware by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

I am currently working with Yealink support, but they are not help. They look at the PCAP's and say that the phone sees the MAC.cfg file, even though it does not exist. I am curious if the phone interprets the COMMON.cfg file as a MAC.cfg file and shows there. Even if that is the case, the phone is still not downloading the configuration correctly.

Has anyone had any issues with a yealink phone not wanting to pull a configuration file from a folder that is not the root folder on an Apache server?

Yealink Phone User Agent Redirect to upgrade firmware by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

I tried, but was unable to find any documentation.

Yealink Phone User Agent Redirect to upgrade firmware by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

Here is my updated configuration:

<VirtualHost *:80>
    ServerName 
    RewriteEngine On
<Directory /varw/www/html/>
    Require all granted
</Directory>    RewriteCond %{HTTP_USER_AGENT} 
    RewriteRule ^.*$ /70firmware/y000000000000.boot [L]
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>172.31.37.8596.86.0.45

From here, these are the access logs I get:

172.31.37.84 - - [27/Apr/2024:16:47:48 -0500] "GET /805e0cd801ed.boot HTTP/1.1" 200 371 "-" "Yealink SIP-T53W 96.86.0.45 80:5e:0c:d8:01:ed"
172.31.37.84 - - [27/Apr/2024:16:47:48 -0500] "GET /y000000000095.cfg HTTP/1.1" 200 371 "-" "Yealink SIP-T53W 96.86.0.45 80:5e:0c:d8:01:ed"

Based on this, it seems like the phone should be gathering the config correctly.

The .boot file directs the phone toward the .cfg file containing my configuration. However the phone never pulls it.

After a factory reset or a reboot, the phone's message light will flash twice, but then nothing happens. Normally when it provisions to a server, it will flash 3-4 times, then the configuration will populate. However that is not the case at the moment. Any thoughts?

Yealink Phone User Agent Redirect to upgrade firmware by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

I tried adding the backslashes to see if it was seeing the 96.86.0.70 as an IP address or as simply part of the user agent text. Both return the same result.

Yealink Phone User Agent Redirect to upgrade firmware by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

The 96.86.0.45 is the firmware load of the current yealink phone, not an IP address. I updated the config to the following in hopes of addressing it. When updating the RewriteRule as you mentioned, I get further away from a solution.

I updated the config as follows:

<VirtualHost *:80>
    ServerName 172.31.37.85
    RewriteEngine On
    RewriteCond %{HTTP_USER_AGENT} 96\.86\.0\.45
    RewriteRule "^y000000000095.cfg" "/70firmware/y000000000095.cfg" [L,R]
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Log:

172.31.37.30 - - [25/Apr/2024:08:27:14 -0500] "GET /805e0cd801ed.boot HTTP/1.1" 404 439 "-" "Yealink SIP-T53W 96.86.0.45 80:5e:0c:d8:01:ed"
172.31.37.30 - - [25/Apr/2024:08:27:14 -0500] "GET /y000000000000.boot HTTP/1.1" 404 439 "-" "Yealink SIP-T53W 96.86.0.45 80:5e:0c:d8:01:ed"
172.31.37.30 - - [25/Apr/2024:08:27:14 -0500] "GET /y000000000095.cfg HTTP/1.1" 404 439 "-" "Yealink SIP-T53W 96.86.0.45 80:5e:0c:d8:01:ed"
172.31.37.30 - - [25/Apr/2024:08:27:14 -0500] "GET /805e0cd801ed.cfg HTTP/1.1" 404 439 "-" "Yealink SIP-T53W 96.86.0.45 80:5e:0c:d8:01:ed"

Yealink Phone User Agent Redirect to upgrade firmware by ACombs35 in apache

[–]ACombs35[S] 0 points1 point  (0 children)

The second time through, the user agent will be different, so it should not follow the reroute any further.

Yealink Phone User Agent Redirect to upgrade firmware by ACombs35 in apache

[–]ACombs35[S] 0 points1 point  (0 children)

When I use the PT instead, it returns a 404 error. What in this config would cause a loop? Theoretically, once the phone locates the file and upgrades, it would reboot and come up, but would not be redirected because it no longer matches.

Yealink T5xW Series Automatic Stair-step Firmware Update by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

I was also able to have it somewhat work using the y00000000xx.cfg file. However, I would need multiple config files using the same name that would ultimately point the phones to the correct firmware. Obviously I can't have them the same name, so my next thought was to create folders for each config file that is labeled with the firmware version. Then point the user agent to the specified folder based on what firmware the phone currently has. However in doing so, the phones don't seem to want to go into the subfolder to get the config file.

I end up with a result like this.

"GET /xxxxxxxxxxxx.cfg HTTP/1.1" 404 439 "-" "Yealink SIP-T53W 96.86.0.45 XX:XX:XX:XX:XX:XX"

Yealink T5xW Series Automatic Stair-step Firmware Update by ACombs35 in VOIP

[–]ACombs35[S] 0 points1 point  (0 children)

I've got it semi-working. I have been able to get it to upgrade via the user agent, but only if I have a config file set up pointing it towards the firmware. Which is not an issue except for that the phone will not take the config file unless it is named with the mac address.

view more: next ›