Do not treat every SIP peer as if they were configured with insecure=port.
authorRussell Bryant <russell@russellbryant.com>
Fri, 4 Sep 2009 13:14:25 +0000 (13:14 +0000)
committerRussell Bryant <russell@russellbryant.com>
Fri, 4 Sep 2009 13:14:25 +0000 (13:14 +0000)
commitca23afaf2d2ad38a0b881addc37097c45a942c47
tree691919ade6335320f13a6f266a3d58521e37a594
parent773e22596a7e44de482add4c6f30e3e6b2f290e4
Do not treat every SIP peer as if they were configured with insecure=port.

There was a problem in the function responsible for doing peer matching by
IP address and port number such that during the second pass for checking for
a peer configured with insecure=port, it would end up treating every peer as
if it had been configured that way.  These changes fix the logic in the peer
IP and port comparison callback to handle insecure=port checking properly.

This problem was introduced when SIP peers were converted to astobj2.  Many
thanks to dvossel for noticing this while working on another peer matching
issue.

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