[asterisk-users] Psst... Top secret information: Codename Pineapple

[Brian Candler]

On Fri, Oct 13, 2006 at 07:00:54PM -0500, Eric ManxPower Wieling wrote:
> >>>* Phones = stations, regardless of where they are
> Asterisk = SIP Server, Phone = SIP Client
> 
> >>>* Trunks = trunks to other SIP servers, bilateral
> Asterisk and the other server is "peer to peer"
> 
> >>>* Services = services you register for, like BroadVoice, Voop or FWD.
> >>>   (where asterisk acts as a "phone")
> 
> Asterisk = SIP Client, Other End = SIP Server

Hmm, but I don't see how these ideas map to formal SIP concepts (RFC 3261).

Phone = User Agent Client (places outgoing calls) and also User Agent Server
(accepts incoming calls)

But then Asterisk is both of these too.

The term "SIP Client" does not appear in RFC 3261 at all. The term "SIP
Server" does, in a loose generic way, when they mean "SIP Proxy" and/or "SIP
Registrar".

Asterisk is never a SIP Proxy, it's a SIP endpoint (UAC/UAS). I think it
*is* a registrar though.

So what I'm asking is: what's fundamentally different between a phone, and
trunk, and a service? How does Asterisk treat them differently?

After all, placing a SIP call to a phone (via a dialplan) and routing a SIP
call down a trunk (via a dialplan) are the same operation, aren't they?

Maybe we need to authenticate to the other side. Maybe we want to require
the other side to authenticate to us. But AFAICS that's something you might
want to do set (or not) for any SIP endpoint. For instance, you might want
to say that all devices with IP address 192.168.1.x can place calls without
authentication.

Regards,

Brian.