Remote Party ID not updating

[japple]

Yealink T46G
version: 28.71.0.85
asterisk version 11.3.0

RPID is not being updated on the phone when calling another extension. I've made adjustments to the cid_source and cp_source via the config file. Changing those settings on the phone made no difference to update the calling party info on the phone. I've attached a pcap file of a call to another extension. The RPID shows up in the 180-ringing packet. Wireshark says it is a "Unrecognized SIP Header (Remote-Party-ID)".

Never had an issue with RPID not working on the Yealink T2X or T3X series.

[Yealink Support]

Hi Japple,
You mean when A call B, A can't see the Caller ID of B?
And T2X/T3X works well with V70 firmware?
Could you also provide us the config.bin file and syslog?
Before you export them , please set log level as 6, and reboot the phone, and reproduce the issue, then click Stop,and export the syslog, config,bin to us.
Then we will submit these files to our R&D to analyze.
Thanks.

[japple]

Yes, that is the correct scenario. On the other series of yealink if I'm extension 100 and I call extension 101, it replaces the 101 on my screen to the name of the person extension 101 is setup as.

I will work on getting the extra debug info for you all later today.

(07-03-2013 02:23 PM)Yealink Support Wrote:  Hi Japple,
You mean when A call B, A can't see the Caller ID of B?
And T2X/T3X works well with V70 firmware?
Could you also provide us the config.bin file and syslog?
Before you export them , please set log level as 6, and reboot the phone, and reproduce the issue, then click Stop,and export the syslog, config,bin to us.
Then we will submit these files to our R&D to analyze.
Thanks.

[japple]

I've included a PCAP, syslog and configuration bin file for both a T38 and T46. The T38 correctly updated the RPID on the screen when calling the other phone. The T46 does not update it at all.

T38 firmware: 38.70.0.100
T46 firmware: 28.71.0.85

[Yealink Support]

Hi Japple,
Thanks for your files, i will submit to our R&D to check.
Any update will let you know ASAP.

[Yealink Support]

Hi Japple,
1.These days our R&D are looking into this issue, but what we found in your files, both T46 and T38 display the name "T46G" or "T38G" and with number when they dial the call.
It means we didn't find there's any different between T46G and T38G from this files.
2.You can see on T38G screen as the attachment, we reproduce the issue with your trace, it display T38G and number, but didn't display the RPID.
So
3. So could you provide us your T38G and T46G screen picture which shows T46G didn't work while T38G works? Together send us the trace, syslog, config.bin files again?
Sorry for the inconvenience.

[CWR]

(07-04-2013 01:31 AM)japple Wrote:  Yes, that is the correct scenario. On the other series of yealink if I'm extension 100 and I call extension 101, it replaces the 101 on my screen to the name of the person extension 101 is setup as.

Hi Japple

Wish 3cx could do this...
Seems odd, but I have to have a local phonebook loaded on my phone to know who is at extension 101 and it uses "Match Remote Phone Book"... This remote book gets updated about every 4 hours by the phone.
If there was another way, that would be great...

[japple]

I'm not sure if 3CX supports remote party id on the extensions.

It is an asterisk system, it will work with 1.8, 10, or 11. On the Yealink T2x and T3x series, you have to set trustrpid = yes and sendrpid = yes (Send Remote-Party-ID Header) on the sip extension. I've never had to use the remote phone book to make it work.

(07-13-2013 02:19 AM)craigreilly Wrote:  Hi Japple

What phone system are you using with the Yealinks?
Just itnerested for my own info... Seems odd, but I have to have a local phonebook loaded on my phone to know who is at extension 101 and it uses "Match Remote Phone Book"... This remote book gets updated about every 4 hours by the phone.
If there was another way, that would be great...