New Forum system requires email address which you used to apply for your account to replace your original username. Password stays the same.Please see this post for more details
http://forum.yealink.com/forum/showthread.php?tid=40344

Yealink Test Club has been officially launched. Please visit post below to get detail information. Come and join us!
http://forum.yealink.com/forum/announcements.php?aid=18

We just had the YMCS online and we are also working on the features plan on the future versions, in this regard we are need to hear your voice about the YMCS.
Please visit : http://forum.yealink.com/forum/showthread.php?tid=42322


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
t28 phones lagged and unreachable after firmware upgrade
Author Message
bsutton Offline
Junior Member
**

Posts: 10
Joined: Nov 2013
Reputation: 0
Post: #1
t28 phones lagged and unreachable after firmware upgrade
We are in the middle of a deployment of 40 yealink t28 handsets.
As part of this deployment we have upgraded our standard install from using the
yealink_T28.2.70.0.140.rom firmware to using the yealink_T28.2.71.0.165.rom firmware (the older firmware has a bug with parking lots).

During trials at the site we noticed that the handsets were regularly falling off the network (becoming lagged and then unreachable).

We initially blamed this problem on the network as we had the phones/pc on a single network with the PC's bridged through the phones.
Yesterday we made the client split the network.
The phones are now on a separate network spread across 4 brand new POE switches.
With only 6 handsets attached to the network we were stunned to see that phones where still becoming lagged and unreachable.

As part of our deployment with the v.71 firmware we had also turned on the failover settings:

Code:
# Concurrent registration to both servers.
account.1.fallback.redundancy_type=0
account.1.sip_server.1.address = YY.YY.YY.YY
account.1.sip_server.1.port = 5060
account.1.sip_server.1.expires = 300
# try to fail back on every sip transaction, this could slow down calls?
account.1.sip_server.1.failback_mode = 0
account.1.sip_server.1.register_on_enable=1
  
# A DR server has been configured so lets enable it.
account.1.sip_server.2.address = XX.XX.XX.XX
account.1.sip_server.2.port = 5060
account.1.sip_server.3.expires = 300
# try to fail back on every sip transaction, this could slow down calls?
account.1.sip_server.2.failback_mode = 0
account.1.sip_server.2.register_on_enable=1

During the trial deployment sip_server.2 was not available so we did wonder if maybe the phones we unable to deal with the second server not being available so we went back and disabled the second server.

The result was no change as the handsets were still falling off the network (lagged and then unreachable).

At this point we decided to revert to the v70 firmware using essentially the same .cfg file with the exception of the sip_server settings as these don't work in v70:

Code:
account.1.sip_server_host = yy.yy.yy.yy
account.1.sip_server_port = 5060
##account.1.sip_listen_random = 0
account.1.sip_listen_port = 5060

As soon as we downgraded the phones, the phones stopped falling of the network.

