Prevent outbound SIP NOTIFY packets from displaying a port of 0
authorKinsey Moore <kmoore@digium.com>
Thu, 1 Mar 2012 14:22:01 +0000 (14:22 +0000)
committerKinsey Moore <kmoore@digium.com>
Thu, 1 Mar 2012 14:22:01 +0000 (14:22 +0000)
commite291318df2c7ed5ebbaec059d73271976c792091
tree491e7c9b3b5d2bbc86121da693d759f45c0d2a0d
parent41f5a1ab3582b01261526f1da8b32dac0cc83c21
Prevent outbound SIP NOTIFY packets from displaying a port of 0

In the change from 1.6.2 to 1.8, ast_sockaddr was introduced which changed the
behavior of ast_find_ourip such that port number was wiped out.  This caused
the port in internip (which is used for Contact and Call-ID on NOTIFYs) to be
0.  This change causes ast_find_ourip to be port-preserving again.

(closes issue ASTERISK-19430)
........

Merged revisions 357665 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........

Merged revisions 357667 from http://svn.asterisk.org/svn/asterisk/branches/10

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@357673 65c4cc65-6c06-0410-ace0-fbb531ad65f3
main/acl.c