Bug 344529

Summary: sip,ougoingcall => incoming call notification
Product: [Applications] kdeconnect Reporter: Philippe ROUBACH <philippe.roubach>
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aleixpol
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Philippe ROUBACH 2015-02-24 14:26:27 UTC
opensuse 13.1 , kde 4.14.4 , kde kdeconnect 0.8-2.1
android 4.2.2 , android kdeconnect 0.8

each time with my smartphone i make a call using Csipsimple (sip phone app) 
then
at the kde desktop i get a notification about an incoming call !

the notification is not complete : no number , no name .

since the beginning of kdeconnect this pb has occured .

Reproducible: Always
Comment 1 Philippe ROUBACH 2015-02-25 09:11:16 UTC
to be accurate :

i lauch the stock app "téléphone" (not Csipsimple)
then in the stock app "téléphone"
 i choose "contacts" then i choose a person in the list then i click on the icon "phone" 
 then i have the choice between using gsm or sip network 
 then i choose sip network then i wait the person answers .

so you see till the last step i don't use any Csipsimple gui . 

same thing for a number : 
i lauch the stock app "téléphone" 
then in the stock app "téléphone" i choose "clavier"" then i type a number 
then i click on the icon "phone" then i have the choice between using gsm or sip network . 
then i choose sip network then i wait the person answers .

if i use android sip feature instead of csipsimple then things are same .
Comment 2 Philippe ROUBACH 2015-02-25 09:24:26 UTC
perhaps it is better to contact the dev about  technology info

https://code.google.com/p/csipsimple/
Comment 3 Philippe ROUBACH 2015-02-25 12:44:52 UTC
i created a bug report here

https://code.google.com/p/csipsimple/issues/detail?id=2893
Comment 4 Aleix Pol 2018-01-17 00:02:57 UTC

*** This bug has been marked as a duplicate of bug 337660 ***