Repository navigation
Releases: yepher/SipClient
Releases · yepher/SipClient
Release list
SipClient 0.2.0-b1
release_notes/0.2.0-b1.html
SipClient 0.1.0-b11
New
- AMR-WB (G.722.2) — all nine bitrate modes (6.60–23.85 kbit/s), both RFC 4867 payload framings (octet-aligned and bandwidth-efficient), dynamic payload-type negotiation and a true 16 kHz RTP clock. Decoding uses the AMR-WB codec built into macOS; encoding uses a vendored copy of vo-amrwbenc (Apache-2.0), since macOS ships no AMR-WB encoder.
- Receive jitter buffer — reorders by RTP sequence number, fills gaps with silence and smooths relays that batch-deliver packets. Optional per profile, with an adjustable target depth.
- Call recording — capture a call to a stereo WAV, this client on the left channel and the peer on the right. Can be armed before the call connects so the start isn't missed. The wire log entry has a Show in Finder button.
- Waveform on the call charts — a recorded call shows its audio alongside the inter-arrival and jitter charts, sharing the same time axis and zoom, with playback and a playhead synced across all three lanes.
- Shareable HTML export — ⌘E in the chart window writes a single self-contained page with the charts and the recording embedded, so a call can be handed to someone who doesn't have the app. No CDN or sibling files; it works offline.
Fixed
- Dialer settings that hadn't been saved yet were ignored by inbound calls and by scenarios — both read the profile as last written to disk, so unsaved edits silently did nothing. They now apply everywhere.
- Restored Sparkle auto-update, the
.sipcallfile association and thecom.yepher.sipclientbundle identifier, which had been dropped from the generated Xcode project. If you are on 0.1.0-b10 this update installs normally; the identifier and update key are unchanged.
SipClient 0.1.0-b10
What’s new in 0.1.0-b10
- In-app updates. SipClient now checks for new releases automatically and offers to download and install them for you. You can also trigger a check manually from SipClient → Check for Updates…
Updates are signed end-to-end (Apple notarization plus a Sparkle EdDSA signature). If verification ever fails, the update is refused — you’ll never end up running a tampered build.