[sip-comm] re - [sip-comm] invite fails with IPv6 but succede with IPv4


#1

Mime-Version: 1.0
Content-Type: text/plain; format=flowed

Looking at the trace below..

In the VIA, the proxy is identifying itself with "172.16.0.60:5070", but the
invite originated at the proxy IPv6 address identified by
"received=fe80:0:0:0:a00:20ff:fef9:cbf6"

The recieved address (either from the header or the internal packet address,
I havent looked code in detail yet) is being substituted for the proxy
address in the VIA, but without the necessary IPv6 brackets
i.e.
    172.16.0.60:5070
after the straight substitution becomes:
   fe80:0:0:0:a00:20ff:fef9:cbf6:5070

This seems to be causing the stack to blow throwing the exception

<message
from="172.16.0.60:5070"
to="[fe80::a00:20ff:fefd:b886]:8080"
time="1074176394747"
isSender="false"
transactionId="z9hg4bkac10003c13ce000000fa19e27d7f1"
callId="3b2d9c25d5ab8b770d2fa9ebb2ec3e9f@[fe80::a00:20ff:fefd:b886]"
firstLine="INVITE sip:[fe80::a00:20ff:fefd:b886]:8080;transport=udp SIP/2.0"
debugLine="0"

<![CDATA[

INVITE sip:[fe80::a00:20ff:fefd:b886]:8080;transport=udp SIP/2.0
Call-ID: 3b2d9c25d5ab8b770d2fa9ebb2ec3e9f@[fe80::a00:20ff:fefd:b886]
CSeq: 1 INVITE
Via: SIP/2.0/UDP
172.16.0.60:5070;branch=z9hG4bKAC10003C13CE000000FA19E27D7F1;received=fe80:0:0:0:a00:20ff:fef9:cbf6,SIP/2.0/UDP
[fe80::a00:20ff:fefd:b886]:8070;branch=z9hG4bK523fbf78d637683d02f29e6c37101b8b
Max-Forwards: 69
Contact: <sip:[fe80::a00:20ff:fefd:b886]:8070;transport=udp>
Content-Type: application/sdp
Content-Length: 167

v=0
o=root 0 0 IN IP4 172.16.0.70
s=-
c=IN IP4 172.16.0.70
t=0 0
m=video 22222 RTP/AVP 20 26 31
a=recvonly
m=audio 22224 RTP/AVP 0 3 4 5 6 8 15 18
a=recvonly

]]>
</message>

···

Date: Thu, 15 Jan 2004 17:09:59 +0000
From: <sip:steve1@anon.net:8070;transport=udp>;tag=9578500
To: <sip:steve2@anon.net:8080>

_________________________________________________________________
Tired of 56k? Get a FREE BT Broadband connection
http://www.msn.co.uk/specials/btbroadband

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#2

Hello Steve,

Good catch! Thanks a lot for spotting the exact problem and reporting.
I'll fix that in the stack code as soon as possible.
Unfortunately I have absolutely no time right now and could probably
get to it no earlier than February. Would you like to give it a try?

If yes then you can find stack sources at

jain-sip.dev.java.net

Otherwise you'll see the fix in early February.

Cheers
Emil

Date: Thu, 15 Jan 2004 17:09:59 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed

Looking at the trace below..

In the VIA, the proxy is identifying itself with "172.16.0.60:5070", but the
invite originated at the proxy IPv6 address identified by
"received=fe80:0:0:0:a00:20ff:fef9:cbf6"

The recieved address (either from the header or the internal packet address,
I havent looked code in detail yet) is being substituted for the proxy
address in the VIA, but without the necessary IPv6 brackets
i.e.
    172.16.0.60:5070
after the straight substitution becomes:
   fe80:0:0:0:a00:20ff:fef9:cbf6:5070

This seems to be causing the stack to blow throwing the exception

<message
from="172.16.0.60:5070"
to="[fe80::a00:20ff:fefd:b886]:8080"
time="1074176394747"
isSender="false"
transactionId="z9hg4bkac10003c13ce000000fa19e27d7f1"
callId="3b2d9c25d5ab8b770d2fa9ebb2ec3e9f@[fe80::a00:20ff:fefd:b886]"
firstLine="INVITE
sip:[fe80::a00:20ff:fefd:b886]:8080;transport=udp SIP/2.0"
debugLine="0"

<![CDATA[

INVITE sip:[fe80::a00:20ff:fefd:b886]:8080;transport=udp SIP/2.0
Call-ID: 3b2d9c25d5ab8b770d2fa9ebb2ec3e9f@[fe80::a00:20ff:fefd:b886]
CSeq: 1 INVITE
From: <sip:steve1@anon.net:8070;transport=udp>;tag=9578500
To: <sip:steve2@anon.net:8080>
Via: SIP/2.0/UDP
172.16.0.60:5070;branch=z9hG4bKAC10003C13CE000000FA19E27D7F1;received=fe80:0:0:0:a00:20ff:fef9:cbf6,SIP/2.0/UDP
[fe80::a00:20ff:fefd:b886]:8070;branch=z9hG4bK523fbf78d637683d02f29e6c37101b8b
Max-Forwards: 69
Contact: <sip:[fe80::a00:20ff:fefd:b886]:8070;transport=udp>
Content-Type: application/sdp
Content-Length: 167

v=0
o=root 0 0 IN IP4 172.16.0.70
s=-
c=IN IP4 172.16.0.70
t=0 0
m=video 22222 RTP/AVP 20 26 31
a=recvonly
m=audio 22224 RTP/AVP 0 3 4 5 6 8 15 18
a=recvonly

]]>>

</message>

_________________________________________________________________
Tired of 56k? Get a FREE BT Broadband connection
http://www.msn.co.uk/specials/btbroadband

---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail:
users-help@sip-communicator.dev.java.net

Cheers
Emil

http://www.emcho.com

···

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net