ASTERISK-01997: sip.conf type=peer not distinguishing hostname with type=user

[Home]

Summary: ASTERISK-01997: sip.conf type=peer not distinguishing hostname with type=user

Reporter: pcheng (pcheng) Labels:

Date Opened: 2004-07-12 14:32:21 Date Closed: 2011-06-07 14:05:16

Priority: Major Regression? No

Status: Closed/Complete Components: Core/General

Versions: Frequency of
Occurrence

Related
Issues:

Environment: Attachments:

Description: I have the following in sip.conf :

[inbound]
context=from-sip
type=user
host=10.1.1.1

[outbound]
type=peer
username=9999
fromuser=9999
secret=9999
auth=md5
host=10.1.1.1
canreinvite=yes
dtmfmode=rfc2833

When an inbound call is received from host 10.1.1.1, Asterisk tries to authenticate the call against the [outbound] peer rather than the [inbound] user. This results in a 403 Unauthorized message. If I comment out the [outbound] peer, then the inbound call goes into the correct extension "from-sip"

Anyone else see this behavior? Previous versions of CVS from March 2004 (my last build) do not exhibit this behavior.

****** ADDITIONAL INFORMATION ******

Asterisk CVS-HEAD-07/10/04

Comments: By: Mark Spencer (markster) 2004-07-12 15:47:57

This is not a bug. Users are authenticated against From: and peers by the calling party. SIP lacks a clear differentiation of callerid and authentication, so generally speaking the "user" concept cannot be strongly used. I recommend using sip peers for both directions. You might also want to follow ASTERISK-1991 which is trying to properly document the meanings of user and peer in sip.conf.