📄 asteriskchantablepdu.java
字号:
{ AsnObjectId oid = res.getOid(); AsnObject value = res.getValue(); if (oid.toString().startsWith(all_oids[n])) { try { switch (n) { case 0: setAstNumChannels(value); break; case 1: setAstChanIndex(value); break; case 2: setAstChanName(value); break; case 3: setAstChanLanguage(value); break; case 4: setAstChanType(value); break; case 5: setAstChanMusicClass(value); break; case 6: setAstChanBridge(value); break; case 7: setAstChanMasq(value); break; case 8: setAstChanMasqr(value); break; case 9: setAstChanWhenHangup(value); break; case 10: setAstChanApp(value); break; case 11: setAstChanData(value); break; case 12: setAstChanContext(value); break; case 13: setAstChanMacroContext(value); break; case 14: setAstChanMacroExten(value); break; case 15: setAstChanMacroPri(value); break; case 16: setAstChanExten(value); break; case 17: setAstChanPri(value); break; case 18: setAstChanAccountCode(value); break; case 19: setAstChanForwardTo(value); break; case 20: setAstChanUniqueId(value); break; case 21: setAstChanCallGroup(value); break; case 22: setAstChanPickupGroup(value); break; case 23: setAstChanState(value); break; case 24: setAstChanMuted(value); break; case 25: setAstChanRings(value); break; case 26: setAstChanCidDNID(value); break; case 27: setAstChanCidNum(value); break; case 28: setAstChanCidName(value); break; case 29: setAstCanCidANI(value); break; case 30: setAstChanCidRDNIS(value); break; case 31: setAstChanCidPresentation(value); break; case 32: setAstChanCidANI2(value); break; case 33: setAstChanCidTON(value); break; case 34: setAstChanCidTNS(value); break; case 35: setAstChanAMAFlags(value); break; case 36: setAstChanADSI(value); break; case 37: setAstChanToneZone(value); break; case 38: setAstChanHangupCause(value); break; case 39: setAstChanVariables(value); break; case 40: setAstChanFlags(value); break; case 41: setAstChanTransferCap(value); break; default: _invalid = true; setTmpErrorIndex(n); _tmpErrorStat = SnmpConstants.SNMP_ERR_GENERR; } } catch (ClassCastException exc) { _invalid = true; setTmpErrorIndex(n); _tmpErrorStat = SnmpConstants.SNMP_ERR_GENERR; } } else { _invalid = true; setTmpErrorIndex(n); _tmpErrorStat = SnmpConstants.SNMP_ERR_NOSUCHNAME; } } if (n >= NO_OID-1) { if (_invalid == true) { setErrorStatus(_tmpErrorStat); setErrorIndex(_tmpErrorInd); } }}/**astNumChannels<br/>TYPE Integer32 ::= [UNIVERSAL 2] INTEGER (-2147483648..2147483647)<br/>OBJECT-TYPE ( Syntax: [UNIVERSAL 2] INTEGER (-2147483648..2147483647) Access: read-only Status: current Description: Current number of active channels.)<br/>*/public void setAstNumChannels(AsnObject new_value){ AsnInteger obj = (AsnInteger) new_value; _astNumChannels = new Integer(obj.getValue());}public Integer getAstNumChannels(){ return _astNumChannels;}/**astChanIndex<br/>TYPE Integer32 ::= [UNIVERSAL 2] INTEGER (-2147483648..2147483647)<br/>OBJECT-TYPE ( Syntax: [UNIVERSAL 2] INTEGER (-2147483648..2147483647) Access: read-only Status: current Description: Index into the channel table.)<br/>*/public void setAstChanIndex(AsnObject new_value){ AsnInteger obj = (AsnInteger) new_value; _astChanIndex = new Integer(obj.getValue());}public Integer getAstChanIndex(){ return _astChanIndex;}/**astChanName<br/>TYPE DisplayString ::= TEXTUAL-CONVENTION ( Display-Hint: 255a Status: current Description: Represents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. Syntax: [UNIVERSAL 4] OCTET STRING (SIZE (0..255)))<br/>OBJECT-TYPE ( Syntax: [UNIVERSAL 4] OCTET STRING (SIZE (0..255)) Access: read-only Status: current Description: Name of the currentl channel.)<br/>*/public void setAstChanName(AsnObject new_value){ AsnOctets obj = (AsnOctets) new_value; _astChanName = obj.toDisplayString();}public String getAstChanName(){ return _astChanName;}/**astChanLanguage<br/>TYPE DisplayString ::= TEXTUAL-CONVENTION ( Display-Hint: 255a Status: current Description: Represents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. Syntax: [UNIVERSAL 4] OCTET STRING (SIZE (0..255)))<br/>OBJECT-TYPE ( Syntax: [UNIVERSAL 4] OCTET STRING (SIZE (0..255)) Access: read-only Status: current Description: Which language the current channel is configured to use -- used mainly for prompts.)<br/>*/public void setAstChanLanguage(AsnObject new_value){ AsnOctets obj = (AsnOctets) new_value; _astChanLanguage = obj.toDisplayString();}public String getAstChanLanguage(){ return _astChanLanguage;}/**astChanType<br/>TYPE DisplayString ::= TEXTUAL-CONVENTION ( Display-Hint: 255a Status: current Description: Represents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. Syntax: [UNIVERSAL 4] OCTET STRING (SIZE (0..255)))<br/>OBJECT-TYPE ( Syntax: [UNIVERSAL 4] OCTET STRING (SIZE (0..255)) Access: read-only Status: current Description: Underlying technology for the current channel.)<br/>*/public void setAstChanType(AsnObject new_value){ AsnOctets obj = (AsnOctets) new_value; _astChanType = obj.toDisplayString();}public String getAstChanType(){ return _astChanType;}/**astChanMusicClass<br/>TYPE DisplayString ::= TEXTUAL-CONVENTION ( Display-Hint: 255a Status: current Description: Represents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -