[reSIProcate] using only TCP transport

[Scott Godin]

Sounds like routing trouble of the ACK by the other endpoint - DUM is
not seeing the ack.  An ethereal trace would probably help find out
what's happening.

 

________________________________

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Amit
Rastogi
Sent: Wednesday, November 02, 2005 11:53 PM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] using only TCP transport

 

Hello,

 

I am trying to use only the tcp transport but running into issues for
sending responses. i am specifying transport parameter as tcp in the
contact /to/from addresses. 

 

i am using the suggestions in the msg
http://list.sipfoundry.org/archive/resiprocate-devel/msg03681.html

 

when i create a session between 2 clients A and B. B can answer but
keeps waiting for ack. following is the stack trace

 

INFO | 20051102-205339.355 | DEBUG | RESIP:DUM | 260 |
DialogUsageManager.cxx:830 | Got: DumTimeout::WaitForAck INVITE: 9
UAS_WaitingToHangup ADDR=<sip:1001 at 65.114.141.66
;transport=tcp>;tag=0d261322
PEER=<sip:vani at 65.114.141.66;transport=tcp>;tag=b205c903: duration=32000
seq=2
INFO | 20051102-205339.355 | DEBUG | RESIP:DUM | 260 |
DialogUsageManager.cxx :942 | Timeout Message
INFO | 20051102-205339.355 | DEBUG | RESIP:DUM | 260 |
InviteSession.cxx:1685 | Sending SipReq:  BYE B at 10.31.11.155:5060
tid=1c68984035745844 cseq=BYE contact=1001 at 10.31.11.160:5060 / 2
from(tu)
INFO | 20051102-205339.355 | DEBUG | RESIP:DUM | 260 |
InviteSession.cxx:1434 | Transition UAS_WaitingToHangup ->
InviteSession::Terminated
 

 

Any ideas.

 

thanks,

Amit

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20051103/75a69bc3/attachment.htm>