Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

Thanks for explaining this. I didnt know much of this. :)

On Thu, Jun 16, 2016 at 1:33 AM, George Kiagiadakis 
wrote:

> On 06/15/2016 05:15 PM, Balram Pariyarath wrote:
> > A few days back my problem was that I cannot make any calls using
> > telepathy (test-calls or msgs). Now I cant connect to my SIP acct. using
> > empathy!
>
> I'm sure there is an explanation to everything. Check the debug logs of
> your connection manager and mission-control. Empathy has a UI for
> showing logs from mission-control and CMs that implement the Debug
> interface, which you can use to inspect them. So does kde-telepathy as
> well.
>
> > @George: can you please elaborate about call1.content and call1.stream?
> > Should they be implemented externally? and how?
> >
>
> As you probably already know, calls in telepathy are represented as
> channel objects that implement Channel.Type.Call1. Ch.T.Call1 cannot
> work on its own, though. Your CM should also expose at least one
> Call1.Content object which then in turn should contain at least one
> Call1.Stream object. Semantically, a Content represents a media content
> in a call (ex. audio or video). A Stream represents an actual media
> stream and is contained within a Content. Usually there is one Stream
> per Content, since you are streaming to one peer (either p2p or to a
> server), but there could be more streams (ex. if you were streaming to
> multiple peers directly without a relay server and using unicast;
> multicast would still be one stream, but with multiple endpoints).
>
> Now typically, protocols such as SIP and XMPP do not do the actual media
> streaming on their own. They are used only for signaling the properties
> of the media stream and the media stream uses some other protocol. In
> order to allow better integration with the UIs, the design of telepathy
> places the signaling protocol in the CM and the actual media streaming
> in the UI. So, when you are doing a call with empathy and tp-gabble,
> gabble does the signaling part, exposes the relevant information, and
> empathy does the actual media streaming. In order to expose this
> information, the CM needs to implement also the media interfaces
> (Call1.Content.Interface.Media & Call1.Stream.Interface.Media) on the
> Content & Stream objects, as well as any other relevant interfaces from
> this category. The UI then uses these interfaces to extract the
> signaling information from the CM and setup the media stream.
>
> In certain cases, however, it is not possible to separate the media
> streaming from the signaling. There are 2 cases there as well. The first
> case is when you have dedicated hardware that does the call (ex. a GSM
> modem on a phone). In this case the software (both the CM and the UI)
> have no control over the media streaming, so the CM exposes the
> Ch.T.Call1.HardwareStreaming=True property and the UI also knows this
> way that it shouldn't bother with the stream. This is not very user
> friendly, though, because the media controls on the UI won't be
> available. The user will have to deal with the device directly somehow.
>
> The second case is when you have a CM for a proprietary protocol, whose
> media streaming cannot be implemented in the UI for legal reasons. In
> this case the UI should still handle the audio/video devices and
> transfer the data to/from the CM, which will handle the actual
> encoding/decoding and streaming. This can be done by normally exposing
> the Media interfaces and setting the transport type [1] to SHM, which
> will tell the media streaming component to actually offload media data
> to/from a shared memory segment that the CM can use on its side to
> exchange this data with the UI.
>
> The reason I asked this question is because I wonder how you are
> implementing calls in your CM. If HardwareStreaming=False, whatever call
> GUI you try to use, it will expect to find the Media interfaces
> available, otherwise it is normal for it to fail.
>
> I hope I didn't confuse you. If you need further help, I'm mostly
> available for talking on irc.
>
> Regards,
> George
>
>
> [1].
>
> https://telepathy.freedesktop.org/spec/Call_Stream_Interface_Media.html#Enum:Stream_Transport_Type
>
> ___
> telepathy mailing list
> telepathy@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/telepathy
>



-- 


*Balram P MenonTech Head | Excel 2016*
Computer Science and Engineering (Batch: 2013-17)
Govt. Model Engineering College, Kochi-21

[image: ☎]: 8129130866
✉: balb...@gmail.com 
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[George Kiagiadakis]

On 06/15/2016 05:15 PM, Balram Pariyarath wrote:
> A few days back my problem was that I cannot make any calls using
> telepathy (test-calls or msgs). Now I cant connect to my SIP acct. using
> empathy! 

I'm sure there is an explanation to everything. Check the debug logs of
your connection manager and mission-control. Empathy has a UI for
showing logs from mission-control and CMs that implement the Debug
interface, which you can use to inspect them. So does kde-telepathy as well.

> @George: can you please elaborate about call1.content and call1.stream?
> Should they be implemented externally? and how?
> 

As you probably already know, calls in telepathy are represented as
channel objects that implement Channel.Type.Call1. Ch.T.Call1 cannot
work on its own, though. Your CM should also expose at least one
Call1.Content object which then in turn should contain at least one
Call1.Stream object. Semantically, a Content represents a media content
in a call (ex. audio or video). A Stream represents an actual media
stream and is contained within a Content. Usually there is one Stream
per Content, since you are streaming to one peer (either p2p or to a
server), but there could be more streams (ex. if you were streaming to
multiple peers directly without a relay server and using unicast;
multicast would still be one stream, but with multiple endpoints).

Now typically, protocols such as SIP and XMPP do not do the actual media
streaming on their own. They are used only for signaling the properties
of the media stream and the media stream uses some other protocol. In
order to allow better integration with the UIs, the design of telepathy
places the signaling protocol in the CM and the actual media streaming
in the UI. So, when you are doing a call with empathy and tp-gabble,
gabble does the signaling part, exposes the relevant information, and
empathy does the actual media streaming. In order to expose this
information, the CM needs to implement also the media interfaces
(Call1.Content.Interface.Media & Call1.Stream.Interface.Media) on the
Content & Stream objects, as well as any other relevant interfaces from
this category. The UI then uses these interfaces to extract the
signaling information from the CM and setup the media stream.

In certain cases, however, it is not possible to separate the media
streaming from the signaling. There are 2 cases there as well. The first
case is when you have dedicated hardware that does the call (ex. a GSM
modem on a phone). In this case the software (both the CM and the UI)
have no control over the media streaming, so the CM exposes the
Ch.T.Call1.HardwareStreaming=True property and the UI also knows this
way that it shouldn't bother with the stream. This is not very user
friendly, though, because the media controls on the UI won't be
available. The user will have to deal with the device directly somehow.

The second case is when you have a CM for a proprietary protocol, whose
media streaming cannot be implemented in the UI for legal reasons. In
this case the UI should still handle the audio/video devices and
transfer the data to/from the CM, which will handle the actual
encoding/decoding and streaming. This can be done by normally exposing
the Media interfaces and setting the transport type [1] to SHM, which
will tell the media streaming component to actually offload media data
to/from a shared memory segment that the CM can use on its side to
exchange this data with the UI.

The reason I asked this question is because I wonder how you are
implementing calls in your CM. If HardwareStreaming=False, whatever call
GUI you try to use, it will expect to find the Media interfaces
available, otherwise it is normal for it to fail.

I hope I didn't confuse you. If you need further help, I'm mostly
available for talking on irc.

Regards,
George


[1].
https://telepathy.freedesktop.org/spec/Call_Stream_Interface_Media.html#Enum:Stream_Transport_Type

___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[George Kiagiadakis]

On 15.06.2016 08:18, George Kiagiadakis wrote:

On 14.06.2016 21:20, Alok Anand wrote:

On Thu, Jun 9, 2016 at 2:30 PM, Balram Pariyarath 
wrote:


Thanks Alok, I too made that mistake. :)
But still I couldnt place a call to the test calls account.
Error: There was an error starting the call


I am facing simmilar issue.
https://lists.freedesktop.org/archives/telepathy/2016-June/006933.html
[1]


Are you guys both testing with Empathy as the frontend? Have you tried
testing calls with XMPP (telepathy-gabble) to see if empathy calls are
working in general?

In addition, have you implemented the media signaling interfaces?
(Call1.Content & Call1.Stream)


Sorry, I meant Call1.Content.* and Call1.Stream.* [1]

[1]. https://telepathy.freedesktop.org/spec/#Call-media-interfaces

___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Alok Anand]

On Thu, Jun 9, 2016 at 2:30 PM, Balram Pariyarath  wrote:
>
> Thanks Alok, I too made that mistake. :)
> But still I couldnt place a call to the test calls account.
> Error: There was an error starting the call

