Hi all, I've read this from iptel website. It is true for SER 0.11.0. What about Openser 1.2 ?
" * Script processing of multiple branches on forking
Warning
ser's request processing language allows to make request decisions based on current URI. When a request if forked to multiple destinations, only the first branch's URI is used as input for script processing. This might lead to unexpected results. Whenever a URI resolves to multiple different next-hop URIs, only the first is processed which may result in handling not appropriate for the other branch. For example, a URI might resolve to an IP phone SIP address and PSTN gateway SIP address. If the IP phone address is the first, then script execution ignores the second branch. If a script includes checking gateway address in request URI, the checks never match. That might result in ignoring of gateway admission control rules or applying them unnecessarily to non-gateway destinations.
List of known problems is publicly available at the ser webpage at [70]http://www.iptel.org/ser/ . See the "ISSUES" link.
This is true for all versions of ser/openser.
Workaround: after lookup() (or whenever you do have multiple branches) if you want to make a check (e.g. checking RURI) you should do this in branch_route[].
regards klaus
Daniel wrote:
Hi all, I've read this from iptel website. It is true for SER 0.11.0. What about Openser 1.2 ?
"
Script processing of multiple branches on forking
Warning
ser's request processing language allows to make request decisions based on current URI. When a request if forked to multiple destinations, only the first branch's URI is used as input for script
processing. This might lead to unexpected results. Whenever a URI resolves to multiple different next-hop URIs, only the first is processed which may result in handling not appropriate for the other branch. For example, a URI might resolve to an IP phone SIP address
and PSTN gateway SIP address. If the IP phone address is the first, then script execution ignores the second branch. If a script includes checking gateway address in request URI, the checks never match. That
might result in ignoring of gateway admission control rules or applying them unnecessarily to non-gateway destinations.
List of known problems is publicly available at the ser webpage at [70]http://www.iptel.org/ser/ . See the "ISSUES" link.
-- Daniel Grotti ________________________ e-mail : d.grotti@gmail.com mailto:d.grotti@gmail.com
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
-
Daniel -
Klaus Darilion