[reSIProcate] can't send proper contect header inSipMessage(anyrequest)

[Scott Godin]

That's normally how the contact header looks when the dum passes it down to
the stack for transmission.  The stack will populate the remainder of the
contact header depending on the transport selected.  Are you seeing this in
a wire trace (ie. Ethereal) or in the resip logs?  Are you sure this is the
message that is actually being sent on the wire?

-----Original Message-----
From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Patel
Parag
Sent: Tuesday, September 27, 2005 4:26 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] can't send proper contect header in SipMessage
(anyrequest)



i get wrong contact in Request SipMessages: example:

REGISTER sip:192.168.0.142;transport=UDP SIP/2.0
To: <sip:8001 at 192.168.0.142;transport=UDP>
From: <sip:8001 at 192.168.0.142;transport=UDP>;tag=b432ca41
Via: SIP/2.0/SCTP ;branch=z9hG4bK-d87543-b4418541e162d27d-1--d87543-;rport
Call-ID: dd0404184d782459 at UG9ja2V0X1BD
CSeq: 1 REGISTER
Contact: <sip:8001>
Expires: 70
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE
Content-Length: 0


i also got wrong contact in Request SipMessage during test with simple
registration test using following simple registration process

attechment: basicRegister.cxx