Sven, did you get a fix?
I'm having a similar problem on 4.2.1. with SipXecs replying to Incoming calls from Bandwidth.com with seemingly inconsistent contact info in the 200 OK reply to the Invite. Sometimes the contact contains the public IP and sometimes the Private IP of the primary server. This acts like a failed transfer to the caller but it is actually SipXecs timing out waiting for the ACK (Which BW.com is trying to send to the private IP in the contact field of the 200 OK). I have a thread open but I'm not getting much activity. Good Luck Ray _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
