Thank you, miconda. We don't set r-uri value in pcscf.cfg, icscf.cfg or scscf.cfg. I will show more details below using the logs with Jitsi. I will omit SDP to save space.
INVITE sip:bob@ims.mnc001.mcc001.3gppnetwork.org SIP/2.0
Call-ID: 0b23b2ee62c061ae9f3cc1569b7824b3@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: "alice" sip:alice@ims.mnc001.mcc001.3gppnetwork.org;tag=94b2833a
To: sip:bob@ims.mnc001.mcc001.3gppnetwork.org
Via: SIP/2.0/UDP [fc00
Max-Forwards: 70
Contact: "alice" sip:alice@[fc00
User-Agent: Jitsi2.10.5550Linux
Content-Type: application/sdp
Content-Length: 910
INVITE sip:bob@ims.mnc001.mcc001.3gppnetwork.org SIP/2.0
Route: sip:orig@scscf.ims.mnc001.mcc001.3gppnetwork.org:5060;lr
Record-Route: sip:mo@[FC00
Call-ID: 0b23b2ee62c061ae9f3cc1569b7824b3@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: "alice" sip:alice@ims.mnc001.mcc001.3gppnetwork.org;tag=94b2833a
To: sip:bob@ims.mnc001.mcc001.3gppnetwork.org
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [fc00
Max-Forwards: 69
Contact: "alice" sip:alice@[fc00
User-Agent: Jitsi2.10.5550Linux
Content-Type: application/sdp
Content-Length: 910
P-Asserted-Identity: sip:alice@ims.mnc001.mcc001.3gppnetwork.org
X-RTP: mo
INVITE sip:bob@ims.mnc001.mcc001.3gppnetwork.org SIP/2.0
Record-Route: sip:mo@[FC00
Record-Route: sip:mo@[FC00
Call-ID: 0b23b2ee62c061ae9f3cc1569b7824b3@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: "alice" sip:alice@ims.mnc001.mcc001.3gppnetwork.org;tag=94b2833a
To: sip:bob@ims.mnc001.mcc001.3gppnetwork.org
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [fc00
Max-Forwards: 68
Contact: "alice" sip:alice@[fc00
User-Agent: Jitsi2.10.5550Linux
Content-Type: application/sdp
Content-Length: 910
X-RTP: mo
P-Asserted-Identity: sip:alice@ims.mnc001.mcc001.3gppnetwork.org
INVITE sip:bob@ims.mnc001.mcc001.3gppnetwork.org SIP/2.0
Route: sip:scscf.ims.mnc001.mcc001.3gppnetwork.org:5060
Record-Route: sip:mo@[FC00
Record-Route: sip:mo@[FC00
Call-ID: 0b23b2ee62c061ae9f3cc1569b7824b3@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: "alice" sip:alice@ims.mnc001.mcc001.3gppnetwork.org;tag=94b2833a
To: sip:bob@ims.mnc001.mcc001.3gppnetwork.org
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [fc00
Max-Forwards: 67
Contact: "alice" sip:alice@[fc00
User-Agent: Jitsi2.10.5550Linux
Content-Type: application/sdp
Content-Length: 910
X-RTP: mo
P-Asserted-Identity: sip:alice@ims.mnc001.mcc001.3gppnetwork.org
INVITE sip:bob@[fc00
Record-Route: sip:mt@[FC00
Route: sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org:5060;nat=yes;received=sip:FC00
Record-Route: sip:mo@[FC00
Record-Route: sip:mo@[FC00
Call-ID: 0b23b2ee62c061ae9f3cc1569b7824b3@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: "alice" sip:alice@ims.mnc001.mcc001.3gppnetwork.org;tag=94b2833a
To: sip:bob@ims.mnc001.mcc001.3gppnetwork.org
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [FC00
Via: SIP/2.0/UDP [fc00
Max-Forwards: 66
Contact: "alice" sip:alice@[fc00
User-Agent: Jitsi2.10.5550Linux
Content-Type: application/sdp
Content-Length: 910
X-RTP: mo
P-Asserted-Identity: sip:alice@ims.mnc001.mcc001.3gppnetwork.org
In the last invite message, there is sip:FC00
Any thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.