-
```
What steps will reproduce the problem?
1. Press Recents button
2. Notice only calls made through siphon (gsm/sip) are visible.
3. No incoming/missed calls available
What is the expected output? …
-
```
What steps will reproduce the problem?
1. Follow the building guide for doubango
in(https://code.google.com/p/webrtc2sip/wiki/Building_Source_v2_0),
skipping libyuv.
2. Do full build of doubango…
-
```
What steps will reproduce the problem?
1. Press Recents button
2. Notice only calls made through siphon (gsm/sip) are visible.
3. No incoming/missed calls available
What is the expected output? …
-
```
What steps will reproduce the problem?
1. Press Recents button
2. Notice only calls made through siphon (gsm/sip) are visible.
3. No incoming/missed calls available
What is the expected output? …
-
To avoid some issues with corrupted data, we should read GSM data character by character, if possible.
-
```
Currently only some GET requests succeed because the GET request is not
properly formulated. Each line shall be terminated by a carriage return
followed by a line feed.
Currently implemented:
…
-
```
Currently only some GET requests succeed because the GET request is not
properly formulated. Each line shall be terminated by a carriage return
followed by a line feed.
Currently implemented:
…
-
### Feature Description
Currently, the GSM Retrieve API (/gsm/get) accepts requests using the POST method, with fields being submitted in the request body. Ideally, it should be a GET method API, w…
-
```
Currently only some GET requests succeed because the GET request is not
properly formulated. Each line shall be terminated by a carriage return
followed by a line feed.
Currently implemented:
…
-
```
Currently only some GET requests succeed because the GET request is not
properly formulated. Each line shall be terminated by a carriage return
followed by a line feed.
Currently implemented:
…