Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • jami-project jami-project
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 158
    • Issues 158
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-projectjami-project
  • Issues
  • #353
Closed
Open
Created Mar 07, 2017 by RingBot@RingBotOwner

daemon : two call id received for same call

Issue generated from Tuleap's migration script. Originally submitted by: Hadrien De Sousa (hdesousa)

* Environment:
Test on Android version 69

* Reproduce steps:
Make a call on Android and use daemon to get call id (getCallList)

* Expected result:
The daemon should return one call id bound to the contact ring id

* Actual result:
The daemon returns two call ids for the same call ;

  • one bound to the contact device id, e.g. sips:1baa0e29e8d36e3dff05038dbe6ced5e57bc3dda@192.168.49.104:35422;transport=dtls
  • the other bound to the contact actual ring id

The id bound to the device id is unnecessary and should not be returned as its confusing for clients to receive two different call ids for the same call.

Assignee
Assign to
Time tracking