[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Confidence = shaken
Author Message
anomaly0617 Offline
Junior Member
**

Posts: 3
Joined: Nov 2014
Reputation: 0
Post: #1
Confidence = shaken
Hi all,

So, I'm having a frustrating time with one Yealink T32G phone. Sadly, it's the second T32G phone I've been having problems with.

About 6 months ago we bought a Yealink T38G. It replaced a Polycom IP430 that people were telling us we sounded garbled on (it was in our conference room). Instantly people told us the call quality was better, and we liked and still like the phone. Only one problem with it for general use in other places: No wall mount option.

About a month ago I start replacing other Polycom IP430's in the office. I discover the T32G, which has all the features I like (color screen, gigabit passthrough port, easy UI, wall mount option, and it's a supported managed configuration option under my PBX, which is a FreePBX distro called PBX In A Flash). Anyway, I buy 2 of these phones.

Here in the US, getting these phones can sometimes be a problem. The major distributors like NewEgg don't carry them. The minor distributors have them and then sell out of them for a month at a time.

In any case, I buy 2 from a great vendor down in Texas. He ships them to me. One of them configures just fine right out of the box... I shift the phone in the Managed Configuration tool on the PBX, boot up the phone, and voila... instant extension for use.

The other one, not so much. It boots up, grabs it's config file from the server, and looks good to go until I touch a button repeatedly, like, say, the volume up button. The phone reboots.

After the reboot, phone looks good, I push a few buttons and... reboot.

I call the vendor in question, explain the situation, and he sends me a new phone about a week later.

I unbox it, power it on, and it won't boot. I can see in my phone server's log files where it's grabbing the configuration files from the TFTP server, but... it just keeps rebooting.

I'm now thinking "What are the chances I have two phones with the same problem... could my config be an issue?" I delete the phone out of the managed config tool. I delete the [MAC].cfg file out of the tftp server. I download the one there from the other T32G that works fine, rename it, modify it with my SIP Registration and Password, etc. etc. and upload it. Now I should have a stable config.

Nope. Still reboots in a loop.

I search on Google. Find people with similar issues. I factory reset the phone. I move the config file so it's not a problem.

Still reboots in a loop.

I download the T38.rom and the latest firmware for the T32G. I rename T38.rom to T32.rom. Rename the firmware file to T32.bin. Upload them to my tftp server. Then I use the force option where I hold the speaker button in while plugging the network cable into the wall, and get to the menu. I confirm the settings and it updates the phone.

Still reboots all the time.

I download the oldest T38 ROM I can find, which happens to be version 32.70.0.100. Force boot. Update phone. Let it sit for 45 minutes and HEY, I have a phone again.

I leave it alone for a day. Because at this point, I'm boiling over the issues I've been having with these phones, and because I have a working, stable-like phone.

But it then gets me wondering... does my phone still reboot sometimes, and I just don't know it because it does it when I'm away from my desk?

I decide to experiment ever so cautiously with it.

I get into the HTTP interface of the phone and upload a wallpaper to it. I select that wallpaper. Then I wait a day. No change in stability that I can see.

Today I decided to add the commands to enable SNMP to the config file, so I can perhaps monitor the uptime, and I reboot the phone.

Guess what? I'm back to a #&^#%$(*&#%( reboot loop!

My concern is this. We run a network integration company. We support customers who don't have IT departments, and that sometimes includes replacing their phone system. Yealink phones were going to be my "go-to" phone for customers, but.... now my confidence is totally shaken in them. Worse, as I understand it, there's "ZERO" US Support for these phones. So, I have two problems:

1. How can I fix this phone so it stops being a turd and is a stable desk phone (Thankfully it's MY phone and not my accounting guy's phone!)

2. How can any of us in the United States trust that the phones will be stable if we get batches of unstable phones?

The MAC address of this particular phone is 00-15-65-6b-5b-80


Edit: Some additional data: Here's what happens when I set a reservation in my DHCP server for the phone and then run a continuous ping against the IP:
Code:
Reply from 192.168.121.162: Destination host unreachable
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.121.143: bytes=32 time=9ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.121.143: Destination net unreachable.
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Reply from 192.168.121.143: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.

... Over and over and over again.
(This post was last modified: 11-15-2014 06:25 AM by anomaly0617.)
11-15-2014 06:00 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Messages In This Thread
Confidence = shaken - anomaly0617 - 11-15-2014 06:00 AM
RE: Confidence = shaken - anomaly0617 - 11-15-2014, 07:03 AM
RE: Confidence = shaken - James_Yealink - 11-21-2014, 04:08 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication