I am seeing the following message within the rls logs: sipxrls:"OsSSLServerSocket SSL_accept SSL handshake error:\n SSL error: 1 'error:00000001:lib(0):func(0):reason(1)'" sipxrls:"OsSSLServerSocket SSL_accept SSL handshake error:\n SSL error: 336027900 'error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol'" sipxrls:"SipPublishContentMgr::getContent no container found for key 'sip:~~rl~C~~~id~xmpprlsclient...
(as is relates to the RLS component) So I am wondering if someone can explain what the "unknown protocol" means in this instance. The certificate was created in the exact way it should have, by the system, one time at startup. I see presenceserver says disabled but shows "running" in sipxconfig and if I start manually via sipxproc it stays "running" (no change in sipxconfig). I then tried to disable TLS and that broke nat traversal rules and failed to start proxy, so that did not help. I tried deleting the tmp imdb.* files and restarting presence from sipxconfig but that did not help. The ownership of the files and sizes look accurate (they were recreated when I restarted presence manually). So this is SOLVED as far as the CPU level is concerned. I found a device that has not been reconfigured (a valcom paging gateway) that is essentially trying to register without an account, and the registrar logs show 50-100 per minute (attempts). I still think there is an SSL issue. Does anyone have any ideas on how to figure this out? On Mon, Nov 5, 2012 at 2:16 PM, Tony Graziano <[email protected]>wrote: > I am looking at a strange issue with a system which had a drive failure. > We replaced the drive and reloaded (did not restore) the system, then > updated it to the latest update. We see the proxy staying steady at 10% > CPU, with not active calls or transactions. It is a basic system with > trunking and 12 phones, there should not be such a load. > > I have sent the server its profiles. I have restarted the system. There is > no memory or swap memory issue. I have reviewed the configuration and all > of the speeddials and registrations. > > The first thing I noticed is that noone was able to place outbound calls > easily, then when I started looking into it I checked user speeddials, > presense and overall configuration and hardware functionality. I still see > no issues except that the sipXproxy is taking up "enormous" CPU time. There > are 12 phones and a total of 24 subscriptions. Does anyone else have an > install similar and can verify whether they are seeing this or not? > -- > ~~~~~~~~~~~~~~~~~~ > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > ~~~~~~~~~~~~~~~~~~ > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > ~~~~~~~~~~~~~~~~~~ > > Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab > 2013! > <http://sipxcolab2013.eventbrite.com/?discount=tony2013> > > -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013> -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
