The problem solved after deleting the callcontrol package from /usr/lib/python2.5/site-packages/ directory and re-installing the package.
Om. On Tue, Jul 6, 2010 at 3:48 PM, Om Bikram Thapa <[email protected]> wrote: > Hello, > > I have been running callcontrol 2.0.3 with opensips-1.5.1 which has > been running fine so far. Today after restarting callcontrol, the > callcontrol module is not starting and the startup script doesn't show > any error. However, syslog shows the error as: > > Jul 6 15:43:34 proxy call-control[3524]: [-] Log opened. > Jul 6 15:43:34 proxy call-control[3524]: [-] Starting SIP call-control 2.0.8 > Jul 6 15:43:34 proxy call-control[3524]: [-] Traceback (most recent call > last): > Jul 6 15:43:34 proxy call-control[3524]: [-] File > "/usr/bin/call-control", line 104, in <module> > Jul 6 15:43:34 proxy call-control[3524]: [-] from > callcontrol.controller import CallControlServer > Jul 6 15:43:34 proxy call-control[3524]: [-] File > "/usr/lib/python2.5/site-packages/callcontrol/controller.py", line 12, > in <module> > Jul 6 15:43:34 proxy call-control[3524]: [-] from > application.configuration import ConfigSection, ConfigSetting > Jul 6 15:43:34 proxy call-control[3524]: [-] ImportError: cannot > import name ConfigSetting > > I have made no changes in anything. What could be the issue? > > Thanks, > Om. > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
