I forgot to mention that I saw this as well:
http://track.sipfoundry.org/browse/XX-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44640#action_44640

What puzzles me is that Bria Pro gets the hostname instead of the domain 
name for the Jabber-id via provisioning.
In the debug from XX-6879 it looks like SMC (Bria) uses the domain.
Can anyone explain why Bria does not work with u...@domain, but only works 
with u...@host?

I think my DNS records are OK:

the ones normally needed, th.internal.epo.org is the domain:

> _xmpp-client._tcp.conference.th.internal.epo.org
Server:  gdns01.internal.epo.org
Address:  10.0.10.11

_xmpp-client._tcp.conference.th.internal.epo.org        SRV service 
location:
          priority       = 1
          weight         = 0
          port           = 5222
          svr hostname   = gssipx02.internal.epo.org
> _xmpp-server._tcp.conference.th.internal.epo.org
Server:  gdns01.internal.epo.org
Address:  10.0.10.11

_xmpp-server._tcp.conference.th.internal.epo.org        SRV service 
location:
          priority       = 1
          weight         = 0
          port           = 5222
          svr hostname   = gssipx02.internal.epo.org

The ones added because Bria uses hostname instead of domain, so 
"conference.gssipx02.internal.epo.org" instead of 
"conference.th.internal.epo.org"
> _xmpp-server._tcp.conference.gssipx02.internal.epo.org
Server:  gdns01.internal.epo.org
Address:  10.0.10.11

_xmpp-server._tcp.conference.gssipx02.internal.epo.org  SRV service 
location:
          priority       = 1
          weight         = 0
          port           = 5222
          svr hostname   = gssipx02.internal.epo.org
> _xmpp-client._tcp.conference.gssipx02.internal.epo.org
Server:  gdns01.internal.epo.org
Address:  10.0.10.11

_xmpp-client._tcp.conference.gssipx02.internal.epo.org  SRV service 
location:
          priority       = 1
          weight         = 0
          port           = 5222
          svr hostname   = gssipx02.internal.epo.org
>


BTW: In the mean time I discovered that you can also dynamically create a 
conference in pidgin by selecting "Add Chat".



Best regards / Mit freundlichen Grüßen / Sincères salutations

Paul Scheepens
Administrator Network Engineering | Dir. 2.7.3.2
European Patent Office
Patentlaan 3-9 | 2288 EE Rijswijk | The Netherlands
Tel. +31 (0)70 340 3331
Mobile +31 (0)642724894
[email protected]
http://www.epo.org

----- Forwarded by Paul Scheepens/EPO on 28-04-2010 13:18 -----

Paul Scheepens/EPO wrote on 28-04-2010 12:09:27:

> From:
> 
> Paul Scheepens/EPO
> 
> To:
> 
> [email protected]
> 
> Date:
> 
> 28-04-2010 12:09
> 
> Subject:
> 
> XMPP works for Pidgin, not for Bria
> 
> I have been trying to get XMPP working for Bria Pro 2.5 because some
> users wanted a Chatroom functionality.
> I enabled the [Bundle.IM] role on the SipX server (4.2.0)
> I created a usergroup "GroupChat", enabled "IM account" and "Add 
> user group as IM group"
> for the group  and added 3 users that use Bria Pro. 
> 
> When restarting Bria we got a new contacts group "GroupChat" with 
> the users in there.
> When you right-click a contact Bria shows the "Start Group Chat..." 
> option to start a groupchat.
> When I select this option an invite is send to the server, but it is
> not received on the other client (Bria nor Pidgin).
> In the Bria debug of the inviter I see a 
> <error code='404' type='cancel'><remote-server-not-found 
> xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error>
> 
> See attached file "Bria-Invite.txt".
> 
> The SIP-domain is th.internal.epo.org.
> The XMPP server is gssipx02.internal.epo.org (primary sip server).
> 
> As the groupchat is send to "conference.gssipx02.internal.epo.org" 
> instead of "conference.th.internal.epo.org" (our SIP domain) I have 
> added an A record and SRV records
> but this did not help. 
> Do I need to set up a conference for this?
> Any other suggestions?
> 
> BTW: For info only: I got it working with Pidgin, but this works 
> completely different from Bria, with Pidgin you first search for 
> Chat Rooms, then join one and then you can invite users.
> I made a conference "Mine" and left it "public" so that it can be found.
> This works well, including inviting Bria users.
> I did have to remove the password of the conference otherwise Bria 
> can't accept the invite.
> In the Bria debug I got a 
> <error code='401' type='auth'><not-authorized 
> xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error>
> 
> See the second file "Bria-Pidgin.txt", first the Bria debug with the
> error, then the successfull join after I removed the password.
> 
> Best regards / Mit freundlichen Grüßen / Sincères salutations
> 
> Paul Scheepens
> [attachment "Bria-Invite.txt" deleted by Paul Scheepens/EPO] 
> [attachment "Bria-Pidgin.txt" deleted by Paul Scheepens/EPO] 
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to