Are you using the latest code? I know i have corrected this after you transferred the TLS work.

On Saturday, 11 December, 2010 05:41 AM, Arman Güngör wrote:
Hi,

sipXproxy opens too many sockets (on port 5061) to itself, it does not use existing ones. After some time, it ran out of resource.

netstat -tanp | grep 5061
tcp 0 0 192.168.0.100:5061 <http://192.168.0.100:5061> 0.0.0.0:* LISTEN 11193/sipXproxy tcp 0 0 192.168.0.100:5061 <http://192.168.0.100:5061> 192.168.0.100:48150 <http://192.168.0.100:48150> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:5061 <http://192.168.0.100:5061> 192.168.0.100:48025 <http://192.168.0.100:48025> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:48157 <http://192.168.0.100:48157> 192.168.0.100:5061 <http://192.168.0.100:5061> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:48127 <http://192.168.0.100:48127> 192.168.0.100:5061 <http://192.168.0.100:5061> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:48049 <http://192.168.0.100:48049> 192.168.0.100:5061 <http://192.168.0.100:5061> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:5061 <http://192.168.0.100:5061> 192.168.0.100:48046 <http://192.168.0.100:48046> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:5061 <http://192.168.0.100:5061> 192.168.0.100:48095 <http://192.168.0.100:48095> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:48015 <http://192.168.0.100:48015> 192.168.0.100:5061 <http://192.168.0.100:5061> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:48027 <http://192.168.0.100:48027> 192.168.0.100:5061 <http://192.168.0.100:5061> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:48044 <http://192.168.0.100:48044> 192.168.0.100:5061 <http://192.168.0.100:5061> ESTABLISHED 11193/sipXproxy tcp 0 0 192.168.0.100:48017 <http://192.168.0.100:48017> 192.168.0.100:5061 <http://192.168.0.100:5061> ESTABLISHED 11193/sipXproxy
..........
..........
..........

netstat -tanp | grep 5061 -c
264

There are 264 connections and it continues increasing.




Probably related with this error in sipXproxy.log :

"2010-12-10T21:32:00.064894Z":19201:SIP:DEBUG:arman.ucap.com:SipClientTcp-32:B5672B70:SipXProxy:"SipClient[SipClientTls-46]::isAcceptableForDestination matches 192.168.0.100:5061 <http://192.168.0.100:5061> but is not trusted" "2010-12-10T21:32:00.064912Z":19202:SIP:DEBUG:arman.ucap.com:SipClientTcp-32:B5672B70:SipXProxy:"SipClient[SipClientTls-50]::isAcceptableForDestination matches 192.168.0.100:5061 <http://192.168.0.100:5061> but is not trusted" "2010-12-10T21:32:00.064931Z":19203:SIP:DEBUG:arman.ucap.com:SipClientTcp-32:B5672B70:SipXProxy:"SipClient[SipClientTls-62]::isAcceptableForDestination matches 192.168.0.100:5061 <http://192.168.0.100:5061> but is not trusted" "2010-12-10T21:32:00.064945Z":19204:SIP:DEBUG:arman.ucap.com:SipClientTcp-32:B5672B70:SipXProxy:"SipClient[SipClientTls-65]::isAcceptableForDestination matches 192.168.0.100:5061 <http://192.168.0.100:5061> but is not trusted" "2010-12-10T21:32:00.064964Z":19205:SIP:DEBUG:arman.ucap.com:SipClientTcp-32:B5672B70:SipXProxy:"SipClient[SipClientTls-74]::isAcceptableForDestination matches 192.168.0.100:5061 <http://192.168.0.100:5061> but is not trusted" "2010-12-10T21:32:00.064978Z":19206:SIP:DEBUG:arman.ucap.com:SipClientTcp-32:B5672B70:SipXProxy:"SipClient[SipClientTls-77]::isAcceptableForDestination matches 192.168.0.100:5061 <http://192.168.0.100:5061> but is not trusted" "2010-12-10T21:32:00.064996Z":19207:SIP:DEBUG:arman.ucap.com:SipClientTcp-32:B5672B70:SipXProxy:"SipClient[SipClientTls-87]::isAcceptableForDestination matches 192.168.0.100:5061 <http://192.168.0.100:5061> but is not trusted" "2010-12-10T21:32:00.065010Z":19208:SIP:DEBUG:arman.ucap.com:SipClientTcp-32:B5672B70:SipXProxy:"SipClient[SipClientTls-89]::isAcceptableForDestination matches 192.168.0.100:5061 <http://192.168.0.100:5061> but is not trusted"

Regards,

Arman


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to