transporter error, how to fix
- 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.Outgoing call not work, I tried with many providers
2.
3.
What is the expected output? What do you see instead?
outgoing call to work
Please commit me how to fix it.
Thank you.
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `j.nila...@gmail.com` on 15 Mar 2015 at 9:26
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is identified. First reproduce the outgoing-call failure across the reported providers and collect the product version, operating system, Wireshark network capture, or Android DDMS log; the issue is not complete until the failure is narrowed to a specific cause and fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- mobile, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100