[reSIProcate] CSeq not increasing.

[Brian D'Souza]

Hello,

I am just trying out your DUM project and really like what I see – in
terms of flexibility and ease-of-use. However, I have noticed a few
small issues , I have included a trace of one of my calls in this email.
To save you time sifting through it – the problem I am seeing is that
the C-Sequence number is NOT being incremented after authorization.
According to RFC3261 (Section 22.2)


When a UAC resubmits a request with its credentials after receiving a
401 (Unauthorized) or 407 (Proxy Authentication Required) response,
it MUST increment the CSeq header field value as it would normally
when sending an updated request.


The reason that the Cseq is not incremented is that the dispatch method in the 
DialogSet class does not increment it after it does authentication. I am not
sure where would be an appropriate place to increase the number – 
you could increase it the ClientAuthenticationManager handle method as well.

Any feedback would be useful,

Thanks,

Brian.

==================================================================

TRACE OF DUM CALL 


Frame 1 (672 bytes on wire, 672 bytes captured)
Linux cooked capture
Internet Protocol, Src Addr: 192.168.0.30 (192.168.0.30), Dst Addr:
65.39.205.114 (65.39.205.114)
User Datagram Protocol, Src Port: 15060 (15060), Dst Port: 5082 (5082)
Session Initiation Protocol
Request line: INVITE sip:77998 at fwd.pulver.com SIP/2.0
Method: INVITE
Message Header
To: <sip:77998 at fwd.pulver.com>
From: <sip:52017 at fwd.pulver.com>;tag=dd60bc1e
Via: SIP/2.0/UDP
192.168.0.30:15060;branch=z9hG4bK-c87542-132608321-1--c87542-;rport
Call-ID: fd5eb85783fe5970
CSeq: 1 INVITE
Contact: <sip:52017 at 192.168.0.30:15060>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 266
Session Description Protocol

Frame 2 (561 bytes on wire, 561 bytes captured)
Linux cooked capture
Internet Protocol, Src Addr: 65.39.205.114 (65.39.205.114), Dst Addr:
192.168.0.30 (192.168.0.30)
User Datagram Protocol, Src Port: 5082 (5082), Dst Port: 15060 (15060)
Session Initiation Protocol
Status line: SIP/2.0 407 Proxy Authentication Required
Status-Code: 407
Message Header
To: <sip:77998 at fwd.pulver.com>;tag=ec5154884c15db89cef5049aa4f06328.773d
From: <sip:52017 at fwd.pulver.com>;tag=dd60bc1e
Via: SIP/2.0/UDP
192.168.0.30:15060;branch=z9hG4bK-c87542-132608321-1--c87542-;rport
Call-ID: fd5eb85783fe5970
CSeq: 1 INVITE
Proxy-Authenticate: Digest realm="fwd.pulver.com",
nonce="40ec6c5547bf878657b4d2076864ab39365208aa"
Server: Free World Dialup (0.8.11rc3 (i386/linux))
Record-Route: <sip:PPC420378 at 65.39.205.114:5082>
Content-Length: 0

Frame 3 (350 bytes on wire, 350 bytes captured)
Linux cooked capture
Internet Protocol, Src Addr: 192.168.0.30 (192.168.0.30), Dst Addr:
65.39.205.114 (65.39.205.114)
User Datagram Protocol, Src Port: 15060 (15060), Dst Port: 5082 (5082)
Session Initiation Protocol
Request line: ACK sip:77998 at fwd.pulver.com SIP/2.0
Method: ACK
Message Header
To: <sip:77998 at fwd.pulver.com>;tag=ec5154884c15db89cef5049aa4f06328.773d
From: <sip:52017 at fwd.pulver.com>;tag=dd60bc1e
Via: SIP/2.0/UDP
192.168.0.30:15060;branch=z9hG4bK-c87542-132608321-1--c87542-;rport
Call-ID: fd5eb85783fe5970
CSeq: 1 ACK
Content-Length: 0

Frame 4 (877 bytes on wire, 877 bytes captured)
Linux cooked capture
Internet Protocol, Src Addr: 192.168.0.30 (192.168.0.30), Dst Addr:
65.39.205.114 (65.39.205.114)
User Datagram Protocol, Src Port: 15060 (15060), Dst Port: 5082 (5082)
Session Initiation Protocol
Request line: INVITE sip:77998 at fwd.pulver.com SIP/2.0
Method: INVITE
Message Header
To: <sip:77998 at fwd.pulver.com>
From: <sip:52017 at fwd.pulver.com>;tag=dd60bc1e
Via: SIP/2.0/UDP
192.168.0.30:15060;branch=z9hG4bK-c87542-231856629-1--c87542-;rport
Call-ID: fd5eb85783fe5970
CSeq: 1 INVITE
Contact: <sip:52017 at 192.168.0.30:15060>
Max-Forwards: 70
Content-Type: application/sdp
Proxy-Authorization: Digest
username=52017,realm="fwd.pulver.com",nonce="40ec6c5547bf878657b4d2076864ab39365208aa",uri="sip:77998 at fwd.pulver.com",response="c9a606f0d9ea8431280dff1347d3b1fd",algorithm=MD5
Content-Length: 266
Session Description Protocol