The user label length supported by Nokia Management system is currently 200 Characters.
As per Nokia Optical Management system :
_The Connection Filed following is the requirement for connection name :
Supports string of 200 characters.
The valid characters that can be used for an infrastructure connection or service name are the following:
A-Z, a-z, 0-9, plus ‘/’, ‘|’, ‘,’, ‘.’, ‘_’, ‘-’, ‘#’,, and a space.
Infrastructure connection or service names also support the international character set (for example, circumflex and accents) and UTF-8 encoding.
The following subset of capital and small letters from the Latin alphabet # 1 in ISO/IEC 8859-1 is also supported:
Where as TAPI currently in 2.1.0 supports only 64 Characters for Topology -> Link > Name.
List of {value-name: value}
• "value-name": "LINKNAME"
"value": " [0-9a-zA-Z]{64}"
Would it be possible to support name value to have 200 characters along with support of all characters as mentioned above as NFMT is already deployed in customer location and would be easy to adapt to TAPI standard.
The user label length supported by Nokia Management system is currently 200 Characters. As per Nokia Optical Management system :
_The Connection Filed following is the requirement for connection name :
Supports string of 200 characters. The valid characters that can be used for an infrastructure connection or service name are the following:
A-Z, a-z, 0-9, plus ‘/’, ‘|’, ‘,’, ‘.’, ‘_’, ‘-’, ‘#’,, and a space.
Infrastructure connection or service names also support the international character set (for example, circumflex and accents) and UTF-8 encoding.
The following subset of capital and small letters from the Latin alphabet # 1 in ISO/IEC 8859-1 is also supported:
À, Á, Â, Ã, Ä, Å, Æ, Ç, È, É, Ê, Ë, Ì, Í, Î,
Ï, Ñ, Ò, Ó, Ô, Õ, Ö, Ø, Ù, Ú, Û, Ü, ß,
à, á, â, ã, ä, å, æ, ç, è, é, ê, ë, ì, í, î, ï, ,ñ, ò,
ó, ô, õ, ö, ⊘, ù, ú, û, ü, ÿ_
Where as TAPI currently in 2.1.0 supports only 64 Characters for Topology -> Link > Name.
List of {value-name: value} • "value-name": "LINKNAME" "value": " [0-9a-zA-Z]{64}"
Would it be possible to support name value to have 200 characters along with support of all characters as mentioned above as NFMT is already deployed in customer location and would be easy to adapt to TAPI standard.
@amazzini