optional vty items are stricter than expected

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Tue Aug 22 17:49:44 UTC 2017


Got no replies on this, so I guess I'll submit a patch to try and fix it.

On Sun, Aug 13, 2017 at 01:54:11AM +0200, Neels Hofmeyr wrote:
> Trying to get the newest 2G+3G developments thru the test suites (including the
> vty ones), I face a problem with this VTY definition from libosmo-sccp:
> 
>   routing-key RCONTEXT DPC [si (aal2|bicc|b-isup|h248|isup|sat-isup|sccp|tup)] [ssn SSN]
> 
[...]
> 
> With above command
>   routing-key RCONTEXT DPC [si (aal2|bicc|b-isup|h248|isup|sat-isup|sccp|tup)] [ssn SSN]
> it seems to me it is intended as optionally providing none, si or both si and ssn?

Actually it seems to be all permutations of {si, no-si}x{ssn, no-ssn}

> I guess we need separate command definitions:
> 
>   routing-key RCONTEXT DPC
>   routing-key RCONTEXT DPC si (aal2|bicc|b-isup|h248|isup|sat-isup|sccp|tup)
>   routing-key RCONTEXT DPC si (aal2|bicc|b-isup|h248|isup|sat-isup|sccp|tup) ssn SSN
and
    routing-key RCONTEXT DPC ssn SSN

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170822/0a5ca2b4/attachment.bin>


More information about the OpenBSC mailing list