New Forum system requires email address which you used to apply for your account to replace your original username. Password stays the same.Please see this post for more details
http://forum.yealink.com/forum/showthread.php?tid=40344

Yealink Test Club has been officially launched. Please visit post below to get detail information. Come and join us!
http://forum.yealink.com/forum/announcements.php?aid=18

We just had the YMCS online and we are also working on the features plan on the future versions, in this regard we are need to hear your voice about the YMCS.
Please visit : http://forum.yealink.com/forum/showthread.php?tid=42322


Post Reply 
 
Thread Rating:
  • 1 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
T19P E2 identifies itself as wrong User - from TO header of incoming request
Author Message
Travis_Yealink Offline
Super Moderator
******

Posts: 171
Joined: Mar 2016
Reputation: 1
Post: #2
RE: T19P E2 identifies itself as wrong User - from TO header of incoming request
(05-02-2017 10:29 PM)ivanp Wrote:  We are testing T19P E2 phone running firmware 53.80.0.80 and found the following issue: it seems when T19P E2 responds to an incoming SIP message (such as INVITE) it just copies User part of the URI from the TO header into Contact header of the response, which is fundamentally wrong. SIP endpoint (the handset) should rather present itself in the Contact header of the response according to provisioned configuration. Instead it uses whatever comes in the TO header - this could be anything and will cause problems one way or another.

Example is provided below:

1) Relevant part of the configuration file we used to provision this phone:

account.1.label = LCD 2719
account.1.display_name = LCD 2719
account.1.user_name = 2719

account.1.sip_server.1.address = 1.1.1.1
account.1.sip_server.1.port = 5060


2) Request to REGISTER from the phone (note "2719" in the Contact header):

REGISTER sip:1.1.1.1:5060 SIP/2.0
Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK3100258795
Contact: <sip:2719@2.2.2.2:5060>
Call-ID: 0_1730271111@2.2.2.2
CSeq: 1 REGISTER
From: "LCD 2719" <sip:2719@1.1.1.1:5060>;tag=2003548043
To: "LCD 2719" <sip:2719@1.1.1.1:5060>
Content-Length: 0
Expires: 3600
User-Agent: Yealink SIP-T19P_E2 53.80.0.80
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
Allow-Events: talk,hold,conference,refer,check-sync


3) Incoming INVITE (note that TO header is different from the URI above, and TO can be literally anything!)

INVITE sip:2719@2.2.2.2:5060 SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;rport;branch=z9hG4bKylwlx8pz
Via:SIP/2.0/UDP 1.1.1.1:5062;branch=z9hG4bKdd*ftgd*;received=1.1.1.1;rport=5062
Contact: "1234 (Outside)"<sip:1234@3.3.3.3:5060>
Record-Route: <sip:1.1.1.1:5060;lr>
Record-Route: <sip:1.1.1.1:5062;lr>
Remote-Party-ID: "1234 (Outside)" <sip:1234@1.1.1.1:5060>;party=calling;id-type=subscriber;privacy=off
Call-ID: bj.2c2hzoz3u
CSeq: 1 INVITE
From: "1234 (Outside)"<sip:1234@1.1.1.1>;tag=jitb*hy_
To: <sip:72719@1.1.1.1:5060>
Content-Length: 207
Content-Type: application/sdp
User-Agent: some user agent
Accept: application/sdp
Max-Forwards: 19
Session-ID: 0194c712746c47d9e5848c634e6e3ef4


4) Response from T19P E2 (note that User part of the CONTACT header is a copied from the TO header of the INVITE)

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 1.1.1.1:5060;rport=5060;branch=z9hG4bKylwlx8pz
Via: SIP/2.0/UDP 1.1.1.1:5062;branch=z9hG4bKdd*ftgd*;received=1.1.1.1;rport=5062
Contact: <sip:72719@2.2.2.2:5060>
Record-Route: <sip:1.1.1.1:5060;lr>
Record-Route: <sip:1.1.1.1:5062;lr>
Call-ID: bj.2c2hzoz3u
CSeq: 1 INVITE
From: "1234 (Outside)" <sip:1234@1.1.1.1>;tag=jitb*hy_
To: <sip:72719@1.1.1.1:5060>;tag=3379432752
Content-Length: 0
User-Agent: Yealink SIP-T19P_E2 53.80.0.80
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Allow-Events: talk,hold,conference,refer,check-sync

Hi,

We met similar case before, but unsure if it's the same cause.

Suggest you kindly upgarde the firmware to the newest and reset the phone to factory and test again:
http://support.yealink.com/documentFront...umentId=78

If the issue still exist, please kindly provide all THREE trace files, so that we can help you find out the cause.
a. Level 6 syslog
b. PCAP trace
c. Config.bin
You can get the guide from this link to see how to export the issue data(trace files):
http://support.yealink.com/faq/faqInfo?id=311

Any question, freely to let me know.

Regards,
Travis
05-04-2017 09:13 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Messages In This Thread
RE: T19P E2 identifies itself as wrong User - from TO header of incoming request - Travis_Yealink - 05-04-2017 09:13 AM

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
Photo Yealink T21P E2 displays VIA and FROM headers on incoming call DmitryTsyganov 1 1,424 07-12-2018 07:28 PM
Last Post: johnkiniston
  T19P E2 identifies itself as whatever User specified in TO header of incoming request ivanp 0 1,218 05-02-2017 10:27 PM
Last Post: ivanp
  T19P E2 identifies itself as whatever specified in To: header of incoming request ivanp 0 1,330 05-02-2017 10:26 PM
Last Post: ivanp
  Missing Contact header in VQ RTCP XR messages (x.73.0.50) oliv 3 3,791 03-21-2017 01:35 PM
Last Post: Klaus_Yealink
  SIP-T29G user manual in italian language econnet 1 3,149 10-26-2016 08:47 AM
Last Post: Lucia_Yealink
  SIP-T28P Can't Answer Multiple Incoming Calls Trutelecom 1 2,744 08-31-2016 05:10 AM
Last Post: Trutelecom
  T19p E2 recovry firmware benase 3 6,403 07-13-2016 11:27 PM
Last Post: troy.ferrell
  T20P not receiving incoming calls paulbarton 0 2,646 04-27-2016 08:10 PM
Last Post: paulbarton
  T28P Phone identifies itself by IP address instead of user and extension mazuno13 5 4,159 03-08-2016 01:24 AM
Last Post: mazuno13
  T19P ghost call secureip 2 4,108 01-12-2016 05:41 AM
Last Post: secureip

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication