9 Nov
2007
9 Nov
'07
4:57 p.m.
Can someone tell me why the pseudo variable $rr (SIP reply reason) is not present in a
failure_route?
If a call fails, this pseudo var contains the SIP response code, '404' for a Not
Found for example. I would think that it should DEFINITELY be set in a failure route.
OTHER pseudo variables are set in a failure route. Why not the SIP response code? This is
probably the most important pseudo variable to have available in a failure route!
Douglas.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
9 Nov
9 Nov
8:02 p.m.
Hi Douglas,
In reply_route you need to check/test $T_reply_code.
Daniel already pointed that out in a previous post.
Regards,
Ovidiu Sas
On Nov 9, 2007 1:57 PM, Douglas Garstang <dougmig33(a)yahoo.com> wrote:
Can someone tell me why the pseudo variable $rr (SIP reply reason) is not
present in a failure_route?
If a call fails, this pseudo var contains the SIP response code, '404' for a
Not Found for example. I would think that it should DEFINITELY be set in a
failure route. OTHER pseudo variables are set in a failure route. Why not
the SIP response code? This is probably the most important pseudo variable
to have available in a failure route!
Douglas.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
8:16 p.m.
Douglas Garstang wrote:
Can someone tell me why the pseudo variable $rr (SIP
reply reason) is
not present in a failure_route?
If a call fails, this pseudo var contains the SIP response code, '404'
for a Not Found for example. I would think that it should DEFINITELY be
set in a failure route. OTHER pseudo variables are set in a failure
route. Why not the SIP response code? This is probably the most
important pseudo variable to have available in a failure route!
You can use t_check_status
(http://www.openser.org/docs/modules/1.2.x/tm.html#AEN407) in
failure_route, but I agree, it would be nice to have $rr working as well.
/Christian
12 Nov
12 Nov
6:57 a.m.
Hi all,
$rr is a shortcut the the reply reason of the currently processed reply.
But in failure route you do not process a reply, but a request (you
re-process the original request, in case of failure).
so, none of the PVs related to reply info will work.
As already suggested, use $T_reply_code from TM - this PV will return
the reply code of the winning reply (in the transaction engine).
regards,
bogdan
Christian Schlatter wrote:
Douglas Garstang wrote:
Can someone tell me why the pseudo variable $rr
(SIP reply reason) is
not present in a failure_route?
If a call fails, this pseudo var contains the SIP response code, '404'
for a Not Found for example. I would think that it should DEFINITELY be
set in a failure route. OTHER pseudo variables are set in a failure
route. Why not the SIP response code? This is probably the most
important pseudo variable to have available in a failure route!
You can use t_check_status
(http://www.openser.org/docs/modules/1.2.x/tm.html#AEN407) in
failure_route, but I agree, it would be nice to have $rr working as well.
/Christian
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
6156
days inactive
6159
days old
3 comments
4 participants
participants (4)
-
Bogdan-Andrei Iancu -
Christian Schlatter -
Douglas Garstang -
Ovidiu Sas