[asterisk-dev] I finally did it! * IMPORTANT NEWS ON CHAN_SIP IN TRUNK

Johansson Olle E oej at edvina.net
Thu Jul 10 04:10:38 CDT 2008

10 jul 2008 kl. 00.20 skrev Raj Jain:

> On Wed, Jul 9, 2008 at 10:40 AM, Johansson Olle E <oej at edvina.net>  
> wrote:
>> In the future, I want to change the type= field and create better
>> object structures that work with the SIP protocol. The user/peer
>> model for SIP is really awful, but that's a separate issue.
> I thought that user/peer notion resembled a typical PBX's
> station/trunk construct very well. This also seems to fit very well
> with SIP paradigm (users are SIP UAs that you control in your own
> domain and peers are SIP proxy servers that belong to external
> domains). Just curious, where do you see problems with this model?
Long story. You have to understand that users are one-way, only
inbound calls. So you need one peer for outbound and one user
for inbound for one phone, which is not the SIP model.

So what you write fits better to the SIP model, but it is not the
Asterisk model. You apply what you believe it should be to
the Asterisk model, which is what I also want to do.

I would like to have

type=device or phone		
type=service		- something you register for, where asterisk
			          acts as a single "phone" and masquerades
type=trunk		- mutual exchange of traffic



More information about the asterisk-dev mailing list