2010/3/11 Pascal Maugeri <[email protected]>: > Hola Iñaki > Here is the SIP flow you asked me. > Hope it helps to spot the problem. Observe the watcher is behind NAT.
> SUBSCRIBE sip:[email protected] SIP/2.0 > Record-Route: <sip:xxx.xxx.xxx.xxx:6666;lr=on> > Call-ID: [email protected] > CSeq: 1 SUBSCRIBE > From: "watcher" <sip:[email protected]>;tag=94671740 > To: <sip:[email protected]> > Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:6666;branch=z9hG4bK581b.d3f0fa41.0 > Via: SIP/2.0/UDP > 10.1.1.235:5060;rport=5060;received=yyy.yyy.yyy.yyy;branch=z9hG4bKc5Obqwa8W > Max-Forwards: 69 > Contact: <sip:[email protected]:5060;transport=tcp> > Event: presence > Expires: 3600 > User-Agent: XXX > Accept: application/pidf+xml > Content-Length: 0 Hi Pascal, the above initial SUBSCRIBE has a Record-Route containing a SIP URI without ;transport=tcp parameter, so there is a proxy between the NATted client and the presence server. I suspect the topology is as follows: client --- Router-NAT ---- (SIP TCP) ---- Proxy ---- (SIP UDP) ---- Presence-Server Is it correct? -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
