asterisk users - Feb 2016 - Asterisk 13.7.0 Pickup with namedcallgroup/namedpickupgroup

Should setting a namedcallgroup & namedpickupgroup supersede numeric
callgroups and pickupgroup ?

I've got 5 peers on my 13.7.0 box,

Three of them have a namedcallgroup & namedpickupgroup of 'kiniston'
and
Two of them have a namedcallgroup & namedpickupgroup of 'sanday'.

I'm not specifying a numeric callgroup or pickupgroup so all the peers are
defaulting to a value of '1' for both it appears.

Peers:

7001kiniston
7002kiniston
7003kiniston

7001sanday
7002sanday


If I have 7003kiniston call 7002kiniston and I dial a *8 on 7001sanday I'm
picking up the ringing 7002kiniston which isn't the behavior I want to have
happen.

I've got my own custom dialplan that works if a user dials *8 followed by
extension number (7002) that uses PickupChan to just pickup calls for that
extension that's working correctly but I'm matching it on the channel
name
so the groups shouldn't apply.



-- 
A human being should be able to change a diaper, plan an invasion, butcher
a hog, conn a ship, design a building, write a sonnet, balance accounts,
build a wall, set a bone, comfort the dying, take orders, give orders,
cooperate, act alone, solve equations, analyze a new problem, pitch manure,
program a computer, cook a tasty meal, fight efficiently, die gallantly.
Specialization is for insects.
---Heinlein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20160202/d18e2ca4/attachment.html>

On Tue, Feb 2, 2016 at 11:32 AM, John Kiniston <johnkiniston at gmail.com>
wrote:
>
> Should setting a namedcallgroup & namedpickupgroup supersede numeric
> callgroups and pickupgroup ?
>
No.  They operate in parallel.

>
> I've got 5 peers on my 13.7.0 box,
>
> Three of them have a namedcallgroup & namedpickupgroup of
'kiniston' and
> Two of them have a namedcallgroup & namedpickupgroup of
'sanday'.
>
> I'm not specifying a numeric callgroup or pickupgroup so all the peers
are
> defaulting to a value of '1' for both it appears.
>
Since you didn't specify the channel driver, I took a quick look at the
chan_dahdi, chan_sip, and chan_pjsip channel drivers to see if they
set any default groups.  I didn't see any of those channel drivers set
default pickup groups.  Somewhere in your config files the groups are
being set.to 1.  You need to look at your config files for the specific
channel driver.  Alternatively, you should be able to clear a configured
group by setting it to the empty string.

Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20160202/2acdfd18/attachment.html>

On Tue, Feb 2, 2016 at 11:11 AM, Richard Mudgett <rmudgett at digium.com>
wrote:
>
> Since you didn't specify the channel driver, I took a quick look at the
> chan_dahdi, chan_sip, and chan_pjsip channel drivers to see if they
> set any default groups.  I didn't see any of those channel drivers set
> default pickup groups.  Somewhere in your config files the groups are
> being set.to 1.  You need to look at your config files for the specific
> channel driver.  Alternatively, you should be able to clear a configured
> group by setting it to the empty string.
>
>
Whoops, I should have specified that yes sorry, chan_sip.

I took a second look at my configuration and realized I was applying a
template to the peers where I foolishly specified both callgroup and
pickupgroup as 1.

Now that I've cleared those settings from the template the sip peers no
longer have them and it looks like the behavior of the features based *8 is
doing what I want now, Excellent!

Thank you so much for your help Richard.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20160202/94c45c06/attachment.html>