You can see from the following logs the occurance of handsets falling of the network. Across a full 24 hours we see a handset become unreachable ever 15 to 30 minutes. We downgraded the phones at 15:30. As you can see we have not had a single phone become unreachable since then (and I'm writting this email some 15 hours after the downgrade).

So it looks to me like we have a major bug in the v71 firmware.
I've attached the full config file we use.

Note : we use a macro language (velocity) to generate the templates at runtime. I've left the velocity macros in place but I think you can easily see what is going on.
The variables NJPROVISION_SIP_REGISTRAR_DR and NJPROVISION_SIP_REGISTRAR simply contain the ip address of the SIP server, whilst expressions like $Extension contains the handsets extension no.

We need an urgent response on this as we need the v71 firmware for the call parking but we can't go live with handsets falling off the network (the client is an inbound call centre - message service - which operates 24 x 7).



Thanks in advance.
Brett

[Dec 22 14:47:28] NOTICE[1990] chan_sip.c: Peer '111' is now Reachable. (26ms / 2000ms)
[Dec 22 14:48:44] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 521
[Dec 22 14:48:54] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (31ms / 2000ms)
[Dec 22 14:49:32] NOTICE[1990] chan_sip.c: Peer '108' is now UNREACHABLE! Last qualify: 20
[Dec 22 14:49:43] NOTICE[1990] chan_sip.c: Peer '109' is now UNREACHABLE! Last qualify: 22
[Dec 22 14:49:43] NOTICE[1990] chan_sip.c: Peer '108' is now Reachable. (26ms / 2000ms)
[Dec 22 14:49:53] NOTICE[1990] chan_sip.c: Peer '109' is now Reachable. (24ms / 2000ms)
[Dec 22 14:51:59] NOTICE[1990] chan_sip.c: Peer '108' is now Lagged. (2192ms / 2000ms)
[Dec 22 14:52:10] NOTICE[1990] chan_sip.c: Peer '134' is now UNREACHABLE! Last qualify: 24
[Dec 22 14:52:10] NOTICE[1990] chan_sip.c: Peer '108' is now Reachable. (22ms / 2000ms)
[Dec 22 14:52:21] NOTICE[1990] chan_sip.c: Peer '111' is now UNREACHABLE! Last qualify: 64
[Dec 22 14:52:21] NOTICE[1990] chan_sip.c: Peer '134' is now Reachable. (53ms / 2000ms)
[Dec 22 14:52:25] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 23
[Dec 22 14:52:31] NOTICE[1990] chan_sip.c: Peer '111' is now Reachable. (25ms / 2000ms)
[Dec 22 14:52:40] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (21ms / 2000ms)
[Dec 22 14:52:54] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 21
[Dec 22 14:53:18] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (30ms / 2000ms)
[Dec 22 14:54:36] NOTICE[1990] chan_sip.c: Peer '134' is now Lagged. (2467ms / 2000ms)
[Dec 22 14:54:46] NOTICE[1990] chan_sip.c: Peer '134' is now Reachable. (36ms / 2000ms)
[Dec 22 14:55:22] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 22
[Dec 22 14:55:31] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (38ms / 2000ms)
[Dec 22 14:57:35] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 34
[Dec 22 14:57:45] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (44ms / 2000ms)
[Dec 22 14:59:06] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 39
[Dec 22 14:59:17] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (578ms / 2000ms)
[Dec 22 15:02:50] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 40
[Dec 22 15:03:00] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (26ms / 2000ms)
[Dec 22 15:04:21] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 42
[Dec 22 15:04:31] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (23ms / 2000ms)
[Dec 22 15:08:33] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 79
[Dec 22 15:08:57] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (29ms / 2000ms)
[Dec 22 15:11:02] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 23
[Dec 22 15:11:20] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (42ms / 2000ms)
[Dec 22 15:12:24] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 42
[Dec 22 15:12:35] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (623ms / 2000ms)
[Dec 22 15:14:38] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 26
[Dec 22 15:15:01] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (29ms / 2000ms)
[Dec 22 15:18:17] NOTICE[1990] chan_sip.c: Peer '134' is now UNREACHABLE! Last qualify: 789
[Dec 22 15:18:23] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 22
[Dec 22 15:18:34] NOTICE[1990] chan_sip.c: Peer '129' is now Reachable. (36ms / 2000ms)
[Dec 22 15:18:50] NOTICE[1990] chan_sip.c: Peer '109' is now Reachable. (36ms / 2000ms)
[Dec 22 15:18:58] NOTICE[1990] chan_sip.c: Peer '134' is now Reachable. (40ms / 2000ms)
[Dec 22 15:19:10] NOTICE[1990] chan_sip.c: Peer '111' is now Reachable. (37ms / 2000ms)
[Dec 22 15:19:19] NOTICE[1990] chan_sip.c: Peer '106' is now Reachable. (37ms / 2000ms)
[Dec 22 15:19:27] NOTICE[1990] chan_sip.c: Peer '107' is now Reachable. (37ms / 2000ms)
[Dec 22 15:19:40] NOTICE[1990] chan_sip.c: Peer '108' is now Reachable. (33ms / 2000ms)
[Dec 22 15:19:55] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (33ms / 2000ms)
[Dec 22 15:20:02] NOTICE[1990] chan_sip.c: Peer '134' is now UNREACHABLE! Last qualify: 40
[Dec 22 15:20:59] NOTICE[1990] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 33
[Dec 22 15:22:28] NOTICE[1990] chan_sip.c: Peer '134' is now Reachable. (430ms / 2000ms)
[Dec 22 15:24:15] NOTICE[1990] chan_sip.c: Peer '126' is now Reachable. (38ms / 2000ms)


Attached File(s)
.zip  yealink.zip (Size: 5.08 KB / Downloads: 1)
(This post was last modified: 12-23-2013 06:52 AM by bsutton.)
12-23-2013 06:49 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Messages In This Thread
t28 phones lagged and unreachable after firmware upgrade - bsutton - 12-23-2013 06:49 AM

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  T27G firmware phnau 1 32 05-21-2019 10:19 AM
Last Post: complex1
  Phones Web UI Not Working after Firmware Update Rockses 0 136 04-09-2019 01:24 PM
Last Post: Rockses
Question Hide Call History on Yealink IP Phones wizardwebsolutions 5 740 04-04-2019 09:58 AM
Last Post: Marie7
  Will the VP59 have either SfB or Teams firmware ksesock 0 217 02-23-2019 05:38 AM
Last Post: ksesock
  Firmware update failed Utendo 1 739 12-17-2018 11:02 AM
Last Post: complex1
  EHS 36 Firmware VOIP 0 356 11-16-2018 07:08 PM
Last Post: VOIP
Question V84 Firmware Model Support Eden 0 406 11-14-2018 02:41 PM
Last Post: Eden
  Yealink T41S Phones (available) MahnIT 1 692 08-30-2018 10:10 AM
Last Post: complex1
  Firmware url version variables possible? rromano 1 649 08-22-2018 05:28 PM
Last Post: johnkiniston
  Use case for Bluetooth enabled IP phones? bradpitt 12 7,105 08-17-2018 10:35 AM
Last Post: Expo

Forum Jump:


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

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