-
```
The stack sends "sendrcv" in its SDP response instead of "sendonly".
```
Original issue reported on code.google.com by `jmauffret@gmail.com` on 28 Jan 2014 at 1:20
-
```
The stack sends "sendrcv" in its SDP response instead of "sendonly".
```
Original issue reported on code.google.com by `jmauffret@gmail.com` on 28 Jan 2014 at 1:20
-
The current JVM interop was bolted on in a week, so we should do something better. For example, the Flix program could be written with a mapping of Flix names to native names (i.e. native declarations…
mhyee updated
8 years ago
-
```
What steps will reproduce the problem?
1.invite another rcs account using 3g not using wifi
2.the receiver is going into the chat view, but the inviter cannot get into the
chatview
3.check the lo…
-
Call-flow mode assume that endpoint is strict IP:PORT. This create additional node in call-flow graphs, if my node send request from one port and expect answer on different port (contact header).
He…
-
```
What steps will reproduce the problem?
1.invite another rcs account using 3g not using wifi
2.the receiver is going into the chat view, but the inviter cannot get into the
chatview
3.check the lo…
-
-
```
TCP Stitching permits to establish MSRP connection even behind a NAT and wthout
any application server.
This means that the terminating is in active mode.
The problem here is that the MSRP connec…
-
-
```
What steps will reproduce the problem?
1.invite another rcs account using 3g not using wifi
2.the receiver is going into the chat view, but the inviter cannot get into the
chatview
3.check the lo…