[SR-Users] Group call advice: remove calling branch after alias_db_lookup/lookup_branches
Olle E. Johansson
oej at edvina.net
Sat Mar 7 10:22:32 CET 2015
On 07 Mar 2015, at 01:32, Anthony Messina <amessina at messinet.com> wrote:
> In terms of implementing "group" calling via the append_branch feature of both
> alias_db_lookup followed by lookup_branches, I'm looking for a reliable way to
> ensure that if the caller happens to be a member of the group (list of
> branches), the branch that's created to the original caller is dropped.
>
> Originally, I was thinking of comparing $rU and $fU in branch_route, but this
> would limit the ability for one contact of an AOR to call another contact of
> the same AOR.
>
> Can anyone offer an example of an efficient method to accomplish this?
From reading your e-mail it seems that you propose a possible idea
- why not compare contact URI's?
If they have +sip.instance, just compare that. If they have not,
try to compare the full SIP URI's in the contacts.
Just brainstorming.
/O
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2374 bytes
Desc: not available
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20150307/e4fd245d/attachment.bin>
More information about the sr-users
mailing list