Properly use peer's outboundproxy for outbound REGISTERs.
authorMark Michelson <mmichelson@digium.com>
Tue, 25 May 2010 20:59:04 +0000 (20:59 +0000)
committerMark Michelson <mmichelson@digium.com>
Tue, 25 May 2010 20:59:04 +0000 (20:59 +0000)
commit01db62bdbe085c8fe02c30a84ff125137540df86
tree8d9fa4bec96ce812f44e94ae69dd7950a45402ab
parent170fdad7dff11683d249ed0a0b3796b55fdf69b7
Properly use peer's outboundproxy for outbound REGISTERs.

The logic used in transmit_register to get the outboundproxy for a peer
was flawed since this value would be overridden shortly afterwards when
create_addr was called.

In addition, this also fixes some logic used when parsing users.conf so
that the peer name is placed in the internally-generated register string
so that an outboundproxy set in the Asterisk GUI will be used for outbound
REGISTERs.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@265698 65c4cc65-6c06-0410-ace0-fbb531ad65f3
channels/chan_sip.c