Skip to content

Phone Island : Inconsistent call transfer behavior between WebRTC, NethLink, and phones #7444

Open

Description

@viktec

Steps to reproduce

  • Make a call to an external number (e.g., 1234567890).
  • Transfer the call to another internal extension (e.g., Antonio).
  • Observe what Antonio sees when receiving the transferred call using WebRTC or NethLink.
  • Repeat the same process, but using a traditional phone, and check the difference in behavior.

Expected behavior

  • When the call is transferred, Antonio should first see the extension that is transferring the call, and then, once the transfer is complete, see the external number being called (e.g., 1234567890).

Actual behavior

  • With WebRTC and NethLink, Antonio initially sees our number (e.g., 0987654321), and once the transfer is completed, he correctly sees the external number being called.
  • With the traditional phone, Antonio correctly sees my internal extension (e.g., "Vittorio Russo") and, after the transfer, he correctly sees the external number being called.

Components

  • NethVoice 1.3.1 (NS8)
  • Phone Island 0.13.7

Activity

  1. added
    nethvoiceBug or features releted to the NethVoice project
    nethvoice-ctiThe issue is related to NethLink (NethVoice Web client)
    on May 7, 2025
  2. added theissue type on May 7, 2025
  3. added
    nethlinkThe issue is related to NethLink (NethVoice Desktop client)
    on May 7, 2025
  4. added this to the NethVoice 1.3 milestone on May 7, 2025
  5. removed
    nethlinkThe issue is related to NethLink (NethVoice Desktop client)
    on May 7, 2025
  6. moved this from Todo to In Progress in NethVoiceon May 14, 2025
  7. changed the title [-]Phone Island : Inconsistent call transfer behavior between WebRTC, NethLink, and traditional phones[/-] [+]Phone Island : Inconsistent call transfer behavior between WebRTC, NethLink, and phones[/+] on May 23, 2025
  8. removed
    nethvoice-ctiThe issue is related to NethLink (NethVoice Web client)
    on Jul 4, 2025
  9. 12 remaining items

  10. self-assigned this
    on May 4, 2026
  11. moved this from In Progress to Todo in NethVoiceon May 11, 2026
  12. removed their assignment
    on Jul 23, 2026
  13. moved this from Todo to In Progress in NethVoiceon Oct 26, 2026
  14. added
    testingPackages are available from testing repositories
    on Oct 26, 2026
  15. moved this from In Progress to Testing in NethVoiceon Oct 26, 2026
  16. edospadoni commented on Oct 26, 2026

    @edospadoni
    Member

    Test

    PR: nethesis/ns8-nethvoice#1104

    Setup: user A with an outbound CID configured on an outbound route/trunk, user B logged in the CTI with a WebRTC device (or NethLink), a physical phone registered to a third user C for the comparison. A ring group and a queue with agents on WebRTC for Test Case 2.

    Test Case 1 - Attended transfer of an outbound call to an extension

    • A calls an external number, then starts an attended transfer to B from the CTI
    • While B rings and during the consultation the phone island of B shows A (name and extension), not the company number
    • After A completes the transfer, B shows the external number
    • Same sequence on the physical phone of C as transfer target
    • In the call history of B the consultation appears as a call from A (not from the company number)
    • A sees B (name and extension) during the consultation

    Test Case 2 - Ring group and queue as transfer target

    • Attended transfer to a ring group with the members on WebRTC: the ringing members see A, then the external number once completed
    • Attended transfer to a queue with the agents on WebRTC: same expectations
    • Call history of the member/agent: the consultation appears as a call from A

    Test Case 3 - Transfer without consultation from the CTI

    • A hangs up while B is still ringing: B sees A while ringing and the external number as soon as A hangs up, before and after answering
    • Inbound call from a trunk answered by A as a queue agent, then transferred without consultation to B: B sees the original caller number, not A

    Test Case 4 - Regression

    • Attended transfer started from a physical phone (SIP REFER): unchanged behaviour
    • Internal call between two extensions transferred with consultation: the target sees the transferer, then the other internal party
    • Transfer target is an external number: the external party receives the outbound CID of A as before

    Testing release: 1.8.0-testing.42 (nethesis/ns8-nethvoice#1104)

    ghcr.io/nethesis/nethvoice:1.8.0-testing.42
    

    Update command (replace nethvoiceX with the NethVoice instance):

    api-cli run update-module --data '{"module_url":"ghcr.io/nethesis/nethvoice:1.8.0-testing.42","instances":["nethvoiceX"],"force":true}'
    
  17. removed
    testingPackages are available from testing repositories
    on Oct 26, 2026
  18. moved this from Testing to Verified in NethVoiceon Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    nethlinkThe issue is related to NethLink (NethVoice Desktop client)nethvoiceBug or features releted to the NethVoice projectnethvoice-ctiThe issue is related to NethLink (NethVoice Web client)verifiedAll test cases were verified successfully

    Type

    Projects

    • Status
      Verified

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions