Print

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

[CountryBumkin]

I use the OBi110 with GoogleVoice for my VoIP phone service. I works good but I have some voice drop out and background noise, and occassionally the connection is dropped, while using the phone and internet at the same time. I think making the VoIP a priority (in QoS) might help.

So my qustion is how do I set this up? The terminology from OBi forum is a little different than the D-Link setup in GameFuel. Perhaps someone can help.

I need SIP ports 5060-5061. I read elsewhere that "SIP" is TCP/UDP.
I need RTP ports 166600 - 16998. I read elsewhere that "RTP" is UDP.
My OBi device is set to static address of 192.168.0.200.

In D-Link (as you know) my choices are:
1) Protocol (TCP, UDP, Both, ICMP, Other)  -- I assume I set this to Both.
2) Local IP Range (from XXX to XXX) -- I assume this is 192.168.0.200 to 192.168.0.200
3) Local Port Range (from xxx to xxxx) -- I assume here I put 5060 to 5061
3) Remote IP Range (from XXX to XXX) -- no idea.
4) Remote Port Range (from xxx to xxx) -- no idea. Is this the 16660 to 16998?

Thanks.

[fraggboy]

Hello.  The D-Link Help link on your 4500 explains what portion does what:

GameFuel Rules
    A GameFuel Rule identifies a specific message flow and assigns a priority to that flow. For most applications, automatic classification will be adequate, and specific GameFuel Rules will not be required.

    GameFuel supports overlaps between rules, where more than one rule can match for a specific message flow. If more than one rule is found to match the rule with the highest priority will be used.

    Name
        Create a name for the rule that is meaningful to you.
    Priority
        The priority of the message flow is entered here -- 0 receives the highest priority (most urgent) and 255 receives the lowest priority (least urgent).
    Protocol
        The protocol used by the messages.
    Local IP Range
        The rule applies to a flow of messages whose LAN-side IP address falls within the range set here.
    Local Port Range
        The rule applies to a flow of messages whose LAN-side port number is within the range set here.
    Remote IP Range
        The rule applies to a flow of messages whose WAN-side IP address falls within the range set here.
    Remote Port Range
        The rule applies to a flow of messages whose WAN-side port number is within the range set here.

As far as the SIP protocol, it can be both, but I have found numerous topics that it should be set as UDP.

SOURCE: http://www.onsip.com/blog/mike/2008/12/04/sip-via-udp-vs-tcp

RTP should also be set using UDP as well.

SOURCE: http://www.cs.columbia.edu/~hgs/rtp/faq.html#tcp

You might need to adjust the NAT Endpoint Filtering under Advanced --> Firewall page.


Hope this helps.

[CountryBumkin]

Thanks for your help and help.
I did read the D-Link help section (and manual) but I still don't know what to do with the Remote IP and Ports. Nothing I got from the OBi (VoIP) site talks about WAN side or Remote settings - jus the SIP and RTP. Dose the "R" in RTP mean remote?

Is the SIP the Local (LAN) side, and the RTP the remote (WAN side)?

I'll check out links. Thanks.

[fraggboy]

The remote address/port should point to the VoIP server's public IP address.  See if they give you the IP address of the server.  *Most* of the time they will leave the ports default (Not in all cases).

SIP initiates the session between two endpoints.  RTP is what carries the information.

More information regarding SIP and RTP:  http://blog.lithiumblue.com/2007/07/understanding-relationship-between-sip.html

If you can't find the public IP, try selecting "Auto Classification" and don't set up a 'rule' (If you haven't already tried this).

[Hard Harry]

Just FYI, first you need to set a DHCP reservation for the VOIP unit or the QoS rule won't "stick".

Second, once done, you can check the internet [Status > Internet Sessions] for that IP, and that should tell everything you need to know. Here is a sample

Local                     NAT                     Internet        Protocol   State       Dir   Priority  Time Out
192.168.0.196:56708   70.188.x.x:56708     69.194.x.x:443   TCP       EST   Out    143        3592

So from that data we can gather

Name - Test
Priority - 143
Protocal - TCP
Local IP Range - 192.168.0.196
Local Port - 56708 (This is random and tracked by NAT)
Remote IP - 69.194.x.x
Remote Port Range - 443

Your probably going to want to use the same port for Local and Remote, unless your already using that port on your local network, in which case you will have to set up a port trigger, but thats a different issue. Hope this helps you discover the port and IP for your VOIP session for the QoS rule.