Fix G.722/G.711 mixed recording half-rate + flaky rtpchannel suite (3.2.5)

[tinpotnick]

Summary

Two independent bug fixes plus a patch version bump to 3.2.5 (ready for npm).

1. G.722/G.711 mixed recording played back at half rate (the reported bug)

When one leg is G.722 (16 kHz) and the other G.711 (8 kHz), a recording on the G.722 leg played back at half speed.

Cause: the recorder's WAV sample rate was derived from codecx.is_wideband(), which only inspected the live wire payload type. That's still 255 when record is issued before the first inbound RTP packet decodes (the normal SIP ordering), so a G.722 channel was misclassified as narrowband and the file stamped 8 kHz — while the per-tick feed path wrote true 16 kHz wideband frames. 16 kHz audio in an 8 kHz container = half-speed playback.

Fix: CodecBundle now also tracks the negotiated (SDP) payload type, set at remote-config (known before any packet). is_wideband()/native_samplerate() consider it, so the stamp and the fed audio agree from the first frame. Added a regression test that records on the G.722 leg and asserts the WAV is stamped 16 kHz.

2. Consistently-failing rtpchannel test suite (12 tests)

The full npm test run consistently failed all 12 rtpchannel tests with done() called multiple times / Timeout 2000ms, even though the tests actually pass in isolation.

Cause (traced via mocha timer instrumentation): the "check event emitter" test is an arrow function calling this.timeout(2000). In an arrow, this is the enclosing describe Suite, and mocha 11's Suite.timeout() re-arms the timeout timer of every test in the suite. That re-armed all 12 already-passed sibling tests; their stale 2000 ms timers fired 2 s later and retroactively flipped them to failed. Only visible in the full suite, where the process stays alive long enough for the timers to fire (in isolation it exits first).

Fix: switched the test to a regular function() so this.timeout() binds to the test, not the suite. (Swept the whole test/ tree — this was the only offending case.)

3. Harness honesty

index.js swallowed throws from the channel event callback via console.trace, so a failed assertion inside a close/record/play handler surfaced only as an unrelated timeout. It now re-raises asynchronously (setImmediate) so the real error becomes a visible uncaughtException.

Verification

• npm test: 143 passing, 6 pending, 0 failing.
• cargo test --lib (single-threaded): 77 passing.

🤖 Generated with Claude Code