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

Best way to rebroadcast SIP traffic on a local lan?

Discussion in 'Tomato Firmware' started by ehunt123, May 22, 2010.

  1. ehunt123

    ehunt123 Networkin' Nut Member

    I've got a WRT54GL 1.1 rocking with Tomato WRT and recently inherited a SPA-3102. Since my current setup isn't voip, I've looked into ways to get caller ID from a standard POTS line that the device, setup on the analog line to do nothing more than redirect, into something useful. Thankfully the SIP NOTIFY that is sent has been solved and ncid looks like my best bet since its designed to relay these notices from a SIP device onto a variety of devices.

    Since I'm currently running the ncid server on the same /24 (generic linksys non-managed 12port switch that connects into the WRT54GL) but different box, the packets are not being rebroadcast since the switch is doing its job. Since it is not managed, I can't do a quick stopgap and think my two options are:

    1.) place both these devices directly on the WRT54GL and mingle iptables or the vlan setup to rebroadcast traffic as they were on a hub
    2.) Setup iptables to rebroadcast all SIP traffic from the SPA to the lan itself
    3.) Get a hub which I really don't want to do.

    Wondering if anyone has done this or something similar and what approach is the easiest/most easily implemented here?

    I'm assuming #2 would be.

    And, does anyone run ncid?

    Thanks.
     
  2. rhester72

    rhester72 Network Guru Member

    See the --tee option for target ROUTE in iptables, I think it's exactly what you're looking for:

    Code:
    ROUTE target v1.11 options:
        --oif       ifname          Route packet through `ifname' network interface
        --iif       ifname          Change packet's incoming interface to `ifname'
        --gw        ip              Route packet via this gateway `ip'
        --continue                  Route packet and continue traversing the
                                    rules. Not valid with --iif or --tee.
        --tee                       Duplicate packet, route the duplicate,
                                    continue traversing with original packet.
                                    Not valid with --iif or --continue.
    
    Rodney
     

Share This Page