[Serusers] ser support IPv6 ?

Jiri Kuthan jiri at iptel.org
Mon Aug 25 13:21:34 CEST 2003


Hello,

is the ipv6 problem you reported on previously still around?

-jiri

At 01:46 PM 8/4/2003, Yoshiharu Maekawa (=?iso-2022-jp?B?GyRCQTBAbjJCPVUbKEI=?=) wrote:
>Hi,
>
>> On Aug 01, 2003 at 12:21, Yoshiharu Maekawa <maekawa at cd.jp.nec.com> wrote:
>> > Hi,
>> > 
>> > I have installed ser-0.8.11pre29-1.i386.rpm on Linux PC.
>> > I added IPv6 global address to the interface on Linux PC.
>> > Now, I just only started ser.
>> > 
>> > I cannot see IPv6 address and port with netstat command.(see bellow)
>> 
>> By default ser does not listen on any ipv6 address. You have to
>> explicitely specify the ipv6 addresses on which it will listen (either
>> add -l ipv6_address to the command line or listen= ipv6_address1
>> ipv6_address2  to the ser.cfg).
>
>I started "ser-0.8.1.pre29-1" with ipv6 command line (-l ipv6_address ).
>and send register message from ipv6 sip client.
>
>I received a following SIP error message from ser.
>
>I have two questions.
>
>(1)As for this error, is it fixed a bug already?
>
>(2)I want to create Red hat RPM of ser from cvs source code .
>
>> BTW: try the latest stable cvs version (ser 0.8.11 rc2), it contains
>> some ipv6 fixes.
>> 
>> Andrei
>
>
>Regards,
>maekawa
>
>==================================== ipv6 sip client => ser
>Internet Protocol Version 6
>    Version: 6
>    Traffic class: 0x00
>    Flowlabel: 0x00000
>    Payload length: 552
>    Next header: UDP (0x11)
>    Hop limit: 128
>    Source address: 2001:3e8:1240:1::1
>    Destination address: 2001:3e8:1240:1::8
>User Datagram Protocol, Src Port: 1030 (1030), Dst Port: 5060 (5060)
>    Source port: 1030 (1030)
>    Destination port: 5060 (5060)
>    Length: 552
>    Checksum: 0xc67d (correct)
>Session Initiation Protocol
>    Request line: REGISTER sip:ssfch29.ssf.abk.nec.co.jp SIP/2.0
>    Method: REGISTER
>    Message Header
>        Via: SIP/2.0/UDP [2001:3e8:1240:1::1]:13774
>        From: <sip:ymaekawa at ssfch29.ssf.abk.nec.co.jp>;tag=ad9691c0-8042-49bf-ba58-78d9183657b1
>        To: <sip:ymaekawa at ssfch29.ssf.abk.nec.co.jp>
>        Call-ID: 9a112d58-06f7-4fbf-b460-665d85c84811 at 10.41.133.231
>        CSeq: 1 REGISTER
>        Contact: <sip:[2001:3e8:1240:1::1]:13774>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK";q=0.5
>        User-Agent: Windows RTC/1.0
>        Expires: 1200
>        Event: registration
>        Allow-Events: presence
>        Content-Length: 0
>==================================== ipv6 sip client <= ser
>Internet Protocol Version 6
>    Version: 6
>    Traffic class: 0x00
>    Flowlabel: 0x00000
>    Payload length: 692
>    Next header: UDP (0x11)
>    Hop limit: 64
>    Source address: 2001:3e8:1240:1::8
>    Destination address: 2001:3e8:1240:1::1
>User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 13774 (13774)
>    Source port: 5060 (5060)
>    Destination port: 13774 (13774)
>    Length: 692
>    Checksum: 0x6a61 (correct)
>Session Initiation Protocol
>    Status line: SIP/2.0 500 I'm terribly sorry, server error occured (7/TM)
>    Status-Code: 500
>    Message Header
>        Via: SIP/2.0/UDP [2001:3e8:1240:1::1]:13774;received=[2001:3E8:1240:1:0:0:0:1]
>        From: <sip:ymaekawa at ssfch29.ssf.abk.nec.co.jp>;tag=ad9691c0-8042-49bf-ba58-78d9183657b1
>        To: <sip:ymaekawa at ssfch29.ssf.abk.nec.co.jp>;tag=e1201a00721ecf0105c9d54759cb26c7-b3fd
>        Call-ID: 9a112d58-06f7-4fbf-b460-665d85c84811 at 10.41.133.231
>        CSeq: 1 REGISTER
>        Server: Sip EXpress router (0.8.11pre29 (i386/linux))
>        Content-Length: 0
>        Warning: 392 2001:3e8:1240:1::8:5060 "Noisy feedback tells:  pid=5185 req_src_ip=2001:3E8:1240:1:0:0:0:1 req_src_port=1030 in_uri=sip:ssfch29.ssf.abk.nec.co.jp out_uri=sip:ssfch29.ssf.abk.nec.co.jp via_cnt==1"
>
> 
>
>_______________________________________________
>Serusers mailing list
>serusers at lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers

--
Jiri Kuthan            http://iptel.org/~jiri/ 




More information about the sr-users mailing list