Dear Giuseppe, How are you?
Are you using RTPproxy with PortaSIP? I believe this pattern represents the way their version of Sippy B2BUA talking to RTPproxy. Please confirm. It appears to be unintentional bug introduced in 1.1 that broke session matching logic resulting in two separate sessions being created on INVITE and on 200 OK. Please apply the following patch, recompile, reinstall and let me know if it helps or not. http://sobomax.sippysoft.com/~sobomax/rtpproxy.diff Giuseppe Cardone wrote: > Hi > > I'm having problems changing from rtpproxy 1.0.2 to 1.1 > I have installed the new version and although everything seems fine (rtp > proxy talks to SER and sets up ports correctly) > packets don't actually get proxied. > If I restart the 1.0.2 version on the same machine, everything works > fine (so it doesn't seem host config /OS issue). > > In particular when a call is set up by SER, rtpproxy log seems to show > the right thing (xxxx is the ip address): Regards, -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts T/F: +1-646-651-1110 Web: http://www.sippysoft.com _______________________________________________ Users mailing list Users@rtpproxy.org http://lists.rtpproxy.org/mailman/listinfo/users
