search

john990 / sipdroid

Automatically exported from code.google.com/p/sipdroid
GNU General Public License v3.0
0 stars 0 forks source link

SIPDROID and ASTERISK - Authentication issue #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Sipdroid fails to register to Asterisk Server. Obviously I have changed the
CLIENT-IP, DOMAIN.COM, and IP.CHANGED.FOR.SECURITY for security reasons. 

Sipdroid is giving up on passing authentication digest to Asterisk. 

REGISTER sip:domain.com SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport;branch=z9hG4bK20481
Max-Forwards: 70
To: <sip:31337@domain.com>
From: <sip:31337@domain.com>;tag=z9hG4bK64544479
Call-ID: 337010618356@127.0.0.1
CSeq: 1 REGISTER
Contact: <sip:31337@127.0.0.1>
Expires: 3600
User-Agent: mjsip stack 1.6
Content-Length: 0

SIP/2.0 100 Trying
Via: SIP/2.0/UDP
127.0.0.1:5060;branch=z9hG4bK20481;received=CLIENT-IP;rport=5060
From: <sip:31337@domain.com>;tag=z9hG4bK64544479
To: <sip:31337@domain.com>
Call-ID: 337010618356@127.0.0.1
CSeq: 1 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:31337@IP.CHANGED.FOR.SECURITY>
Content-Length: 0

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
127.0.0.1:5060;branch=z9hG4bK20481;received=CLIENT-IP;rport=5060
From: <sip:31337@domain.com>;tag=z9hG4bK64544479
To: <sip:31337@domain.com>;tag=as55f988eb
Call-ID: 337010618356@127.0.0.1
CSeq: 1 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="5d25430a"
Content-Length: 0

Original issue reported on code.google.com by vreme...@gmail.com on 4 May 2009 at 9:35

GoogleCodeExporter commented 9 years ago 
With no comment - this has been changed to "Status: Fixed"

Has it been resolved? Who has tested it? Which version has the fixes in it? Has 
it
been uploaded to the Market?

Original comment by troykel...@gmail.com on 12 Jul 2009 at 10:06

GoogleCodeExporter commented 9 years ago 
Kind of disappointed that the 1.0.0 release moved even further toward PBXes
dependence rather than less. Maybe time to rename the project PBXesdroid.

Original comment by jas...@gmail.com on 13 Jul 2009 at 1:38

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Can somebody clarify if this issue is "fixed" or "ignored". I think the latter 
more
suits, as the issue has not been fixed as far as I can see.

Or by "fixed" does the project mean that it never intends to support SIP fully, 
and
only integrate with PBXes? (This is fine, I just would like some clarification)

Original comment by troykel...@gmail.com on 13 Jul 2009 at 7:16

GoogleCodeExporter commented 9 years ago 
Actually I made the patch. It's working with at least asterisk 1.4.20. Before
authentication it extracts realm information from coming response. From 
returning 407
messages. 

I can now use sipdroid within my company. There are some remaining problems 
while
receiving calls. But at least it works now without auth=user:pass@domain line.

Original comment by buzm...@gmail.com on 13 Jul 2009 at 10:40

GoogleCodeExporter commented 9 years ago 
Which patch did you make?

Is it included in the release version? Is that why this is marked as fixed?

Original comment by troykel...@gmail.com on 13 Jul 2009 at 10:43

GoogleCodeExporter commented 9 years ago 
I cant see any additions to the GUI or the FAQ screen about where we configure 
the
Realm settings?

Where do we do this?

Original comment by wom...@gmail.com on 13 Jul 2009 at 11:52

GoogleCodeExporter commented 9 years ago 
Pascal integrated the patch to 1.0 release. We discussed in sipdroid-developers.
Realm related message.

You don't configure realm. It uses the value returned from server. 

But just moving one line of source code i think we fix issue #27 also.

Original comment by buzm...@gmail.com on 13 Jul 2009 at 12:08

GoogleCodeExporter commented 9 years ago 
I had a small problem with registering, but by changing the protocol to udp 
instead of 
tcp changed it and it works perfect.

Original comment by sysp...@gmail.com on 9 Jan 2010 at 3:14

GoogleCodeExporter commented 9 years ago 
When I am registering with SIPDROID, I am getting registraion failed, but when 
I am 
registring through XLITE on my computer I am being able to do so on my Astrix 
PBX. Dont 
know why

Original comment by ksaraogi...@gmail.com on 31 May 2010 at 7:23

GoogleCodeExporter commented 9 years ago 
I can't register my SIPDroid app on my home Asterisk box.  Softphones (XLITE) 
works fine.

Original comment by gbcue....@gmail.com on 8 Mar 2011 at 5:59

GoogleCodeExporter commented 9 years ago 
hi all this is my sip configuration 
this is working ok with x-lite sip client 
now i am trying to work in android it not connection to server 
my asterisk server is:  asterisk-1.4
sipdroid client is :sipdroid 4.2.

in extension.conf
[test] 
exten => 100,1,Answer() 
exten => 100,2Playback(tt-weasels) 
exten => 100,3,Hangup() 
exit;

in sip.conf
[101]
type=friend
context=phones
host=dynamic
bindport=5060;

Original comment by ramana05...@gmail.com on 6 Jan 2012 at 2:07