[asterisk-users] Hint extension issue - bug?

[Watkins, Bradley]

Woah there...  Relax, man.  I will concur that there are some
inconsistencies and things are not exactly how they should be.  I'm
mostly just pointing out that, for various reasons that I'm not
particularly well-equipped to discuss (oej would be able to regale you
with the necessary history if you require it), this is how it works.  

It works that way intentionally, and is not a bug per se.  It is an
unfortunate design decision, but one which was necessary in order to
implement the functionality without requiring a full rewrite.

But what I previously said stands:  do not use friend, it gains you
nothing and breaks certain things.

I know that when Olle gets the time, the full rewrite of the sip channel
will do away with the user/peer/friend nonsense (among many, many other
things) that exists today.  But that is not what exists in Asterisk at
the moment, and I was mostly trying to point out how things are now.

Anyway, I'll be the last to acuse you of not putting your money where
your mouth is.  I know you've contributed to Asterisk (both code and
wisdom on the lists), probably much more than I have.  No worries there.

Regards,
- Brad

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Andrew
Kohlsmith
Sent: Wednesday, August 23, 2006 9:30 AM
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] Hint extension issue - bug?

On Wednesday 23 August 2006 08:48, Watkins, Bradley wrote:
> It's not a bug.  When you use type=friend, it will create a user 
> object
> *and* a peer object.  This will make call-limit not function, thereby 
> breaking hints.  There is no reason to use friend anyway.  It does not

> gain you any functionality, and in fact breaks some.

This is broken behaviour.

I don't know why we have the distinction of users and peers in the first
place.  A single entry with something along the line of "calltype"
taking "incoming", "outgoing" or "both" would be far clearer and
eliminate all this inconsistency.  

Call-limiting not working with users is just as dumb an idea as users
not being able to trunk calls in iax2.  They're artificial boundaries
set up for no reason other than to force a distinction between the two
types of entries.  
Eliminate all the crap and let me use the damn PBX how I want; that's
one of the biggest features of Asterisk.  Stop trying to protect me for
my own good.  
Document the shit, make it consistent and let the community support the
clueless.  You don't see this kind of crap with apache, openswan,
postfix or even the kernel itself. 

There's no need to tie my hands behind my back in order to protect the
newb.  
All you'll end up with is a system only newbs want to use.

Before anyone accuses me of not putting my money where my mouth is: I've
submitted a number of patches over the years to correct or address what
I consider inconsistencies, and I do what I can to test out trunk,
report bugs and document.  I'm doing what I can to help the system.  :-)

-A.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.