I am facing simmilar issue.
https://lists.freedesktop.org/archives/telepathy/2016-June/006933.html

> I am working on that.
> I just cloned the latest build of resiprocate1.10.0 and configured it.
But while I ran make check I got the following error.
>
> Makefile:1381: recipe for target 'test-suite.log' failed
> make[6]: *** [test-suite.log] Error 1


--
Regards,
Alok Anand
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

Again I cannot connect to Empathy using my SIP acct.! :(

On Thu, Jun 9, 2016 at 2:30 PM, Balram Pariyarath  wrote:

> Thanks Alok, I too made that mistake. :)
> But still I couldnt place a call to the test calls account.
> Error: There was an error starting the call
> I am working on that.
> I just cloned the latest build of resiprocate1.10.0 and configured it. But
> while I ran make check I got the following error.
>
> Makefile:1381: recipe for target 'test-suite.log' failed
> make[6]: *** [test-suite.log] Error 1
>
> for more details, see the attachment.
>
> On Thu, Jun 9, 2016 at 12:29 AM, Daniel Pocock  wrote:
>
>>
>>
>> On 08/06/16 12:30, Alok Anand wrote:
>> >
>> >
>> > On Wed, Jun 8, 2016 at 9:41 AM, Balram Pariyarath > > > wrote:
>> >>
>> >> Hey, I think it works. I could connect using the credentials. :)
>> >>
>> >> But still there are some things,
>> >>
>> >> When I try to make a test call or chat with someone, I get an error
>> > like: Could not start a conversation with the given contact
>> >
>> >
>> >
>> > ​It offers basic support for making and receiving audio calls.
>> > There is currently no support for video, presence or chat messaging.
>> >
>> > ​
>> > This is from [1]
>> >
>> > Also keep in mind that while making a new call add "sip:" before the
>> > account address you are calling to.
>> > For example, sip:al...@ws.sip5060.net > sip%3aal...@ws.sip5060.net>
>> > I made this mistake earlier.
>> >
>>
>>
>> Balram, I'm glad to hear you got to this stage
>>
>> You are correct in observing that many of the functions don't work, this
>> code is a proof-of-concept and therefore it provides various
>> opportunities for GSoC students to work on it.
>>
>> I've sent you a private email about the next steps for your project.
>>
>
>
>
> --
>
>
> *Balram P MenonTech Head | Excel 2016*
> Computer Science and Engineering (Batch: 2013-17)
> Govt. Model Engineering College, Kochi-21
>
> [image: ☎]: 8129130866
> ✉: balb...@gmail.com 
>



-- 


*Balram P MenonTech Head | Excel 2016*
Computer Science and Engineering (Batch: 2013-17)
Govt. Model Engineering College, Kochi-21

[image: ☎]: 8129130866
✉: balb...@gmail.com 


recent_bustle.pdf
Description: Adobe PDF document
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

Thanks Alok, I too made that mistake. :)
But still I couldnt place a call to the test calls account.
Error: There was an error starting the call
I am working on that.
I just cloned the latest build of resiprocate1.10.0 and configured it. But
while I ran make check I got the following error.

Makefile:1381: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1

for more details, see the attachment.

On Thu, Jun 9, 2016 at 12:29 AM, Daniel Pocock  wrote:

>
>
> On 08/06/16 12:30, Alok Anand wrote:
> >
> >
> > On Wed, Jun 8, 2016 at 9:41 AM, Balram Pariyarath  > > wrote:
> >>
> >> Hey, I think it works. I could connect using the credentials. :)
> >>
> >> But still there are some things,
> >>
> >> When I try to make a test call or chat with someone, I get an error
> > like: Could not start a conversation with the given contact
> >
> >
> >
> > ​It offers basic support for making and receiving audio calls.
> > There is currently no support for video, presence or chat messaging.
> >
> > ​
> > This is from [1]
> >
> > Also keep in mind that while making a new call add "sip:" before the
> > account address you are calling to.
> > For example, sip:al...@ws.sip5060.net  >
> > I made this mistake earlier.
> >
>
>
> Balram, I'm glad to hear you got to this stage
>
> You are correct in observing that many of the functions don't work, this
> code is a proof-of-concept and therefore it provides various
> opportunities for GSoC students to work on it.
>
> I've sent you a private email about the next steps for your project.
>



-- 


*Balram P MenonTech Head | Excel 2016*
Computer Science and Engineering (Batch: 2013-17)
Govt. Model Engineering College, Kochi-21

[image: ☎]: 8129130866
✉: balb...@gmail.com 
Making check in rutil
make[1]: Entering directory '/home/balram/Projects/gsoc/resiprocate/rutil'
Making check in .
make[2]: Entering directory '/home/balram/Projects/gsoc/resiprocate/rutil'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/home/balram/Projects/gsoc/resiprocate/rutil'
Making check in test
make[2]: Entering directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
make  testCompat testCoders testConfigParse testCountStream testData 
testDataPerformance testDataStream testDnsUtil testFifo testFileSystem 
testInserter testIntrusiveList testLogger testMD5Stream testNetNs 
testParseBuffer testRandomHex testRandomThread testThreadIf testXMLCursor
make[3]: Entering directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
make[3]: 'testCompat' is up to date.
make[3]: 'testCoders' is up to date.
make[3]: 'testConfigParse' is up to date.
make[3]: 'testCountStream' is up to date.
make[3]: 'testData' is up to date.
make[3]: 'testDataPerformance' is up to date.
make[3]: 'testDataStream' is up to date.
make[3]: 'testDnsUtil' is up to date.
make[3]: 'testFifo' is up to date.
make[3]: 'testFileSystem' is up to date.
make[3]: 'testInserter' is up to date.
make[3]: 'testIntrusiveList' is up to date.
make[3]: 'testLogger' is up to date.
make[3]: 'testMD5Stream' is up to date.
make[3]: 'testNetNs' is up to date.
make[3]: 'testParseBuffer' is up to date.
make[3]: 'testRandomHex' is up to date.
make[3]: 'testRandomThread' is up to date.
make[3]: 'testThreadIf' is up to date.
make[3]: 'testXMLCursor' is up to date.
make[3]: Leaving directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
make  check-TESTS
make[3]: Entering directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
make[4]: Entering directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
PASS: testCompat
PASS: testCoders
PASS: testConfigParse
PASS: testCountStream
PASS: testData
PASS: testDataPerformance
PASS: testDataStream
PASS: testDnsUtil
PASS: testFifo
PASS: testFileSystem
PASS: testInserter
PASS: testIntrusiveList
PASS: testLogger
PASS: testMD5Stream
PASS: testNetNs
PASS: testParseBuffer
PASS: testRandomHex
PASS: testRandomThread
PASS: testThreadIf
PASS: testXMLCursor
make[5]: Entering directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'

Testsuite summary for resiprocate 1.10.0

# TOTAL: 20
# PASS:  20
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

make[4]: Leaving directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
make[3]: Leaving directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
make[2]: Leaving directory '/home/balram/Projects/gsoc/resiprocate/rutil/test'
make[1]: Leaving directory '/home/balram/Projects/gsoc/resiprocate/rutil'
Making check in resip
make[1]: Entering 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Daniel Pocock]

On 08/06/16 12:30, Alok Anand wrote:
> 
> 
> On Wed, Jun 8, 2016 at 9:41 AM, Balram Pariyarath  > wrote:
>>
>> Hey, I think it works. I could connect using the credentials. :)
>>
>> But still there are some things,
>>
>> When I try to make a test call or chat with someone, I get an error
> like: Could not start a conversation with the given contact
> 
> 
> 
> ​It offers basic support for making and receiving audio calls.
> There is currently no support for video, presence or chat messaging.
> 
> ​
> This is from [1]
> 
> Also keep in mind that while making a new call add "sip:" before the
> account address you are calling to.
> For example, sip:al...@ws.sip5060.net  
> I made this mistake earlier.
> 


Balram, I'm glad to hear you got to this stage

You are correct in observing that many of the functions don't work, this
code is a proof-of-concept and therefore it provides various
opportunities for GSoC students to work on it.

I've sent you a private email about the next steps for your project.
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Alok Anand]

