Hi, I've been doing a little research for a few weeks, looking for an sip proxy, ip pbx, messaging server and the like. I came across to sipxecs, and jumped to it when I saw something like "can be operational in hours". Unfortunately, it's now 10th day since I first tried to install by compiling, and yet it will be operational in a stable way. I had given up compiling, and installed from rpms, still no result. I finally used iso image for installation, still I can't use it for production.
I noticed that actually the hard part wasn't the installation (even the compilation had completed without major problems), it's the configuration and troubleshooting. Oh, and the lack of enough documentation :(. Every document exists in the first look, but when you actually read them, you see it's only a little bit more than the heading :) By the way, a forum instead of the mailing lists may be more useful imho. Ok, enough complaining... Sipxecs still looks very promising, actually one of the most promising systems, if not the most at all. I had a few unsolved problems to BEGIN experimenting with sipxecs. When I try to import LDAP users from Active Directory, it says on the job status page: The name "<username>" is already being used by a user or service. <username> is the sAMAccountName of the user the same error message appears for every user in the directory, and it doesn't import anything. sAMAccountName is only available if you select securityPrincipal on the object classes page when setting up the LDAP Server, a golden information not readily accessible by the available documents, but from an old mail in the mailing list archives. Google'ing the "is already being used by a user or service", with quotation marks :), it gives a single result: http://track.sipfoundry.org/browse/XCF-1168 It seems to be a "fixed" issue in version 3.6.0 . I'm currently using 3.10.2, and I wonder if there may be an Active Directory side of the problem. Because I was able to import all of the users two days ago, and then I saw it doesn't sync, deleted all of the users, dropped the database, retried, no solution. Then I installed the sipx from the ISO image, tried on the newly installed system, the same thing occurs. And speaking of Active Directory, I am yet to find some documentation on how to import the passwords from the Active Directory (the document on the site says it changes depending on how u configure AD, and not much more, the problem here is I didn't configure AD :) ). I actually don't know if I have to import the passwords into sipxecs side, or is there another mechanism? One last problem yet I couldn't solve: When I click Diagnostics->Services, it says "Broken Pipe" . I guess this is somehow related to sipxproc -l, which gives the following error when entered on the command line: /usr/lib/ruby/1.8/net/http.rb:586:in `connect': tlsv1 alert decrypt error (OpenSSL::SSL::SSLError) from /usr/lib/ruby/1.8/net/http.rb:586:in `connect' from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' from /usr/lib/ruby/1.8/net/http.rb:542:in `start' from /usr/lib/ruby/1.8/net/http.rb:1035:in `request' from /usr/lib/ruby/1.8/net/http.rb:992:in `post2' from /usr/lib/ruby/1.8/xmlrpc/client.rb:535:in `do_rpc' from /usr/lib/ruby/1.8/xmlrpc/client.rb:420:in `call2' from /usr/lib/ruby/1.8/xmlrpc/client.rb:410:in `call' from /usr/bin/sipxproc:144 This, again I guess, may be something with our certificates, which are signed by our own CA. I put the CA cert into /etc/sipxpbx/ssl/cacert and it built the /etc/sipxpbx/ssl/.authorities.jks file, but I don't know. The hostname of the server (padme) is different from the hostname it gives the service with (sip), perhaps it's the cause, but I couldn't find a way to make everything use the "sip" hostname. In some logs, the default hostname still appears. Anyway, any help, orientation to some documentation or suggestion will be greatly appreaciated. Thanks in advance... Cya, Tufan _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
