Mike,

I have this problem too, not sure at all why, but Spark give almost no
reason other than it cannot authenticate, pidgin, empathy, and other XMPP
clients work as long as I tell them to ignore certificate errors.

Kyle

On Mon, Oct 10, 2011 at 11:38 PM, m...@grounded.net <m...@grounded.net>wrote:

> I forgot to mention. The spark client connects just fine to a stand alone
> openfire I installed for testing.
> It is only the sipx server I cannot connect to.
>
>
> On Mon, 10 Oct 2011 21:43:00 -0500, m...@grounded.net wrote:
> > What's the trick to getting spark to connect to the sipx integrated
> > openfire server? :)
> > One can use the IM user ID as name/password which doesn't work.
> > Not sure if one can use the sipx account but that doesn't work either.
> >
> > All I find on the net is one question from someone saying they used to be
> > able to connect to sipx's openfire server but no longer can using client
> > 2.60/2.6.2. I have also tried the IP, the host/domain and of course, SRV
> > meaning domain only.
> >
> > Mike
> >
> >
> > On Mon, 10 Oct 2011 07:22:48 -0600, Aaron Pursell wrote:
> >> I have SipX integrated Openfire working with Video and Audio with Spark.
> >> But not on Tablets because the flash clients on said tablets do not
> >> support
> >> the Camera hook, they can view video/audio but not send. So we're
> >> basically
> >> waiting for Adobe to hook this up or another client comes through.
> >>
> >>
> >> Aaron Pursell, Sr.
> >> Network Systems Administrator
> >>
> >> Easter Seals-Goodwill Northern Rocky Mountain, Inc.
> >> 4400 Central Ave
> >> Great Falls, Montana  59405
> >>
> >> (406) 771-3721
> >> aar...@esgw.org
> >>>>> "m...@grounded.net" <m...@grounded.net> 10/7/2011 7:22 PM >>>
> >> On Fri, 7 Oct 2011 15:40:15 -0400, Tony Graziano wrote:
> >>> Then change the subject (i.e., start a new thread) to reflect the
> >>> different
> >>> avenues you are pursuing. You just admitted the "many different
> >>> directions"
> >>>
> >> Tony, you're the only one who has decided that this cannot be done. The
> >> thread has received input and ideas. There have been others who
> >> contributed
> >> thoughts trying to come up with ideas and solutions to problems.
> >> When things get too personal in threads though, that's pretty much the
> end
> >> of the thread.
> >>
> >> It started relevant and I can't say that it isn't yet because there may
> be
> >> more input.
> >>
> >>> to accomplish what you are trying to do, most of which actually do
> >>> not/may
> >>> not even have anything to do with sipx. If you want input from sipx
> >>> users,
> >>> it should be relevant. It's hard for it to be relevant to sift through
> >>> now
> >>> 35 posts and noone is probably all that clear in what you are trying to
> >>> do.
> >>>
> >> I have said several times what I am trying to accomplish and it was
> >> initially a sipx or at least sipx users question
> >> It is simply now becoming a bit more obvious that the solution isn't
> >> related to sipx. That doesn't mean nobody wants to hear about it because
> >> it
> >> may be a relevant idea to others as well. In fact, it seems to be
> >> something
> >> that a lot of people are trying to figure out
> >>
> >> Anyways...
> >>
> >>
> >> _______________________________________________
> >> sipx-users mailing list
> >> sipx-users@list.sipfoundry.org
> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> > _______________________________________________
> > sipx-users mailing list
> > sipx-users@list.sipfoundry.org
> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
Kyle Haefner, M.S.
Communication Systems Programmer
Colorado State University
Fort Collins, CO
Phone: 970-491-1012
Email:  kyle.haef...@colostate.edu
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to