ahhh. Thus I guess the "outgoing" credentials will be supplied in the [authentication] section and in incoming credentials will be defined in the peer section.
thanks klaus Leif Madsen schrieb: > Try using auth= > > From sip.conf.sample: > > [authentication] > ; Global credentials for outbound calls, i.e. when a proxy challenges your > ; Asterisk server for authentication. These credentials override > ; any credentials in peer/register definition if realm is matched. > ; > ; This way, Asterisk can authenticate for outbound calls to other > ; realms. We match realm on the proxy challenge and pick an set of > ; credentials from this list > ; Syntax: > ; auth = <user>:<secret>@<realm> > ; auth = <user>#<md5secret>@<realm> > ; Example: > ;auth=mark:[email protected] > ; > ; You may also add auth= statements to [peer] definitions > ; Peer auth= override all other authentication settings if we match on realm > > Klaus Darilion wrote: >> Hi! >> >> I wonder how to configure a SIP peer which >> - requires authentication for calls to sent to the peer >> - needs to authenticate for incoming calls >> >> I want to have different username/password for incoming and outgoing >> direction. >> >> Thanks >> Klaus >> >> _______________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
