A few fixes to SIP with regards to connected line updates during transfers.
authorMark Michelson <mmichelson@digium.com>
Fri, 29 May 2009 15:48:04 +0000 (15:48 +0000)
committerMark Michelson <mmichelson@digium.com>
Fri, 29 May 2009 15:48:04 +0000 (15:48 +0000)
commit14d05f57d72959ae0a26c32e041e483d31cafbcb
treedb10470cb7b8ed31d1dca66ddcb947873d51e7e3
parentce004fbf1f91dcfc6766bbc5116e08c447922506
A few fixes to SIP with regards to connected line updates during transfers.

* Set the invitestate to INV_CALLING when we send a connected line reinvite.
This prevents us from potentially rapid-firing reinvites to a single peer.

* Use the astdb to store a peer's allowed methods. This prevents us from sending
an UPDATE during the interval between startup and the peer's first registration
if the peer does not support the UPDATE method.

* Handle Polycom's method of indicating allowed methods in REGISTER. Instead of
using an Allow header, they place the allowed methods in a methods= parameter
in the Contact header.

ABE-1873

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