[asterisk-users] SIP peer lookup problems

[Jon Schøpzinsky]

Hello

I am currently having a problem, that threatens to drive me insane...
I cannot understand how Asterisk matches up a sip request with a peer.

Here is my example:

INVITE sip:87654321 at 192.168.100.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.59:5060;branch=z9hG4bK00d97b99;rport
From: "1088200336" <sip:1088200336 at 192.168.100.59>;tag=as54af3e4d
To: <sip:87654321 at 192.168.100.4>
Contact: <sip:1088200336 at 192.168.100.59>
Call-ID: 2c7a6e5817c0706027e35268286ca7db at 192.168.100.59
CSeq: 103 INVITE
User-Agent: gw03
Max-Forwards: 70
Proxy-Authorization: Digest username="voipsip", realm="asterisk", algorithm=MD5, uri="sip:87654321 at 192.168.100.4", nonce="xxxx", response="xxxxx", opaque=""
Date: Thu, 04 Jan 2007 17:38:27 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 242

v=0
o=root 1348 1349 IN IP4 192.168.100.59
s=session
c=IN IP4 192.168.100.59
t=0 0
m=audio 11720 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
--- (14 headers 11 lines)---
Using INVITE request as basis request - 2c7a6e5817c0706027e35268286ca7db at 192.168.100.59
Sending to 192.168.100.59 : 5060 (NAT)
Found peer '12345678'
Jan  4 18:38:28 NOTICE[19589]: chan_sip.c:10469 handle_request_invite: Failed to authenticate user "1088200336" <sip:1088200336 at 192.168.100.59>;tag=as54af3e4d
Jan  4 18:38:28 NOTICE[19589]: chan_sip.c:10469 handle_request_invite: Failed to authenticate user "1088200336" <sip:1088200336 at 192.168.100.59>;tag=as54af3e4d


Why does Asterisk identify this request as coming from the user 12345678 and not from the user voipsip as its clearly stated in the Proxy-Auth string????
The user 12345678 is registered on the server, coming from the same IP as voipsip, but if voipsip is a different user, why on earth does asterisk not identify it as voipsip instead of 12345678???

Some of the values and numbers are changed for security, etc. nonce="xxxx", response="xxxxx" and such.




Kind Regards

Jon Leren Schøpzinsky