[SR-Users] RLS issue

Hi everybody, I'm using the Kamailio RLS+Presence module integrated with OpenIMSCore. All the servers are running properly but when sending a RLS subscribe. The flow of SIP messages is the following: A.1) Watcher ---- SUBSCRIBE (rls-services uri) ---> RLS SUBSCRIBE sip:restricted_areas@open-ims.test SIP/2.0 Call-ID: dcKTUqpGi8lsPuQzqI0m922XEmSQpAxU36XScBNuu1A. CSeq: 1 SUBSCRIBE From: "restricted_areas" <sip:restricted_areas@open-ims.test>;tag=11afb48e To: <sip:restricted_areas@open-ims.test> Via: SIP/2.0/TCP 155.54.190.166:8060;rport;branch=z9hG4bK-d8754z-29095b2cee722e34-1---d8754z- Max-Forwards: 70 Event: presence Accept: multipart/related, application/rlmi+xml, application/pidf+xml, application/auth-policy+xml Expires: 30000 Contact: <sip:restricted_areas@155.54.190.166:8060> Supported: eventlist Route: <sip:orig@scscf.open-ims.test:6060;lr> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite IMS-OSGi-Client 0.1 CVS-Thu_Dec_16_10-48-31_CET_2010 Content-Length: 0 A.2) RLS ---- 200 Ok ----> Watcher B.1) RLS ---- SUBSCRIBE (presentity in the rls-services user's list) ---> I-CSCF SUBSCRIBE sip:restricted_areas@open-ims.test SIP/2.0 Record-Route: <sip:mo@scscf.open-ims.test:6060;lr> Route: <sip:ciervo.inf.um.es:5060;lr>, <sip:iscmark@scscf.open-ims.test:6060;lr;s=1;h=0;d=0;a=7369703a726573747269637465645f6172656173406f70656e2d696d732e74657374> Record-Route: <sip:mo@pcscf.open-ims.test:4060;lr> Call-ID: dcKTUqpGi8lsPuQzqI0m922XEmSQpAxU36XScBNuu1A. CSeq: 1 SUBSCRIBE From: "restricted_areas" <sip:restricted_areas@open-ims.test>;tag=11afb48e To: <sip:restricted_areas@open-ims.test> Via: SIP/2.0/UDP 155.54.210.135:6060;branch=z9hG4bKfc46.88774fc7.0 Via: SIP/2.0/UDP 155.54.210.134:4060;branch=z9hG4bKfc46.8dfcbef7.0;i=2 Via: SIP/2.0/TCP 155.54.190.166:8060;rport=42816;branch=z9hG4bK-d8754z-29095b2cee722e34-1---d8754z- Max-Forwards: 15 Event: presence Accept: multipart/related, application/rlmi+xml, application/pidf+xml, application/auth-policy+xml Expires: 30000 Contact: <sip:restricted_areas@155.54.190.166:8060> Supported: eventlist Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite IMS-OSGi-Client 0.1 CVS-Thu_Dec_16_10-48-31_CET_2010 Content-Length: 0 P-Asserted-Identity: <sip:restricted_areas@open-ims.test> P-Charging-Vector: icid-value="P-CSCFabcd000000004d09e21300000005";icid-generated-at=155.54.210.134;orig-ioi="open-ims.test" B.2) I-CSCF ---- QUERY ----> HSS B.3) I-CSCF ---- SUBSCRIBE ----> S-CSCF SUBSCRIBE sip:testuser01@open-ims.test SIP/2.0 Route: <sip:scscf.open-ims.test:6060> Via: SIP/2.0/UDP 155.54.210.136;branch=z9hG4bK07df.3688b985.0 Via: SIP/2.0/UDP 155.54.190.245;branch=z9hG4bK07df.964e0ba7.0 To: sip:testuser01@open-ims.test From: sip:restricted_areas@open-ims.test;tag=533cb9e91f4b999cf76861cbb9ed54ed-32d5 CSeq: 10 SUBSCRIBE Call-ID: 7fd8dfdd-21694(a)127.0.0.1 Content-Length: 0 User-Agent: kamailio (3.2.0-dev1 (i386/linux)) Max-Forwards: 16 Event: presence Contact: <sip:155.54.190.245:5060;transport=udp> Expires: 10810 Max-Forwards: 70 Support: eventlist B.4) S-CSCF ---- SUBSCRIBE ----> P-CSCF SUBSCRIBE sip:testuser01@155.54.190.245:8060;rinstance=9b7761b4bcaa4bd0 SIP/2.0 Record-Route: <sip:mt@scscf.open-ims.test:6060;lr> Route: <sip:term@pcscf.open-ims.test:4060;lr> Via: SIP/2.0/UDP 155.54.210.135:6060;branch=z9hG4bK07df.8a35e4f3.0 Via: SIP/2.0/UDP 155.54.210.136;branch=z9hG4bK07df.3688b985.0 Via: SIP/2.0/UDP 155.54.190.245;branch=z9hG4bK07df.964e0ba7.0 To: sip:testuser01@open-ims.test From: sip:restricted_areas@open-ims.test;tag=533cb9e91f4b999cf76861cbb9ed54ed-32d5 CSeq: 10 SUBSCRIBE Call-ID: 7fd8dfdd-21694(a)127.0.0.1 Content-Length: 0 User-Agent: kamailio (3.2.0-dev1 (i386/linux)) Max-Forwards: 15 Event: presence Contact: <sip:155.54.190.245:5060;transport=udp> Expires: 10810 Max-Forwards: 70 Support: eventlist P-Called-Party-ID: <sip:testuser01@open-ims.test> B.5) P-CSCF ---- SUBSCRIBE ----> Presentity??? SUBSCRIBE sip:testuser01@155.54.190.245:8060;rinstance=9b7761b4bcaa4bd0 SIP/2.0 Record-Route: <sip:mt@pcscf.open-ims.test:4060;lr> Record-Route: <sip:mt@scscf.open-ims.test:6060;lr> Via: SIP/2.0/TCP 155.54.210.134:4060;branch=z9hG4bK07df.baa7cf24.0 Via: SIP/2.0/UDP 155.54.210.135:6060;received=155.54.210.135;rport=6060;branch=z9hG4bK07df.8a35e4f3.0 Via: SIP/2.0/UDP 155.54.210.136;branch=z9hG4bK07df.3688b985.0 Via: SIP/2.0/UDP 155.54.190.245;branch=z9hG4bK07df.964e0ba7.0 To: sip:testuser01@open-ims.test From: sip:restricted_areas@open-ims.test;tag=533cb9e91f4b999cf76861cbb9ed54ed-32d5 CSeq: 10 SUBSCRIBE Call-ID: 7fd8dfdd-21694(a)127.0.0.1 Content-Length: 0 User-Agent: kamailio (3.2.0-dev1 (i386/linux)) Max-Forwards: 14 Event: presence Contact: <sip:155.54.190.245:5060;transport=udp> Expires: 10810 Max-Forwards: 70 Support: eventlist P-Called-Party-ID: <sip:testuser01@open-ims.test> The step B.5 is sent directly to the presentity testuser01. Instead of that, I thought that message was suppose to be sent to the presence server in the URI that is shown in Contact header. Regards, Andrés.