Some UAs, when not explicitly configured with an outbound proxy (some even in this), follow rfc's recommendation of sending a request with a preloaded route set containing one entry, that of what they think it is their outbound proxy, determined through various means. This is a problem when ser as a serving proxy for multiple domains does the loose_route'ing: if the route entry in the message is an ip address, ser will realise that it is him that must serve the request and everything goes smooth. BUT if the client places a virtual domain in the route set, ser is fooled to believe that it should just proxy forward the request. Forwarding might be ok, as ser will forward to itself (suboptimal), but in this case how can i prevent illegal relaying? How should this be elegantly dealt with? The most obvious answer is to add "alias"es, but i want to handle the domains through domain module only. Shouldn't the domain module have some functionality to load the domains as aliases (at least on demand by module parameter)? Thanks.

_______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers