Achaz / Achaz/imsdroid

New frame size in a sIP reinvite is not seen in the SDP

Open
#395 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. Start a video session.
2. Change the preferred video size then send a reINVITE. (In my case I trigger
the framesize change by clicking a button. I do the following in the button
click handler:

mConfigurationService.putString(NgnConfigurationEntry.QOS_PREF_VIDEO_SIZE,tmedia
_pref_video_size_t.tmedia_pref_video_size_720p.toString());

if(mConfigurationService.commit())

boolean res =
MediaSessionMgr.defaultsSetPrefVideoSize(tmedia_pref_video_size_t.tmedia_pref_vi
deo_size_720p);

avSession.setRemotePartyUri(mRemoteURI); // HACK

avSession.makeCall(mRemoteURI);

==================================================================
3.

What is the expected output? What do you see instead?
The new SDP should contain the new frame size. But I still see the original
size.

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

IMSDroid - r521

Please provide any additional information below.

More information on this issue can be found here:
https://groups.google.com/forum/?fromgroups=#!topic/doubango/0IHXoG9VNzE

I have attached the network dump and app logs.

```

Original issue reported on code.google.com by `krupa.p` on 4 Oct 2012 at 7:27

Attachments:
- [log_1004.txt](https://storage.googleapis.com/google-code-attachments/imsdroid/issue-395/comment-0/log_1004.txt)
- [capture_1004.pcap](https://storage.googleapis.com/google-code-attachments/imsdroid/issue-395/comment-0/capture_1004.pcap)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the reported calls to putString, commit, MediaSessionMgr.defaultsSetPrefVideoSize, and avSession.makeCall, then compare the attached Android log and network capture. Trace how the preferred video size is carried into the reINVITE SDP. Done means the changed frame size appears in the subsequent SDP.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.