Caller id presentation info on BLF visual display

[Chris Barron]

(09-23-2016 09:27 AM)Yealink_kevin Wrote:  Dear Chris

This is Kevin from Yealink support team, nice to know you.

For this issue, We replace the phone as character, such as T46:A; T41:B; caller phone:C.
Then let us check again with the sutiation:
B set BLF to monitor A, then C call A, B phone will display A<-C;
A set BLF to monitor B, then C call B, A just display B<-B, right?

Let me know if any misunderstanding. Also, please send the pacp,syslog,config.bin files to me , then i can do more trouleshooting. For how to get them, please refer to the FAQ:http://support.yealink.com/faq/faqInfo?id=311
NOTE：please reproduce the issue and send files to me. You should reproduce the 2 sutiation and send all fies to me, then i can do a comparison.



BR
Kevin

HI Kevin,
thanks for the quick response - yes the logic you describe is how i've set it up. Strangely, since i first tested on thursday the situation has changed. On the T46 its no longer showing the inbound number.

I've attached pcap traces from the phone and pcap traces from a local network capture via a bridge so i see both directions. The detail in the SIP notify shows only the extension number not the calling party's number. I tried changing the CID settings and it made no difference, the calling party did not appear in the notify messages however I set it.

Am I right in thinking that the phone presents the called party's name by referencing the extension number in the blf key and pulling back the name rather than relying on it being sent by the server. Because we are seeing the called extension number appearing in the Notify message for the called and call party then its showing Barry<<Barry.
I;ve got a tech case running with the third line support guys on the server side so I will update you.

Also I think I may have missed the syslog files - will end those later - chris[attachment=2994]