diff options
author | Kevin Harwell <kharwell@digium.com> | 2015-03-09 16:12:18 +0000 |
---|---|---|
committer | Kevin Harwell <kharwell@digium.com> | 2015-03-09 16:12:18 +0000 |
commit | 110b99646cec9128d9dec4bc764dfb585b3e9844 (patch) | |
tree | 19418971a669a91caf9fd19c9006118bc3ea8fcb /CHANGES | |
parent | 714cb27000ba34daebceb4e23c35708475d8816d (diff) |
res_pjsip: Allow configuration of endpoint identifier query order
It's possible to have a scenario that will create a conflict between endpoint
identifiers. For instance an incoming call could be identified by two different
endpoint identifiers and the one chosen depended upon which identifier module
loaded first. This of course causes problems when, for example, the incoming
call is expected to be identified by username, but instead is identified by ip.
This patch adds a new 'global' option to res_pjsip called
'endpoint_identifier_order'. It is a comma separated list of endpoint
identifier names that specifies the order by which identifiers are processed
and checked.
ASTERISK-24840 #close
Reported by: Mark Michelson
Review: https://reviewboard.asterisk.org/r/4455/
git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/13@432638 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'CHANGES')
-rw-r--r-- | CHANGES | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -26,6 +26,13 @@ res_ari_channels technologies, this is either a 302 Redirect response to an on-going INVITE dialog or a SIP REFER request. +res_pjsip +------------------ + * A new 'endpoint_identifier_order' option has been added that allows one to + set the order by which endpoint identifiers are processed and checked. This + option is specified under the 'global' type configuration section. + + ------------------------------------------------------------------------------ --- Functionality changes from Asterisk 13.1.0 to Asterisk 13.2.0 ------------ ------------------------------------------------------------------------------ |