[OpenSIPS-Users] OpenSIPS 2.1 - Record-Routing back to itself

[Damien Sandras]

Good evening,

I have a strange problem. I am experimenting with 2 OpenSIPS 2.1
instances : one listening on port 5060 and one on port 5050.

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.

On OpenSIPS:5050, logging gives me that :
Nov  3 15:08:40 golgoth05 opensips[23153]: RELAY: Relaying NOTIFY
(From: 752) to sip:754 at 172.26.0.46:5060;transport=tcp via
sip:172.30.3.83;transport=tcp;lr;ftag=68ca1f0d-a280-e511-8e2c-
78843c3891dd;router=yes 

=> 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.

Nov  3 15:08:40 golgoth05 opensips[23153]: IN_DIALOG: Received NOTIFY
(752 -> 754) from 172.30.3.83:5050 (using record routing)

=> that's the same NOTIFY. OpenSIPS:5050 routed the NOTIFY to itself,
and did not route it to $du

What could cause this ?

Thanks,
-- 
Damien Sandras <dsandras at seconix.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20151103/28b004f0/attachment.htm>