Project

General

Profile

Support #2628

add osmo-mgw to port numbers wiki page

Added by neels 15 days ago. Updated 9 days ago.

Status:
In Progress
Priority:
Immediate
Assignee:
Target version:
-
Start date:
11/09/2017
Due date:
% Done:

100%

Spec Reference:

Description

make sure OsmoMGW is fully listed on Port Numbers
and also look at the footer on that page to make sure all the other code locations are also adjusted.

History

#1 Updated by dexter 14 days ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 100

osmo-mgw still uses the port number of osmo-bsc_mgcp. I have assigned a new port number now, see commit in gerrit:

https://gerrit.osmocom.org/#/c/4768/
https://gerrit.osmocom.org/#/c/4769/
https://gerrit.osmocom.org/#/c/4770/

#2 Updated by neels 13 days ago

we should actually also reserve CTRL ports ... after all, the MGW has rate counters that could be published on CTRL already, and we'll probably want to add other CTRL commands soon.

#3 Updated by neels 13 days ago

on Port numbers, I fixed the link to the OsmoMGW project ... next time make sure the link isn't red

#4 Updated by neels 13 days ago

  • % Done changed from 100 to 50

I wonder, should we also pick a different MGCP port for OsmoMGW? ... actually no, not necessary nor good.

#5 Updated by neels 13 days ago

  • Checklist item vty added
  • Checklist item ctrl added

#6 Updated by neels 13 days ago

  • Checklist item mgcp added

#7 Updated by neels 13 days ago

  • Checklist item changed from mgcp to mgcp (mention on port numbers wiki page)

#8 Updated by laforge 13 days ago

On Fri, Nov 10, 2017 at 02:56:22PM +0000, neels [REDMINE] wrote:

I wonder, should we also pick a different MGCP port for OsmoMGW? ... actually no, not necessary nor good.

The MGCP port is standardized / well-known by IETF, right? I don't see
any reason for us running it on a non-standard port, it will just mean
people won't have wireshark dissection without manual intervention?

#9 Updated by laforge 13 days ago

On Fri, Nov 10, 2017 at 10:11:00AM +0000, dexter [REDMINE] wrote:

osmo-mgw still uses the port number of osmo-bsc_mgcp. I have assigned a new port number now, see commit in gerrit:

I'm not sure this is a good idea. In which systems would you run them in parallel?

OsmoBSC-SCCPlite and OsmoBSC and OsmoNITB all share the same VTY port number, e.g.

Also, we really have to stop introducing large user-visible changes. How is anyone
going to be able to follow-up with all of those? I fear we'll loose all users
if our attitude is not oriented towards stable user interfaces at least now after
the tagged versions are available.

#10 Updated by dexter 9 days ago

  • % Done changed from 50 to 60

@laforge: I agree with you, it makes more sense to keep the old port number, than changing it. I have now reverted the changes and proposed new changes that are more of cosmetic nature. The port number stays the same, but osmo-mgw gets its own constant.

https://gerrit.osmocom.org/4832 Revert "vty: add port number for osmo-mgw"
https://gerrit.osmocom.org/4833 vty: add port number constant for osmo-mgw
https://gerrit.osmocom.org/4834 Revert "common: add VTY port number for osmo-mgw"
https://gerrit.osmocom.org/4835 common: add VTY port number of osmo-mgw
https://gerrit.osmocom.org/4836 cosmetic: use correct VTY port numbr constant

#11 Updated by dexter 9 days ago

  • Checklist item ctrl set to Done
  • Checklist item mgcp (mention on port numbers wiki page) set to Done
  • % Done changed from 60 to 100

I have added osmo-mgw to the list of programs that use the MGCP port (2427):

https://gerrit.osmocom.org/4837 common: add osmo-mgw to mgcp

Since we are now re-using the VTY port of osmo-bsc_mgcp we can not reserve a conecutive port for the CTRL interface anyway. So I would suggest to skip this until we introduce the CTRL-interface on osmo-mgw.

Also available in: Atom PDF