[SR-Users] rtpproxy delete fails

[Richard Fuchs]

Hi,

While I can't really answer your question, the logic in mediaproxy-ng is
that if the to-tag is given in the "D"elete message, it has to match the
to-tag that was previously given in the "L"ookup message alongside with
the from-tag. If no to-tag is given in the delete message, then only the
from-tag is used for matching.

If no lookup was ever performed, then mediaproxy obviously has no way of
knowing the to-tag and so can't match on it. In that case, only the
from-tag should be given in the delete message.

I suppose it could make sense to change mediaproxy's behaviour to ignore
the to-tag given in the delete message if it hadn't received a lookup
for that particular branch yet. Although right off the bat I'm not 100%
certain if that would be correct behaviour or if there might be some
undesired side effects to that...

The ";1" is the sequence number of the media stream within the call. If
more than one stream is present, you'll see ";1", ";2" and so on.

cheers


On 10/19/12 10:18, Juha Heinanen wrote:
> 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
> 
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20121019/ca26b0a7/attachment.pgp>