On Wed, Jun 8, 2016 at 9:41 AM, Balram Pariyarath  wrote:
>
> Hey, I think it works. I could connect using the credentials. :)
>
> But still there are some things,
>
> When I try to make a test call or chat with someone, I get an error like:
Could not start a conversation with the given contact



​It offers basic support for making and receiving audio calls.
> There is currently no support for video, presence or chat messaging.

​
This is from [1]

Also keep in mind that while making a new call add "sip:" before the
account address you are calling to.
For example, sip:al...@ws.sip5060.net
I made this mistake earlier.

[1]
https://github.com/resiprocate/resiprocate/blob/master/apps/telepathy/README.txt
​​
--
Regards,
Alok Anand
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

Hey, I think it works. I could connect using the credentials. :)

But still there are some things,

When I try to make a test call or chat with someone, I get an error
like: Could not start a conversation with the given contact


On Tue, Jun 7, 2016 at 5:04 PM, Daniel Pocock  wrote:

> On 07/06/16 09:59, Balram Pariyarath wrote:
>
> ok..will look into that..I used both my accounts but couldnt connect using
> any.
>
> OK, I've just reset the passwords on both to the original passwords I sent
> you on 25 May
>
> I see two other students connected to the SIP proxy so I believe it is
> working normally, please let me know if you still have problems.
>
> Regards,
>
> Daniel
>
> ___
> telepathy mailing list
> telepathy@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/telepathy
>
>


-- 


*Balram P MenonTech Head | Excel 2016*
Computer Science and Engineering (Batch: 2013-17)
Govt. Model Engineering College, Kochi-21

[image: ☎]: 8129130866
✉: balb...@gmail.com 
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Daniel Pocock]

On 07/06/16 09:59, Balram Pariyarath wrote:
> ok..will look into that..I used both my accounts but couldnt connect
> using any. 
>
OK, I've just reset the passwords on both to the original passwords I
sent you on 25 May

I see two other students connected to the SIP proxy so I believe it is
working normally, please let me know if you still have problems.

Regards,

Daniel
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

ok..will look into that..I used both my accounts but couldnt connect using
any.

On Sun, Jun 5, 2016 at 12:40 AM, Daniel Pocock  wrote:

>
>
> On 03/06/16 05:12, Balram Pariyarath wrote:
> > Not much. I used the tools like bustle to check if resiprocate is
> > working while try to connect to SIP server. It is working. I have
> > attached the bustle report once again.
> > Since I have not started to code, I thought I'll go through the files
> > till you reply. Am also trying to run it on another system using Ubuntu.
> > I also tried to login to Lumicall using the credential, but it didnt
> > work then. But I have got to check on it once more.
> > Am currently working on the latest version of resiprocate.
> >
>
> Did you try only one of the accounts I created for you or all of them?
>
> I can try changing the passwords for you, but do you see an
> authentication error?  Look for the SIP logs from reSIProcate, if you
> enable the DEBUG or STACK level logs you should see each SIP request and
> response, including error codes.
>
> Regards,
>
> Daniel
>



-- 


*Balram P MenonTech Head | Excel 2016*
Computer Science and Engineering (Batch: 2013-17)
Govt. Model Engineering College, Kochi-21

[image: ☎]: 8129130866
✉: balb...@gmail.com 
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Daniel Pocock]

On 03/06/16 05:12, Balram Pariyarath wrote:
> Not much. I used the tools like bustle to check if resiprocate is
> working while try to connect to SIP server. It is working. I have
> attached the bustle report once again.
> Since I have not started to code, I thought I'll go through the files
> till you reply. Am also trying to run it on another system using Ubuntu.
> I also tried to login to Lumicall using the credential, but it didnt
> work then. But I have got to check on it once more.
> Am currently working on the latest version of resiprocate.
> 

Did you try only one of the accounts I created for you or all of them?

I can try changing the passwords for you, but do you see an
authentication error?  Look for the SIP logs from reSIProcate, if you
enable the DEBUG or STACK level logs you should see each SIP request and
response, including error codes.

Regards,

Daniel
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

Not much. I used the tools like bustle to check if resiprocate is working
while try to connect to SIP server. It is working. I have attached the
bustle report once again.
Since I have not started to code, I thought I'll go through the files till
you reply. Am also trying to run it on another system using Ubuntu.
I also tried to login to Lumicall using the credential, but it didnt work
then. But I have got to check on it once more.
Am currently working on the latest version of resiprocate.

On Fri, Jun 3, 2016 at 2:10 AM, Daniel Pocock  wrote:

>
> We can discuss the telepathy-specific issues like this on the telepathy
> mailing list.  Please only use the resiprocate mailing list for things
> exclusive to the reSIProcate code, I dropped it from CC.
>
> Did you already make further progress with this?
>
>
> On 01/06/16 00:36, Balram Pariyarath wrote:
> > Hey guys, when I run ./telepathy-resiprocate, it shows:
> >
> > tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not
> > containing ConnMgrParamFlagHasDefault and a default value, updating
> > flags to contain ConnMgrParamFlagHasDefault
> > tp-qt 0.9.6.1 DEBUG: Interface
> > "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
> > tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
> > tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
> > "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
> > "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> > "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> > tp-qt 0.9.6.1 DEBUG: Registered object
> > "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus
> > name "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> > tp-qt 0.9.6.1 DEBUG: Registering CM
> > "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> > "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> > tp-qt 0.9.6.1 DEBUG: Registered object
> > "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> > "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> >
> > But when I choose to connect to my SIP account, it doesnt happens. Says
> > its unable to connect to the SIP account. No reason specified.
> >
> >
> >
> > --
> >
> > *Balram P Menon
> > Tech Head | Excel 2016*
> > Computer Science and Engineering (Batch: 2013-17)
> > Govt. Model Engineering College, Kochi-21
> >
> > ☎: 8129130866
> > ✉: balb...@gmail.com 
> >
> ___
> telepathy mailing list
> telepathy@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/telepathy
>



-- 


*Balram P MenonTech Head | Excel 2016*
Computer Science and Engineering (Batch: 2013-17)
Govt. Model Engineering College, Kochi-21

[image: ☎]: 8129130866
✉: balb...@gmail.com 


bustle_balram_resip.pdf
Description: Adobe PDF document
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Daniel Pocock]

We can discuss the telepathy-specific issues like this on the telepathy
mailing list.  Please only use the resiprocate mailing list for things
exclusive to the reSIProcate code, I dropped it from CC.

Did you already make further progress with this?


On 01/06/16 00:36, Balram Pariyarath wrote:
> Hey guys, when I run ./telepathy-resiprocate, it shows:
> 
> tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not
> containing ConnMgrParamFlagHasDefault and a default value, updating
> flags to contain ConnMgrParamFlagHasDefault  
> tp-qt 0.9.6.1 DEBUG: Interface
> "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged  
> tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM  
> tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"  
> tp-qt 0.9.6.1 DEBUG: Registered object
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus
> name "org.freedesktop.Telepathy.ConnectionManager.resiprocate"  
> tp-qt 0.9.6.1 DEBUG: Registering CM
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"  
> tp-qt 0.9.6.1 DEBUG: Registered object
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate" 
> 
> But when I choose to connect to my SIP account, it doesnt happens. Says
> its unable to connect to the SIP account. No reason specified.
> 
> 
> 
> -- 
> 
> *Balram P Menon
> Tech Head | Excel 2016*
> Computer Science and Engineering (Batch: 2013-17)
> Govt. Model Engineering College, Kochi-21
> 
> ☎: 8129130866
> ✉: balb...@gmail.com 
> 
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

ok..I'll check them once more.

On Wed, Jun 1, 2016 at 11:13 PM, Mateus Bellomo 
wrote:

