Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration

2009-10-17 Thread Adrian Georgescu
For this 401 problem, can you provide an example of the document your  
try to PUT and let us know the XCAP client you use so that we can  
reproduce your problem.

--
Adrian


On Oct 14, 2009, at 4:11 AM, Sanjeev BA wrote:

 Even with basic authentication, OpenXCAP returns 401 - UnAuthorized  
 response for a XCAP GET request.

 And I have 10.0.0.0/24 in my trusted peer list of openxcap config.

 Not sure what is the issue here. Please help.

 Regard,s
 sanjeev

 -Original Message-
 From: Sanjeev BA [mailto:as290...@samsung.com]
 Sent: Monday, October 12, 2009 8:59 PM
 To: 'OpenSIPS users mailling list'
 Subject: RE: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration

 Thanks for the quick reply.

 I would like to know if there is a way to get rid of OpenXCAP and  
 let OpenSIPS perform the role of XDM server as well.
 Is this possible? Are there any XDMS modules for OpenSIPS?

 Regards,
 Sanjeev

 -Original Message-
 From: users-boun...@lists.opensips.org 
 [mailto:users-boun...@lists.opensips.org 
 ] On Behalf Of Inaki Baz Castillo
 Sent: Monday, October 12, 2009 7:24 PM
 To: OpenSIPS users mailling list
 Subject: Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration

 El Domingo, 11 de Octubre de 2009, Sanjeev BA escribio:
 Hi,

 I have successfully been able to test opensips with openxcap. XCAP
 documents are modified and subscribe/notify/watcher procedures are  
 fine
 with third party SIP clients. I am in the process of testing my  
 presence
 user agent in this setup. While trying to add a new contact, I get  
 a 401
 unauthorized response.

 The 401 sent by OpenXCAP is wrong as it has a malformed WWW- 
 Authenticate
 header:
  http://openxcap.org/ticket/121

 Perhaps it works with some devices/softphones ignoring the invalid  
 \n
 character in opaque field. However a HTTP strict client will fail  
 (as
 EyeBeam does).

 Anyhow it seems that nobody cares this bug (no response, comment or  
 bug
 confirmation in 3 months). I tryed to find it but I haven't good  
 Python
 skills.

 As a dirty workaround you can use Basic authentication. However note  
 that some
 clients (as EyeBeam) don't support Basic authentication.

 Regards.

 -- 
 Inaki Baz Castillo i...@aliax.net

 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration

2009-10-17 Thread Sanjeev BA
Hi,
I was able to get around this issue by giving the complete IP address.
Please refer to OpenXCAP Ticket #90: subnet in trusted_peers does not work

The issue I am currently facing is as follows.
OpenXCAP receives a PUT request to add a new contact and shows an error as
below.

error: Unhandled error in Deferred:
Traceback (most recent call last):
  File /usr/lib/python2.5/site-packages/twisted/protocols/basic.py, line
239, in dataReceived
return self.rawDataReceived(data)
  File /usr/lib/python2.5/site-packages/twisted/web/http.py, line 467, in
rawDataReceived
self.handleResponseEnd()
  File /usr/lib/python2.5/site-packages/twisted/web/http.py, line 430, in
handleResponseEnd
self.handleResponse(b)
  File /usr/lib/python2.5/site-packages/twisted/web/xmlrpc.py, line 279,
in handleResponse
self.factory.parseResponse(contents)
--- exception caught here ---
  File /usr/lib/python2.5/site-packages/twisted/web/xmlrpc.py, line 307,
in parseResponse
response = xmlrpclib.loads(contents)[0][0]
  File /usr/lib/python2.5/xmlrpclib.py, line 1132, in loads
return u.close(), u.getmethodname()
  File /usr/lib/python2.5/xmlrpclib.py, line 787, in close
raise Fault(**self._stack[0])
xmlrpclib.Fault: Fault -506: 'Requested command (pua_publish) is not
available!'
Stopping factory twisted.web.xmlrpc._QueryFactory instance at 0x891f70c

Kindly let me know how to address this.

Regards,
Sanjeev



-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Adrian Georgescu
Sent: Saturday, October 17, 2009 3:56 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration

For this 401 problem, can you provide an example of the document your  
try to PUT and let us know the XCAP client you use so that we can  
reproduce your problem.

--
Adrian


On Oct 14, 2009, at 4:11 AM, Sanjeev BA wrote:

 Even with basic authentication, OpenXCAP returns 401 - UnAuthorized  
 response for a XCAP GET request.

 And I have 10.0.0.0/24 in my trusted peer list of openxcap config.

 Not sure what is the issue here. Please help.

 Regard,s
 sanjeev

 -Original Message-
 From: Sanjeev BA [mailto:as290...@samsung.com]
 Sent: Monday, October 12, 2009 8:59 PM
 To: 'OpenSIPS users mailling list'
 Subject: RE: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration

 Thanks for the quick reply.

 I would like to know if there is a way to get rid of OpenXCAP and  
 let OpenSIPS perform the role of XDM server as well.
 Is this possible? Are there any XDMS modules for OpenSIPS?

 Regards,
 Sanjeev

 -Original Message-
 From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org 
 ] On Behalf Of Inaki Baz Castillo
 Sent: Monday, October 12, 2009 7:24 PM
 To: OpenSIPS users mailling list
 Subject: Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration

 El Domingo, 11 de Octubre de 2009, Sanjeev BA escribio:
 Hi,

 I have successfully been able to test opensips with openxcap. XCAP
 documents are modified and subscribe/notify/watcher procedures are  
 fine
 with third party SIP clients. I am in the process of testing my  
 presence
 user agent in this setup. While trying to add a new contact, I get  
 a 401
 unauthorized response.

 The 401 sent by OpenXCAP is wrong as it has a malformed WWW- 
 Authenticate
 header:
  http://openxcap.org/ticket/121

 Perhaps it works with some devices/softphones ignoring the invalid  
 \n
 character in opaque field. However a HTTP strict client will fail  
 (as
 EyeBeam does).

 Anyhow it seems that nobody cares this bug (no response, comment or  
 bug
 confirmation in 3 months). I tryed to find it but I haven't good  
 Python
 skills.

 As a dirty workaround you can use Basic authentication. However note  
 that some
 clients (as EyeBeam) don't support Basic authentication.

 Regards.

 -- 
 Inaki Baz Castillo i...@aliax.net

 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users