Hi Juha,
On 06/13/2012 05:07 PM, Juha Heinanen wrote:
> i did some more presence tests with jitsi. when i start jitsi, it
> registers its sip uri, subscribes to its own presence.winfo and presence
> of another uri, and publishes its own presence.
>
> when i then quit jitsi, it un-publishes its ow
Hi Juha
thanks a lot.
Will do
min
On 06/13/2012 05:10 PM, Juha Heinanen wrote:
Min Wang writes:
Just wondering which version of are you using on the kamailio server
side ?
3.3.
If I restart jitsi, jitis did send publish from the trace, but
kamailio did not s
Min Wang writes:
> Just wondering which version of are you using on the kamailio server
> side ?
3.3.
> If I restart jitsi, jitis did send publish from the trace, but
> kamailio did not send out the notification.
try with kamailio 3.3 and tell exactly which publish you are talking
ab
i did some more presence tests with jitsi. when i start jitsi, it
registers its sip uri, subscribes to its own presence.winfo and presence
of another uri, and publishes its own presence.
when i then quit jitsi, it un-publishes its own presence, un-subscribes
presence of the other uri, unregisters
Hi Juha:
Just wondering which version of are you using on the kamailio server
side ?
I've used kamailio 3.1, jitsi/bria are subscribed to each other and
both's status=1 in the watchers.
If I restart jitsi, jitis did send publish from the trace, but
kamailio did not send out the
Andreas Granig writes:
> Looks like that has been addressed already. At least with svn trunk
> verison, it's sending SIP-If-Match with Expires: 0. Could be worth
> taking another try with a nightly 1.1 build?
yes, the bug is fixed in nightly build.
-- juha
__
Hi Juha,
On 06/13/2012 11:50 AM, Juha Heinanen wrote:
>> For me, reporting a presence bug on the jitsi-users mailing list, along
>> with pointing out exactly where in the code and how to fix it eventually
>> worked. Did you get in touch with them on one of the lists?
>
> i don't remember if i sen
Andreas Granig writes:
> For me, reporting a presence bug on the jitsi-users mailing list, along
> with pointing out exactly where in the code and how to fix it eventually
> worked. Did you get in touch with them on one of the lists?
i don't remember if i send anything to mailing list. the bug i
Hi,
On 06/13/2012 10:52 AM, Juha Heinanen wrote:
> my feeling is that there is no real commitment in jitsi for sip
> presence/xcap. i found a presence bug long time ago and reported it on
> jitsi tracker. so far nothing has happened.
For me, reporting a presence bug on the jitsi-users mailing l
Min Wang writes:
> BTW, it seems jitsi does not support RLS at this moment even
> though it store the contact list in the xcap?? I guess I should asked
> this in the jitsi mailing list.
my feeling is that there is no real commitment in jitsi for sip
presence/xcap. i found a presence bug
HI Daniel
thanks a lot.
Each xcap document is stored for a specific user, whose ID is taken
from first parameter of xcap_put(...)/etc. Now the user id can be the
same as in xcap url or something known only internally, looked up via
some logic in config. In this way you have full flexibilit
Hello,
On 6/12/12 12:51 PM, Min Wang wrote:
HI Daniel:
thanks a lot for the explaination.
I have tried the jitsi and bria.
jitsi use this kind of xcap uri:
/xcap/resource-lists/users/sip:w102@192.168.51.20/index
while bria/eyebeam use:
/xcap/org.openmobilealliance.pres
HI Daniel:
thanks a lot for the explaination.
I have tried the jitsi and bria.
jitsi use this kind of xcap uri:
/xcap/resource-lists/users/sip:w102@192.168.51.20/index
while bria/eyebeam use:
/xcap/org.openmobilealliance.pres-rules/users/w103@192.168.51.20/pre
Hello,
On 6/12/12 11:28 AM, Min Wang wrote:
Hi
I am trying to use kamailio xcap server, saw the sample code:
if($xcapuri(u=>xuid)=~"^sip:.+@.+")
$var(uri) = $xcapuri(u=>xuid);
else
$var(uri) = "sip:"+ $xcapuri(u=>xuid) + "@" + $Ri;
why should the
14 matches
Mail list logo
