Cellular Network Infrastructure » OsmoMGW

I have implemented the missing fields into the MGCP client. I see that we already generate those fields on the server side, so I copied the static values which we use from there.

The only field that contains dynamic values is the -o field. There we need to supply a session id and a local IP address. On the server side we use the connection ID as session id and the local ip on which osmo-mgw runs. On the client side I implemented it so that it determines the IP-Address on which the client runs and I use the Call-Id as session identifier.

I might be wrong, but I think what osmo-mgw now should do is to extract the session id that the client supplies and store it so that it can be used in the responses (instead of the Connection Id, which I think is wrong).

daniel, maybe it is the best if you just try the patch and see what the TTCN3 MGW emulation returns?

See also patch: https://gerrit.osmocom.org/5994

The patch is now merged. Can you see if this solved your problem?

There was also a problem with the ordering of the parameters. Technically the ordering should not matter at all since each parameter has its identifier, but the specification specifies a certain order and that is why TTCN3 still does not accept our SDP. This problem is now fixed and the patch is merged, see also: https://gerrit.osmocom.org/#/c/6217/