Re: [Serusers] Inoltra: Problems with Rtpproxy traffic balancing in SER 0.10.x

I've done correctly anything you wrote in your mail. I've found my mistake with $node: in database i put it with flag 32 instead of 33. Anyway one problem remains: it isn't enough inserting rtpproxy IP address in modparam (in ser.cfg). If I dont't give this IP to function/ force_rtp_proxy/ in ser.cfg it doesn't work, that is it doesn't write correctly rtpproxy IP in connection information (SDP) during SDP rewriting . I've looked at code. SER expects rtpproxy IP address in reply from rtpproxy. But rtpproxy in its message to SER doesn't write its IP!!!!! So in my ser.cfg I have to define a variable conteining rtpproxy IP address and I have to give it to function force_rtp_proxy. Only in this way it works. I wait for your replay. I'm using SER 10.0.x CVS version! Thanks in advance Angelo */Ladislav Andel &lt;ladaan(a)iptel.org&gt;/* ha scritto: It is saved in database table "user_attrs". Look at the page 24 in optimized_nat_traversal.pdf document how it should look like. UID in that table means username. The value of variable "node" means the index of RTPproxy starting from 0. For example: modparam("nathelper", "rtpproxy_sock", "unix:/var/run/rtpproxy.sock udp:5.6.7.8:22222") unix:/var/run/rtpproxy.sock is O udp:5.6.7.8:22222 is 1 Within your ser.cfg you load these AVP variables through load_attrs(); and use them in nat mangle route. You can check the value of "node" by dump_attrs(); before calling force_rtp_proxy and see if there is correct value. Lada Angelo Taddeo wrote: ------------------------------------------------------------------------ ------------------------------------------------------------------------ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail <%20http://us.rd.yahoo.com/mail/it/taglines/hotmail/nowyoucan/nextgen/*%20http://it.docs.yahoo.com/nowyoucan.html>