a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (wireshark) or Android log (DDMS output)
if you want quick response
What steps will reproduce the problem?
1. Initiate IMSDroid
2. Rotue call from IMSDroid, one IMSDroid application to another IMSDroid
application
3. Video calls are not initializing and connecting.
What is the expected output? What do you see instead?
Calls are not initializing. Not getting and sending details to the server.
What version of the product are you using? On what operating system?
IMSDroid 2.0.520 on windows Vista and Android 2.2 and above
Please provide any additional information below.
<<< 106.206.210.48:48960
2012-10-29 07:33:02.19 [Debug:]:-OutgoingPacket to be sent to
106.206.210.48:48960 Length :409
2012-10-29 07:33:02.19 [Worker:(5):runAlong]:-The message received is processed
: false
2012-10-29 07:33:02.902 [Worker:(15):runAlong]:-Rxed Time: 2012-10-29
07:33:02.902
2012-10-29 07:33:02.902 [Worker:(15):runAlong]:->>> 106.206.210.48:48960 Raw
Message Before parsing:
ACK sip:200@IPAddress SIP/2.0
Via: SIP/2.0/UDP 106.206.210.48:48960;branch=z9hG4bK1659921352;rport
From: <sip:100@IPAddress>;tag=836367348
To: <sip:200@IPAddress>
Call-ID: f8ce73b6-ef88-2321-1007-eeb5bfff4954
CSeq: 582660339 ACK
Content-Length: 0
Max-Forwards: 70
Route: <sip:IPAddress:5060;lr;transport=udp>
2012-10-29 07:33:02.903 [Worker:(15):initialize]:-Initialization failed: Call
is not present for callId :f8ce73b6-ef88-2321-1007-eeb5bfff4954
Message:sip:200@188.138.48.112
2012-10-29 07:33:02.903 [Worker:(15):processRequest]:-Request received
ACK sip:200@IPAddress SIP/2.0
Via: SIP/2.0/UDP 106.206.210.48:48960;branch=z9hG4bK1659921352;rport
From: <sip:100@IPAddress>;tag=836367348
To: <sip:200@IPAddress>
Call-ID: f8ce73b6-ef88-2321-1007-eeb5bfff4954
CSeq: 582660339 ACK
Max-Forwards: 70
Content-Length: 0
Original issue reported on code.google.com by mahesh.s...@gmail.com on 6 Nov 2012 at 4:17
Original issue reported on code.google.com by
mahesh.s...@gmail.comon 6 Nov 2012 at 4:17