<br>
I think I am missing something very simple here, but I cannot figure out what it is. <br>
<br>
I have DID aliases set up for SER usernames, so when a call comes in as
2125551234, I do a lookup("aliases") which results in something like
<a href="mailto:username1@sip.mydomain.com">username1@sip.mydomain.com</a>. Username1 is the registered SER
user. the numbers are all aliases.<br>
<br>
I also have a secondary aliases table called "hunt" which I use to
store call hunt sequences. The problem is that if a user
does not pick up the phone and SER calls failure_route[1], I get a hunt
for both 2125551234 and username1. Shouldn't my revert_uri() in
failure_route cause the hunt lookup to be done on 2125551234 only?<br>
<br>
route[7] is called from failure_route only, so there isn't any
other logic that might put me into these route blocks. Included
below the call routing blocks are some syslogs.<br>
<br>
If anyone could offer a suggestion or has seen anything like this and
could let me know what they did to solve it I would be eternally
grateful.<br>
<br>
Thank you.<br>
<br>
Dan<br>
<br>
<br>
<br>
###<br>
# Hunt (8), but only on 404/408/486<br>
route[7] {<br>
if (t_check_status("408") | # Timeout<br>
t_check_status("404") | # Not found<br>
t_check_status("486")) # Busy<br>
{<br>
route(8);<br>
} else {<br>
xlog("L_NOTICE",<br>
"%ci: r7: hunt but not 404/408/486\n");<br>
};<br>
}<br>
<br>
###<br>
# Hunt to the next number in sequence<br>
route[8] {<br>
# See if we're in a hunt<br>
if(search("P-hint: pt-hunt")) {<br>
xlog("L_NOTICE",<br>
"wanted to hunt, but hunt already in progress\n");<br>
break;<br>
};<br>
<br>
# Assumes URI has been revert and prefixed with "h#-"<br>
# Also assumes t_on_failure (#+1) has been set.<br>
xlog("L_NOTICE", "%ci: r8: hunt on %ru\n");<br>
if(lookup("hunt")) {<br>
xlog("L_NOTICE",<br>
"%ci: r8: hunt changed URI to %ru, relaying\n");<br>
append_branch();<br>
append_hf("P-hint: pt-hunt\r\n");<br>
setflag(9);<br>
t_relay();<br>
break;<br>
} else {<br>
xlog("L_NOTICE",<br>
"%ci: r8: no further hunts, giving up\n");<br>
};<br>
<br>
}<br>
<br>
failure_route[1] { revert_uri(); prefix("h1-"); t_on_failure("2"); route(7); }<br>
failure_route[2] { revert_uri(); prefix("h2-"); t_on_failure("3"); route(7); }<br>
failure_route[3] { revert_uri(); prefix("h3-"); t_on_failure("4"); route(7); }<br>
failure_route[4] { revert_uri(); prefix("h4-"); t_on_failure("5"); route(7); }<br>
failure_route[5] { revert_uri(); prefix("h5-"); t_on_failure("6"); route(7); }<br>
failure_route[6] { revert_uri(); prefix("h6-"); t_on_failure("7"); route(7); }<br>
failure_route[7] { revert_uri(); prefix("h7-"); t_on_failure("8"); route(7); }<br>
failure_route[8] { revert_uri(); prefix("h8-"); t_on_failure("9"); route(7); }<br>
failure_route[9] { xlog("L_ERR", "too many hunts!\n"); }<br>
<br>
<br>
<br>
<br>
<br>
Jul 18 11:17:23 sip /usr/sbin/ser[18279]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.18">192.168.32.18</a>]
INVITE sip:2125551234@192.168.32.30:5060<br>
Jul 18 11:17:23 sip /usr/sbin/ser[18279]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: alias lookup changed
uri to <a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:17:23 sip /usr/sbin/ser[18279]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.30">192.168.32.30</a>]
INVITE <a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:17:53 sip /usr/sbin/ser[18301]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: r8: hunt on
<a href="mailto:sip:h1-username1@sip.mydomain.com">sip:h1-username1@sip.mydomain.com</a><br>
Jul 18 11:17:53 sip /usr/sbin/ser[18301]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: r8: hunt changed URI
to <a href="mailto:sip:2125551234@vm.packetalk.net">sip:2125551234@vm.packetalk.net</a>, relaying<br>
Jul 18 11:17:53 sip /usr/sbin/ser[18301]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: r8: hunt on
sip:h1-2125551234@192.168.32.30:5060<br>
Jul 18 11:17:53 sip /usr/sbin/ser[18301]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: r8: hunt changed URI
to <a href="mailto:sip:2125551234@vm.packetalk.net">sip:2125551234@vm.packetalk.net</a>, relaying<br>
Jul 18 11:17:53 sip /usr/sbin/ser[18281]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.30">192.168.32.30</a>]
CANCEL <a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:17:55 sip /usr/sbin/ser[18295]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200<br>
Jul 18 11:17:56 sip /usr/sbin/ser[18285]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200<br>
Jul 18 11:17:57 sip /usr/sbin/ser[18295]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200<br>
Jul 18 11:17:58 sip /usr/sbin/ser[18289]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200<br>
Jul 18 11:17:59 sip /usr/sbin/ser[18298]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200<br>
Jul 18 11:18:00 sip /usr/sbin/ser[18281]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200<br>
Jul 18 11:18:08 sip /usr/sbin/ser[18280]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.18">192.168.32.18</a>]
CANCEL sip:2125551234@192.168.32.30:5060<br>
Jul 18 11:18:08 sip /usr/sbin/ser[18280]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: alias lookup changed
uri to <a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:18:08 sip /usr/sbin/ser[18289]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.30">192.168.32.30</a>] ACK
<a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:18:09 sip /usr/sbin/ser[18285]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.30">192.168.32.30</a>] ACK
<a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:18:10 sip /usr/sbin/ser[18289]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.30">192.168.32.30</a>] ACK
<a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:18:11 sip /usr/sbin/ser[18298]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.30">192.168.32.30</a>] ACK
<a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:18:12 sip /usr/sbin/ser[18298]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.30">192.168.32.30</a>] ACK
<a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
Jul 18 11:18:13 sip /usr/sbin/ser[18287]:
<a href="mailto:29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18">29FF0A3-F6D611D9-938FBF07-9CC1DBD7@192.168.32.18</a>: [<a href="http://192.168.32.30">192.168.32.30</a>] ACK
<a href="mailto:sip:username1@sip.mydomain.com">sip:username1@sip.mydomain.com</a><br>
<br>