There's quite a lot of trace to go through there, but this screams that you're looping to me.. I suggest you look at the routing on the OTHER boxes, see if you can spot something that might be doing that.
On Tue, May 31, 2016 at 11:07 AM, Saioa Perurena < [email protected]> wrote: > Hi, > > We have only one proxy Opensips (version 1.11) that does all the work > (register's, invite's, tls conection...) on a DMZ behind a firewall. > > We want to move that to a new schema, with one Opensips (version 2.1) > as a frontend that handles the tls connections (with a public ip) on > the DMZ, and another Opensips (version 1.11) at the backend (with > private ip), but we are not able to complete the invite signaling > correctly. Register, message, options worked ok, but we have problems > with the invite. > The invite request arrives to the callee, and the OK answers arrives > to the caller, but the caller does not send and ACK to this OK, so the > callee keeps sending OK until it send a BYE because of timeout. > > Any idea of where is the problem or what am i doing wrong?? Any advice > will be appreciated!! > > I attach the sip_trace log and the Opensips script of the frontend server: > > Caller: sip:[email protected] > Callee: [email protected] > Opensips frontend ip: internal -> 192.168.3.35, external -> 192.168.1.18 > Opensips backend ip: internal -> 192.168.2.6 > > > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
