[Asterisk-Users] setting caller id number and using sip
type=peerfor incomming calles.
morgan at telappliant.com
Mon Feb 21 10:32:15 MST 2005
> > To get around this i updated CVS HEAD and changed the sip entity
> > type=user to type=peer (yes peer!) (type=friend works too but im
> > a point) the client now must register to set his outbound caller*ID
> Yes, that is normal. SIP has difficulty separating the remote party
> identification from the authentication identification (although it
> be done).
> > this seems to be working but it hardly seems correct, i mean using a
> > peer for inbound calls when the docs all say it is for outbound
> In CVS HEAD, soon _all_ SIP entries will be type=peer, because it's
> logical this way.
you mean amalgamating user and peer so there will eventually only be one
type for both incoming and outgoing calls, (hopefully have an option to
disable enable in/out bound calls).
As long as it is the way it is supposed to be working I will quit
> > im not up on the sip protocol but wouldn't it be better if, when
> > receiving an unknown connection (ie when caller*ID number is set to
> > pstn number) it first sends an authentication request to the
> > return it checks that username/secret against its list of users. if
> > still doesn't find it then drop it into the guest account.
> I believe it can already be configured to work that way, if you
> access to "guest" connections (I've not tried it, though). Remember
> that it works this way because there are number of providers out
> (Broadvoice being one) that will _not_ authenticate when they send
> call, only when they register.
Now that's a bit of a bitch :/ but at the moment registration will have
But it would still be nice to have the ability to have a client that
doesn't have to register, ie they have multiple servers that can dial
though us and set caller id number.
If I get time I might tinker with this myself for some fun :).
Thanks for your reply.
More information about the asterisk-users