Re: [sr-dev] [kamailio/kamailio] IPv6 parse_uri error (#1136)

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. 1. When PCSCF received the Sip Invite from caller, the Sip headers look fine: 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:1234:3:1:0:0:0:0]:5060;branch=z9hG4bK-393032-567b1c47371a83386f685807100ab5bd Max-Forwards: 70 Contact: "alice" <sip:alice@[fc00:1234:3:1:0:0:0:0]:5060;transport=udp;registering_acc=ims_mnc001_mcc001_3gppnetwork_org> User-Agent: Jitsi2.10.5550Linux Content-Type: application/sdp Content-Length: 910 2. Then PCSCF sent it to SCSCF: 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:1234:1:0:0:0:0:45];lr=on;ftag=94b2833a;nat=yes;did=991.9181> 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:1234:1:0:0:0:0:45];branch=z9hG4bK0d1b.9247221bd3cd63299ff9b3e1486a94e0.0 Via: SIP/2.0/UDP [fc00:1234:3:1:0:0:0:0]:5060;rport=5060;branch=z9hG4bK-393032-567b1c47371a83386f685807100ab5bd Max-Forwards: 69 Contact: "alice" <sip:alice@[fc00:1234:3:1:0:0:0:0]:5060;transport=udp;registering_acc=ims_mnc001_mcc001_3gppnetwork_org> 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 3. The SCSCF sent to ICSCF: INVITE sip:bob@ims.mnc001.mcc001.3gppnetwork.org SIP/2.0 Record-Route: <sip:mo@[FC00:1234:1:0:0:0:0:47];lr=on;ftag=94b2833a;did=991.b322> Record-Route: <sip:mo@[FC00:1234:1:0:0:0:0:45];lr=on;ftag=94b2833a;nat=yes;did=991.9181> 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:1234:1:0:0:0:0:47];branch=z9hG4bK0d1b.3b5263a0a9b70cdde23243c3423be371.0 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:45];branch=z9hG4bK0d1b.9247221bd3cd63299ff9b3e1486a94e0.0 Via: SIP/2.0/UDP [fc00:1234:3:1:0:0:0:0]:5060;rport=5060;branch=z9hG4bK-393032-567b1c47371a83386f685807100ab5bd Max-Forwards: 68 Contact: "alice" <sip:alice@[fc00:1234:3:1:0:0:0:0]:5060;transport=udp;registering_acc=ims_mnc001_mcc001_3gppnetwork_org> 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> 4. Then ICSCF sent it to SCSCF: 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:1234:1:0:0:0:0:47];lr=on;ftag=94b2833a;did=991.b322> Record-Route: <sip:mo@[FC00:1234:1:0:0:0:0:45];lr=on;ftag=94b2833a;nat=yes;did=991.9181> 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:1234:1:0:0:0:0:46];branch=z9hG4bK0d1b.acefb88ca4d295d2bd315467f0670d7f.1 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:47];branch=z9hG4bK0d1b.3b5263a0a9b70cdde23243c3423be371.0 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:45];branch=z9hG4bK0d1b.9247221bd3cd63299ff9b3e1486a94e0.0 Via: SIP/2.0/UDP [fc00:1234:3:1:0:0:0:0]:5060;rport=5060;branch=z9hG4bK-393032-567b1c47371a83386f685807100ab5bd Max-Forwards: 67 Contact: "alice" <sip:alice@[fc00:1234:3:1:0:0:0:0]:5060;transport=udp;registering_acc=ims_mnc001_mcc001_3gppnetwork_org> 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> 5. Then SCSCF sent it to the PCSCF of the callee: INVITE sip:bob@[fc00:1234:3:2:0:0:0:0]:5060;transport=udp;registering_acc=ims_mnc001_mcc001_3gppnetwork_org SIP/2.0 Record-Route: <sip:mt@[FC00:1234:1:0:0:0:0:47];lr=on;ftag=94b2833a;did=991.b322> Route: <sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org:5060;nat=yes;received=sip:FC00:1234:3:2:0:0:0:0:5060;lr> Record-Route: <sip:mo@[FC00:1234:1:0:0:0:0:47];lr=on;ftag=94b2833a;did=991.b322> Record-Route: <sip:mo@[FC00:1234:1:0:0:0:0:45];lr=on;ftag=94b2833a;nat=yes;did=991.9181> 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:1234:1:0:0:0:0:47];branch=z9hG4bK0d1b.da418b33c49aee4296db5cf6393c2c36.0 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:46];branch=z9hG4bK0d1b.acefb88ca4d295d2bd315467f0670d7f.1 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:47];branch=z9hG4bK0d1b.3b5263a0a9b70cdde23243c3423be371.0 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:45];branch=z9hG4bK0d1b.9247221bd3cd63299ff9b3e1486a94e0.0 Via: SIP/2.0/UDP [fc00:1234:3:1:0:0:0:0]:5060;rport=5060;branch=z9hG4bK-393032-567b1c47371a83386f685807100ab5bd Max-Forwards: 66 Contact: "alice" <sip:alice@[fc00:1234:3:1:0:0:0:0]:5060;transport=udp;registering_acc=ims_mnc001_mcc001_3gppnetwork_org> 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:1234:3:2:0:0:0:0:5060 which doesn't have [ ] and probably cause this issue. Any thoughts? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1136#issuecomment-306533802