<html><head></head><body><div>Good evening,</div><div><br></div><div>I have a strange problem. I am experimenting with 2 OpenSIPS 2.1 instances : one listening on port 5060 and one on port 5050.</div><div><br></div><div>An external UA is SUBSCRIBING for presence, and the SUBSCRIBE is routed from OpenSIPS:5060 to OpenSIPS:5050 to elsewhere. When a NOTIFY is generated, it is supposed to be routed back to OpenSIPS:5050 then to OpenSIPS:5060 then to the original UA.</div><div><br></div><div>On OpenSIPS:5050, logging gives me that :</div><div>Nov 3 15:08:40 golgoth05 opensips[23153]: RELAY: Relaying NOTIFY (From: 752) to sip:<a href="mailto:754@172.26.0.46"><a href="mailto:754@172.26.0.46">754@172.26.0.46</a></a>:5060;transport=tcp via sip:172.30.3.83;transport=tcp;lr;ftag=68ca1f0d-a280-e511-8e2c-78843c3891dd;router=yes </div><div><br></div><div>=> via sip:172.30.3.83;... is the OpenSIPS running on port 5060. It is a direct output of $du. So, $du points to the correct destination.</div><div><br></div><div>Nov 3 15:08:40 golgoth05 opensips[23153]: IN_DIALOG: Received NOTIFY (752 -> 754) from 172.30.3.83:5050 (using record routing)</div><div><br></div><div>=> that's the same NOTIFY. OpenSIPS:5050 routed the NOTIFY to itself, and did not route it to $du</div><div><br></div><div>What could cause this ?</div><div><br></div><div>Thanks,</div><div class="-x-evo-signature-wrapper"><span>-- <br>Damien Sandras <<a href="mailto:dsandras@seconix.com">dsandras@seconix.com</a>></span></div></body></html>