Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NethLink: Caller’s Information Missing After First Transfer to Queue #7115

Open
viktec opened this issue Nov 14, 2024 · 0 comments
Open

NethLink: Caller’s Information Missing After First Transfer to Queue #7115

viktec opened this issue Nov 14, 2024 · 0 comments
Labels
nethlink The issue is related to NethLink (NethVoice Desktop client) nethvoice Bug or features releted to the NethVoice project
Milestone

Comments

@viktec
Copy link

viktec commented Nov 14, 2024

When a call is transferred from a salesperson to the riv queue, the information shown on the display is inconsistent. On the first attempt, only the name of the person transferring the call appears, but the caller’s information (name and origin) is missing. However, on the second attempt, both the caller's name and their origin are displayed correctly.

Steps to Reproduce:

  1. Receive an incoming call in a queue.
  2. Transfer the call from the agent to another queue.
  3. Observe that only the transfer agent's name is displayed initially, without the caller's information.
  4. After the call times out and re-rings, the correct caller information is displayed.

Expected Behavior:
The caller’s name and origin should be displayed consistently from the first transfer attempt.

@edospadoni edospadoni changed the title Caller’s Information Missing After First Transfer to Queue NethLink: Caller’s Information Missing After First Transfer to Queue Nov 14, 2024
@edospadoni edospadoni added nethvoice Bug or features releted to the NethVoice project nethlink The issue is related to NethLink (NethVoice Desktop client) labels Nov 14, 2024
@edospadoni edospadoni removed this from NethServer Nov 14, 2024
@Amygos Amygos added this to the NethVoice 1.2 milestone Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nethlink The issue is related to NethLink (NethVoice Desktop client) nethvoice Bug or features releted to the NethVoice project
Projects
Status: Todo
Development

No branches or pull requests

3 participants