a c wrote:
Isn't this a bug interms of RFC? Shouldn't the ruri contain the next hop address?
ac, I'm really not an RFC expert, I just read it when I need an answer to a specific question... However, I believe this is perfectly valid for some situations and the same thing as when you do ex. a t_relay_to_udp().
As for making changes to the dispatcher module..this will be dangerous in my hands :-( Could someone add this?
Contact the maintainer, I think it is Klaus? He should be able to answer why the dst_uri and not ruri is changed and whether adding a flag for changing ruri is a good idea. g-)
thank you ac
--- "Greger V. Teigre" greger@teigre.com wrote:
I believe dispatcher changes dst_uri (the uri the message will be sent to, not the ruri). I'm not aware of any function that will copy the dst_uri to ruri, but maybe avpops can do that?! Anyway, it should be fairly straightforward adding a parameter to dispatcher controlling whether also the ruri will be changed. After a quick check (no guarantees), I believe you can use this function in the same location in dispatcher module where set_dst_uri is called: int rewrite_uri(struct sip_msg* _m, str* _s)
g-)
a c wrote:
hello,
I have SER doing load balance across app servers.
I
would like SER to change the request URI with the ipaddress of the server in the returned
destination
set{using dispatcher module to Load balance}. How would I do this?
rewritehost(?)
regards, ac
Discover Yahoo! Find restaurants, movies, travel and more fun for
the weekend. Check
it out! http://discover.yahoo.com/weekend.html
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com