Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
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) --- --- 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: Stopping factory 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 > > ___ > 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
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 > > ___ > 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
El Martes, 13 de Octubre de 2009, Sanjeev BA escribió: > I use Pytho-twisted 8.2.0-1ubuntu1on Ubuntu 8.04.3 Have you checked if your issue is the same as the report?: http://openxcap.org/ticket/121 Thanks. -- Iñaki Baz Castillo ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
2009/10/15 Sanjeev BA :
> "/usr/lib/python2.5/site-packages/twisted/web2/auth/digest.py", line 257, in
> verifyOpaque
> error: key = opaqueParts[1].decode('base64')
> error: File "/usr/lib/python2.5/encodings/base64_codec.py", line 43, in
> base64_decode
> error: output = base64.decodestring(input)
> error: File "base64.py", line 321, in decodestring
> error: return binascii.a2b_base64(s)
> error: binascii.Error: Incorrect padding
Interesting error. I suggest you to open a ticket with it in OpenXCAP tracker.
--
Iñaki Baz Castillo
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
Tried to get around this by adding IP address individually to trusted_peer list. Seems to do the trick. A config setting like 10.0.0.0/24 does not seem to work. Kindly check this ticket. http://openxcap.org/ticket/90 Regards Sanjeev -Original Message- From: Sanjeev BA [mailto:as290...@samsung.com] Sent: Thursday, October 15, 2009 2:56 PM To: 'OpenSIPS users mailling list' Subject: RE: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration Has anyonbe been able to make OpenXCAP work with OpenSIPS using digest authentication?I am seeing an error in twisted/web2 python script, but I do not know how to fix it. I cannot proceed any further due to the error detailed below. Any help regarding this issue would be highly appreciated. Thanks in advance, Regards Sanjeev -Original Message- From: Sanjeev BA [mailto:as290...@samsung.com] Sent: Thursday, October 15, 2009 8:50 AM To: 'OpenSIPS users mailling list' Subject: RE: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration Yes. Here's the sequence. After changing to digest, I can observe a 500 Internal Server Error in the OpenXCAP server. Logs are provided below. Client Request T 2009/10/15 08:42:04.997913 10.254.140.240:43525 -> 10.89.10.235:80 [AP] GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1. Host: 10.89.10.235:80. Content-length: 0. Connection: keep-alive. . 401 Response ## T 2009/10/15 08:42:05.106696 10.89.10.235:80 -> 10.254.140.240:43525 [AP] HTTP/1.1 401 Unauthorized. Date: Wed, 14 Oct 2009 23:42:05 GMT. Content-Length: 141. Content-Type: text/html. WWW-Authenticate: digest nonce="62026475982401434245613", opaque="23870f726b78fb5d872eced92ca0c1dd-NjI0NDQ0MDI2NDc1OTgyNDAxNDM0MjQ1NjE zLDEwLjI1NC4xNDAuMjQwLDEyNTU1NjM3MjU=", realm="imsdemo.com", algorithm=MD5, qop="auth". Server: OpenXCAP/1.1.2.. Date: Wed, 14 Oct 2009 12:17:24 GMT. Content-Length: 141. Content-Type: text/html. WWW-Authenticate: basic realm="imsdemo.com". Server: OpenXCAP/1.1.2. . UnauthorizedUnauthorized You are not authorized to access this resource. Second GET from client # T 2009/10/15 08:42:05.378179 10.254.140.240:43527 -> 10.89.10.235:80 [AP] GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1. Host: 10.89.10.235:80. Authorization: Digest username="tester", realm="imsdemo.com", qop=auth, nonce="62026475982401434245613", algorithm=MD5, uri="/xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40i msdemo.com/directory.xml", response="", cnonce="poc123test", opaque="23870f726b78fb5d872eced92ca0c1dd-NjI0NDQ0MDI2NDc1OTgyNDAxNDM0MjQ1NjE zLDEwLjI1NC4xNDAuMjQwLDEyNTU1NjM.", nc=0001. Content-length: 0. Connection: keep-alive. 500 Internal Server Error ## T 2009/10/15 08:42:05.387184 10.89.10.235:80 -> 10.254.140.240:43527 [AP] HTTP/1.1 500 Internal Server Error. Date: Wed, 14 Oct 2009 23:42:05 GMT. Content-Length: 96. Content-Type: text/plain. Server: OpenXCAP/1.1.2. . An error occurred while processing the request. More information is available in the server log. XCAP Server Error Log. 10.254.140.240 'GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1' 401 0 141 - - REQUEST headers: Host: 10.89.10.235:80 NjI0NDQ0MDI2NDc1OTgyNDAxNDM0MjQ1NjEzLDEwLjI1NC4xNDAuMjQwLDEyNTU1NjM error: 10.254.140.240 'GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1' 500 0 96 - - error: REQUEST headers: error: Host: 10.89.10.235:80 error: Authorization: Digest username="tester", realm="imsdemo.com", qop=auth, nonce="62026475982401434245613", algorithm=MD5, uri="/xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40i msdemo.com/directory.xml", response="", cnonce="poc123test", opaque="23870f726b78fb5d872eced92ca0c1dd-NjI0NDQ0MDI2NDc1OTgyNDAxNDM0MjQ1NjE zLDEwLjI1NC4xNDAuMjQwLDEyNTU1NjM", nc=0001 error: RESPONSE headers: error: Content-Type: text/plain error: RESPONSE: Content-Type: text/plain error: An error occurred while processing the request. More information is available in the server log. error: TRACEBACK (most recent call last): error:File "/usr/lib/python2.5/site-packages/twisted/web2/server.py", line 268, in error: d.addCallback(lambda res, req: res.renderHTTP(req), self) error:File "/usr/lib/python2.5/site-packages/xcap/authentication.py", line 284, in renderHTTP error: d = self.authenticate(request) error:File "/usr/lib/python2.5/site-packages/xcap/authentication.py", line 212, in authenticate error: (request,), None) error:File "/usr/lib/python2.5/site-packages/t
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
Has anyonbe been able to make OpenXCAP work with OpenSIPS using digest authentication?I am seeing an error in twisted/web2 python script, but I do not know how to fix it. I cannot proceed any further due to the error detailed below. Any help regarding this issue would be highly appreciated. Thanks in advance, Regards Sanjeev -Original Message- From: Sanjeev BA [mailto:as290...@samsung.com] Sent: Thursday, October 15, 2009 8:50 AM To: 'OpenSIPS users mailling list' Subject: RE: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration Yes. Here's the sequence. After changing to digest, I can observe a 500 Internal Server Error in the OpenXCAP server. Logs are provided below. Client Request T 2009/10/15 08:42:04.997913 10.254.140.240:43525 -> 10.89.10.235:80 [AP] GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1. Host: 10.89.10.235:80. Content-length: 0. Connection: keep-alive. . 401 Response ## T 2009/10/15 08:42:05.106696 10.89.10.235:80 -> 10.254.140.240:43525 [AP] HTTP/1.1 401 Unauthorized. Date: Wed, 14 Oct 2009 23:42:05 GMT. Content-Length: 141. Content-Type: text/html. WWW-Authenticate: digest nonce="62026475982401434245613", opaque="23870f726b78fb5d872eced92ca0c1dd-NjI0NDQ0MDI2NDc1OTgyNDAxNDM0MjQ1NjE zLDEwLjI1NC4xNDAuMjQwLDEyNTU1NjM3MjU=", realm="imsdemo.com", algorithm=MD5, qop="auth". Server: OpenXCAP/1.1.2.. Date: Wed, 14 Oct 2009 12:17:24 GMT. Content-Length: 141. Content-Type: text/html. WWW-Authenticate: basic realm="imsdemo.com". Server: OpenXCAP/1.1.2. . UnauthorizedUnauthorized You are not authorized to access this resource. Second GET from client # T 2009/10/15 08:42:05.378179 10.254.140.240:43527 -> 10.89.10.235:80 [AP] GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1. Host: 10.89.10.235:80. Authorization: Digest username="tester", realm="imsdemo.com", qop=auth, nonce="62026475982401434245613", algorithm=MD5, uri="/xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40i msdemo.com/directory.xml", response="", cnonce="poc123test", opaque="23870f726b78fb5d872eced92ca0c1dd-NjI0NDQ0MDI2NDc1OTgyNDAxNDM0MjQ1NjE zLDEwLjI1NC4xNDAuMjQwLDEyNTU1NjM.", nc=0001. Content-length: 0. Connection: keep-alive. 500 Internal Server Error ## T 2009/10/15 08:42:05.387184 10.89.10.235:80 -> 10.254.140.240:43527 [AP] HTTP/1.1 500 Internal Server Error. Date: Wed, 14 Oct 2009 23:42:05 GMT. Content-Length: 96. Content-Type: text/plain. Server: OpenXCAP/1.1.2. . An error occurred while processing the request. More information is available in the server log. XCAP Server Error Log. 10.254.140.240 'GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1' 401 0 141 - - REQUEST headers: Host: 10.89.10.235:80 NjI0NDQ0MDI2NDc1OTgyNDAxNDM0MjQ1NjEzLDEwLjI1NC4xNDAuMjQwLDEyNTU1NjM error: 10.254.140.240 'GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1' 500 0 96 - - error: REQUEST headers: error: Host: 10.89.10.235:80 error: Authorization: Digest username="tester", realm="imsdemo.com", qop=auth, nonce="62026475982401434245613", algorithm=MD5, uri="/xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40i msdemo.com/directory.xml", response="", cnonce="poc123test", opaque="23870f726b78fb5d872eced92ca0c1dd-NjI0NDQ0MDI2NDc1OTgyNDAxNDM0MjQ1NjE zLDEwLjI1NC4xNDAuMjQwLDEyNTU1NjM", nc=0001 error: RESPONSE headers: error: Content-Type: text/plain error: RESPONSE: Content-Type: text/plain error: An error occurred while processing the request. More information is available in the server log. error: TRACEBACK (most recent call last): error:File "/usr/lib/python2.5/site-packages/twisted/web2/server.py", line 268, in error: d.addCallback(lambda res, req: res.renderHTTP(req), self) error:File "/usr/lib/python2.5/site-packages/xcap/authentication.py", line 284, in renderHTTP error: d = self.authenticate(request) error:File "/usr/lib/python2.5/site-packages/xcap/authentication.py", line 212, in authenticate error: (request,), None) error:File "/usr/lib/python2.5/site-packages/twisted/internet/defer.py", line 186, in addCallbacks error: self._runCallbacks() error: --- --- error:File "/usr/lib/python2.5/site-packages/twisted/internet/defer.py", line 328, in _runCallbacks error: self.result = callback(self.result, *args, **kw) error:File "/usr/lib/python2.5/site-packages/xcap/authentication.py", line 217, in _trustedPeerLoginFailed error: return HTTPAuthResource.authenticate(se
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
st.py", line 257, in
verifyOpaque
error: key = opaqueParts[1].decode('base64')
error:File "/usr/lib/python2.5/encodings/base64_codec.py", line 43, in
base64_decode
error: output = base64.decodestring(input)
error:File "base64.py", line 321, in decodestring
error: return binascii.a2b_base64(s)
error: binascii.Error: Incorrect padding
-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Inaki Baz Castillo
Sent: Wednesday, October 14, 2009 9:41 PM
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
El Miércoles, 14 de Octubre de 2009, Sanjeev BA escribió:
> T 2009/10/14 21:17:24.833815 10.254.140.202:34878 -> 10.89.10.235:80 [AP]
> GET
>
/xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsde
> m o.com/directory.xml HTTP/1.1.
> Host: 10.89.10.235:80.
> Content-length: 0.
> Connection: keep-alive.
> .
>
> ##
> T 2009/10/14 21:17:24.835431 10.89.10.235:80 -> 10.254.140.202:34878 [AP]
> HTTP/1.1 401 Unauthorized.
> Date: Wed, 14 Oct 2009 12:17:24 GMT.
> Content-Length: 141.
> Content-Type: text/html.
> WWW-Authenticate: basic realm="imsdemo.com".
> Server: OpenXCAP/1.1.2.
Doesn't the client send a new GET request containing credentials after that
401???
Note however that, theorically, XCAP doesn't allow Basic authentication, but
just Digest. And some clients (as EyeBeam) just implements Digest.
If you client doesn't re-send the request with credentials upon receipt of
401
then:
- Your XCAP client doesn't support Basic.
- You XCAP client doesn't like the 401 for any other reason.
--
Iñaki Baz Castillo
___
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
El Miércoles, 14 de Octubre de 2009, Sanjeev BA escribió: > T 2009/10/14 21:17:24.833815 10.254.140.202:34878 -> 10.89.10.235:80 [AP] > GET > /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsde > m o.com/directory.xml HTTP/1.1. > Host: 10.89.10.235:80. > Content-length: 0. > Connection: keep-alive. > . > > ## > T 2009/10/14 21:17:24.835431 10.89.10.235:80 -> 10.254.140.202:34878 [AP] > HTTP/1.1 401 Unauthorized. > Date: Wed, 14 Oct 2009 12:17:24 GMT. > Content-Length: 141. > Content-Type: text/html. > WWW-Authenticate: basic realm="imsdemo.com". > Server: OpenXCAP/1.1.2. Doesn't the client send a new GET request containing credentials after that 401??? Note however that, theorically, XCAP doesn't allow Basic authentication, but just Digest. And some clients (as EyeBeam) just implements Digest. If you client doesn't re-send the request with credentials upon receipt of 401 then: - Your XCAP client doesn't support Basic. - You XCAP client doesn't like the 401 for any other reason. -- Iñaki Baz Castillo ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
T 2009/10/14 21:17:24.833815 10.254.140.202:34878 -> 10.89.10.235:80 [AP] GET /xcap-root/org.openmobilealliance.xcap-directory/users/sip%3Atester%40imsdem o.com/directory.xml HTTP/1.1. Host: 10.89.10.235:80. Content-length: 0. Connection: keep-alive. . ## T 2009/10/14 21:17:24.835431 10.89.10.235:80 -> 10.254.140.202:34878 [AP] HTTP/1.1 401 Unauthorized. Date: Wed, 14 Oct 2009 12:17:24 GMT. Content-Length: 141. Content-Type: text/html. WWW-Authenticate: basic realm="imsdemo.com". Server: OpenXCAP/1.1.2. -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Inaki Baz Castillo Sent: Wednesday, October 14, 2009 8:56 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration El Miércoles, 14 de Octubre de 2009, Sanjeev BA escribió: > 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. Get a capture of the HTTP traffic *in the server*: ngrep -d eth0 -W byline -T -i -t "" port OPENXCAP_LISTEN_PORT and paste it here. -- Iñaki Baz Castillo ___ 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
El Miércoles, 14 de Octubre de 2009, Sanjeev BA escribió: > 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. Get a capture of the HTTP traffic *in the server*: ngrep -d eth0 -W byline -T -i -t "" port OPENXCAP_LISTEN_PORT and paste it here. -- Iñaki Baz Castillo ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
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 ___ 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
Hi, With XCAP auth scheme set to basic I do observe the same issue as mentioned in the ticket. I tried changing the XCAP authentication scheme from basic to digest. After this change, xdm client posted a second PUT with Auth details, but this time the server returned 500 Internal server error. Internally, I can see an OpenXCAP failure in base64.decodestring(input) Error base64.py, line 321 ... return bin2ascii.a2b_base64(s) incorrect padding. Not sure how to resolve this. Regards, Sanjeev -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Inaki Baz Castillo Sent: Tuesday, October 13, 2009 4:39 PM To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration El Martes, 13 de Octubre de 2009, Sanjeev BA escribió: > I use Pytho-twisted 8.2.0-1ubuntu1on Ubuntu 8.04.3 Have you checked if your issue is the same as the report?: http://openxcap.org/ticket/121 Thanks. -- Iñaki Baz Castillo ___ 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
I use Pytho-twisted 8.2.0-1ubuntu1on Ubuntu 8.04.3 Regards, Sanjeev -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Inaki Baz Castillo Sent: Tuesday, October 13, 2009 12:04 AM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration El Lunes, 12 de Octubre de 2009, Adrian Georgescu escribio: > We will address this issue. Thanks. Just to add more info, I use Debian Leeny 64 bits so Twisted version is 8.1.0: ii python-twisted-bin 8.1.0-4 ii python-twisted-conch1:8.1.0-1 ii python-twisted-core 8.1.0-4 ii python-twisted-names8.1.0-1 ii python-twisted-web 8.1.0-1 ii python-twisted-web2 8.1.0-1 -- Inaki Baz Castillo ___ 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
Thanks for the clarification. 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 9:14 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration El Lunes, 12 de Octubre de 2009, Sanjeev BA escribió: > 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? Not sure what you mean. OpenSIPS acts, in this case, as presence server while OpenXCAP acts as a XCAP server. OpenSIPS presence_xml module reads the XCAP documents from database. Other approach is using xcap_client module so OpenSIPS will fetch the document fomr the XCAP server using HTTP/XCAP protocol. About XDM, note that OpenSIPS and OpenXCAP don't implement OMA's stuf. Instead they implement IETF "pure" SIMPLE/SCAP protocol (which is a specification that doesn't exist at all). -- Iñaki Baz Castillo ___ 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
El Lunes, 12 de Octubre de 2009, Adrian Georgescu escribió: > We will address this issue. Thanks. Just to add more info, I use Debian Leeny 64 bits so Twisted version is 8.1.0: ii python-twisted-bin 8.1.0-4 ii python-twisted-conch1:8.1.0-1 ii python-twisted-core 8.1.0-4 ii python-twisted-names8.1.0-1 ii python-twisted-web 8.1.0-1 ii python-twisted-web2 8.1.0-1 -- Iñaki Baz Castillo ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
We will address this issue. -- Adrian On Oct 12, 2009, at 5:59 AM, Iñaki Baz Castillo wrote: > El Lunes, 12 de Octubre de 2009, Stanisław Pitucha escribió: >> 2009/10/12 Iñaki Baz Castillo : >>> The 401 sent by OpenXCAP is wrong as it has a malformed >>> "WWW-Authenticate" header: >>> http://openxcap.org/ticket/121 >>> >>> 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. >> >> They seem to be using the Twisted framework to generate packets. If >> there's a problem it will be on their side. Try upgrading twisted to >> the latest version - it could help. > > I use Debian Lenny with updated packages. I expect such a bug > doesn't exist in > a HTTP framework :( > > >> (or even raising the ticket with >> them instead, but that might need a lot of explanation) > > I hope AG could, at least, comment something about it. > > > -- > Iñaki Baz Castillo > > ___ > 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
El Lunes, 12 de Octubre de 2009, Stanisław Pitucha escribió: > 2009/10/12 Iñaki Baz Castillo : > > The 401 sent by OpenXCAP is wrong as it has a malformed > > "WWW-Authenticate" header: > > http://openxcap.org/ticket/121 > > > > 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. > > They seem to be using the Twisted framework to generate packets. If > there's a problem it will be on their side. Try upgrading twisted to > the latest version - it could help. I use Debian Lenny with updated packages. I expect such a bug doesn't exist in a HTTP framework :( > (or even raising the ticket with > them instead, but that might need a lot of explanation) I hope AG could, at least, comment something about it. -- Iñaki Baz Castillo ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
2009/10/12 Iñaki Baz Castillo : > The 401 sent by OpenXCAP is wrong as it has a malformed "WWW-Authenticate" > header: > http://openxcap.org/ticket/121 > > 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. They seem to be using the Twisted framework to generate packets. If there's a problem it will be on their side. Try upgrading twisted to the latest version - it could help. (or even raising the ticket with them instead, but that might need a lot of explanation) -- KTHXBYE, Stanisław Pitucha, Gradwell Voip Engineer ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS - OpenXCAP integration
El Lunes, 12 de Octubre de 2009, Sanjeev BA escribió: > 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? Not sure what you mean. OpenSIPS acts, in this case, as presence server while OpenXCAP acts as a XCAP server. OpenSIPS presence_xml module reads the XCAP documents from database. Other approach is using xcap_client module so OpenSIPS will fetch the document fomr the XCAP server using HTTP/XCAP protocol. About XDM, note that OpenSIPS and OpenXCAP don't implement OMA's stuf. Instead they implement IETF "pure" SIMPLE/SCAP protocol (which is a specification that doesn't exist at all). -- Iñaki Baz Castillo ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
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 ___ 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
El Domingo, 11 de Octubre de 2009, Sanjeev BA escribió: > 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. -- Iñaki Baz Castillo ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] OpenSIPS - OpenXCAP integration
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. Subscriber table has the entry for the user. OpenXCAP uses OpenSIPS backend with basic authentication. OpenSIPS operates with mi_proxy module. Content Type = application/resource-list+xml The XCAP request is as follows. friends Are there any changes required in openxcap/opensips setup to support this PUT request? Please advice. Regards, Sanjeev ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
