Re: [reSIProcate-users] TCP connect failure - 503 response

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

As long as you are sending new SIP messages (ie: retrying the registration) the stack will attempt to re-connect.  There is no need to shutdown and restart the stack.  If this is not happening, please post a DEBUG or STACK level resip log of this occurring.

Scott

On Mon, Jun 24, 2013 at 7:00 AM, Nauman Sulaiman <nauman762-home@xxxxxxxxxxx> wrote:

Specifically when the connection is lost this code in TransportSelector.cxx throws an

exception, how should we recover from this

int ret = connect(tmp,&target.getSockaddr(), target.length());

      if (ret < 0)

      {

         int e = getErrno();

         Transport::error( e );

         InfoLog(<< "Unable to route to " << target << " : [" << e << "] " << strerror(e) );

         throw Transport::Exception("Can't find source address for Via", __FILE__,__LINE__);

      }

Thanks

---

From: Nauman Sulaiman <nauman762-home@xxxxxxxxxxx>
To: "resiprocate-users@xxxxxxxxxxxxxxx" <resiprocate-users@xxxxxxxxxxxxxxx>
Sent: Monday, 24 June 2013, 11:36
Subject: [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

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/