Project

General

Profile

Activity

From 10/19/2017 to 11/17/2017

Today

08:06 PM Bug #2650 (New): how can osmo-mgw send a dummy RTP packet before CRCX ACK?
in CRCX processing of handle_create_con(), we send a dummy packet even before we have responded with the CRCX respons... laforge
08:01 PM Bug #2649 (New): MGCP connection idetnifiers are hex strings, not integers
See https://gerrit.osmocom.org/4906 as a starting point laforge
07:29 PM Bug #2649 (In Progress): MGCP connection idetnifiers are hex strings, not integers
laforge
07:28 PM Bug #2649 (New): MGCP connection idetnifiers are hex strings, not integers
The MGCP spec in RFC3435 is quite clear: Connection Identifiers are
hexadecimal strings of up to 32 characters. We ...
laforge
08:00 PM Bug #2648: osmo-mgw expects connection-ID from call agent in CRCX ?
See https://gerrit.osmocom.org/4905 as a starting point. This semantic change of course requires corresponding change... laforge
07:29 PM Bug #2648 (In Progress): osmo-mgw expects connection-ID from call agent in CRCX ?
laforge
06:55 PM Bug #2648 (In Progress): osmo-mgw expects connection-ID from call agent in CRCX ?
I was re-running the MGCP test cases from osmo-ttcn3-hacks and all of them failed.
The odd part is: osmo-mgw appea...
laforge

11/16/2017

09:31 PM Feature #1937: Implement way how to handle IuUP on RTP endpoints
Based on seveal soruces, and the fact that IuUp is more or less identical to IuNp, the SDP for IuUP should look like ... laforge

11/11/2017

01:07 AM Bug #2633 (In Progress): 'N@mgw' number translation uses base-16 which will break for decimal end...
https://gerrit.osmocom.org/4780 neels

11/10/2017

04:49 PM Bug #2632 (In Progress): osmo-mgw's VTY config modifies the length used for internal endpoints ar...
The function allocate_trunk() is a bit missleading. It does nothing else than checking a return code and printing an ... dexter
01:41 AM Bug #2632 (In Progress): osmo-mgw's VTY config modifies the length used for internal endpoints ar...
the option 'mgcp' / 'number endpoints 123' currently tells osmo-mgw how many endpoints to keep ready. So far it does ... neels
11:05 AM Bug #2625 (Resolved): osmo-mgw leaks host data when forwarding RTP packets
dexter
04:20 AM Feature #2631: allow arbitrary endpoint names, be more dynamic in allocation and iteration
On Fri, Nov 10, 2017 at 01:37:59AM +0000, neels [REDMINE] wrote:
> Break that direct link between '23@mgw' endpoint n...
laforge
01:48 AM Feature #2631: allow arbitrary endpoint names, be more dynamic in allocation and iteration
In a related note, osmo-mgw wants to treat "1" as the first endpoint, not zero, and hence allocates one more endpoint... neels
01:37 AM Feature #2631 (New): allow arbitrary endpoint names, be more dynamic in allocation and iteration
Break that direct link between '23@mgw' endpoint name and the 23rd item in an array of endpoints.
A client should ...
neels
02:02 AM Bug #2633: 'N@mgw' number translation uses base-16 which will break for decimal endpoint IDs near...
I'll change this to base-10, which is a single-character change, until #2631 might be implemented one day. neels
01:58 AM Bug #2633 (In Progress): 'N@mgw' number translation uses base-16 which will break for decimal end...
osmo-mgw parses the endpoint IDs like ... neels
01:33 AM Bug #2630 (New): OsmoMGW has no VTYreference manual in osmo-gsm-manuals
laforge
01:32 AM Bug #2629 (New): OsmoMGW has no user manual
OsmoMGW has no user manual in osmo-gsm-manuals. Please create one. laforge

11/08/2017

