After a long discussion on #asterisk-bugs, it seems kind of
authorMark Michelson <mmichelson@digium.com>
Fri, 17 Oct 2008 00:13:35 +0000 (00:13 +0000)
committerMark Michelson <mmichelson@digium.com>
Fri, 17 Oct 2008 00:13:35 +0000 (00:13 +0000)
commit1b1efebf4b917f6d8b513a1f88d29957d3f08017
tree24fa673043981063c46fe3ea9f8aa0de7c1c65c1
parent4ad187cba4c6109cff0cc8ca4b8ad1721082a143
After a long discussion on #asterisk-bugs, it seems kind of
odd that a channel would be named after the originating port.
For endpoints that always include ":5060" as part
of the From: header, it will mean that you have a ton of
channels with names like "SIP/5060-3ea38a8b."

I am boldly moving forward with this change in trunk, but I'm
not touching other branches with this one since this definitely
would qualify as a behavior change. If there is a problem with
this commit, and I haven't seen the obvious reason why you'd want
to name the channel after the port from which the call originated,
then please feel free to revert this

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