secondlife / secondlife/viewer

Incoming p2p call notification does not appear if the recipient had closed the IM tab in the Conversations floater

Open
#6,010 1 comment 0 reactions 1 assignee View on GitHub

@kylelinden is already working on this.

Since Jul 21, 2026.

bug stale triage webrtc
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Environment

Second Life Release 26.2.0.25386466510 (64bit)
Release Notes

You are at 119.7, 32.0, 30.4 in Murray located at simhost-0c48e78cc33b5fbb2.agni
SLURL: https://maps.secondlife.com/secondlife/Murray/120/32/30
(global coordinates 255608.0, 256032.0, 30.4)
Second Life RC LeTigre 2026-07-10.29110850825
Release Notes

CPU: Apple M1 Pro (2400 MHz)
Memory: 16384 MB
OS Version: macOS 26.5.2 Darwin 25.5.0 Darwin Kernel Version 25.5.0: Tue Jun 9 22:18:58 PDT 2026; root:xnu-12377.121.10~1/RELEASE_ARM64_T6000 arm64
Graphics Card Vendor: Apple
Graphics Card: Apple M1 Pro

OpenGL Version: 4.1 Metal - 90.5

Window size: 1113x724
Font Size Adjustment: 96pt
UI Scaling: 0.75
Draw distance: 96m
Bandwidth: 10000kbit/s
LOD factor: 1.125
Render quality: 1
Texture memory: 12124MB
Disk cache: Max size 2150.4 MB (100.0% used)
HiDPI display mode:

J2C Decoder Version: KDU v8.4.1
Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.24.2 / OpenAL Community / OpenAL Soft: OpenAL Soft
Dullahan: 1.24.0.202510081737
CEF: 139.0.40+g465474a+chromium-139.0.7258.139
Chromium: 139.0.7258.139
LibVLC Version: 3.0.21
Voice Server Version: Secondlife WebRTC Gateway

Packets Lost: 0/1760 (0.0%)
July 16 2026 10:55:58

Description

If a user closes an IM tab in the conversations floater, they do not see any future incoming voice call offers from the user who's conversation tab they closed.

I am not sure if this is a UI issue or if the viewer is sending an 'unsubscribe' message when the IM tab is closed, similar to how closing a group chat in the Conversations list will prevent any incoming group chat messages to appear.

Reproduction steps
  1. UserA, UserB: login (can be to the same region or different regions)
  2. UserA: Send a basic text IM to UserB
  3. UserB: Observe that UserA's IM opens a new tab in the conversations floater - close this tab
  4. UserA: Initiate a p2p voice call with UserB in your Conversations floater
  5. UserB: Note if incoming call notification appears

Expected results:
In (5), UserB should see a 'UserA is calling you' notification, with 'Answer', 'Ignore', 'Open IM Instead' buttons available

Actual results:
In (5), UserB does not see any indication that UserA is calling them

Other notes:

  • If UserB reopens the conversation tab with UserA (sending a message isn't necessary), then they see the next incoming call from UserA
  • If no conversation tab had opened between the agents in the viewer session (i.e. skip steps 2 and 3), UserB gets the incoming call notification from UserA as expected
  • If the call direction in step (4) is reversed (UserB calls UserA), UserA gets the incoming call notification properly

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.