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
Caller-id after attended transfer not working properly on T19P/T41P
Author Message
ddyx Offline
Junior Member
**

Posts: 5
Joined: Oct 2015
Reputation: 0
Post: #1
Caller-id after attended transfer not working properly on T19P/T41P
Hi.

I have read many posts about this issue and have tried the proposed solutions to no avail.

I'm using a T19P (E2) phone and a T41P phone for the tests. So, the scenario is similar as described on other posts:
1. Incoming call to T19P
2. T19P answers
3. T19P makes a new call to T41P
4. T41P answers
5. T19P performs an attended transfer
6. Caller id shown on T41P's display still shows T19P data and does not update with the original incoming call caller id (name/number)

My first tests were on some of the 80s firmware versions, then I upgraded both phones to the latest 82, because the only documentation that confirmed the existence of the "refresh_remote_id" parameter was on the autoprovisioning template files of the version 82.

After provisioning both phones with this new parameter enabled (through autoprovision), I downloaded the configuration in order to check if the parameter was or wasn't configured, and it turned out that it didn't appear on the downloaded configuration. I tested in spite of this evidence, and of course it didn't work.

Since there is no documentation about what RFC this new parameter supports, it's even more difficult to make modifications on my system to satisfy Yealink phones limitations (for example RFC 5876 doesn't seem to be supported, and it would be of great help to use PAI on UPDATE requests instead of FROM).

I still haven't tested it on other phone models, but I need this to work on these.

Best regards.
01-31-2018 01:17 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Messages In This Thread
Caller-id after attended transfer not working properly on T19P/T41P - ddyx - 01-31-2018 01:17 PM

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  T19P E2 auto provision firmware. NI 1 850 10-08-2018 05:15 PM
Last Post: NI
  Does not answer properly when in a ring group davemcbr 4 1,665 06-01-2018 02:02 AM
Last Post: Michael_Yealink
  T41P: Error when uploading ringtones DanielFrank 3 6,823 01-03-2018 07:00 AM
Last Post: Billiem
  T19P E2 recovery files jgonzalez 1 1,569 12-22-2017 12:35 AM
Last Post: Aishion_Yealink
  T41P will not register DavidAC 2 2,415 07-12-2017 11:44 AM
Last Post: Phonism
  T41P not registering DavidAC 1 1,712 06-23-2017 07:03 AM
Last Post: Kevin_Yealink
  t19p recovery files? freefall2900 7 7,977 11-21-2016 12:15 PM
Last Post: Siegfried05
  Recovery Mode for T41P not working Tonyn 1 3,475 11-21-2016 07:13 AM
Last Post: Yealink_Michael
  Yealink T19P Action URI denis 1 2,848 10-19-2016 09:07 PM
Last Post: denis
  SIP-T19P E2 DTMF not working with g.729 seulater 1 2,443 09-29-2016 11:29 AM
Last Post: Travis_Yealink

Forum Jump:


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

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