[cisco-voip] File Transfer in Jabber

Wed Feb 17 16:16:38 EST 2016

Thanks Brian, 

Network Connectivity is good.   Client 2 is one of our developers and Client 1 is me.  The issue is easily reproducible .   Both of which are behind firewalls.   Both Firewalls have been tail’d to see if there are any deny’s.   No deny’s

-Mike

-- 

Michael T. Voity

Network Engineer

University of Vermont

(802)656-8112

From: bmeade90 at gmail.com [mailto:bmeade90 at gmail.com] On Behalf Of Brian Meade
Sent: Wednesday, February 17, 2016 16:09
To: Michael Voity <mvoity at uvm.edu>
Cc: Ryan Huff <ryanhuff at outlook.com>; voip puck <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] File Transfer in Jabber

BFCP is only needed if escalating a video call to screen-sharing.  Regular screen sharing from the Jabber client while not on a call shouldn't use it.

I'd suggest getting a problem report and packet capture from the 2 clients doing these tasks to get a better idea if there are any network connectivity issues.

On Wed, Feb 17, 2016 at 4:01 PM, Michael Voity <mvoity at uvm.edu <mailto:mvoity at uvm.edu> > wrote:

By the looks of it, No.    

But it looks like I should follow this guide - 

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_0/CJAB_BK_D657A25F_00_deployment-installation-guide-jabber-110/CJAB_BK_D657A25F_00_deployment-installation-guide-jabber-110_chapter_0111.html

-Mike

-- 

Michael T. Voity

Network Engineer

University of Vermont

From: Ryan Huff [mailto:ryanhuff at outlook.com <mailto:ryanhuff at outlook.com> ] 
Sent: Wednesday, February 17, 2016 15:43
To: Michael Voity <mvoity at uvm.edu <mailto:mvoity at uvm.edu> >; 'voip puck' <cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> >
Subject: Re: File Transfer in Jabber

Michael,

Do you have binary floor control protocol (BFCP) enabled on both of the clients?

Thanks,

= Ryan = 

Email:  <mailto:ryanhuff at outlook.com> ryanhuff at outlook.com

Spark:  <mailto:ryanhuff at outlook.com> ryanhuff at outlook.com

Twitter:  <http://twitter.com/ryanthomashuff> @ryanthomashuff

LinkedIn:  <http://linkedin.com/in/ryanthomashuff> ryanthomashuff

Web  <http://ryanthomashuff.com> ryanthomashuff.com

  _____  

From: cisco-voip < <mailto:cisco-voip-bounces at puck.nether.net> cisco-voip-bounces at puck.nether.net> on behalf of Michael Voity < <mailto:mvoity at uvm.edu> mvoity at uvm.edu>
Sent: Wednesday, February 17, 2016 3:36 PM
To: 'voip puck'
Subject: [cisco-voip] File Transfer in Jabber 

Hello, 

I seem to be having an issue with my CUPS cluster.   Hoping someone on list can guide me in a good direction.

My CUPS servers – are at 10.5.2.22900-2

Server 1 is publisher – 13 users assigned

Server 2 is Subscriber – 13 users assigned 

Client 1 is assigned to Server 1 with Windows Jabber v11.1.2 Build 24949

Client 2 is assigned to Server 2 with Mac Jabber 11.1.0 Build 221135

I have External DB and file server setup for 2 separate Postgres Databases and 2 separate users on the same RHEL6 Server.

My mode is Managed and Peer-to-Peer File Transfer.

Client 1 cannot send screen captures and files to Client 2 and same in reverse.

Client 1 cannot share his screen with Client 2 and the same in reverse

Client 1 and Client 2 can make and receive calls and video calls to each other.

All XCP services have been restarted.   High availability presence is normal.

Just shy of opening a tac case and getting Costa Ria Tac, L,     Ideas?

-Mike

-- 

Michael T. Voity

Network Engineer

University of Vermont

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> 
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160217/767ab204/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5984 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160217/767ab204/attachment.p7s>