Achaz / Achaz/imsdroid

Not able to Send Binary Encoded SMS, To=tel:998 SMSC=tel:777

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

```
Hi Team,

IMSDroid always defaults to using Plain Text instead of Binary Encoded SMS'es
over WIFI?

What steps will reproduce the problem?
1. Connect to an IMS Network via WiFi (I'm using www.projectclearwater.org )
1. Enable "Enable Binary SMS (RP-DATA)"
2. Set SMSC = tel:777
3. Create new SMS Message to = tel:998

What is the expected output? What do you see instead?
I expected to capture tcp packets in wireshark containing a Binary-Encoded SMS
with the headers "Content-Transfer-Encoding", "binary" and "Content-Type",
ContentType.SMS_3GPP. Instead the code thinks the URI is wrong and defaults to
using "Content-Type", "text/plain".

Below is a link to the code I'm talking about;
https://code.google.com/p/imsdroid/source/browse/trunk/imsdroid/src/org/doubango
/imsdroid/Screens/ScreenSMSCompose.java?r=369#143

I have also checked-out the util code and the URI (tel:998, tel:777), should
pass the tests ?

What version of the product are you using? On what operating system?
IMSDroid: 2.548.870
Android: Cynogenmod: 11.0-installerXNPQ32P Rooted, Android: 4.4.4
Samsun S3

Please provide any additional information below.
As stated before the Phone is connected to the IMS P-CSCF via WIFI. I am able
to send normal plain-text messages to other UA's and make calls to them.

I can't see any packets trying to get to the SMSC I configured using SIP.

Also note that I'm forcing all communication over TCP. I'm attaching a PCAP
file that can be opened with https://www.wireshark.org/.

Rgs,
John

```

Original issue reported on code.google.com by `greenjal...@gmail.com` on 10 Mar 2015 at 7:12

Attachments:
- [SIP TCP Packets Plain Text.pcapng](https://storage.googleapis.com/google-code-attachments/imsdroid/issue-551/comment-0/SIP TCP Packets Plain Text.pcapng)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with ScreenSMSCompose.java at the linked location and review the URI utility tests mentioned in the report for tel:998 and tel:777. Reproduce the configuration over WiFi with binary SMS enabled, then inspect the SIP packets in the supplied PCAP or Wireshark. Done means the configured SMS uses binary encoding with the reported headers instead of text/plain.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.