> I think this errors are related to bustle not resiprocate.
>
> One more thing: when you run bustle, if you select some line in the debug
> you could see more info about that debug. Maybe if you select the ones
> related to resiprocate (Reconnect or ...RequestConnection) you could
> find some helpful info about this problem.
>
> 2016-06-01 14:35 GMT-03:00 Balram Pariyarath :
>
>> thanks man! :)
>>
>> this is something I got when I ran bustle &
>>
>>  Gtk-Message: Failed to load module "canberra-gtk-module"
>> Error creating proxy: The connection is closed (g-io-error-quark, 18)
>> Error creating proxy: The connection is closed (g-io-error-quark, 18)
>> Error creating proxy: The connection is closed (g-io-error-quark, 18)
>> Error creating proxy: The connection is closed (g-io-error-quark, 18)
>> Error creating proxy: The connection is closed (g-io-error-quark, 18)
>>
>> I hope the package doesn't have anything to do with resiprocate.
>>
>> On Wed, Jun 1, 2016 at 10:51 PM, Mateus Bellomo 
>> wrote:
>>
>>> It seems that you are using the telepathy-resiprocate actually. The
>>> strange thing is that you should be able to see some debug when you try to
>>> connect empathy. Maybe Daniel could help you more. If I have another idea I
>>> will tell you...
>>>
>>> 2016-06-01 14:09 GMT-03:00 Balram Pariyarath :
>>>
 Hi, I ran bustle, then tried connecting to my SIP account using empathy.
 I have exported the bustle output. can you please check it?

 On Wed, Jun 1, 2016 at 10:24 PM, Mateus Bellomo <
 mateusbell...@gmail.com> wrote:

> Maybe you can try with bustle to see if empathy is actually
> communicating with telepathy-resiprocate.
>
> $ bustle &
> $ libtool --mode=execute ./apps/telepathy/telepathy-resiprocate
>
>
> 2016-06-01 13:46 GMT-03:00 Balram Pariyarath :
>
>> Yup.
>>
>> On Wed, Jun 1, 2016 at 10:10 PM, Mateus Bellomo <
>> mateusbell...@gmail.com> wrote:
>>
>>> Did you get same output (couldn't connect) with both SIP options?
>>>
>>> 2016-06-01 13:36 GMT-03:00 Balram Pariyarath :
>>>
 I too have got 2 SIP options and I also used the first one. I tried
 both commands. I dont have anything on sofiasip installed on my system 
 and
 for rakia I still get,

 dpkg: dependency problems prevent removal of telepathy-rakia:
  gnome depends on telepathy-rakia.

 dpkg: error processing package telepathy-rakia (--purge):
  dependency problems - not removing
 Errors were encountered while processing:
  telepathy-rakia


 On Wed, Jun 1, 2016 at 5:39 PM, Mateus Bellomo <
 mateusbell...@gmail.com> wrote:

> I also remove my rakia and sofiasip packages to test and I could
> do it with this:
>
> $ dpkg --purge autoremove telepathy-sofiasip
> $ dpkg --purge autoremove telepathy-rakia
>
> the autoremove option removes unused dependencies.
>
> 2016-06-01 9:02 GMT-03:00 Mateus Bellomo 
> :
>
>> How many SIP accounts to register did you see (at the menu to add
>> new account)?
>>
>> I've installed telepathy-rakia and telepathy-sofiasip and when I
>> try to add an account I see two SIP options: the first one I know is 
>> for
>> resiprocate and the other I don't know if it's for rakia or sofiasip.
>>
>>
>> 2016-06-01 0:54 GMT-03:00 Balram Pariyarath :
>>
>>> Hi Mateus,
>>> I am running telepathy on Debian. I followed your wiki and
>>> threads to configure telepathy in empathy. So I think am using SIP 
>>> from
>>> resiprocate (am not sure about it though).
>>>
>>> I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what
>>> it showed
>>> pi  telepathy-rakia   0.8.0-3
>>>amd64SIP connection manager for the Telepathy
>>> framework
>>>
>>> I dont have sofiasip installed, but when I tried to purge
>>> rakia,  dpkg --purge telepathy-rakia (as a su), it shows
>>> dpkg: dependency problems prevent removal of telepathy-rakia:
>>>  gnome depends on telepathy-rakia.
>>>
>>> dpkg: error processing package telepathy-rakia (--purge):
>>>  dependency problems - not removing
>>> Errors were encountered while processing:
>>>  telepathy-rakia
>>>
>>>
>>>
>>> On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo <
>>> 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Mateus Bellomo]

I think this errors are related to bustle not resiprocate.

One more thing: when you run bustle, if you select some line in the debug
you could see more info about that debug. Maybe if you select the ones
related to resiprocate (Reconnect or ...RequestConnection) you could
find some helpful info about this problem.

2016-06-01 14:35 GMT-03:00 Balram Pariyarath :

> thanks man! :)
>
> this is something I got when I ran bustle &
>
>  Gtk-Message: Failed to load module "canberra-gtk-module"
> Error creating proxy: The connection is closed (g-io-error-quark, 18)
> Error creating proxy: The connection is closed (g-io-error-quark, 18)
> Error creating proxy: The connection is closed (g-io-error-quark, 18)
> Error creating proxy: The connection is closed (g-io-error-quark, 18)
> Error creating proxy: The connection is closed (g-io-error-quark, 18)
>
> I hope the package doesn't have anything to do with resiprocate.
>
> On Wed, Jun 1, 2016 at 10:51 PM, Mateus Bellomo 
> wrote:
>
>> It seems that you are using the telepathy-resiprocate actually. The
>> strange thing is that you should be able to see some debug when you try to
>> connect empathy. Maybe Daniel could help you more. If I have another idea I
>> will tell you...
>>
>> 2016-06-01 14:09 GMT-03:00 Balram Pariyarath :
>>
>>> Hi, I ran bustle, then tried connecting to my SIP account using empathy.
>>> I have exported the bustle output. can you please check it?
>>>
>>> On Wed, Jun 1, 2016 at 10:24 PM, Mateus Bellomo >> > wrote:
>>>
 Maybe you can try with bustle to see if empathy is actually
 communicating with telepathy-resiprocate.

 $ bustle &
 $ libtool --mode=execute ./apps/telepathy/telepathy-resiprocate


 2016-06-01 13:46 GMT-03:00 Balram Pariyarath :

> Yup.
>
> On Wed, Jun 1, 2016 at 10:10 PM, Mateus Bellomo <
> mateusbell...@gmail.com> wrote:
>
>> Did you get same output (couldn't connect) with both SIP options?
>>
>> 2016-06-01 13:36 GMT-03:00 Balram Pariyarath :
>>
>>> I too have got 2 SIP options and I also used the first one. I tried
>>> both commands. I dont have anything on sofiasip installed on my system 
>>> and
>>> for rakia I still get,
>>>
>>> dpkg: dependency problems prevent removal of telepathy-rakia:
>>>  gnome depends on telepathy-rakia.
>>>
>>> dpkg: error processing package telepathy-rakia (--purge):
>>>  dependency problems - not removing
>>> Errors were encountered while processing:
>>>  telepathy-rakia
>>>
>>>
>>> On Wed, Jun 1, 2016 at 5:39 PM, Mateus Bellomo <
>>> mateusbell...@gmail.com> wrote:
>>>
 I also remove my rakia and sofiasip packages to test and I could do
 it with this:

 $ dpkg --purge autoremove telepathy-sofiasip
 $ dpkg --purge autoremove telepathy-rakia

 the autoremove option removes unused dependencies.

 2016-06-01 9:02 GMT-03:00 Mateus Bellomo :

> How many SIP accounts to register did you see (at the menu to add
> new account)?
>
> I've installed telepathy-rakia and telepathy-sofiasip and when I
> try to add an account I see two SIP options: the first one I know is 
> for
> resiprocate and the other I don't know if it's for rakia or sofiasip.
>
>
> 2016-06-01 0:54 GMT-03:00 Balram Pariyarath :
>
>> Hi Mateus,
>> I am running telepathy on Debian. I followed your wiki and
>> threads to configure telepathy in empathy. So I think am using SIP 
>> from
>> resiprocate (am not sure about it though).
>>
>> I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what
>> it showed
>> pi  telepathy-rakia   0.8.0-3
>>  amd64SIP connection manager for the Telepathy 
>> framework
>>
>> I dont have sofiasip installed, but when I tried to purge
>> rakia,  dpkg --purge telepathy-rakia (as a su), it shows
>> dpkg: dependency problems prevent removal of telepathy-rakia:
>>  gnome depends on telepathy-rakia.
>>
>> dpkg: error processing package telepathy-rakia (--purge):
>>  dependency problems - not removing
>> Errors were encountered while processing:
>>  telepathy-rakia
>>
>>
>>
>> On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo <
>> mateusbell...@gmail.com> wrote:
>>
>>> Hello Balram,
>>>
>>> when I try to connect a SIP account with rakia or sofia-sip I
>>> get the same error (I don't know why). But you should see some 
>>> debug going
>>> on if 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

thanks man! :)

this is something I got when I ran bustle &

 Gtk-Message: Failed to load module "canberra-gtk-module"
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)

