29 Dec
2011
29 Dec
'11
3:53 p.m.
would it be a big deal to extend onsend route to work also on replies or
introduce a new onsend_reply_route for that purpose?
for example, i would like to be able to change response code/reason to
something else in such a route based on some conditions (flags, avp
values).
-- juha
29 Dec
29 Dec
4:58 p.m.
Hello,
On 12/29/11 2:53 PM, Juha Heinanen wrote:
would it be a big deal to extend onsend route to work
also on replies or
introduce a new onsend_reply_route for that purpose?
for example, i would like to be able to change response code/reason to
something else in such a route based on some conditions (flags, avp
values).
in onsend_route, the content of outgoing buffer cannot be changed for
requests, it is the one printed with via/record-route/route headers. It
should be the same for replies (e.g., via stack updated), so even
extended, the route block does not seem to meet your needs.
Do you want for local replies also, or just for received?
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
5:05 p.m.
Daniel-Constantin Mierla writes:
Do you want for local replies also, or just for
received?
yes, that is why i asked. it is easy to handle replies from external
sources in onreply_route.
i can make the checks before calling send_reply() in the script, but
it would have been easier to do the work in one place.
-- juha
4712
days inactive
4712
days old
2 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Juha Heinanen