Achaz / Achaz/imsdroid

Voice is not heared between IMSDroid clients

Open
#364 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

```
What steps will reproduce the problem?
1.Install the android 2.2.3 emulator in windows XP
2.Install the IMSDroid on top of the emulator
3.Make a call from the IMSDroid client1 to the OpenVCS server bridge
4.same way make call from the client2(IMSDroid)to the OpenVCS server bridge

What is the expected output? What do you see instead?
Both Clients has to connected to the conference and get speech path.
But the clients are succesfully connected to the bridge but NOT ABLE TO GET THE
SPEECH PATH.

What version of the product are you using? On what operating system?
Android 2.2.3

Please provide any additional information below.

The OpenVCS server has connected the clients in the conference bridge
succesfully.But not able hear the voice on both the sides.

Note : The same call is succesful when tried with Boghe clients.i.e if the 2
Boghe are connected to the same bridge,then we can hear the voice.

Could you please clarifications on the following questions
1.Will Speech can be heared if the IMSDroid is installed in PC.
2.Is there any specific codec that has to be enabled for the speech.
```

Original issue reported on code.google.com by `priya.ni...@gmail.com` on 21 Jun 2012 at 5:57

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the call using two IMSDroid clients on the Android 2.2.3 emulator in Windows XP, connecting through the OpenVCS conference bridge. Compare the result with two Boghe clients, which reportedly provide speech, and determine why the clients connect without a speech path. Done when both IMSDroid clients can hear voice through the bridge.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
audio-video-rtc, mobile
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.