<DIV>Hi</DIV>
<DIV>I have the same problem, please take a look into this report: <A href="http://lists.iptel.org/pipermail/serusers/2004-August/010930.html">http://lists.iptel.org/pipermail/serusers/2004-August/010930.html</A></DIV>
<DIV> </DIV>
<DIV>...if the called-user belongs to the voicemail group and the caller-user cancels the call I see irregular behavior in both ser instances and no Sip-Response-Code=487 is recorded in radius acc (just an start record without stop).</DIV>
<DIV> </DIV>
<DIV>I´ve just tried with "t_check_status" but I have the same problem... please send us some advice...</DIV>
<DIV> </DIV>
<DIV>thank you</DIV>
<DIV>Rafael</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>ser.cfg::</DIV>
<DIV> # does the user wish redirection on no availability? (i.e., is he<BR> # in the voicemail group?) -- determine it now and store it in<BR> # flag 4, before we rewrite the flag using UsrLoc</DIV>
<DIV> if (is_user_in("Request-URI", "voicemail")) {<BR> setflag(4);<BR> };</DIV>
<DIV> # native SIP destinations are handled using our USRLOC DB<BR> if (!lookup("location")) {<BR> # handle user which was not found<BR> route(4);<BR> break; <BR> };</DIV>
<DIV> # if user is on-line and is in voicemail group, enable redirection<BR> if (method == "INVITE" && isflagset(4)) {<BR> t_on_failure("1");<BR> };<BR> t_relay();<BR>}</DIV>
<DIV># ------------- handling of unavailable user ------------------<BR>route[4] {</DIV>
<DIV> # non-Voip -- just send "off-line"<BR> if (!(method=="INVITE" || method=="ACK" || method=="CANCEL" || method=="BYE")) {<BR> sl_send_reply("404", "Not Found");<BR> acc_rad_request("404 Not Found");<BR> break;<BR> };</DIV>
<DIV> # not voicemail subscriber<BR> if (!isflagset(4)) {<BR> sl_send_reply("404", "Not Found and no voicemail turned on");<BR> acc_rad_request("404 Not Found");<BR> break;<BR> };</DIV>
<DIV> # forward to voicemail now<BR> rewritehostport("call.millicom.com.pe:5090");<BR> t_relay_to_udp("call.millicom.com.pe", "5090"); <BR>}</DIV>
<DIV># if forwarding downstream did not succeed, try voicemail running<BR># at bat.iptel.org:5090</DIV>
<DIV><STRONG>failure_route[1]{<BR> if (t_check_status("408|486|487")){<BR> revert_uri ();<BR> rewritehostport ("call.millicom.com.pe:5090");<BR> append_branch();<BR> t_relay();<BR> break;<BR> }<BR></STRONG>}<BR><BR><B><I>Richard <richard@o-matrix.org></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">You can use t_check_status("487") to check the code in failure_route[1].<BR><BR>Richard<BR><BR><BR>-----Original Message-----<BR>From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] On<BR>Behalf Of Zhang Wei<BR>Sent: Friday, September 03, 2004 8:30 PM<BR>To: Jan Janak<BR>Cc: serusers@lists.iptel.org<BR>Subject: [Serusers] How can I distinguish 487 and 603 reply?<BR><BR>hello,Jan<BR>I meet some trouble when I use SER .I hope that when the call timeouts<BR>or is declined by the callee the call would be forward to SEMS. In my<BR>ser.cfg ,I wrote :<BR>if (method=="INVITE")<BR>{<BR>t_on_failure("1");<BR>} <BR>But when the caller cancels the call,487 reply the callee sends aslo<BR>make INVITE enter the failure_route. I don't export it. So how can I<BR>distinguish 487 and 603 ?<BR><BR>Thanks for your help<BR><BR>Wei<BR><BR>_______________________________________________<BR>Serusers
mailing list<BR>serusers@lists.iptel.org<BR>http://lists.iptel.org/mailman/listinfo/serusers<BR></BLOCKQUOTE><p><br><hr size=1 noshade><b>Do You Yahoo!?</b><br>
<a href=http://espanol.yahoo.com/mail_tagline/*http://espanol.news.yahoo.com><img src="http://us.i1.yimg.com/us.yimg.com/i/not/dailynews.gif" width=30 height=26 border=0 align=left></a>
Todo lo que quieres saber de Estados Unidos, América Latina y el resto del Mundo.<br>
Visíta <a href=http://espanol.yahoo.com/mail_tagline/*http://espanol.news.yahoo.com>Yahoo! Noticias</a>.<br>