Hi Stefan,
Bria uses the hostname to connect to the XMPP domain, it only partially
uses SRV records.
It means that to get some sort of XMPP support in Bria you need an XMPP
server with hostname=XMPP-domain (=SIP-domain).
I installed a dedicated XMPP server for that purpose (third server in a
HA-setup).
What's more important is that XMPP support in Bria is still not OK in 3.1,
also the 3.2 Beta still had issues.
3.2 final is announced and should appear within weeks, maybe it's a bit
better.....
Still, XMPP support is not yet OK, most annoying is the XMPP session loss.
With 3.1 this happens because Bria resets the session. With 3.2 beta
Counterpath "fixed" something and now the session is FIN-ed by the server.
Net-effect is that you lose the XMPP session and thus presence info (and
others lose your presence as well).
BTW: Why are you testing with 2.4.3, this is quite old and not the final
2.x (that was 2.5 if I am not mistaken).
Paul
Stefan Sabolowitsch wrote on 10-04-2011 17:30:47:
>
> Hi all
> If i make a XMPP login with Bria 2.4.3, i get this error message.
>
> Account temporarily unavailable
>
> but with Pidgin works.
> I found in the debugfile on bria.
> "XMPP/Gloox (XML In): <failure xmlns='urn:ietf:params:xml:ns:xmpp-
> sasl'><not-authorized/></failure> " | sua::XmppAccessImpl::handleLog
> "XMPP/Gloox (client): SASL authentication failed! " |
> sua::XmppAccessImpl::handleLog
>
>
> Does it concern the same problem here as already once described
> (bria XMPP bug)?
> http://forum.sipfoundry.org/index.php?
> t=msg&th=13497&goto=47629&S=72d46ecfc7e15d1ee87c3b7d667b0825#msg_47629
>
>
> Thanks for each assistance.
>
> Stefan_______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
