1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Problems with Toastman v1.28.7500 MIPSR2Toastman-RT K26 USB VPN and SIPgate

Discussion in 'Tomato Firmware' started by Arghtastic, Nov 14, 2012.

  1. Arghtastic

    Arghtastic Networkin' Nut Member

    I've used sipgate for years. I've had various Nokia ESeries phones and always use the built in client to have a cheap second line. My current phone is an E7 and I've had it for 2 years or more--it's been using sipgate the whole time.

    After replacing my WRT54GL with a Netgear3500L-100NAS and toastman v1.28.7500 MIPSR2Toastman-RT K26 USB VPN the sip client has stopped working. I can dial numbers but never get ANY sound. I can dial the local sipgate test number (10000) and it works fine. I can dial the sipgate echo test (10005) and it does not work.

    I know it's this router because I have a cable modem with a wi-fi access point built into it and when I connect there, my client works fine.

    Any tips would be appreciated. This is major problem for me as I use that 2nd line often.

    And PS. I do have QoS and have the same rules as I did previously. I have watched via the QoS details and all the traffic appears to be properly handled by the rules.
     
  2. Arghtastic

    Arghtastic Networkin' Nut Member

    *bump* Can someone help, please.
     
  3. koitsu

    koitsu Network Guru Member

    Please provide a wiring diagram for how things are connected to each other.

    The reason I ask for this is that you said "I have a cable modem with a wi-fi access point built into it {which works fine}". The Netgear 3500L-100NAS has no cable modem in it, it's just a router, so that would mean you potentially have a two routers involved, which could mean double NAT.

    So please provide a wiring diagram noting what ports everything is plugged into (LAN vs. Internet/WAN, etc.). :)
     
  4. Arghtastic

    Arghtastic Networkin' Nut Member

    Current Setup:

    Incoming Cable -> Cable Modem with Access Point (access point not used normally) -> WRN3500L-100NAS (v1) -> WDS to WRT54GLv1.1

    Port 4 on cable modem (4 port switch and wireless access point are built in) is plugged into Internet Port on WRN3500L. Port 4 was the same port used previously.

    Prior Setup when SIPGate worked:

    Incoming Cable -> Cable Modem with Access Point (access point not used normally) -> WRT54GLv1.1 -> WDS to WRT54GLv1.1

    Port 4 on the cable modem ((4 port switch and wireless access point are built in) is plugged into Internet Port on WRT54GL. Port 4 was always the port used.

    The WRN3500 above is directly connected to the cable modem via cat5e. It is the access point I am closest to most of the day. The other access point is directly above my head on a higher floor. The WRN3500L has QoS setup--the same rules I had previously. The prior setup had the same QoS rules and the equipment was in the same location otherwise. I have also watched the traffic (via QoS monitor) and can't find anything amiss traffic wise--it appears that it's all going through and nothing is being blocked or dropped.
     
  5. Arghtastic

    Arghtastic Networkin' Nut Member

    *bump*

    Port forwards allow echo test to work. Calls to my own sipgate number work fine. Calls to any external num do not work. Calls from my Obi202 using sipgate work fine. Only calls from wifi client have problem.
     
  6. Arghtastic

    Arghtastic Networkin' Nut Member

    So . . . . I turned on all firewall logging to track this down. To my shock. . . .I noticed that no traffic was being sent for calls to external numbers. Not blocked. Not rejected. No traffic. Calls to sipgate test numbers clearly showed traffic. I had to put my sip phone to a static ip address and stick it in the DMZ. It now works. Can toastman or someone help me out here with an apparent bug in firewall rules?
     

Share This Page