[Asterisk-Users] Re: [Asterisk-Users] Re: [Asterisk-Users] SIP config documentation

[Fran Boon]

On Sat, 2004-02-21 at 09:06, Costa Tsaousis wrote: 
> >> callgroup= ; UP
> >> pickupgroup= ; UP
> >> Q4: Since a user cannot accept calls, why to setup call pickup for
> >> him/her?
> > Sorry, haven't used or checked call groups. Anyone else?
> No answer on this yet...

I use pickup groups just fine (using type=friend).
I agree that it only makes sense to me for Peers...I can't speak for why
the code is currently the way it is.
Perhaps logging it as a BUG would be a better way to draw comment?

> >> accountcode= ; U- CDR's account code
> >> incominglimit= ; U- concurrent call limitations ( >= 0 )
> >> outgoinglimit= ; U- concurrent call limitations ( >= 0 )
> >>
> >> Q6: How is it possible for a type=user phone to have BOTH incoming and
> >> outgoing limits?
> > Interesting question. Anyone else?
> No help on this either so far.

I don't yet have a need for the feature & can't comment on the reasoning
for the current settings in the code.
However your logic seems right to me:
incominglimit should be for peers
outgoinglimit should be for users
It looks to me like a BUG:
Maybe you should log it as such (along with a little patch if you can!)

> >> mask= ; -P netmask for host= parameter.
> > This has to be defined *before* the host= parameter.
> Thanks for the hint. I didn't notice this.
> > What it does? Don't know. Anyone else? Why do Asterisk apply a host mask
> > to an IP address for a host?
> This is still open too.

Since this is for peers (i.e. outgoing calls) we need to be more precise than a subnet for directing the calls out, so it can't fully replace username/password (unlike the simple host=, which can)
It only makes sense to me for providing additional security restrictions to the username/password for the REGISTER to be succesful.
I can't comment on whether this is how it gets used in the code.

F