> On March 10, 2014, 3:38 p.m., opticron wrote: > > This solved the issues I was having when using 0.0.0.0 as the bind address > > for the only defined transport on my multihomed setup. Previously, the > > issue this fixes was causing all kinds of weirdness when trying to connect > > calls and resulted in a hangup a few tens of seconds into the call after a > > delay setting up the audio path (this was a result of responses going to an > > incorrect address due to a contact header being wrong). After adding this > > module, everything cleared up.
Some further details on the setup I used: Networks: * 10.24.16.0/21 ** hard phone ** default gateway * 10.24.64.0/21 ** softphone with pjsip-based stack Transport details: bind address: 0.0.0.0 protocol: UDP All endpoints were tested with explicitly configured transports and unconfigured transports. Asterisk version: Trunk r410395 with and without this patch applied This was tested with inbound and outbound calls, both of which were experiencing detrimental effects from incorrect IP addresses in SIP messages. These effects were only experienced by the soft phone on the 10.24.64.0 network since the messages to the hard phone on the 10.24.16.0 network had the correct IP address. - opticron ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3102/#review11142 ----------------------------------------------------------- On Feb. 23, 2014, 11:57 a.m., Joshua Colp wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/3102/ > ----------------------------------------------------------- > > (Updated Feb. 23, 2014, 11:57 a.m.) > > > Review request for Asterisk Developers. > > > Bugs: ASTERISK-23020 > https://issues.asterisk.org/jira/browse/ASTERISK-23020 > > > Repository: Asterisk > > > Description > ------- > > This module adds messaging rewriting for multihomed situations. When messages > are sent out it determines what interface and transport the message is going > out on. The IP address for this is then placed into the message. > > I've written this as a module since it does add a bit of additional logic for > outgoing messages. > > > Diffs > ----- > > /branches/12/res/res_pjsip_multihomed.c PRE-CREATION > > Diff: https://reviewboard.asterisk.org/r/3102/diff/ > > > Testing > ------- > > Sent and received calls/traffic in two configurations. > > 1. Two transports each bound to specific interfaces > 2. One transport bound to 0.0.0.0 > > Confirmed that the correct IP address for each interface went into the > message. > > Some additional testing by others would be nice. > > > Thanks, > > Joshua Colp > >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