I hope the package doesn't have anything to do with resiprocate.

On Wed, Jun 1, 2016 at 10:51 PM, Mateus Bellomo 
wrote:

> It seems that you are using the telepathy-resiprocate actually. The
> strange thing is that you should be able to see some debug when you try to
> connect empathy. Maybe Daniel could help you more. If I have another idea I
> will tell you...
>
> 2016-06-01 14:09 GMT-03:00 Balram Pariyarath :
>
>> Hi, I ran bustle, then tried connecting to my SIP account using empathy.
>> I have exported the bustle output. can you please check it?
>>
>> On Wed, Jun 1, 2016 at 10:24 PM, Mateus Bellomo 
>> wrote:
>>
>>> Maybe you can try with bustle to see if empathy is actually
>>> communicating with telepathy-resiprocate.
>>>
>>> $ bustle &
>>> $ libtool --mode=execute ./apps/telepathy/telepathy-resiprocate
>>>
>>>
>>> 2016-06-01 13:46 GMT-03:00 Balram Pariyarath :
>>>
 Yup.

 On Wed, Jun 1, 2016 at 10:10 PM, Mateus Bellomo <
 mateusbell...@gmail.com> wrote:

> Did you get same output (couldn't connect) with both SIP options?
>
> 2016-06-01 13:36 GMT-03:00 Balram Pariyarath :
>
>> I too have got 2 SIP options and I also used the first one. I tried
>> both commands. I dont have anything on sofiasip installed on my system 
>> and
>> for rakia I still get,
>>
>> dpkg: dependency problems prevent removal of telepathy-rakia:
>>  gnome depends on telepathy-rakia.
>>
>> dpkg: error processing package telepathy-rakia (--purge):
>>  dependency problems - not removing
>> Errors were encountered while processing:
>>  telepathy-rakia
>>
>>
>> On Wed, Jun 1, 2016 at 5:39 PM, Mateus Bellomo <
>> mateusbell...@gmail.com> wrote:
>>
>>> I also remove my rakia and sofiasip packages to test and I could do
>>> it with this:
>>>
>>> $ dpkg --purge autoremove telepathy-sofiasip
>>> $ dpkg --purge autoremove telepathy-rakia
>>>
>>> the autoremove option removes unused dependencies.
>>>
>>> 2016-06-01 9:02 GMT-03:00 Mateus Bellomo :
>>>
 How many SIP accounts to register did you see (at the menu to add
 new account)?

 I've installed telepathy-rakia and telepathy-sofiasip and when I
 try to add an account I see two SIP options: the first one I know is 
 for
 resiprocate and the other I don't know if it's for rakia or sofiasip.


 2016-06-01 0:54 GMT-03:00 Balram Pariyarath :

> Hi Mateus,
> I am running telepathy on Debian. I followed your wiki and threads
> to configure telepathy in empathy. So I think am using SIP from 
> resiprocate
> (am not sure about it though).
>
> I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what it
> showed
> pi  telepathy-rakia   0.8.0-3
>  amd64SIP connection manager for the Telepathy 
> framework
>
> I dont have sofiasip installed, but when I tried to purge
> rakia,  dpkg --purge telepathy-rakia (as a su), it shows
> dpkg: dependency problems prevent removal of telepathy-rakia:
>  gnome depends on telepathy-rakia.
>
> dpkg: error processing package telepathy-rakia (--purge):
>  dependency problems - not removing
> Errors were encountered while processing:
>  telepathy-rakia
>
>
>
> On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo <
> mateusbell...@gmail.com> wrote:
>
>> Hello Balram,
>>
>> when I try to connect a SIP account with rakia or sofia-sip I get
>> the same error (I don't know why). But you should see some debug 
>> going on
>> if you do try to connect with resiproctate. Are you sure that you 
>> are using
>> SIP from resiprocate?
>>
>> If you do:
>>
>> $ dpkg -l | egrep 'telepathy-(sofia|rakia)'
>>
>> you could see if you have sofiasip or rakia installed. In that
>> case you could purge them.
>>
>> ps: in ubuntu I couldn't connect resiprocate with empathy (It
>> wont show an option for SIP account).
>>
>>
>> 2016-05-31 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Mateus Bellomo]

It seems that you are using the telepathy-resiprocate actually. The strange
thing is that you should be able to see some debug when you try to connect
empathy. Maybe Daniel could help you more. If I have another idea I will
tell you...

2016-06-01 14:09 GMT-03:00 Balram Pariyarath :

