Skype on WAAS and FWSM problem

Unanswered Question
Sep 29th, 2008
User Badges:

The customer network has two kind of situations, behind the FWSM or not.Skype already normally operated under these two kind of network construction.When WAAS disposition,behind FWSM's client to use skype , it has very heavy detention even connection error.Another network does not have the FWSM's client to be possible at the same time to use Skype normally as before.

I use wireshack to sniffer the packet.Skype behind FWSM will use tcp to replace udp.WAAS will intercept tcp and causes voice to create the detention .

I set client's skype software setting to use 14676 port for connection and disable 80/443 as substitution.And I make classifier on WAAS to pass-through the port 14676 and 443. I see the transaction-logs on WAAS,some APP CFG bypass can see,but some not.

I sniffer client again.Skype behind FWSM use 443 port and 14676 or other random port to connection.When skype use 443 or 14676 port,he can use happyly,but when skype random other port,it fail again.

How should I solve this problem ,WAAS cannot bypass Skype voice traffic.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Zach Seils Mon, 09/29/2008 - 23:40
User Badges:
  • Cisco Employee,

How are the WAEs deployed (in-path versus off-path)? What version of code are you running on the FWSM? Do you have WAAS inspection enabled on the FWSM?


ivan_tung Tue, 09/30/2008 - 08:09
User Badges:

WAE deployed in-path which version is 4.019.

FWSM version is 3.2.6 and have WAAS inspection enabled already.

Zach Seils Thu, 10/02/2008 - 06:27
User Badges:
  • Cisco Employee,


Are all of the necessary ports open on the FWSM? Does Skype work when FWSM is removed? WAAS is not doing anything specific to Skype traffic, it is just being handled at the TCP layer. If possible, a packet capture from the client and WAEs may help point us down the right path.



This Discussion