T19P E2 identifies itself as whatever specified in To: header of incoming request
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
|