04:13 PM Bug #2625: osmo-mgw leaks host data when forwarding RTP packets
The patch fixes the issue for me. We can close the issue once it's merged. pespin
04:01 PM Bug #2625 (In Progress): osmo-mgw leaks host data when forwarding RTP packets
The excess data we see in the trace is data from the stack from previous memory usage, its not overflowing anything, ... dexter
03:31 PM Bug #2625 (Resolved): osmo-mgw leaks host data when forwarding RTP packets
I was testing the new osmo-mgw+osmo-bsc from today's master (54dd4b3f72d90dfbed19ffa7b1e98112add067a6). I can place t... pespin

11/06/2017

08:59 PM Feature #2263: osmo-mgw: support multiple BTS/RNC and pass the IP address via MGCP
> Do we also reject any RTP coming from an IP that wasn't negotiated by MGCP beforehand?
yes, we do. However, it c...
dexter

11/03/2017

06:21 PM Feature #2263: osmo-mgw: support multiple BTS/RNC and pass the IP address via MGCP
Do we also reject any RTP coming from an IP that wasn't negotiated by MGCP beforehand? neels
01:56 PM Feature #2263 (Feedback): osmo-mgw: support multiple BTS/RNC and pass the IP address via MGCP
@neels: I have checked on that problem, and I think we got rid of the problem.
See: https://gerrit.osmocom.org/#/c...
dexter
01:42 PM Bug #2535 (Resolved): improve mgcp client API
dexter
01:42 PM Bug #2598 (Resolved): Choose correct interface/ip automatically
The test on the NG40 tester looks ok, see also #2478 dexter
12:44 PM Bug #2597 (Resolved): revisit log categories
dexter
12:43 PM Bug #2454 (Resolved): Restructure existing code
dexter
12:43 PM Feature #2574 (Resolved): drop the concept of dummy packets from libosmo-mgcp
dexter

11/02/2017

04:32 PM Bug #2598: Choose correct interface/ip automatically
Patch is up for review: https://gerrit.osmocom.org/4650 dexter

11/01/2017

12:06 PM Feature #2574: drop the concept of dummy packets from libosmo-mgcp
dexter wrote:
> there is indeed already an option to disable the sending of dummy packets (no rtp keep-alive).
ah...
neels
09:48 AM Feature #2574: drop the concept of dummy packets from libosmo-mgcp
I have now visited the code locations that control how dummy packets are send. It is not very obvious on the first lo... dexter

10/30/2017

09:59 PM Bug #2598 (In Progress): Choose correct interface/ip automatically
dexter

10/27/2017

11:11 AM Bug #2598 (Resolved): Choose correct interface/ip automatically
If we run osmo-mgw in a setup where RTP streams are switched through more than a single interface will run into a pro... dexter
10:34 AM Bug #2597: revisit log categories
Added a new log category for the mgcp_network.c
Patch is up for review: https://gerrit.osmocom.org/4443
dexter

10/26/2017

07:29 PM Feature #2398 (Closed): Implement initial osmo-mgw
laforge
04:35 PM Bug #2597 (Resolved): revisit log categories
The network and the protocol part of osmo-mgw use the same logging category (DLMGCP). This is a problem because when ... dexter

10/24/2017

10:16 AM Bug #2561: osmo-mgw OBS nightly builds failing for 3 consecutive days
dexter wrote:
> @neels Is the problem still present?
Patch is merged, and osmo-mgw builds successfully, as can be...
neels
10:14 AM Bug #2561: osmo-mgw OBS nightly builds failing for 3 consecutive days
Philipp,
On Mon, Oct 23, 2017 at 09:07:42PM +0000, dexter [REDMINE] wrote:
> @neels Is the problem still present?
w...
laforge

10/23/2017

09:07 PM Bug #2561 (Feedback): osmo-mgw OBS nightly builds failing for 3 consecutive days
@neels Is the problem still present? dexter
09:00 PM Bug #2454 (In Progress): Restructure existing code
Oh, I see https://gerrit.osmocom.org/#/c/4146/ and https://gerrit.osmocom.org/#/c/4227/ are still open. Please ignore... dexter
08:57 PM Bug #2454 (Resolved): Restructure existing code
The patch is merged, so we can set this to resolved. dexter
 

Also available in: Atom