Repository navigation
Conversation
…ix DLD ACK to post-valiation;
…bly as large, some transfer frames to sysview can reach the 8k boundary and become truncated, this increase in buffer size should allievate that issue;
…ion occurs, this is smarter then the existing logic in that a stream will fail processing validation and be rejected once identified as a collider;
… few issues with trunked voice handling for NXDN, when a VC is a trunked participant the outgoing voice frames are RTCH vs RDCH;
…tigate multi-threaded race condition from rapid disconnect/connection scenarios;
…ers to internal minimums/maximums;
…is really only intended for debugging purposes;
…ode and send net_event for NXDN RCCH data;
…en encountering a grant demand TDU;
…peer routing like U2U calls;
… in the source code with a clear warning that removing the checks is irresponsible, the protection is not for *YOU* the end user, its for people with poorly programmed subscribers that may roam incorrectly somewhere they should not be;
…ing for P25, DMR and NXDN, including P25 ISP emergency alarm, cancellation and acknowledgement procedures;
…e and decode TDULC group voice channel updates;
…rable WUID validity timing and properly encode blank Motorola BSI callsign characters;
…iliation queries, refresh WUID validity only for acknowledged valid transactions and complete group affiliation query support;
…asts, preserve per-channel service classes, properly encode and decode advertised site data and retain multiple secondary control channels;
…up access during affiliation, RF ingress and channel grants for P25, DMR and NXDN while excluding U2U and telephone interconnect traffic, and add round-robin and protocol controller admission tests;
…ck scope during connection lifecycle callbacks;
…nd NXDN, add U2U grant handling, local channel assignment, traffic channel permit and grant release cleanup, correct dedicated control channel traffic handling and P25 deny response decoding, remove supervisor configuration in favor of topology-driven traffic permits, document authoritative operating modes and add grant lifecycle regression tests;
…dentity by source RID, destination RID and LCO, preserve last MFId as the DVRS compatible fallback, clear expired and completed transactions and add MFId isolation, cleanup, expiration and fallback regression tests;
…o checks, P25 status queries, status updates and message updates, expose operation and status retrieval over REST and metadata networks, add dvmcmd queries, consume acknowledgements without peer fanout and add protocol, routing and store regression tests;
* add SNDCP data page TSBKs, correct PDU disassembly with a header offset and clear autonomous access in the SNDCP channel announcement; - add ISP_SNDCP_DATA_PAGE_RES ($13) and OSP_SNDCP_DATA_PAGE_REQ ($15) - Assembler::disassemble no longer shifts the coded block stream by the data header offset; the offset counts octets of reassembled user data - OSP_SNDCP_CH_ANN no longer sets autonomous access; the announced channel is the control channel, which receives no SN-Data * echo data service options in SNDCP grants, handle SNDCP data pages and relay SNDCP grants to the FNE; - the SNDCP data channel grant echoes the Data Service Options of the request; an SU ignores a grant whose options differ - transmit an SNDCP data page request received from the FNE and answer a "proceed" page response with a data channel grant - pass the first copy of each SNDCP grant to the network, so the FNE knows the SU has been directed to a data channel - read the SNDCP reconnect request as an ISP_SNDCP_REC_REQ, the class the factory builds for it * implement trunked SNDCP packet data in the FNE: activation ACK, SN-Data uplink and downlink, data paging and downlink retransmission; - send the link-layer ACK for the SNDCP context activation request - strip the SNDCP header from SN-Data received on the user data SAP and handle the IPv4 datagram as packet data - frame downlink datagrams as SN-Data for an SU with an SNDCP context - raise the standby timer in the context accept from 1 minute to 4 hours - page an SU that has left the data channel through the control channel that last granted it one, and hold the PDU until the grant is reported - retransmit a confirmed downlink the SU does not acknowledge, up to twice, with the same N(S) --------- Co-authored-by: David Andrzejewski <181952+dandrzejewski@users.noreply.github.com>
…ations, route protocol messages to the requested or registered peer and add operation start regression tests;
…onse; an SU that registers with a manufacturer MFID rejects a response carrying the standard MFID as undeliverable; (#135) Co-authored-by: David Andrzejewski <181952+dandrzejewski@users.noreply.github.com>
…ames, use monotonic receive timing and prevent queued or active audio from being terminated by delayed watchdog checks;
…se these intentionally fail open;
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is the team r05a06_dev branch merge into master. This will include several outstanding next version changes, and bump the overall project version from R05A04 to R06A00.
This is a major version release, as such all configurations should be validated and vetted. There are very likely breaking changes that will need to be addressed.
Component(s)
Which part(s) of the project does this affect?
Type of change
Related issues
Link any related bug reports.
Closes #
Refs #
Build & test notes
Debian 12 x86_64
GCC 12.2.0
Checklist
Notes for maintainers