[asterisk-dev] bug: autocreate peer + sippeers table entry => auth required

[Mark Price]

I posted a similar message to asterisk-users a few days ago and no-one
replied, and this looks like a bug, so I'm both sending another message to
asterisk-users and reporting it here.

In my setup, sip calls coming in through a proxy with a sip.conf entry set
to "autocreatepeer=yes" and context="proxy" get placed into context proxy in
the dial plan.  That is expected.

However, if the username in the From: address exists in the sippeers table,
it gets challenged for the password and on success is dropped into context
"default," even if the sip domain is not being served by asterisk.

Here is my sip.conf:

[general]
Autocreatepeer = no
context=default
domain = b.com
domain = sip.b.com
realm=b.com
bindport=5060
bindaddr=4.2.2.2
allow=g729,ulaw,alaw,speex,gsm
dtmfmode=rfc2833
rtcachefriends=yes
;bindaddr=0.0.0.0
srvlookup=yes
rtpkeepalive=1000
rtupdate=yes
port=5060
defaultexpirey=3600
tos=0x18
insecure=no

[ser]
type=peer
context=ser
host=4.2.2.3
canreinvite=yes
inseure=very
autocreatepeer=yes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20061027/7979121d/attachment.htm