[asterisk-users] pjsip: don't require authentication from remote i register to

[Brian J. Murrell]

On Fri, 2019-03-01 at 14:15 -0500, Joshua C. Colp wrote:
> 
> You either configure IP based matching using an identify section[1] 

That's what I did:

[itsp]
type=registration
transport=transport-udp
outbound_auth=itsp-auth
server_uri=sip:pop1.itsp.example.com
client_uri=sip:XXX at pop1.itsp.example.com

[itsp-auth]
type=auth
auth_type=userpass
password=XXX
username=XXX

[itsp-endpoint](!)
type=endpoint
transport=transport-udp
context=from-itsp
message_context=messages
disallow=all
allow=ulaw
from_user=XXX
outbound_auth=itsp-auth
auth=itsp-auth
send_pai=yes

[itsp-aor](!)
type=aor
qualify_frequency=15

[itsp-pop1](itsp-endpoint)
aors=itsp-pop1
[itsp-pop1](itsp-aor)
contact=sip:XXX at pop1.itsp.example.com:5060

[itsp-pop1]
type=identify
endpoint=itsp-pop1
;match=pop1.itsp.example.com
match=192.168.5.6

but SIP INVITE and SIP MESSAGE packets coming from 192.168.5.6 are
still being challenged with 401 and not even printing any
errors/warnings in the console about not being able to find an
endpoint.

> or you can try line functionality on the outbound registration which
> may or may not work[2] (requires the upstream to adhere to the RFC,
> which not all do).

I'll read up on that and try in the meanwhile.

Cheers,
b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20190301/b09b6e35/attachment.sig>