-
- Downloads
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/ ........ Merged revisions 432638 from http://svn.asterisk.org/svn/asterisk/branches/13 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@432639 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Showing
- CHANGES 7 additions, 0 deletionsCHANGES
- configs/samples/pjsip.conf.sample 4 additions, 0 deletionsconfigs/samples/pjsip.conf.sample
- contrib/ast-db-manage/config/versions/45e3f47c6c44_add_pjsip_endpoint_identifier_order.py 21 additions, 0 deletions...sions/45e3f47c6c44_add_pjsip_endpoint_identifier_order.py
- include/asterisk/res_pjsip.h 11 additions, 0 deletionsinclude/asterisk/res_pjsip.h
- res/res_pjsip.c 105 additions, 3 deletionsres/res_pjsip.c
- res/res_pjsip/config_global.c 20 additions, 1 deletionres/res_pjsip/config_global.c
- res/res_pjsip_endpoint_identifier_anonymous.c 1 addition, 0 deletionsres/res_pjsip_endpoint_identifier_anonymous.c
- res/res_pjsip_endpoint_identifier_ip.c 1 addition, 0 deletionsres/res_pjsip_endpoint_identifier_ip.c
- res/res_pjsip_endpoint_identifier_user.c 1 addition, 0 deletionsres/res_pjsip_endpoint_identifier_user.c
Loading
Please register or sign in to comment