Am 16.12.2010 13:36, schrieb "Andrés S. García Ruiz":
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@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.
If the P-CSCF is not forwarding the request as supposed, I guess you have to fix the routing on the P-CSCF.
klaus