[Serusers] Mediaproxy gets confused

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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)192.168.15.3: called signed in from 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)