Re: [Sipwitch-devel] sipw 100% cpu

[paul]

Dear Robert Dyck,

Yes, this mailing list is monitored, this is an open source project, not paid 
support for a commercial project where one gets turnarounds within twenty 
four(24) hours. Kindly bear that in mind when posting requests.

Now to your question, the instructions including examples are more than 
sufficient for one to get SIPWITCH 1.1.1 up and running out of the box! 
Provided you've installed all dependecies !

I will suggest the following:

1. compile, make and install sipwitch from source

2. Install all modules, not some. This is your first installation, you will 
troubleshoot later on which modules you need and which ones you don't !

3. Run in server mode

4. Load your own users in your sipwitch.conf file. Remember to specify the 
location of your sipwitch.conf file at start up.

5. Run sipwitch specify remember to set debug level = 9 . This will allow you 
to see all debug info as sipwitch runs.


Now

1. Your users created in sipwitch.conf should be able to register, if you've 
set your debug level to 9 you should see this in the console where you've 
started sipwitch in the foreground !

2. Once two clients have both registered they should be able to call one 
another.

3. Check your logs, there are several for SIPWITCH under /var/log/ (under 
debian linux). 

Once all this is done. You can now start playing around with other 
configuration options such as 'desktop configuration', 'adjusting concurrency 
values etc etc', 'removing certain modules' BECAUSE you've shown SIPWITCH works 
in your environment not with the setup you started with, that setup you can do 
once you know your way around SIPWITCH.


Sipwitch assumes local/private network configuration and does not yet support 
NAT traversal. I suppose(speculative) you can always get it to work in the wild 
with a stun server for your clients behind NAT.

Sipwitch user.
Sent from my BlackBerry® Paul M. Mathebula

-----Original Message-----
From: Robert Dyck <address@hidden>
Sender: address@hidden: Thu, 8 Sep 2011 14:48:20 
To: <address@hidden>
Subject: Re: [Sipwitch-devel] sipw 100% cpu

Bump
Does anyone monitor this list? Am I in the wrong place?

I am new to sipwitch but not SIP. I built sipwitch-1.1.1 and used your example 
configuration except for my local network. In /etc/sysconfig/sipwitch I enabled 
module subscriber and module forward and set security to desktop. When I start 
service sipwitch, sipw uses any available CPU cycles. Switchview appeared in 
the system tray. Clicking on it gives the response "No server connected". The 
sipwitch tool says the server is offline.

What am I missing?

Some comments about building sipwitch
The configure script does not check for an up to date ucommon. Fedora's version 
by the way is out of date.

I also think the configure script should check for moc-qt4 and uic-qt4 and if 
they are present use them instead of moc and uic.

Sipwitch is an interesting project and I wish it well.