linphone-sdk icon indicating copy to clipboard operation
linphone-sdk copied to clipboard

The Contact in the sdp header is not local domain

Open TenXu opened this issue 2 years ago • 0 comments

Hello author, I found a problem when using linphone, please advise

When I use new version to call out,the sdp is as follows

2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: INVITE sip:[email protected]:45741;user=phone SIP/2.0 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: Via: SIP/2.0/UDP 172.16.105.131:5012;branch=z9hG4bK-63d7895d-2C4;rport 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: From: sip:[email protected]:45741;user=phone;tag=00007681-00000001-1532677394 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: To: sip:[email protected]:45741;user=phone 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: Call-ID: [email protected] 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: CSeq: 1 INVITE 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: Contact: sip:[email protected]:5012;transport=udp 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: Max-Forwards: 70 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: X-YQ-GUID: 336314849 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, UPDATE, PRACK, REGISTER 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: Content-Type: application/sdp 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: Content-Length: 452 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: v=0 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: o=11502010008004 3298 1232 IN IP4 172.16.77.1 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: s=Talk 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: c=IN IP4 172.16.77.1 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: t=0 0 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtcp-xr:rcvr-rtt=all:10000 stat-summary=loss,dup,jitt,TTL voip-metrics 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: m=audio 37263 RTP/AVP 96 97 98 8 99 100 101 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtpmap:96 opus/48000/2 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtpmap:97 speex/16000 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtpmap:98 speex/8000 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtpmap:99 telephone-event/48000 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtpmap:100 telephone-event/16000 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtpmap:101 telephone-event/8000 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtcp:48599 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtcp-fb:* trr-int 1000 2023-01-30 17:09:50.303 912-912/org.linphone.outgoingcall I/Hello Linphone: a=rtcp-fb:* ccm tmmbr

As you can see, the Contact is sip:[email protected]:5012;transport=udp

When I use linphone-sdk-android-5.0.72-pre.3+92ad42d to call out,the sdp is as follows

2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: INVITE sip:[email protected]:5012 SIP/2.0 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: Via: SIP/2.0/UDP 172.16.76.78:41339;branch=z9hG4bK.wFwgwJ2H8;rport 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: From: sip:[email protected];tag=dfdRwSSrl 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: To: sip:[email protected] 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: CSeq: 20 INVITE 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: Call-ID: ttN5jQ9JcH 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: Max-Forwards: 70 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: Supported: replaces, outbound, gruu 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, PRACK, UPDATE 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: Content-Type: application/sdp 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: Content-Length: 503 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: Contact: sip:[email protected]:41339;transport=udp;+sip.instance="urn:uuid:361c07e2-93c2-00a5-88c5-d89116b1856d" 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: User-Agent: Unknown 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: v=0 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: o=11502010008006 2276 2008 IN IP4 172.16.76.78 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: s=Talk 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: c=IN IP4 172.16.76.78 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: t=0 0 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtcp-xr:rcvr-rtt=all:10000 stat-summary=loss,dup,jitt,TTL voip-metrics 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: m=audio 7078 RTP/AVP 96 97 98 0 8 101 99 100 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtpmap:96 opus/48000/2 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=fmtp:96 useinbandfec=1 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtpmap:97 speex/16000 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=fmtp:97 vbr=on 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtpmap:98 speex/8000 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=fmtp:98 vbr=on 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtpmap:101 telephone-event/48000 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtpmap:99 telephone-event/16000 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtpmap:100 telephone-event/8000 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtcp-fb:* trr-int 1000 2023-01-30 17:15:04.923 17618-17618/com.yunqu.avayaivr I/YunQuSipSdk: a=rtcp-fb:* ccm tmmbr

As you can see, the Contact is sip:[email protected]:41339;transport=udp;+sip.instance="urn:uuid:361c07e2-93c2-00a5-88c5-d89116b1856d

When using version linphone-sdk-android-5.0.72-pre.3+92ad42d, Contact is a local domain and can be hung up normally. When using new version,Contact is server domain and cannot be hang up normally

TenXu avatar Jan 30 '23 09:01 TenXu