Hi,
I've fixed a bug in t_next_contacts where the ruid was not retrieved and
put into the contact flows xavp. I don't know if that will help with
this issue if you are not using multiple flows.
I've also added the ruid to the append_branch debug in t_next_contacts
which should show if it is corrupt before or after the request is sent.
Hugh
On 06/04/2013 07:45, Juha Heinanen wrote:
hugh,
sometimes unregistering in event_route[tm:branch-failure] works fine,
e.g.:
Apr 6 09:39:00 siika /usr/sbin/sip-proxy[21504]: INFO:
event_route[tm:branch-failure]
Apr 6 09:39:00 siika /usr/sbin/sip-proxy[21504]: INFO: Unregistering
<sip:[email protected]> with ruid <uloc-515fc1d4-53ff-2>
but sometimes looks like $T_reply_ruid is corrupted:
Apr 6 09:39:06 siika /usr/sbin/sip-proxy[21533]: INFO:
event_route[tm:branch-failure]
Apr 6 09:39:06 siika /usr/sbin/sip-proxy[21533]: INFO: Unregistering
<sip:[email protected]> with ruid <ulo`
Apr 6 09:39:06 siika /usr/sbin/sip-proxy[21533]: WARNING: registrar
[save.c:993]: AOR/Contact not found
Apr 6 09:39:06 siika /usr/sbin/sip-proxy[21533]: WARNING: Failed to unregister
<sip:[email protected]> with ruid <ulo`
the piece of config file producing the above is:
if (t_check_status("(408|486)")) {
xlog("L_INFO", "Unregistering <$avp(REQUEST_URI_AVP)> with ruid
<$T_reply_ruid>\n");
if (!unregister("location", "$avp(REQUEST_URI_AVP)",
"$T_reply_ruid")) {
xlog("L_WARN", "Failed to unregister <$avp(REQUEST_URI_AVP)> with ruid
<$T_reply_ruid>\n");
};
...
i added 486 (busy) to t_check_status just to ease testing.
in usrloc table ruid field values are correct, i.e., there is no value
"ulo`".
-- juha
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Hugh Waite
Principal Design Engineer
Crocodile RCS Ltd.
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
