Yealink Phone to Send Private IP Address on Register

[Ari]

A really helpful feature of the < 83 firmware was to send the private IP address of the phone on register. This is helpful for locating and administering a phone in a network.

Code:

2019/09/17 10:53:05.975177 PUBLIC_IP:12326 -> PBX_IP:5060                                    │2019/09/17 10:53:18.681875 PUBLIC_IP:12282 -> PBX_IP:7331
                                                                                             │
REGISTER sip:sub.dom.tld:5060 SIP/2.0                                                        │REGISTER sip:sub.dom.tld:7331 SIP/2.0
Via: SIP/2.0/TCP PUBLIC_IP:12326;branch=z9hG4bK3539585581;rport                              │Via: SIP/2.0/TCP 10.0.0.12:5060;branch=z9hG4bK4046200025;rport
From: "234" <sip:234@sub.dom.tld:5060>;tag=4231823471                                        │From: "623" <sip:623@sub.dom.tld:7331>;tag=1609913972
To: "234" <sip:234@sub.dom.tld:5060>                                                         │To: "623" <sip:623@sub.dom.tld:7331>
Call-ID: 0_2813005062                                                                        │Call-ID: 3_3967202445@10.0.0.12
CSeq: 1 REGISTER                                                                             │CSeq: 47362 REGISTER
Contact: <sip:234@PUBLIC_IP:12326;transport=TCP>                                             │Contact: <sip:623@10.0.0.12:5060;transport=TCP>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PU│Authorization: Digest username="623", realm="sub.dom.tld", nonce="e4002605-e9a1-
LISH, UPDATE, MESSAGE                                                                        │841-aff7-8ffb480434fe", uri="sip:sub.dom.tld:7331", response="81a2b738efbe4eb374
Max-Forwards: 70                                                                             │5f481d00fe0e0", algorithm=MD5, cnonce="0a4f113b", qop=auth, nc=00047361
User-Agent: Yealink SIP-T46S 66.84.0.15                                                      │Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PU
Expires: 600                                                                                 │LISH, UPDATE, MESSAGE
Allow-Events: talk,hold,conference,refer,check-sync                                          │Max-Forwards: 70
Content-Length: 0                                                                            │User-Agent: Yealink SIP-T52S 70.81.0.10
                                                                                             │Expires: 60
                                                                                             │Allow-Events: talk,hold,conference,refer,check-sync
                                                                                             │Content-Length: 0

On the right is a registration from a Yealink phone on 81 firmware and in the "Call-ID" header you can see the private IP address sent. On the left, you can see the 84 firmware does not send the private IP address.
Is there a config on the Yealink to change that?

[Clan_Yealink]

(09-17-2019 01:23 AM)Ari Wrote:  A really helpful feature of the < 83 firmware was to send the private IP address of the phone on register. This is helpful for locating and administering a phone in a network.

Code:

2019/09/17 10:53:05.975177 PUBLIC_IP:12326 -> PBX_IP:5060                                    │2019/09/17 10:53:18.681875 PUBLIC_IP:12282 -> PBX_IP:7331
                                                                                             │
REGISTER sip:sub.dom.tld:5060 SIP/2.0                                                        │REGISTER sip:sub.dom.tld:7331 SIP/2.0
Via: SIP/2.0/TCP PUBLIC_IP:12326;branch=z9hG4bK3539585581;rport                              │Via: SIP/2.0/TCP 10.0.0.12:5060;branch=z9hG4bK4046200025;rport
From: "234" <sip:234@sub.dom.tld:5060>;tag=4231823471                                        │From: "623" <sip:623@sub.dom.tld:7331>;tag=1609913972
To: "234" <sip:234@sub.dom.tld:5060>                                                         │To: "623" <sip:623@sub.dom.tld:7331>
Call-ID: 0_2813005062                                                                        │Call-ID: 3_3967202445@10.0.0.12
CSeq: 1 REGISTER                                                                             │CSeq: 47362 REGISTER
Contact: <sip:234@PUBLIC_IP:12326;transport=TCP>                                             │Contact: <sip:623@10.0.0.12:5060;transport=TCP>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PU│Authorization: Digest username="623", realm="sub.dom.tld", nonce="e4002605-e9a1-
LISH, UPDATE, MESSAGE                                                                        │841-aff7-8ffb480434fe", uri="sip:sub.dom.tld:7331", response="81a2b738efbe4eb374
Max-Forwards: 70                                                                             │5f481d00fe0e0", algorithm=MD5, cnonce="0a4f113b", qop=auth, nc=00047361
User-Agent: Yealink SIP-T46S 66.84.0.15                                                      │Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PU
Expires: 600                                                                                 │LISH, UPDATE, MESSAGE
Allow-Events: talk,hold,conference,refer,check-sync                                          │Max-Forwards: 70
Content-Length: 0                                                                            │User-Agent: Yealink SIP-T52S 70.81.0.10
                                                                                             │Expires: 60
                                                                                             │Allow-Events: talk,hold,conference,refer,check-sync
                                                                                             │Content-Length: 0

On the right is a registration from a Yealink phone on 81 firmware and in the "Call-ID" header you can see the private IP address sent. On the left, you can see the 84 firmware does not send the private IP address.
Is there a config on the Yealink to change that?

Hi Sir, how are you today？

This is Clan from Yealink Technical Support team, nice to work with you.

There are configuration statements in the phone to control whether the IP address is in the Call-ID.
Statement: account.x.call_id_no_ip_addr.enable = 0 (X is the account number)

Any queries, please feel free to let me know. Thanks.

Best Regards!
Clan

[Ari]

(09-20-2019 10:03 AM)Clan_Yealink Wrote:  There are configuration statements in the phone to control whether the IP address is in the Call-ID.
Statement: account.x.call_id_no_ip_addr.enable = 0 (X is the account number)

Thank you for that information.
I uploaded both

Code:

account.1.call_id_no_ip_addr.enable = 0

and

Code:

account.1.call_id_no_ip_addr.enable = 1

but neither of them worked.

The REGISTRATION attempt looked identical in both cases.

I looked in Yealink SIP IP Phones Release Notes of Version 81, 82, 83, and 84 and I could not find mention of this variable.
Is there documentation which shows this configuration variable?

[Ari]

Hi,

This was definitely based on a firmware update.
Could you please provide the right option to change or an escalation point?

[Ari]

I ran my own investigation into the issue.
In my case, setting:

Code:

network.ip_address_mode = 2

Disables sending the IPv4 address in the (as shown) during registration.

I would make a suggestion that if a phone has this set to option 2 and it still has an IPv4 address (irrespective of the IPv6 address) it should still send the IPv4 address.