-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/29/09 10:07 AM, Paul Witty wrote:
> Peter Saint-Andre wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 9/29/09 5:15 AM, Pedro Melo wrote:
>>
>>> Hi,
>>>
>>> On 2009/09/29, at 11:20, Paul Witty wrote:
>>>
As a bit of b
Peter Saint-Andre wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/29/09 5:15 AM, Pedro Melo wrote:
Hi,
On 2009/09/29, at 11:20, Paul Witty wrote:
As a bit of background on what I'm trying to do, I'm implementing a
SIP to XMPP/Jingle gateway. The gateway is connected to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/29/09 5:15 AM, Pedro Melo wrote:
> Hi,
>
> On 2009/09/29, at 11:20, Paul Witty wrote:
>> As a bit of background on what I'm trying to do, I'm implementing a
>> SIP to XMPP/Jingle gateway. The gateway is connected to the XMPP
>> server as a compo
On Sep 29, 2009, at 7:06 AM, Paul Witty wrote:
Pedro Melo wrote:
Hi,
On 2009/09/29, at 11:20, Paul Witty wrote:
As a bit of background on what I'm trying to do, I'm implementing
a SIP to XMPP/Jingle gateway. The gateway is connected to the
XMPP server as a component (e.g. sipgw.xmppserve
Pedro Melo wrote:
Hi,
On 2009/09/29, at 11:20, Paul Witty wrote:
As a bit of background on what I'm trying to do, I'm implementing a
SIP to XMPP/Jingle gateway. The gateway is connected to the XMPP
server as a component (e.g. sipgw.xmppserver.com) and so the Jingle
client can make a call to
Hi,
On 2009/09/29, at 11:20, Paul Witty wrote:
As a bit of background on what I'm trying to do, I'm implementing a
SIP to XMPP/Jingle gateway. The gateway is connected to the XMPP
server as a component (e.g. sipgw.xmppserver.com) and so the Jingle
client can make a call to 1.2@sipgw.xm
Nathan Fritz wrote:
On Sep 25, 2009, at 4:33 AM, Paul Witty wrote:
Is there documented anywhere the rules of how presence information
works with components? e.g. can components subscribe to clients'
presence information, or send presence probes etc. Likewise, can a
component publish presen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/28/09 8:35 PM, Nathan Fritz wrote:
> On Sep 28, 2009, at 5:33 PM, Peter Saint-Andre wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 9/25/09 8:57 AM, Nathan Fritz wrote:
>>> On Sep 25, 2009, at 4:33 AM, Paul Witty wrote:
>>
On Sep 28, 2009, at 5:33 PM, Peter Saint-Andre
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/25/09 8:57 AM, Nathan Fritz wrote:
On Sep 25, 2009, at 4:33 AM, Paul Witty wrote:
Is there documented anywhere the rules of how presence information
works with components? e.g. can c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/25/09 8:57 AM, Nathan Fritz wrote:
> On Sep 25, 2009, at 4:33 AM, Paul Witty wrote:
>
>> Is there documented anywhere the rules of how presence information
>> works with components? e.g. can components subscribe to clients'
>> presence informat
On Sep 25, 2009, at 4:33 AM, Paul Witty wrote:
Is there documented anywhere the rules of how presence information
works with components? e.g. can components subscribe to clients'
presence information, or send presence probes etc. Likewise, can a
component publish presence, and clients su
Is there documented anywhere the rules of how presence information works
with components? e.g. can components subscribe to clients' presence
information, or send presence probes etc. Likewise, can a component
publish presence, and clients subscribe to its presence, but including
things like p
12 matches
Mail list logo
