diff --git a/docs/TN.1000 - FNE Network.adoc b/docs/TN.1000 - FNE Network.adoc index 6d35c9cb..8778a733 100644 --- a/docs/TN.1000 - FNE Network.adoc +++ b/docs/TN.1000 - FNE Network.adoc @@ -772,7 +772,67 @@ For both activity logs, diagnostic logs and peer status the packet format is ide |Message Payload | | -|=== +|=== + +==== 3.5.1 Peer Status JSON Structure + +[source,json] + { + "state": , + "isTxCW": , + "fixedMode": , + "dmrTSCCEnable": , + "dmrCC": , + "p25CtrlEnable": , + "p25CC": , + "nxdnCtrlEnable": , + "nxdnCC": , + "tx": , + "channelId": , + "channelNo": , + "lastDstId": , + "lastSrcId": , + "peerId": , + "sysId": , + "siteId": , + "p25RfssId": , + "p25NetId": , + "p25NAC": , + "vcChannels": [ + { + "channelId": , + "channelNo": , + "tx": , + "lastDstId": , + "lastSrcId": , + } + ], + "modem": { + "portType": "", + "modemPort": "", + "portSpeed": , + "rxLevel": , + "cwTxLevel": , + "dmrTxLevel": , + "p25TxLevel": , + "nxdnTxLevel": , + "rxDCOffset": , + "txDCOffset": , + "fdmaPremables": , + "dmrRxDelay": , + "p25CorrCount": , + "rxFrequency": , + "txFrequency": , + "rxTuning": , + "txTuning": , + "rxFrequencyEffective": , + "txFrequencyEffective": , + "v24Connected": , + "protoVer": + } + } + +NOTE: For the "state" (Modem State) value See TN.1001 - Modem Protocol Section 2.3.2, the state value is shared between host and modem. === 3.6 Announce Data Announce data, is announcement to the master CFNE about various subscriber operations, such as group affiliation, unit registration and unit deregistration. @@ -1096,11 +1156,13 @@ Talkgroup rewriting should be used *sparingly* it is an expensive operation to p === 4.3 Transfers -*TODO TODO TODO* +The CFNE provides facilities for end-point applications to transfer activity, diagnostic and peer status logs to the CFNE. (See Section 3.5) + +NOTE: Transfer messages can be quite noisy, especially if full diagnostic log transfer is enabled on both the CFNE and the end-point applications. It is recommended to utilize the alternate port operation to offload these messages to a secondary port to prevent delays on the main traffic port. (See fne-config.example.yml, useAlternatePortForDiagnostics). === 4.4 Announcements -*TODO TODO TODO* +The CFNE provides facilities for end-point applications to announce a variety of subscriber events to the CFNE. These events are self explanatory, and are documented above. (See Section 3.6) === 4.5 Peer-Link