< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[reSIProcate-users] TCP connect failure - 503 response


Hi, 

Using resip 1.8.6 if a TCP connection dies then the stack generates a 503 to REGISTER
request. However there seems no way to recover from this ie a new connection is not 
made on REGISTER retry. 

All I can see is that the application is informed of a 503 so it all it can do is shutdown the
stack and restart, this is not ideal. Is there a better  way to manage this? There does not seem to
be a way of removing the TCP transport and adding again

Thanks