Caller ID Issue

YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com
Caller&Callee ID Issue
 Feature Mechanism:
Guide for Your reference:
Please go to support.yealink.com and download the latest “Calling and Connected Line
Identification Presentation on Yealink IP Phones” guide.
The presentation of the Caller/callee identify:

A. The phone will derive the Caller/Callee ID by following priority:
Local Directory>Remote phonebook>Broadsoft Network Directory> UC-one> LDAP directory>
Header of SIP message.
You can see the phone will always match with different kinds of Directory in priority, if no
matching records, then go for SIP header.
B. SIP Header for Caller ID:
You can configure the presentation of the caller identity for account X by WEB or Auto
provisioning:
WEB:
1
www.yealink.com
Auto Provisioning:
account.X.cid_source=
#It configures the presentation of the caller identity when receiving an incoming call for account X. (Same to WEB option ‘Caller ID
source’)
0-FROM (default value)
1-PAI
2-PAI-FROM
3-PRID-PAI-FROM (PRID>PAI>FROM)
4-PAI-RPID-FROM (PAI-PRID-FROM)
5-RPID-FROM (PRID>FROM)
account.X.cid_source_privacy=
#It enables or disables the IP phone to process Privacy header field in the SIP message for account X.
0-Disabled
1-Enabled (Default value, will set the incoming call as ‘anonymous’ call according to ‘privacy’ header)
account.X.cid_source_ppi=
#It enables or disables the IP phone to process the P-Preferred-Identity (PPI) header for caller identity presentation when receiving an
incoming call for account X.
2
www.yealink.com
0-Disabled
1-Enabled (Will handle and display the content of ‘PPI’ header)
So usually, there are ‘Privacy’ >‘PPI’ > ‘FROM’&’PAI’&’PRID’ header from SIP INVITE message,
which the phone can derive the caller ID. A trace example for your reference:
Let’s make an Example:

a) Phone A (register account A) calls to Phone B (register account B), what A ID (Caller ID)
should be displayed on Phone B?
b) Phone B will firstly match all the directory (Local Directory>Remote
phonebook>Broadsoft Network Directory> UC-one> LDAP directory) firstly.
c) If no records in all these directory, then the Phone B will match the SIP INVITE header
which sent by Phone A.
d) If the Phone B was configured to read ‘FROM’ header:
then Phone B will derive SIP INVITE from Phone A :
3
www.yealink.com
And display value in ‘From’ value on Phone B LCD. Like above example is ‘yealink Mason’
The same rules for other Headers
C. SIP Header for Callee ID:

You can configure the presentation of the callee identity for account X via auto provisioning:
account.X.cp_source=
#It configures the presentation of the callee’s identity for account X
0-PAI-RPID (Derives the name and number of the callee from the “PAI” header preferentially. If the server does not send the “PAI” header,
it will derive from the “RPID” header).
1-Dialed Digits (Preferentially displays the dialed digits on the caller’s phone).
2-RFC4916 (Derives the name and number of the callee from “From” header in the Update message). When the RFC 4916 is enabled on
the IP phone, the caller sends the SIP request message which contains the from-change tag in the Supported header. The caller then
receives an UPDATE message from the callee, and displays the identity in the ‘From’ header.
The default value is 0.
 Issue Description:
The Caller ID is wrong when there is an incoming call
 Resolution: （Checking list）

A. Checking with customer about the details such as reproduced steps and what is the expected
Caller ID?
B. Checking with customer if they resort the name in any Directory (Local Directory>Remote
phonebook>Broadsoft Network Directory> UC-one> LDAP directory), if yes, the phone will
derive the names in these directory in priority.
C. If they don’t set any Directory, so we should check SIP header now. Please kindly let
customer to provide us syslog(level 6)/trace/ config.bin files:
Note: Please make sure the trace are with completed SIP message, e.g.:
4
www.yealink.com
Syslog file is in Level6: if it have <6+info> means its Level 6 syslog:
D. Trace/config.bin analysis:
a) Open the trace with wireshark, and filter ‘sip’, find the INVITE message, and check what
Headers inside, for example:
b) Then import config.bin file to phone and check which kind of Caller ID header they
configured. (Or you can ask customer directly). In above case, if customer want caller ID
as ‘David’, they have to configure ‘caller ID source’ to ‘FROM’, and disable PPI header via
auto provisioning parameter: account.X.cid_source_ppi= 0 (caused ppi header is
priority than FROM header as mentioned before, otherwise, the phone will display
Caller ID as ‘21’); the same trouble shooting rules for other SIP headers.
E. If you still have problem for the trouble shooting, please send detailed description and syslog
(level)/trace/config.bin files to our distributor/Yealink FAE for further analysis.
 Products:
5
www.yealink.com
All
 Firmware version:
All
 Case Study 1:
In outgoing call, except dialed number or saved contact, phone can also update the display
information by showing SIP header from message which is sent by server.
1. If customer wants to show PAI header, please check if there is PAI header in 200 OK message.
2. Find “account.X.cp_source=” in configuration files. In this case, customer set it to 2.
3. As we mentioned before, customer wants to show PAI header. So “account.X.cp_source”

value should be 0.
 Case Study 2:
Unlike case study 1, in this case customer doesn’t want to update the display information in
an outgoing call. There are 2 ways to realize it.
1. Set configuration on server to make it stop sending PAI in 200 OK message.
6
www.yealink.com
2. Or you can use auto provisioning sentence to control if phone will update the
display information.
account.x.refresh_remote_id.enable= 0
# 0 -- Won't update through remote ID
# 1-- Will update through remote ID
 Case Study 3:
Customer report an issue. He doesn’t want to display all the information.
The first two lines of display information is set by the following setting.
Check the invite message. We find there is diversion header. This information shows in the
third line.
7
www.yealink.com
This can be disable by following setting. Or make server don’t send diversion header.
Note:
In incoming call, phone will acquire information from Invite message. In outgoing call, phone will
acquire information from 180ringing. During a call, server will send Re-invite and Update
messages to update Call ID display. ACK message can also update Call ID.
Followings are related settings.

account.X.update_ack_while_dialing=
It enables or disables the IP phone to update the display of call ID in the ACK message of a call.
0-Disabled
1-Enabled
account.X.call_id_mode=
It configures the constitution of call ID.
0-Use random digits
1–Use the combination of the digits and letters
2–Use random digits plus MAC address
Display information of Forward:
features.fwd_diversion_enable=
It enables or disables the IP phone to present the diversion information when an incoming call is
forwarded to your IP phone.
0- Disabled
1-Enabled

Caller ID Issue

Uploaded by

Copyright:

Available Formats

Caller ID Issue

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Caller ID Issue

Uploaded by

Copyright:

Available Formats

YEALINK NETWORK TECHNOLOGY CO.,LTD.

The presentation of the Caller/callee identify:

0-FROM (default value)

incoming call for account X.

1-Enabled (Will handle and display the content of ‘PPI’ header)

Let’s make an Example:

then Phone B will derive SIP INVITE from Phone A :

The same rules for other Headers

C. SIP Header for Callee ID:

it will derive from the “RPID” header).

The default value is 0.

 Resolution: （Checking list）

Syslog file is in Level6: if it have <6+info> means its Level 6 syslog:

2. Find “account.X.cp_source=” in configuration files. In this case, customer set it to 2.

3. As we mentioned before, customer wants to show PAI header. So “account.X.cp_source”

Followings are related settings.

Display information of Forward:

You might also like