[Serusers] global contact list
Barta János
j.barta at freemail.hu
Thu Apr 26 09:56:07 CEST 2007
Hello!
Thanks for your answer again, and I'm sorry for the delayed answer, but I was out of office.
My biggest problem is, that I don't know, what I should see :-(.
I have an eyeBeam window, that contains the "Calls & Conntats" parameters.
In this window I can see my (user) contact list, but I didn't see the global one.
For example (the PC is my user contact list):
-PC
-105
-12345
-barta
and it is working fine, but I can not see here (in this window) the global one:
sip:~# cat /var/www/xcap-root/rls-services/global/index
<?xml version="1.0" encoding="UTF-8"?>
<rls-services>
<service uri="sip:bartaj-list at test.intra">
<list name="Human resources">
<entry uri="sip:test1 at test.intra">
<display-name>bartaj</display-name>
</entry>
<entry uri="sip:test2 at test.intra">
<display-name>12345</display-name>
</entry>
</list>
<packages>
<package>presence</package>
</packages>
</service>
<service uri="sip:hr2 at test.intra">
<list name="Human resources">
<entry uri="sip:test1 at test.intra">
<display-name>bartaj</display-name>
</entry>
<entry uri="sip:test2 at test.intra">
<display-name>12345</display-name>
</entry>
</list>
<packages>
<package>presence</package>
</packages>
</service>
</rls-services>
I think in that case I should see the next tree:
-PC
-105
-12345
-barta
-Human resources
-bartaj
-12345
As You asked, I made a capture between the SER and XCAP.
It was a little difficult, because I didn't see interesting traffic between the SER and XCAP, but a few minutes later I realised, that the SER for the communication (in that case) uses the loopback (lo) interface.
You can see here the capture, that I made on the lo interface:
1 0.000000 127.0.0.1 -> 127.0.0.1 TCP 37512 > www [SYN] Seq=0 Len=0 MSS=16396 TSV=3808162073 TSER=0 WS=0
2 0.000056 127.0.0.1 -> 127.0.0.1 TCP www > 37512 [SYN, ACK] Seq=0 Ack=1 Win=32767 Len=0 MSS=16396 TSV=3808162073 TSER=3808162073 WS=0
3 0.000065 127.0.0.1 -> 127.0.0.1 TCP 37512 > www [ACK] Seq=1 Ack=1 Win=32767 Len=0 TSV=3808162073 TSER=3808162073
4 0.000072 127.0.0.1 -> 127.0.0.1 HTTP GET /xcap/pres-rules/users/12345/presence-rules.xml HTTP/1.1
5 0.000079 127.0.0.1 -> 127.0.0.1 TCP www > 37512 [ACK] Seq=1 Ack=113 Win=32767 Len=0 TSV=3808162073 TSER=3808162073
6 0.000545 127.0.0.1 -> 127.0.0.1 HTTP HTTP/1.1 200 OK
7 0.000559 127.0.0.1 -> 127.0.0.1 TCP 37512 > www [ACK] Seq=113 Ack=262 Win=32767 Len=0 TSV=3808162074 TSER=3808162074
8 0.000571 127.0.0.1 -> 127.0.0.1 HTTP Continuation or non-HTTP traffic
9 0.000578 127.0.0.1 -> 127.0.0.1 TCP 37512 > www [ACK] Seq=113 Ack=870 Win=32767 Len=0 TSV=3808162074 TSER=3808162074
10 0.005535 127.0.0.1 -> 127.0.0.1 TCP 37513 > www [SYN] Seq=0 Len=0 MSS=16396 TSV=3808162079 TSER=0 WS=0
11 0.005556 127.0.0.1 -> 127.0.0.1 TCP www > 37513 [SYN, ACK] Seq=0 Ack=1 Win=32767 Len=0 MSS=16396 TSV=3808162079 TSER=3808162079 WS=0
12 0.005565 127.0.0.1 -> 127.0.0.1 TCP 37513 > www [ACK] Seq=1 Ack=1 Win=32767 Len=0 TSV=3808162079 TSER=3808162079
13 0.005616 127.0.0.1 -> 127.0.0.1 HTTP GET /xcap/pres-rules/users/bartaj/presence-rules.xml HTTP/1.1
14 0.005623 127.0.0.1 -> 127.0.0.1 TCP www > 37513 [ACK] Seq=1 Ack=114 Win=32767 Len=0 TSV=3808162079 TSER=3808162079
15 0.005989 127.0.0.1 -> 127.0.0.1 HTTP HTTP/1.1 200 OK
16 0.006000 127.0.0.1 -> 127.0.0.1 TCP 37513 > www [ACK] Seq=114 Ack=262 Win=32767 Len=0 TSV=3808162079 TSER=3808162079
17 0.006011 127.0.0.1 -> 127.0.0.1 HTTP Continuation or non-HTTP traffic
18 0.006017 127.0.0.1 -> 127.0.0.1 TCP 37513 > www [ACK] Seq=114 Ack=870 Win=32767 Len=0 TSV=3808162079 TSER=3808162079
19 2.979491 127.0.0.1 -> 127.0.0.1 HTTP GET /xcap/rls-services/global/index HTTP/1.1
20 2.979722 127.0.0.1 -> 127.0.0.1 HTTP HTTP/1.1 200 OK
21 2.979734 127.0.0.1 -> 127.0.0.1 TCP 37512 > www [ACK] Seq=209 Ack=1126 Win=32767 Len=0 TSV=3808165053 TSER=3808165053
22 2.979745 127.0.0.1 -> 127.0.0.1 HTTP Continuation or non-HTTP traffic
23 2.979751 127.0.0.1 -> 127.0.0.1 TCP 37512 > www [ACK] Seq=209 Ack=1887 Win=32767 Len=0 TSV=3808165053 TSER=3808165053
You can see, that in the message number 19 the SER downloaded the index file.
This file contains correct information:
sip:~# wget 127.0.0.1/xcap/rls-services/global/index
--17:22:43-- http://127.0.0.1/xcap/rls-services/global/index
=> `index'
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 761 [text/plain]
100%[====================================>] 761 --.--K/s
17:22:43 (7.26 MB/s) - `index' saved [761/761]
sip:~#
sip:~# cat index
<?xml version="1.0" encoding="UTF-8"?>
<rls-services>
<service uri="sip:bartaj-list at test.intra">
<list name="Human resources">
<entry uri="sip:test1 at test.intra">
<display-name>bartaj</display-name>
</entry>
<entry uri="sip:test2 at test.intra">
<display-name>12345</display-name>
</entry>
</list>
<packages>
<package>presence</package>
</packages>
</service>
<service uri="sip:hr2 at test.intra">
<list name="Human resources">
<entry uri="sip:test1 at test.intra">
<display-name>bartaj</display-name>
</entry>
<entry uri="sip:test2 at test.intra">
<display-name>12345</display-name>
</entry>
</list>
<packages>
<package>presence</package>
</packages>
</service>
</rls-services>
sip:~#
And at last, how can I add query_rls_services and query_resource_list log informations into the config file?
Thx,
Jani
-----Original Message-----
From: Vaclav Kubart [mailto:vaclav.kubart at iptel.org]
Sent: Tuesday, April 03, 2007 11:18 AM
To: Barta János
Cc: serusers at iptel.org
Subject: Re: [Serusers] global contact list
Hi,
this part of config file is not sufficient for me, but I guess that RLS related things stayed as in the original config you mentioned... In which way it doesn't work? (For example it returns non OK responses?) Please could you try to capture HTTP traffic between XCAP server and SER? (If SER really queries the right resource list document.)
You can add more log information around important config parts (query_rls_services and query_resource_list functions are most important here).
BTW the second message you sent is not subscription to resource list or user, it is subscription to event package 'sip-profile' (content of Event header field) which is not supported by SER.
It is possible to use registration status as source for presence - in this case you have to have PA module on your server handling registrations and PA module parameter 'use_callbacks' must be set to 1.
Vaclav
<br><br>_____________________________________________________________________<br>
Tudod már, hol nyaralsz? Úti beszámolókat, utazási ajánlatokat találsz a <a href="http://ad.adverticum.net/b/cl,1,6022,159388,223268/click.prm" target="new">travelline.hu-n!</a><br>
Ha Te is megírod élményeidet, megnyerhetsz egy párizsi utat vagy egy kalandtúrát az Alpokba!
More information about the sr-users
mailing list