Same extension registering over eth0 and eth1

Home » Asterisk Users » Same extension registering over eth0 and eth1
Asterisk Users 8 Comments

Hello list,

I need to know how to deal with a redundant network with only one asterisk
server, which is receiving registrations from the end points on both of its
ethernet ports. This means extension 201 is registering both from eth0 and
from eth1.

Is there a way/software which can act as a middle man between asterisk and
the ethernet ports, and by default sends registrations to asterisk only from
eth0, and if this port fails, sends registration coming in from eth1?

Zeeshan A Zakaria

8 thoughts on - Same extension registering over eth0 and eth1

  • Any proxy would work, however I would re think your network design.

    Re-registering the same phone, with the same extension, on the same
    PBX is asking for trouble. If you want to do redundancy, I would set
    your network so only one ethernet route is active at one time, then it
    is a matter or routing. If you want both ethernet ports active, then
    you are doing load balancing. Something Asterisk by itself is not
    strong at. Hence the SIP proxy or DNS SRV records.

  • I didn’t design the network, it was already here at clien’t site. It is
    designed for redundancy. I am trying to come up with a solution to make
    asterisk work in it. I am looking into opensips how it can help me.

    Zeeshan A Zakaria

  • DNS SRV will not work since there is only 1 IP in this hot failover
    network. A sip proxy introduces a single point of failure in the redundant network,
    why not keep asterisk the single point of failure?

    IMHO this kind of hot failover setup don’t work with UDP traffic, it’s
    stateless. There where a duplicate TCP packet will be ignored, UDP will
    be processed twice. While I didn’t have this problem with SIP/RTP in a
    hot failover network as described, we changed a hot setup to cold standby
    because of troubles with UDP traffic (can’t remember the specifics).

  • Any reason you cant change the asterisk server to bond the 2 nics
    together ? We use bonded nics a lot to provide resilient networks, and as
    far as any apps on the server are concerned, you are only talking to a
    single interface bond0 instead of eth0 and eth1.

    Rob

    On Mon, 18 Oct
    2010 17:03:45 -0400, Zeeshan Zakaria wrote:

    I didn’t design the
    network, it was already here at clien’t site. It is designed for
    redundancy. I am trying to come up with a solution to make asterisk work in
    it. I am looking into opensips how it can help me.

    Zeeshan A Zakaria