> Hi, I ran bustle, then tried connecting to my SIP account using empathy.
> I have exported the bustle output. can you please check it?
>
> On Wed, Jun 1, 2016 at 10:24 PM, Mateus Bellomo 
> wrote:
>
>> Maybe you can try with bustle to see if empathy is actually communicating
>> with telepathy-resiprocate.
>>
>> $ bustle &
>> $ libtool --mode=execute ./apps/telepathy/telepathy-resiprocate
>>
>>
>> 2016-06-01 13:46 GMT-03:00 Balram Pariyarath :
>>
>>> Yup.
>>>
>>> On Wed, Jun 1, 2016 at 10:10 PM, Mateus Bellomo >> > wrote:
>>>
 Did you get same output (couldn't connect) with both SIP options?

 2016-06-01 13:36 GMT-03:00 Balram Pariyarath :

> I too have got 2 SIP options and I also used the first one. I tried
> both commands. I dont have anything on sofiasip installed on my system and
> for rakia I still get,
>
> dpkg: dependency problems prevent removal of telepathy-rakia:
>  gnome depends on telepathy-rakia.
>
> dpkg: error processing package telepathy-rakia (--purge):
>  dependency problems - not removing
> Errors were encountered while processing:
>  telepathy-rakia
>
>
> On Wed, Jun 1, 2016 at 5:39 PM, Mateus Bellomo <
> mateusbell...@gmail.com> wrote:
>
>> I also remove my rakia and sofiasip packages to test and I could do
>> it with this:
>>
>> $ dpkg --purge autoremove telepathy-sofiasip
>> $ dpkg --purge autoremove telepathy-rakia
>>
>> the autoremove option removes unused dependencies.
>>
>> 2016-06-01 9:02 GMT-03:00 Mateus Bellomo :
>>
>>> How many SIP accounts to register did you see (at the menu to add
>>> new account)?
>>>
>>> I've installed telepathy-rakia and telepathy-sofiasip and when I try
>>> to add an account I see two SIP options: the first one I know is for
>>> resiprocate and the other I don't know if it's for rakia or sofiasip.
>>>
>>>
>>> 2016-06-01 0:54 GMT-03:00 Balram Pariyarath :
>>>
 Hi Mateus,
 I am running telepathy on Debian. I followed your wiki and threads
 to configure telepathy in empathy. So I think am using SIP from 
 resiprocate
 (am not sure about it though).

 I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what it
 showed
 pi  telepathy-rakia   0.8.0-3
amd64SIP connection manager for the Telepathy 
 framework

 I dont have sofiasip installed, but when I tried to purge
 rakia,  dpkg --purge telepathy-rakia (as a su), it shows
 dpkg: dependency problems prevent removal of telepathy-rakia:
  gnome depends on telepathy-rakia.

 dpkg: error processing package telepathy-rakia (--purge):
  dependency problems - not removing
 Errors were encountered while processing:
  telepathy-rakia



 On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo <
 mateusbell...@gmail.com> wrote:

> Hello Balram,
>
> when I try to connect a SIP account with rakia or sofia-sip I get
> the same error (I don't know why). But you should see some debug 
> going on
> if you do try to connect with resiproctate. Are you sure that you are 
> using
> SIP from resiprocate?
>
> If you do:
>
> $ dpkg -l | egrep 'telepathy-(sofia|rakia)'
>
> you could see if you have sofiasip or rakia installed. In that
> case you could purge them.
>
> ps: in ubuntu I couldn't connect resiprocate with empathy (It wont
> show an option for SIP account).
>
>
> 2016-05-31 19:36 GMT-03:00 Balram Pariyarath :
>
>> Hey guys, when I run ./telepathy-resiprocate, it shows:
>>
>> tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not
>> containing ConnMgrParamFlagHasDefault and a default value, updating 
>> flags
>> to contain ConnMgrParamFlagHasDefault
>> tp-qt 0.9.6.1 DEBUG: Interface
>> "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
>> tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
>> tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

Hi, I ran bustle, then tried connecting to my SIP account using empathy.
I have exported the bustle output. can you please check it?

On Wed, Jun 1, 2016 at 10:24 PM, Mateus Bellomo 
wrote:

> Maybe you can try with bustle to see if empathy is actually communicating
> with telepathy-resiprocate.
>
> $ bustle &
> $ libtool --mode=execute ./apps/telepathy/telepathy-resiprocate
>
>
> 2016-06-01 13:46 GMT-03:00 Balram Pariyarath :
>
>> Yup.
>>
>> On Wed, Jun 1, 2016 at 10:10 PM, Mateus Bellomo 
>> wrote:
>>
>>> Did you get same output (couldn't connect) with both SIP options?
>>>
>>> 2016-06-01 13:36 GMT-03:00 Balram Pariyarath :
>>>
 I too have got 2 SIP options and I also used the first one. I tried
 both commands. I dont have anything on sofiasip installed on my system and
 for rakia I still get,

 dpkg: dependency problems prevent removal of telepathy-rakia:
  gnome depends on telepathy-rakia.

 dpkg: error processing package telepathy-rakia (--purge):
  dependency problems - not removing
 Errors were encountered while processing:
  telepathy-rakia


 On Wed, Jun 1, 2016 at 5:39 PM, Mateus Bellomo  wrote:

> I also remove my rakia and sofiasip packages to test and I could do it
> with this:
>
> $ dpkg --purge autoremove telepathy-sofiasip
> $ dpkg --purge autoremove telepathy-rakia
>
> the autoremove option removes unused dependencies.
>
> 2016-06-01 9:02 GMT-03:00 Mateus Bellomo :
>
>> How many SIP accounts to register did you see (at the menu to add new
>> account)?
>>
>> I've installed telepathy-rakia and telepathy-sofiasip and when I try
>> to add an account I see two SIP options: the first one I know is for
>> resiprocate and the other I don't know if it's for rakia or sofiasip.
>>
>>
>> 2016-06-01 0:54 GMT-03:00 Balram Pariyarath :
>>
>>> Hi Mateus,
>>> I am running telepathy on Debian. I followed your wiki and threads
>>> to configure telepathy in empathy. So I think am using SIP from 
>>> resiprocate
>>> (am not sure about it though).
>>>
>>> I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what it
>>> showed
>>> pi  telepathy-rakia   0.8.0-3
>>>amd64SIP connection manager for the Telepathy 
>>> framework
>>>
>>> I dont have sofiasip installed, but when I tried to purge
>>> rakia,  dpkg --purge telepathy-rakia (as a su), it shows
>>> dpkg: dependency problems prevent removal of telepathy-rakia:
>>>  gnome depends on telepathy-rakia.
>>>
>>> dpkg: error processing package telepathy-rakia (--purge):
>>>  dependency problems - not removing
>>> Errors were encountered while processing:
>>>  telepathy-rakia
>>>
>>>
>>>
>>> On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo <
>>> mateusbell...@gmail.com> wrote:
>>>
 Hello Balram,

 when I try to connect a SIP account with rakia or sofia-sip I get
 the same error (I don't know why). But you should see some debug going 
 on
 if you do try to connect with resiproctate. Are you sure that you are 
 using
 SIP from resiprocate?

 If you do:

 $ dpkg -l | egrep 'telepathy-(sofia|rakia)'

 you could see if you have sofiasip or rakia installed. In that case
 you could purge them.

 ps: in ubuntu I couldn't connect resiprocate with empathy (It wont
 show an option for SIP account).


 2016-05-31 19:36 GMT-03:00 Balram Pariyarath :

> Hey guys, when I run ./telepathy-resiprocate, it shows:
>
> tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not
> containing ConnMgrParamFlagHasDefault and a default value, updating 
> flags
> to contain ConnMgrParamFlagHasDefault
> tp-qt 0.9.6.1 DEBUG: Interface
> "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
> tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
> tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> tp-qt 0.9.6.1 DEBUG: Registered object
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus 
> name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> tp-qt 0.9.6.1 DEBUG: Registering CM
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Mateus Bellomo]

Maybe you can try with bustle to see if empathy is actually communicating
with telepathy-resiprocate.

$ bustle &
$ libtool --mode=execute ./apps/telepathy/telepathy-resiprocate


2016-06-01 13:46 GMT-03:00 Balram Pariyarath :

> Yup.
>
> On Wed, Jun 1, 2016 at 10:10 PM, Mateus Bellomo 
> wrote:
>
>> Did you get same output (couldn't connect) with both SIP options?
>>
>> 2016-06-01 13:36 GMT-03:00 Balram Pariyarath :
>>
>>> I too have got 2 SIP options and I also used the first one. I tried both
>>> commands. I dont have anything on sofiasip installed on my system and for
>>> rakia I still get,
>>>
>>> dpkg: dependency problems prevent removal of telepathy-rakia:
>>>  gnome depends on telepathy-rakia.
>>>
>>> dpkg: error processing package telepathy-rakia (--purge):
>>>  dependency problems - not removing
>>> Errors were encountered while processing:
>>>  telepathy-rakia
>>>
>>>
>>> On Wed, Jun 1, 2016 at 5:39 PM, Mateus Bellomo 
>>> wrote:
>>>
 I also remove my rakia and sofiasip packages to test and I could do it
 with this:

 $ dpkg --purge autoremove telepathy-sofiasip
 $ dpkg --purge autoremove telepathy-rakia

 the autoremove option removes unused dependencies.

 2016-06-01 9:02 GMT-03:00 Mateus Bellomo :

> How many SIP accounts to register did you see (at the menu to add new
> account)?
>
> I've installed telepathy-rakia and telepathy-sofiasip and when I try
> to add an account I see two SIP options: the first one I know is for
> resiprocate and the other I don't know if it's for rakia or sofiasip.
>
>
> 2016-06-01 0:54 GMT-03:00 Balram Pariyarath :
>
>> Hi Mateus,
>> I am running telepathy on Debian. I followed your wiki and threads to
>> configure telepathy in empathy. So I think am using SIP from resiprocate
>> (am not sure about it though).
>>
>> I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what it
>> showed
>> pi  telepathy-rakia   0.8.0-3
>>  amd64SIP connection manager for the Telepathy framework
>>
>> I dont have sofiasip installed, but when I tried to purge
>> rakia,  dpkg --purge telepathy-rakia (as a su), it shows
>> dpkg: dependency problems prevent removal of telepathy-rakia:
>>  gnome depends on telepathy-rakia.
>>
>> dpkg: error processing package telepathy-rakia (--purge):
>>  dependency problems - not removing
>> Errors were encountered while processing:
>>  telepathy-rakia
>>
>>
>>
>> On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo <
>> mateusbell...@gmail.com> wrote:
>>
>>> Hello Balram,
>>>
>>> when I try to connect a SIP account with rakia or sofia-sip I get
>>> the same error (I don't know why). But you should see some debug going 
>>> on
>>> if you do try to connect with resiproctate. Are you sure that you are 
>>> using
>>> SIP from resiprocate?
>>>
>>> If you do:
>>>
>>> $ dpkg -l | egrep 'telepathy-(sofia|rakia)'
>>>
>>> you could see if you have sofiasip or rakia installed. In that case
>>> you could purge them.
>>>
>>> ps: in ubuntu I couldn't connect resiprocate with empathy (It wont
>>> show an option for SIP account).
>>>
>>>
>>> 2016-05-31 19:36 GMT-03:00 Balram Pariyarath :
>>>
 Hey guys, when I run ./telepathy-resiprocate, it shows:

 tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not
 containing ConnMgrParamFlagHasDefault and a default value, updating 
 flags
 to contain ConnMgrParamFlagHasDefault
 tp-qt 0.9.6.1 DEBUG: Interface
 "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
 tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
 tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
 "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
 "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
 "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
 tp-qt 0.9.6.1 DEBUG: Registered object
 "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus 
 name
 "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
 tp-qt 0.9.6.1 DEBUG: Registering CM
 "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
 "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
 tp-qt 0.9.6.1 DEBUG: Registered object
 "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
 "org.freedesktop.Telepathy.ConnectionManager.resiprocate"

 But when I choose to connect to my SIP account, it doesnt happens.
 Says its unable 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Mateus Bellomo]

Did you get same output (couldn't connect) with both SIP options?

2016-06-01 13:36 GMT-03:00 Balram Pariyarath :

> I too have got 2 SIP options and I also used the first one. I tried both
> commands. I dont have anything on sofiasip installed on my system and for
> rakia I still get,
>
> dpkg: dependency problems prevent removal of telepathy-rakia:
>  gnome depends on telepathy-rakia.
>
> dpkg: error processing package telepathy-rakia (--purge):
>  dependency problems - not removing
> Errors were encountered while processing:
>  telepathy-rakia
>
>
> On Wed, Jun 1, 2016 at 5:39 PM, Mateus Bellomo 
> wrote:
>
>> I also remove my rakia and sofiasip packages to test and I could do it
>> with this:
>>
>> $ dpkg --purge autoremove telepathy-sofiasip
>> $ dpkg --purge autoremove telepathy-rakia
>>
>> the autoremove option removes unused dependencies.
>>
>> 2016-06-01 9:02 GMT-03:00 Mateus Bellomo :
>>
>>> How many SIP accounts to register did you see (at the menu to add new
>>> account)?
>>>
>>> I've installed telepathy-rakia and telepathy-sofiasip and when I try to
>>> add an account I see two SIP options: the first one I know is for
>>> resiprocate and the other I don't know if it's for rakia or sofiasip.
>>>
>>>
>>> 2016-06-01 0:54 GMT-03:00 Balram Pariyarath :
>>>
 Hi Mateus,
 I am running telepathy on Debian. I followed your wiki and threads to
 configure telepathy in empathy. So I think am using SIP from resiprocate
 (am not sure about it though).

 I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what it
 showed
 pi  telepathy-rakia   0.8.0-3
amd64SIP connection manager for the Telepathy framework

 I dont have sofiasip installed, but when I tried to purge rakia,  dpkg
 --purge telepathy-rakia (as a su), it shows
 dpkg: dependency problems prevent removal of telepathy-rakia:
  gnome depends on telepathy-rakia.

 dpkg: error processing package telepathy-rakia (--purge):
  dependency problems - not removing
 Errors were encountered while processing:
  telepathy-rakia



 On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo  wrote:

> Hello Balram,
>
> when I try to connect a SIP account with rakia or sofia-sip I get the
> same error (I don't know why). But you should see some debug going on if
> you do try to connect with resiproctate. Are you sure that you are using
> SIP from resiprocate?
>
> If you do:
>
> $ dpkg -l | egrep 'telepathy-(sofia|rakia)'
>
> you could see if you have sofiasip or rakia installed. In that case
> you could purge them.
>
> ps: in ubuntu I couldn't connect resiprocate with empathy (It wont
> show an option for SIP account).
>
>
> 2016-05-31 19:36 GMT-03:00 Balram Pariyarath :
>
>> Hey guys, when I run ./telepathy-resiprocate, it shows:
>>
>> tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not
>> containing ConnMgrParamFlagHasDefault and a default value, updating flags
>> to contain ConnMgrParamFlagHasDefault
>> tp-qt 0.9.6.1 DEBUG: Interface
>> "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
>> tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
>> tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>> tp-qt 0.9.6.1 DEBUG: Registered object
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus 
>> name
>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>> tp-qt 0.9.6.1 DEBUG: Registering CM
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>> tp-qt 0.9.6.1 DEBUG: Registered object
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>>
>> But when I choose to connect to my SIP account, it doesnt happens.
>> Says its unable to connect to the SIP account. No reason specified.
>>
>>
>>
>> --
>>
>>
>> *Balram P MenonTech Head | Excel 2016*
>> Computer Science and Engineering (Batch: 2013-17)
>> Govt. Model Engineering College, Kochi-21
>>
>> [image: ☎]: 8129130866
>> ✉: balb...@gmail.com 
>>
>> ___
>> telepathy mailing list
>> telepathy@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/telepathy
>>
>>
>
> 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

I too have got 2 SIP options and I also used the first one. I tried both
commands. I dont have anything on sofiasip installed on my system and for
rakia I still get,

dpkg: dependency problems prevent removal of telepathy-rakia:
 gnome depends on telepathy-rakia.

dpkg: error processing package telepathy-rakia (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 telepathy-rakia


On Wed, Jun 1, 2016 at 5:39 PM, Mateus Bellomo 
wrote:

> I also remove my rakia and sofiasip packages to test and I could do it
> with this:
>
> $ dpkg --purge autoremove telepathy-sofiasip
> $ dpkg --purge autoremove telepathy-rakia
>
> the autoremove option removes unused dependencies.
>
> 2016-06-01 9:02 GMT-03:00 Mateus Bellomo :
>
>> How many SIP accounts to register did you see (at the menu to add new
>> account)?
>>
>> I've installed telepathy-rakia and telepathy-sofiasip and when I try to
>> add an account I see two SIP options: the first one I know is for
>> resiprocate and the other I don't know if it's for rakia or sofiasip.
>>
>>
>> 2016-06-01 0:54 GMT-03:00 Balram Pariyarath :
>>
>>> Hi Mateus,
>>> I am running telepathy on Debian. I followed your wiki and threads to
>>> configure telepathy in empathy. So I think am using SIP from resiprocate
>>> (am not sure about it though).
>>>
>>> I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what it showed
>>> pi  telepathy-rakia   0.8.0-3
>>>amd64SIP connection manager for the Telepathy framework
>>>
>>> I dont have sofiasip installed, but when I tried to purge rakia,  dpkg
>>> --purge telepathy-rakia (as a su), it shows
>>> dpkg: dependency problems prevent removal of telepathy-rakia:
>>>  gnome depends on telepathy-rakia.
>>>
>>> dpkg: error processing package telepathy-rakia (--purge):
>>>  dependency problems - not removing
>>> Errors were encountered while processing:
>>>  telepathy-rakia
>>>
>>>
>>>
>>> On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo 
>>> wrote:
>>>
 Hello Balram,

 when I try to connect a SIP account with rakia or sofia-sip I get the
 same error (I don't know why). But you should see some debug going on if
 you do try to connect with resiproctate. Are you sure that you are using
 SIP from resiprocate?

 If you do:

 $ dpkg -l | egrep 'telepathy-(sofia|rakia)'

 you could see if you have sofiasip or rakia installed. In that case you
 could purge them.

 ps: in ubuntu I couldn't connect resiprocate with empathy (It wont show
 an option for SIP account).


 2016-05-31 19:36 GMT-03:00 Balram Pariyarath :

> Hey guys, when I run ./telepathy-resiprocate, it shows:
>
> tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not
> containing ConnMgrParamFlagHasDefault and a default value, updating flags
> to contain ConnMgrParamFlagHasDefault
> tp-qt 0.9.6.1 DEBUG: Interface
> "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
> tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
> tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> tp-qt 0.9.6.1 DEBUG: Registered object
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> tp-qt 0.9.6.1 DEBUG: Registering CM
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> tp-qt 0.9.6.1 DEBUG: Registered object
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>
> But when I choose to connect to my SIP account, it doesnt happens.
> Says its unable to connect to the SIP account. No reason specified.
>
>
>
> --
>
>
> *Balram P MenonTech Head | Excel 2016*
> Computer Science and Engineering (Batch: 2013-17)
> Govt. Model Engineering College, Kochi-21
>
> [image: ☎]: 8129130866
> ✉: balb...@gmail.com 
>
> ___
> telepathy mailing list
> telepathy@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/telepathy
>
>

 ___
 telepathy mailing list
 telepathy@lists.freedesktop.org
 https://lists.freedesktop.org/mailman/listinfo/telepathy


>>>
>>>
>>> --
>>>
>>>
>>> *Balram P MenonTech Head | Excel 2016*
>>> Computer Science and Engineering (Batch: 2013-17)
>>> Govt. Model 

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Mateus Bellomo]

How many SIP accounts to register did you see (at the menu to add new
account)?

I've installed telepathy-rakia and telepathy-sofiasip and when I try to add
an account I see two SIP options: the first one I know is for resiprocate
and the other I don't know if it's for rakia or sofiasip.

2016-06-01 0:54 GMT-03:00 Balram Pariyarath :

> Hi Mateus,
> I am running telepathy on Debian. I followed your wiki and threads to
> configure telepathy in empathy. So I think am using SIP from resiprocate
> (am not sure about it though).
>
> I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what it showed
> pi  telepathy-rakia   0.8.0-3
>  amd64SIP connection manager for the Telepathy framework
>
> I dont have sofiasip installed, but when I tried to purge rakia,  dpkg
> --purge telepathy-rakia (as a su), it shows
> dpkg: dependency problems prevent removal of telepathy-rakia:
>  gnome depends on telepathy-rakia.
>
> dpkg: error processing package telepathy-rakia (--purge):
>  dependency problems - not removing
> Errors were encountered while processing:
>  telepathy-rakia
>
>
>
> On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo 
> wrote:
>
>> Hello Balram,
>>
>> when I try to connect a SIP account with rakia or sofia-sip I get the
>> same error (I don't know why). But you should see some debug going on if
>> you do try to connect with resiproctate. Are you sure that you are using
>> SIP from resiprocate?
>>
>> If you do:
>>
>> $ dpkg -l | egrep 'telepathy-(sofia|rakia)'
>>
>> you could see if you have sofiasip or rakia installed. In that case you
>> could purge them.
>>
>> ps: in ubuntu I couldn't connect resiprocate with empathy (It wont show
>> an option for SIP account).
>>
>>
>> 2016-05-31 19:36 GMT-03:00 Balram Pariyarath :
>>
>>> Hey guys, when I run ./telepathy-resiprocate, it shows:
>>>
>>> tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not
>>> containing ConnMgrParamFlagHasDefault and a default value, updating flags
>>> to contain ConnMgrParamFlagHasDefault
>>> tp-qt 0.9.6.1 DEBUG: Interface
>>> "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
>>> tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
>>> tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
>>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
>>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>>> tp-qt 0.9.6.1 DEBUG: Registered object
>>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus name
>>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>>> tp-qt 0.9.6.1 DEBUG: Registering CM
>>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>>> tp-qt 0.9.6.1 DEBUG: Registered object
>>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>>>
>>> But when I choose to connect to my SIP account, it doesnt happens. Says
>>> its unable to connect to the SIP account. No reason specified.
>>>
>>>
>>>
>>> --
>>>
>>>
>>> *Balram P MenonTech Head | Excel 2016*
>>> Computer Science and Engineering (Batch: 2013-17)
>>> Govt. Model Engineering College, Kochi-21
>>>
>>> [image: ☎]: 8129130866
>>> ✉: balb...@gmail.com 
>>>
>>> ___
>>> telepathy mailing list
>>> telepathy@lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/telepathy
>>>
>>>
>>
>> ___
>> telepathy mailing list
>> telepathy@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/telepathy
>>
>>
>
>
> --
>
>
> *Balram P MenonTech Head | Excel 2016*
> Computer Science and Engineering (Batch: 2013-17)
> Govt. Model Engineering College, Kochi-21
>
> [image: ☎]: 8129130866
> ✉: balb...@gmail.com 
>
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Balram Pariyarath]

Hi Mateus,
I am running telepathy on Debian. I followed your wiki and threads to
configure telepathy in empathy. So I think am using SIP from resiprocate
(am not sure about it though).

I tried dpkg -l | egrep 'telepathy-(sofia|rakia)', this is what it showed
pi  telepathy-rakia   0.8.0-3
   amd64SIP connection manager for the Telepathy framework

I dont have sofiasip installed, but when I tried to purge rakia,  dpkg
--purge telepathy-rakia (as a su), it shows
dpkg: dependency problems prevent removal of telepathy-rakia:
 gnome depends on telepathy-rakia.

dpkg: error processing package telepathy-rakia (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 telepathy-rakia



On Wed, Jun 1, 2016 at 6:16 AM, Mateus Bellomo 
wrote:

> Hello Balram,
>
> when I try to connect a SIP account with rakia or sofia-sip I get the same
> error (I don't know why). But you should see some debug going on if you do
> try to connect with resiproctate. Are you sure that you are using SIP from
> resiprocate?
>
> If you do:
>
> $ dpkg -l | egrep 'telepathy-(sofia|rakia)'
>
> you could see if you have sofiasip or rakia installed. In that case you
> could purge them.
>
> ps: in ubuntu I couldn't connect resiprocate with empathy (It wont show an
> option for SIP account).
>
>
> 2016-05-31 19:36 GMT-03:00 Balram Pariyarath :
>
>> Hey guys, when I run ./telepathy-resiprocate, it shows:
>>
>> tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not containing
>> ConnMgrParamFlagHasDefault and a default value, updating flags to contain
>> ConnMgrParamFlagHasDefault
>> tp-qt 0.9.6.1 DEBUG: Interface
>> "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
>> tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
>> tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>> tp-qt 0.9.6.1 DEBUG: Registered object
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus name
>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>> tp-qt 0.9.6.1 DEBUG: Registering CM
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>> tp-qt 0.9.6.1 DEBUG: Registered object
>> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
>> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>>
>> But when I choose to connect to my SIP account, it doesnt happens. Says
>> its unable to connect to the SIP account. No reason specified.
>>
>>
>>
>> --
>>
>>
>> *Balram P MenonTech Head | Excel 2016*
>> Computer Science and Engineering (Batch: 2013-17)
>> Govt. Model Engineering College, Kochi-21
>>
>> [image: ☎]: 8129130866
>> ✉: balb...@gmail.com 
>>
>> ___
>> telepathy mailing list
>> telepathy@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/telepathy
>>
>>
>
> ___
> telepathy mailing list
> telepathy@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/telepathy
>
>


-- 


*Balram P MenonTech Head | Excel 2016*
Computer Science and Engineering (Batch: 2013-17)
Govt. Model Engineering College, Kochi-21

[image: ☎]: 8129130866
✉: balb...@gmail.com 
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy

Re: [Telepathy] [telepathy] - Cannot connect to SIP account using empathy

[Mateus Bellomo]

Hello Balram,

when I try to connect a SIP account with rakia or sofia-sip I get the same
error (I don't know why). But you should see some debug going on if you do
try to connect with resiproctate. Are you sure that you are using SIP from
resiprocate?

If you do:

$ dpkg -l | egrep 'telepathy-(sofia|rakia)'

you could see if you have sofiasip or rakia installed. In that case you
could purge them.

ps: in ubuntu I couldn't connect resiprocate with empathy (It wont show an
option for SIP account).


2016-05-31 19:36 GMT-03:00 Balram Pariyarath :

> Hey guys, when I run ./telepathy-resiprocate, it shows:
>
> tp-qt 0.9.6.1 DEBUG: Building ProtocolParameter with flags not containing
> ConnMgrParamFlagHasDefault and a default value, updating flags to contain
> ConnMgrParamFlagHasDefault
> tp-qt 0.9.6.1 DEBUG: Interface
> "org.freedesktop.Telepathy.Protocol.Interface.Addressing" plugged
> tp-qt 0.9.6.1 DEBUG: Protocol "sip" added to CM
> tp-qt 0.9.6.1 DEBUG: Registering protocol "sip" at path
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" for CM
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> tp-qt 0.9.6.1 DEBUG: Registered object
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate/sip" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> tp-qt 0.9.6.1 DEBUG: Registering CM
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
> tp-qt 0.9.6.1 DEBUG: Registered object
> "/org/freedesktop/Telepathy/ConnectionManager/resiprocate" at bus name
> "org.freedesktop.Telepathy.ConnectionManager.resiprocate"
>
> But when I choose to connect to my SIP account, it doesnt happens. Says
> its unable to connect to the SIP account. No reason specified.
>
>
>
> --
>
>
> *Balram P MenonTech Head | Excel 2016*
> Computer Science and Engineering (Batch: 2013-17)
> Govt. Model Engineering College, Kochi-21
>
> [image: ☎]: 8129130866
> ✉: balb...@gmail.com 
>
> ___
> telepathy mailing list
> telepathy@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/telepathy
>
>
___
telepathy mailing list
telepathy@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/telepathy