I would refrain from making the domain and host the same. On Sep 9, 2011 10:26 AM, <[email protected]> wrote: > Hi Cyril, > > You really should bang Counterpath on their heads, they are not doing what
> they should be doing. > If I use XMPP on Bria I lose the XMPP session 5 to 10 times a day, so it's > not useable anyhow. > Some people have less issues, but that's probably because they only added > 2 or 3 XMPP contacts. > > But on the XMPP case, here is a note that I send to them a long time ago > (december 2010): > Hi, > > On request of Sylvain I report this problem with XMPP. > > When using XMPP in Bria we seem to be seeing a strange behavior. > As most XMPP traffic is encrypted I don't know what exactly goes wrong. > > In my opinion it should be possible to have an XMPP domain (SRV record) > that is not equal to a Host name (A-record). > > In the attached trace xmppEQsip2.pcap you can see what happens if the xmpp > domain field in Bria actually has a domain name configured (that is the > same as the sip domain). > -first an SRV lookup of the domain is performed, returning an A record > - the A record is resolved > - a session is set up to the correct address > - some, partly encrypted, xmpp traffic flows > - session is ended by the client > > In the second attached trace xmppEQhost2.pcap you can see what happens if > the xmpp domain field in Bria equals the hostname of the XMPP server (so > xmpp domain == FQDN of the host). > -first an SRV lookup of the "domain" is performed, because the "domain" is > actually an A record "no such name" is returned > - the A record is resolved > - a session is set up to the correct address > - some, partly encrypted, xmpp traffic flows > - all works fine > > Drawback of the second solution is that I can't choose the hostname of my > XMPP server, it has to be the same as the XMPP domain. > Also it is not standards compliant I think. Other XMPP clients have no > problem with the firt setup. > > Best regards / Mit freundlichen Grüßen / Sincères salutations > > Paul Scheepens > > As I have said before, if Bria is not getting their act together then they > are in real trouble. > Since they came out with 3.0 it really did not move a lot. > > We use it for decent HD video conferencing > [email protected] wrote on 09-09-2011 15:54:40: > >> From: >> >> cyril constantin <[email protected]> >> >> To: >> >> Discussion list for users of sipXecs software > <[email protected]> >> >> Date: >> >> 09-09-2011 15:55 >> >> Subject: >> >> Re: [sipx-users] Instant Message group - Bria 3.2.1 >> >> Sent by: >> >> [email protected] >> >> Anyone knows where I can change in a config file the XMPP hostname >> per the XMPP domain name for Bria provisioning as it looks >> impossible to do from GUI ? >> >> Regards. >> >> 2011/9/9 Michael Picher <[email protected]> >> yea, but Polycom phones can monitor your presence as can other XMPP >> users connected to sipXecs. >> > >> On Fri, Sep 9, 2011 at 7:34 AM, Tony Graziano > <[email protected] >> > wrote: >> dont expect to see anything in there in regard to workgroup until >> you populate it in speeddial in sipx and log back in with bria tho... >> > >> On Fri, Sep 9, 2011 at 6:57 AM, Michael Picher <[email protected]> > wrote: >> Also, under the presence tab you will typically want to enable >> workgroup and set the workgroup address to: sip:~~rl~C~YOUREXT@sipdomain >> >> where: YOUREXT = your system extension >> and: sipdomain = your sip domain >> >> Also check 'Allow others to monitor my call activity' >> >> Thanks, >> Mike >> > >> On Fri, Sep 9, 2011 at 4:35 AM, Tony Graziano > <[email protected] >> > wrote: >> once the phone loads its accounts, open the XMPP account and confirm >> the provisioned values are: >> >> 1. user (i.e. 200 not 200@) >> 2. domain (needs to be hostname, not sip domain) >> 3. password >> >> at least that is how mine is working >> >> under advanced >> >> port selection=auto >> connect port=<outbound proxy=<empty> >> resource=<empty> >> priority=0 >> > >> On Thu, Sep 8, 2011 at 5:29 PM, <[email protected]> wrote: >> 3.2.1 the latest >> >> From: Tony Graziano <[email protected]> >> Date: Thu, 8 Sep 2011 17:20:49 -0400 >> To: <[email protected]> >> Cc: Sipx-users Discussion List for users of sipXecs software<sipx- >> [email protected]> >> Subject: Re: [sipx-users] Instant Message group - Bria 3.2.1 >> >> what is the exact bria version you are running? > >> On Thu, Sep 8, 2011 at 5:11 PM, <[email protected]> wrote: >> My config is generated by sipx when I'm using provisioning > functionnality. >> > >> From: Tony Graziano <[email protected]> >> Date: Thu, 8 Sep 2011 15:41:48 -0400 >> To: <[email protected]>; Discussion list for users of >> sipXecs software<[email protected]> >> Subject: Re: [sipx-users] Instant Message group - Bria 3.2.1 >> >> I'm familiar with some of the bria idiosyncrasies, but not as up to >> date on them since i decided their product was not something that >> was worth my effort at this time. i spend more time and money with >> every release they make trying to figure out what broke, it became >> pointless to pursue and use the product any longer. >> >> Where is the config file being generated? manually or by sipx directly? >> >> > >> On Thu, Sep 8, 2011 at 1:01 PM, <[email protected]> wrote: >> Hi Tony, >> >> The hostname is already created as an alias on the domain menu of >> sipxecs, it has been done automatically when I have upgraded sipxecs >> in the past to #update 9. >> >> So why it works when I change into Bria ps0sipx01.webcti.local to >> webcti.local if they don't support XMPP SRV ? >> >> It looks that Bria doesn't permit to use instant message if XMPP >> account domain is not the same than the xmpp contact domain. >> -----Original Message----- >> From: Tony Graziano <[email protected]> >> Sender: [email protected] >> Date: Thu, 8 Sep 2011 12:26:42 >> To: Discussion list for users of sipXecs software<sipx- >> [email protected]> >> Reply-To: Discussion list for users of sipXecs software >> <[email protected]> >> Subject: Re: [sipx-users] Instant Message group - Bria 3.2.1 >> >> _______________________________________________ >> 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/ >> > >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.465.6833 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> >> Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> Ask about our Internet faxservices! >> >> > >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.465.6833 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> >> Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> Ask about our Internet faxservices! >> >> > >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.465.6833 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> >> Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> Ask about our Internet faxservices! >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > >> >> -- >> Michael Picher >> eZuce >> Director of Technical Services >> O.978-296-1005 X2015 >> M.207-956-0262 >> @mpicher <http://twitter.com/mpicher> >> www.ezuce.com > >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.465.6833 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> >> Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> Ask about our Internet faxservices! >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > >> >> -- >> Michael Picher >> eZuce >> Director of Technical Services >> O.978-296-1005 X2015 >> M.207-956-0262 >> @mpicher <http://twitter.com/mpicher> >> www.ezuce.com > >> >> _______________________________________________ >> 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/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
