(12-28-2013 08:11 AM)1sae Wrote: (12-27-2013 04:51 PM)Yealink Support Wrote: Hi 1sae,
In order to do troubleshooting, please supply me syslog level 6, config.bin and pcap.
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
The requested files are attached. FYI the system wouldn't allow me to add a bin file so the extension was changed to txt.
Hi 1sae,
Your problem is the same as ugo.viti.
Because your server send the 200 OK with a display name in P-Asserted-Identity: "CID:5322421" <sip:21335322@xx.xx.xxx> .
In the PAI-FROM, phone will get the display name from your PAI、RPID.(CPSource=0). So you can see the display name CID:5322421 in the history. If you want to change the display name, please change the header of P-Asserted-Identity from server.
If CPSource=1, all the display name of outgoing call will show the caller number, such as 2133. Can you accept this choice?
You can add below syntaxs in CFG file.
-----------------------------------------------
#!version:1.0.0.1
#X means the account number. It ranges from 1~6 for T28P.
account.X.cp_source = 1
-----------------------------------------------
