[asterisk-dev] [Code Review] SIP: peer matching by callbackextension

[Kaloyan Kovachev]

On Fri, 9 Jul 2010 13:30:23 +0200, Olle E. Johansson wrote
> Today, I have had to go through peers and users again twice. These students
have previously received dCAP, many of them have many years of experience of
Asterisk in their network, and we've gone through this in detail during the class.
> 
> The peer/user thing is a BIG issue for me. We do need to clean this up and
deliver something that better fits the needs of the users.
> 
> And no, just using type=friend is not a solution.
> 

I would say 'is not a solution yet'

Why not remove the types completely and provide a way to configure each and
every 'remote UA' section ... may not be the best name, but i am trying to not
use the terms peer, user, service or trunk and it is actualy extending the
type=friend

Some examples below in reply to a previous email:

"A peer registers with Asterisk" - option requirereg=yes|no|allow, so even for
a 'static' device with 'allow', you may get registration even you don't need
it and still be able to 'match on IP' without reg

if you have 'register=yes' - you will register to the remote UA too

there is no need to provide option to limit outbound calls as this is easy
with the dialplan (you just don't dial), but with option to 'match_on_inbound'
 one may get the 'current peer only' functionality

> /O
> -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev