< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[reSIProcate-users] Jitsi-resiprocate ACK issue


Dear All,

For my telephony, I am using FreePBX. However, I would like to depend less on 
telecommunications providers and move more towards federation. Thus, I 
implemented a resiprocate gateway much as described here: 
http://www.rtcquickstart.org/sip-proxy-installation/repro

The only modification to the setup at http://www.opentelecoms.org is, that I 
would like to keep internal phones registered with the FreePBX server for the 
time being rather than with the gateway. For a start, I would like to be 
reachable via SIP-tls (i.e. call to e-mail address) and have calls forwarded 
from the WAN via the repro-proxy gateway to FreePBX and ultimately to local 
phones.

However, when connecting jitsi clients to the gateway, registration works, but 
calls do not go through. The correct phone does ring, but upon pickup, the 
jitsi client signals: "Failed to create ACK request!". The asterisk log in 
FreePBX does look normal, just as if someone did call but did hang up right 
after pickup. The repro messages in the syslog on the gateway server also look 
OK as far as I can tell. However, they are difficult to interpret in detail, as 
medium log levels do not reveal much while higher log levels create 
overwhelming amounts of hard to interpret output.

The same happens if I try to place a call between two jitsi clients which are 
both connected to the resiprocate gateway. If I connect the clients from the 
WAN instead of the LAN, a pfSense router running snort comes into play. Then 
the jitsi client LAN frequently gets blocked based on the "Empty request URI" 
preprocessor rule of snort. That should not happen of course, but I do not know 
how to fix it. If I connect the jitsi clients straight to the FreePBX server, 
however, everything works completely without issues both on the LAN and via VPN.

I would very much welcome if someone could point me to the right direction in 
order to cure this. Looking at the mailing list archive, I have seen some 
previous exchanges about ACK issues. However, I lack a human readable 
explanation as to how to solve this.

I do have both jitsi log files. They do contain statements like:

18:42:23.595 Schwerwiegend: [94847] impl.protocol.sip.SipLogger.logError().122
Error from the JAIN-SIP stack: ACK Was not sent. killing dialog 18:42:34.820
Schwerwiegend: [94847] impl.protocol.sip.SipLogger.logError().122 Error from the
JAIN-SIP stack: ACK Was not sent. killing dialog
18:42:42.821 Schwerwiegend: [94847]
impl.protocol.sip.SipStackSharing.processDialogTerminated().525 Dialog wasn't
marked, please report this to dev at sip-communicator.dev.java.net

If it helps, I would be glad to supply the pcap-file and the full log file, but 
I would prefer to mail the full files for privacy reasons.

Regards,

Michael Schefczyk