Andrei Pelinescu-Onciul writes: > The most likely candidates are: > - blacklisted destination (due to some previous error). > You could check it with sercmd dst_blacklist.view or > dst_blacklist.debug.
i'll check with those commands when the hangup happens again. > - some local firewall rules on the OUTPUT chain i don't have control of the firewall at sr 3.1 end. i know there is one, but the port that sr is listening on is open. > Did you disable the tcp async mode, or you get this in async mode? i have not disabled async mode. in the second case when both ends claimed that tcp connection was in established state, i had to restart sr 3.0 sip proxy in order to make packets flow again. -- juha _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
