sachinletsgo / sipdroid

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

Sipdroid 2.9-beta client unable to register towards Sonetel Server #1093

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Sipdroid is configured for Sonetel (http://www.sonetel.com/en/) . Sipdroid 
client unable to registers and it unable send REGISTER after receiving 401 
response Sonetel Server .

What steps will reproduce the problem?
1. Sipdroid 2.9 beta on Motorola XT 311 /  Samsung GT-I9001 with android 2.3.4
2. Sipdroid does not register towards Sonetel
3) Verified the  same Droid client towards Cellip observed that it able to 
successfully registered

What is the expected output? What do you see instead?
Expect Sipdroid to register towards Sonetel 

What version of the product are you using? On what operating system?
2.9-beta from android market place
OS : android 2.3.4

Please provide any additional information below.

Suspecting that Sipdroid client unable to send the REGISTER request with 
Authorization header after receiving the  401 response.

Response from Sonetel for this Droid unable to send REGISTER with 
WWW-Authorization:

SIP/2.0 401 Unauthorized
WWW-Authenticate:Digest 
realm="sonetel.net",nonce="23305daa44d948ed4bd7e2de16db4c4f",algorithm=MD5,qop="
auth"
From:<sip:logger@sonetel.net>;tag=z9hG4bK10084908
To:<sip:logger@sonetel.net>;tag=EF07324631353641655C9600
Call-ID:029503458604@183.82.113.223
CSeq:1 REGISTER
Via:SIP/2.0/UDP 
183.82.113.223:56645;rport=56645;branch=z9hG4bK53366;received=183.82.113.223
Content-Length:0
User-Agent:Proxy Default

Response from Cellip for this Droid able o send  REGISTER (www-Authoriziation):

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 183.82.113.223:42348;rport=42348;branch=z9hG4bK90132
To: <sip:46855111747@sip.mysecretary.net>;tag=0037c459
From: <sip:46855111747@sip.mysecretary.net>;tag=z9hG4bK70825966
Call-ID: 870425638361@183.82.113.223
CSeq: 1 REGISTER
WWW-Authenticate: Digest 
nonce="1359644767:3b274f4a32344c9593b3ad8f6662d169",algorithm=MD5,realm="sip.mys
ecretary.net"
Content-Length: 0

Original issue reported on code.google.com by qt.ki...@gmail.com on 1 Feb 2013 at 8:08

GoogleCodeExporter commented 8 years ago
Already i have raised a bug for this (Issue 983). With out any explanation they 
marked it as invalid. Even with 3.x beta also they are unable to fix this. 
Before 2.3 it's working well. From 2.3 only the problem starts. 

Original comment by yuvaraja...@gmail.com on 17 May 2013 at 7:10