search for: peerfor

> Yes, exactly (and there will be other settings as well, to identify the > type of peer (network, trunk, endpoint) for other reasons). > cool, I really should read the lists more :) > > That's coming too, but in a different way. Actually if your remote peer > can send you Remote-Party-ID headers now, you can set "trustrpid=yes" in > your peer definition

> > To get around this i updated CVS HEAD and changed the sip entity from > > type=user to type=peer (yes peer!) (type=friend works too but im making > > a point) the client now must register to set his outbound caller*ID > Number. > > Yes, that is normal. SIP has difficulty separating the remote party > identification from the authentication identification