I will try and do that later today. I think i tried to disable HTTPS when I first started testing with the Snom phone, but I believe the Snom phone always tries to use HTTPS. If you notice in the URL path that the Snom sends to OpenXCAP it automatically assumes https://servername then it will attach the port that you provide in the Snom xcap port setting. So then you see https://servername:443 <https://servername/>. I am worried that if I set the Snom XCAP port to be 80 then the url will be https://servername:80
We shall see. Adrian Georgescu, I do realize that the URI that OpenXCAP is seeing is repeated https://xcap.ae.comhttps://xcap.ae.com:443<https://xcap.ae.comhttps//xcap.ae.com:443> But when I look at the wireshark capture that is not the URI that Snom is sending. I will do some more testing, but I was hoping that someone else out there had a snom phone that could do some testing to confirm the same issue. On Wed, May 26, 2010 at 2:07 AM, Saúl Ibarra Corretgé [via OpenSIPS (Open SIP Server)] <[email protected]<ml-node%[email protected]> > wrote: > Hi, > > On 26/5/10 5:36 AM, osiris123d wrote: > > > > > I just did a wireshark capture of a snom 8.2.29 phone sending a XCAP > HTTPS > > request to OpenXCAP and I think OpenXCAP is somehow mutating the resource > > > path. > > > > > > The phone sends the correct path and all > > 253 22:09:18.629127 192.168.0.7 173.203.87.134 HTTP GET > > > https://xcap.ae.com:443/xcap-r...@.../resource-lists/users/sip:9xx2xx2...@.../index<https://xcap.ae.com/[email protected]/resource-lists/users/sip:[email protected]/index> > > > HTTP/1.1 > > > > But OpenXCAP replies with an error > > 254 22:09:18.685811 173.203.87.134 192.168.0.7 HTTP HTTP/1.1 404 Not > Found > > (text/plain) > > > > > > Here is what the OpenXCAP access.log says (You will notice that the first > > > two logs are the snom phone and after that is a successful access log of > a > > Counterpath Bria client) > > > > Could you disable SSL and make a ngrep capture of the HTTP traffic? The > fact that it worked with Bria but gives that error with Snom is > surprising, I could tell you more by looking at a trace. > > > Regards, > > -- > Saúl Ibarra Corretgé > AG Projects > > _______________________________________________ > Users mailing list > [hidden email] <http://user/SendEmail.jtp?type=node&node=5102169&i=0> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ------------------------------ > View message @ > http://opensips-open-sip-server.1449251.n2.nabble.com/OpenXCAP-and-Presence-with-SNOM-version-8-2-29-tp5080886p5102169.html > To unsubscribe from Re: OpenXCAP and Presence with SNOM version 8.2.29, click > here<http://opensips-open-sip-server.1449251.n2.nabble.com/subscriptions/Unsubscribe.jtp?code=ZHVhbmUubGFyc29uQGdtYWlsLmNvbXw1MTAxNjcxfDE0ODIwNjY1Mzk=>. > > > -- -- *--*--*--*--*--* Duane *--*--*--*--*--* -- -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenXCAP-and-Presence-with-SNOM-version-8-2-29-tp5080886p5103644.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
