Achaz / Achaz/imsdroid

transport error on device

Open
#525 0 comments 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
Java
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

```
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.Just dial the number and got the transport error
2.
3.

What is the expected output? What do you see instead?
Call should connect

What version of the product are you using? On what operating system?
android 4.2.2

Please provide any additional information below.

I have installed imsdroid app on two mobiles from sample project using eclipse
which supports video calling. I have my own server for sip services. The
IMSDroid app successfully register on the sip account but when i dial a number
it shows the dial screen but call is not connecting and it gives me transport
error on device not in crash log. i have set up the info in options/Identity
screen and on Network screen i maintained the proxy-CSCF Host(maintioned domain
name here) with ipv4. Could you please help me why the call is not connecting.
i have tried the audio calling using sipdemo class and its working fine on same
crediantials. Please help me what i doing wrong. Also i want to know about the
licencing of app. How to make the app souce public which also give me privacy.
what is gpl and commercial app. How could i launch my app by all the licencing
conditioned fullfilled.
```

Original issue reported on code.google.com by `kdbrc...@gmail.com` on 7 Jul 2014 at 11:01

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file, test, or entry point is named. Start by reproducing the call attempt on Android 4.2.2 and collect the requested Wireshark capture or DDMS log, then compare it with the working audio-call path. Done would require identifying the transport failure and documenting a concrete fix or configuration change.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.