[SR-Users] rtpproxy delete fails

[Juha Heinanen]

i made more tests on deleting rtpprxy session when 480 is received.  in
this test there is only one uas registered for AoR test at test.fi.  when
it times out and replies with 480, sip proxy makes exactly same call

        rtpproxy_manage("FROW3");

first in onreply route and then i failure route.  this i what i get to
syslog:

Oct 19 17:08:40 siika /usr/sbin/sip-proxy[20799]: INFO: Received reply <480>
Oct 19 17:08:40 siika mediaproxy-ng[12832]: Got valid command from udp:127.0.0.1:53325: 20799_12 D kmjhsrcegulqqta at siika.tutpro.com;z9hG4bKxcuqspqh nxaoe qskel
Oct 19 17:08:40 siika mediaproxy-ng[12832]: [kmjhsrcegulqqta at siika.tutpro.com] Tags didn't match for delete message, ignoring
Oct 19 17:08:40 siika /usr/sbin/sip-proxy[20799]: INFO: Got contact failure <480>
Oct 19 17:08:40 siika mediaproxy-ng[12832]: Got valid command from udp:127.0.0.1:53325: 20799_13 D kmjhsrcegulqqta at siika.tutpro.com;z9hG4bKxcuqspqh nxaoe
Oct 19 17:08:40 siika mediaproxy-ng[12832]: [kmjhsrcegulqqta at siika.tutpro.com - z9hG4bKxcuqspqh] Branch deleted
Oct 19 17:08:40 siika mediaproxy-ng[12832]: [kmjhsrcegulqqta at siika.tutpro.com] Deleting full call

my conclusion from this is that rtpproxy_manage("FROW3") does include to
tag in rtpproxy command when called from onreply route, but does not
include it when called from failure route.

why the difference?  it is a bug that to tag is included in onreply
route, because it means that it is not possible to delete rtpproxy
session in onreply route?

-- juha