On 12/23/05, Douglas Garstang <[EMAIL PROTECTED]> wrote: > I have an incoming call from, say, extension 1000 and IP address 192.168.10.4 > in Asterisk. There is no user 1000 defined in sip.conf and allowguest=no. > Here is what sip.conf has: > > [general] > allowguest=no > Context=default > > [proxy1-in] > type=user > host=192.168.10.4 > insecure=very > context=Company1 > > [proxy1] > type=peer > host=192.168.10.4 > insecure=very > context=Company1 > qualify=yes > > When this call comes in, Asterisk logs: > --- (16 headers 9 lines)--- > Using INVITE request as basis request - [EMAIL PROTECTED] > Sending to 192.168.10.4 : 5060 (non-NAT) > Found peer 'proxy1' > > I'm wondering why it matched against the peer before the user, when this was > an incoming call. Shouldn't an incoming call match a 'user' before a 'peer', > if at all on the peer. >
type=user cannot accept incoming calls in SIP. It will always match from the list of peers on inbound calls. -- Bird's The Word Technologies, Inc. http://www.btwtech.com/ _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
