Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[consumeraficionado]

I use Skype quite a bit to conduct & record podcasting interviews.  I currently typically use my laptop at home while on our existing wireless network (we only have a couple of devices connected to the network at anyone time).  Can anyone provide feedback on their experience with call quality while using this router with Skype? 

- Is the VOIP through-put improvement significant?
- How simple is it to configure the GameFuel Engine for Skype?

Thanks in advance everyone.

[Lycan]

It isn't too difficult. Basicly I have a FAQ that should help you to understand.

See if this helps.
http://www.support.dlink.com/faq/view.asp?prod_id=2485&question=DIR-625%20/%20DIR-635%20/%20DIR-655%20/%20DIR-625_revC

[consumeraficionado]

It isn't too difficult. Basicly I have a FAQ that should help you to understand.

That's excellent.  Thank you.

Just doing a little research on Skype and I found this paper, An Analysis of Skype:
http://www1.cs.columbia.edu/~library/TR-repository/reports/reports-2004/cucs-039-04.pdf

In the paper it says:

"2.1 Ports
A Skype client (SC) opens a TCP and a UDP listening port at the
port number configured in its connection dialog box. SC
randomly chooses the port number upon installation. In addition,
SC also opens TCP listening ports at port number 80 (HTTP
port), and port number 443 (HTTPS port). Unlike many Internet
protocols, like SIP [5] and HTTP [6], there is no default TCP or
UDP listening port. Figure 15 shows a snapshot of the Skype
connection dialog box. This figure shows the ports on which a SC
listens for incoming connections."

Given the above, do I simply need to QOS Engine Rules as follows:

Protocol = TCP?
Source Port = Random Port established by Skype upon install?

Do I really care about the UDP & TCP listening ports in the QOS Engine???  Or is it necessary to add these port as well to ensure that Skype receives priority by the router?

[fgl30]

Good question...I wanna prioritize Skype in my QoS engine too.....

[consumeraficionado]

I'm actively seeking a new router to purchase, and I'm also evaluating the SIP VoIP routers, as they can perform QOS as well.  I'd really appreciate it if someone from D-Link could walk-us through the process of optimizing QOS for Skype.

[Lycan]

It's fairly simple. The easiest way would be to locate the IP address of the PC/Device running the skype. Input that as the ip range. Both times. Then leave the ports at 1-65535 and then the Destinantion Ip range should be 0.0.0.0 - 255.255.255.255 and the destination port range will be 1-65535. I would use "both" as the protocol type.

Does that help?

[fgl30]

Thx

[consumeraficionado]

The easiest way would be to locate the IP address of the PC/Device running the skype. Input that as the ip range. Both times. Then leave the ports at 1-65535 and then the Destinantion Ip range should be 0.0.0.0 - 255.255.255.255 and the destination port range will be 1-65535. I would use "both" as the protocol type.

Wouldn't this method give "all" network applications running from the "device/IP" priority?  As I am also simultaneous streaming Winamp audio on this same "device/IP," I want Skype to maintain priority over the Winamp stream.  So, isn't the port setting also important?

Looking at Skpe's "Options -> Advanced -> Connection" setting, it looks like the port for incoming connection is assigned by Skype.  In my case the port is 34088, which I can modify inside Skype's options.  But given that the port setting says "incoming connections,"  I am not sure if this port is responsible for all the network traffic (inbound and outbound) caused by Skype communication.

Comment?

[fgl30]

What about WISH? As I have a wireless Skype phone, if I put its IP in a rule with VOICE priority setted up, IŽll increase voice too?

[JHK]

Average Wireless Throughput Chart
 
http://www.smallnetbuilder.com/component/option,com_wireless/Itemid,200/

[Lycan]

Of course you'd define the IP and the port range, I was leaving it open for customization.
Outbound IP's should not be defined unless you're only calling a specific IP or range. The ports should be defined for VOIP. See if this helps.