[asterisk-bugs] [JIRA] (ASTERISK-24192) Multihomed asterisk b2b calls on different networks

[James Cordell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Cordell updated ASTERISK-24192:
-------------------------------------

    Attachment: sip_routing_multihomed2.patch

This patch is quite crude and needs allot of re structuring. However it does server a purpose of allowing a back to back call to take place on a machine with two different routes. This patch works in conjunction with policy routing and rules.  This patch was written for asterisk 1.6.1.20

> Multihomed asterisk b2b calls on different networks
> ---------------------------------------------------
>
>                 Key: ASTERISK-24192
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24192
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Addons/General, Addons/New Feature
>         Environment: Linux general asterisk 1.6.1.20
>            Reporter: James Cordell
>            Assignee: James Cordell
>            Severity: Minor
>         Attachments: sip_routing_multihomed2.patch, sip_routing_multihomed.patch, sip_routing_multihomed.patch
>
>
> The Problem
> Asterisk has to route RTP to different network gateways. This in effect making asterisk multi-homed.
> A multi homed asterisk box needs to establish a back to back call from one network to another. Allowing the RTP from Asterisk to go to the correct gateway. Thus a call from one network, to another, for example 
> Asterisk binds on address 0.0.0.0 for therefore leaving it to the default route to decide which default gateway is in the routing table to make the decision.
> This patch complete with policy routing routes permits a multi homed asterisk box to bridge a call in such a manor. The first leg of the call can be on one network interface and the second leg on a different interface.



--
This message was sent by Atlassian JIRA
(v6.2#6252)