[OpenSIPS-Users] XCAP_backend_issue

Fri Apr 3 17:44:51 CEST 2009

Hi Larson,

Thanks for reply.
As you said, I commented (enable_publish_xcapdiff=yes). Now Server is
running. But giving the following warning.
**********************************************************************************************************************************************
Starting OpenXCAP 1.0.7
* warning: XCAP Root URI rejected: 'http://192.168.1.130/xcap-root\nbackend
= OpenSIPS' (looks like 'http://192.168.1.130/xcap-root')*
Supported Root URIs: http://192.168.1.130/xcap-root
xcap.server.HTTPFactory starting on 9222
**********************************************************************************************************************************************
I enabled backend=OpenSIPS.
When I try to test the functionality of OpenXCAP with ./test.py, it is
saying as follows.

*Please specify XCAP root with --xcap-root. You can also put the default
root in /root/.sipclient/config.ini.*

However, I put xcap-root at /root/.sipclient/config.ini as specified below,
before itself.

*[Account_Jp]
sip_address=Jp at dev.ongobiz.com
password=jp123
xcap_root = http://192.168.1.130:9222/xcap-root

*What the issue might me?

Thanks
JayaPrakash

On Fri, Apr 3, 2009 at 8:44 PM, <duane.larson at gmail.com> wrote:

> Jaya,
>
> I believe I ran into the same issue. it is because you have
> (enable_publish_xcapdiff = yes) enabled in your openxcap config.
> Comment that out and see if Openxcap starts. I don't know why it causes
> that. I want to enable it, but it gives me the same error.
>
> On Apr 3, 2009 8:21am, JayaPrakash <jp.manchu at gmail.com> wrote:
> > Hi All,
> > I have installed Opensips 1.5 in Debian 5.
> > OpenXCAP 1.0.7, soap-simple-proxy 1.0.5 and opensips-mi-proxy 1.0.2 are
> installed and configured.
> >
> > OpenXCAP's backend is set to opensips as described below.
> >
> >
> >
> ****************************************************************************************************************
>
> > ; The backend to be used for storage and authentication. Current
> supported
> > ; values are Database and OpenSER. OpenSER backend inherits all the
> settings
> >
> >
> > ; from the Database backend but performs extra actions related to the
> > ; integration with OpenSER for which it read the settings from [OpenSER]
> > ; section
> >  backend = OpenSIPS.
> >
> ****************************************************************************************************************
>
> >
> >
> >
> >
> > When OpenXCAP is try to start, it has given the following fatal error,
> saying there is no module named opensips. Opensips didn't start.
> >
> **********************************************************backend=OpenSIPS*********************************************************
>
> >
> >
> >  Log opened.
> >  debian openxcap[22480]: Starting OpenXCAP 1.0.7
> >  debian openxcap[22480]: fatal error: Cannot load 'opensips' backend
> module: No module named opensips
> >
> >
> > To correct this I changed the backend name to OpenSER. Then It has given
> the following errors.
> >
> >
> >
> *********************************************************backend=OpenSER************************************************************
>
> >  Log opened.
> > Apr  3 17:04:09 debian openxcap[22429]: Starting OpenXCAP 1.0.7
> > Apr  3 17:04:09 debian openxcap[22429]: Supported Root URIs:
> http://192.168.1.130/xcap-root
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error: Traceback (most recent
> call last):
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File
> "/usr/bin/openxcap", line 55, in
> > Apr  3 17:04:09 debian openxcap[22429]: error:     from xcap.server
> import XCAPServer
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File
> "/usr/lib/python2.5/site-packages/xcap/server.py", line 17, in
> > Apr  3 17:04:09 debian openxcap[22429]: error:     from xcap import
> authentication
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File
> "/usr/lib/python2.5/site-packages/xcap/authentication.py", line 22, in
> > Apr  3 17:04:09 debian openxcap[22429]: error:     from xcap.appusage
> import getApplicationForURI, namespaces
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File
> "/usr/lib/python2.5/site-packages/xcap/appusage/__init__.py", line 514, in
> > Apr  3 17:04:09 debian openxcap[22429]: error:     theStorage =
> ServerConfig.backend.Storage()
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File
> "/usr/lib/python2.5/site-packages/application/python/util.py", line 35, in
> __call__
> > Apr  3 17:04:09 debian openxcap[22429]: error:     return
> cls._instance_creator(*args, **kw)
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File "", line 1, in
> __init__
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File
> "/usr/lib/python2.5/site-packages/application/python/util.py", line 29, in
> instance_creator
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error:     cls._instances[key] =
> super(Singleton, cls).__call__(*args, **kwargs)
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File
> "/usr/lib/python2.5/site-packages/xcap/interfaces/backend/openser.py", line
> 56, in __init__
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error:     self.notifier =
> Notifier(root_uris[0], ManagementInterface().publish_xcapdiff)
> > Apr  3 17:04:09 debian openxcap[22429]: error:   File
> "/usr/lib/python2.5/site-packages/application/python/util.py", line 35, in
> __call__
> >
> >
> > Apr  3 17:04:09 debian openxcap[22429]: error:     return
> cls._instance_creator(*args, **kw)
> > Apr  3 17:04:09 debian openxcap[22429]: error: TypeError: __init__()
> takes exactly 2 arguments (1 given)
> >
> > I had issues while running Soap-simple-proxy too..
> >
> >
> >
> *******************************************************************************************************************************************8
>
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: Log opened.
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: Starting Soap SIMPLE
> Proxy web service 1.0.5
> >
> >
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: error: Traceback (most
> recent call last):
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: error:   File
> "/usr/bin/soap-simple-proxy", line 56, in
> >
> >
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: error:     from
> ssp.soap.engine import SOAPServer
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: error:   File
> "/usr/lib/python2.5/site-packages/ssp/soap/engine.py", line 6, in
> >
> >
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: error:     from ssp.soap
> import tweaks
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: error:   File
> "/usr/lib/python2.5/site-packages/ssp/soap/tweaks.py", line 5, in
> >
> >
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: error:     from
> SOAPpy.Config import Config
> > Apr  3 17:40:31 debian soap-simple-proxy[22701]: error: ImportError: No
> module named SOAPpy.Config
> >
> > Will you please suggest me how to correct these.
> >
> >
> >
> > Thanks
> > JayaPrakash
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090403/cda73578/attachment.htm 