Help me fix my Vonage, please!!



  • Hi,

    I have searched this forum and have found some very useful information. However, these tips and fixes havent helped me. I am having a hard time getting the traffic shaper to work for the outbound voip queue. All of my other queues work great, inbound and outbound, and p2p.

    The inbound VOIP queue works and I have no problem hearing my incomming calls. The people on the other end complain of all kinds of garble when I have Bittorrent running. When I look in the status of the queues, nothing shows up in the qVoipUp one.

    I ran the wizard and tried both specifying Vonage as my provider, and adding an Alias in that field instead. I have reset the states several times. I also have the p2p catch all running, my Bittorrent runs on ports 54321 and 54322. I have tried all the tips in the previous "Voip woes" post.

    Any help? Do I need to post any files, screenshots??

    Thanks all!!

    System specs:

    PFsense Beta4
    P4 1.6ghz (Overkill, I know, but it was all I had)
    512mb Ram
    10gb HD
    2 10/100 nics
    Cable Modem: 5Mbps/384k  (although a speed test indicates lower)
    Vonage box: Linksys RT31P2 with latest firmware



  • Search the forum for "static-port" or "static port".



  • @Gigamike:

    Cable Modem: 5Mbps/384k  (although a speed test indicates lower)

    Use the alias IP attempt and lower your bandwidth for your line's up/downstream. If you enter the values your provider advertises but have less you overload the line.



  • @hoba:

    @Gigamike:

    Cable Modem: 5Mbps/384k  (although a speed test indicates lower)

    Use the alias IP attempt and lower your bandwidth for your line's up/downstream. If you enter the values your provider advertises but have less you overload the line.

    In my original post, I did say that I already tried an alias. I also put the actual bandwidth for what the recent speed test showed, not what they advertise. Thanks, but so far no workie…



  • 1.0 RC1 is now out, you may want to try it.


Log in to reply