Hi, I was wondering whether anyone has seen this strange error before. It happens intermittently, where mediaproxy gets confused as to who the "called" IP is, it thinks the caller is the called and switches back and forth.
Any ideas?
rusl..
May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
Hi, just to let everyone know, I found the problem.. In mediaproxy 1.4.2, they added a new "feature" which allows the called user to change his media stream with a 183, 200 status w/ SDP. But the thing is that usually it's the caller that initiates a mediachange, so when the caller sent a 200 or 183 for media change, mediaproxy thought it was the called that had a media change, and basically connected the caller to itself by saying that the caller was the called.
I fixed it by "reversing" the functionality in mediaproxy.
On Wednesday 24. May 2006 22:04, rusl wrote:
Hi, I was wondering whether anyone has seen this strange error before. It happens intermittently, where mediaproxy gets confused as to who the "called" IP is, it thinks the caller is the called and switches back and forth.
Any ideas?
rusl..
May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) May 24 21:58:08 voice mediaproxy[15520]: session 7A99B4CF-725E-0952-8C5A-7C17443072C7@192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
rusl