[Sipwitch-devel] Using sipwitch for WAN/LAN calls

[BM-2cTegh37RKoJedFakFBpdqYiwz3cf2szQm]

Hi,

I've been trying to properly set up sipwitch for WAN/LAN use. I want WAN
clients to be able to connect to other WAN clients and also those on my
local LAN.
LAN/LAN (scenario A) works without a problem (using Linphone).

I tried to follow all of this (and I read the complete mailing list), to
no avail so far:
http://forums.debian.net/viewtopic.php?f=16&t=76620
https://lists.gnu.org/archive/html/sipwitch-devel/2012-02/msg00010.html


In scenario A (LAN / LAN)
=========================
I get this on tcpdump (on the system running sipwitch):
192.168.1.2 = client
192.168.1.3 = sipwitch
---------------------------------------------------------------
192.168.1.2.5060 > 192.168.1.3.5060: SIP, length: 393
192.168.1.2.5060 > 192.168.1.3.5060: SIP, length: 762

192.168.1.3.5060 > 192.168.1.2.5060: SIP, length: 497

192.168.1.2.5060 > 192.168.1.3.5060: SIP, length: 566

192.168.1.3.5060 > 192.168.1.2.5060: SIP, length: 307
192.168.1.3.5060 > 192.168.1.2.5060: SIP, length: 510

192.168.1.2.5060 > 192.168.1.3.5060: SIP, length: 4


And this reaction by sipwitch:
---------------------------------------------------------------
sipwitch: registry cleanup; no entries expired
sipwitch: registry cleanup; no entries expired
sipwitch: sip: event new(23); cid=0, did=0, instance=udp
sipwitch: challenge request required
sipwitch: sip: event new(23); cid=0, did=0, instance=udp
sipwitch: authorizing local; target=USER_A
sipwitch: rewrite process; target=USER_A, dialing=USER_A
sipwitch: rewrite process; registry=(nil), dialed=0x57035c
sipwitch: unregistered destination USER_A
sipwitch: rejecting invite from address@hidden; error=410
sipwitch: sip: event new(23); cid=0, did=0, instance=udp
sipwitch: activating USER_A; extension=201
sipwitch: registering USER_A(201) for 3600 seconds from 192.168.1.2:5060
sipwitch: logfile: activating USER_A 2014-01-12 19:31:00
sipwitch: registry cleanup; no entries expired
sipwitch: registry cleanup; no entries expired


Which results in a functional connection between the 2 clients.


In scenario B (WAN / LAN) however
=================================
123.123.123.123 is the WAN (Internet) host connecting to 192.168.1.3 which
is a LAN host running sipwitch, behind NAT.
The tcpdump output, which again is from the system running sipwitch, shows
that the packages arrive at the correct port:

123.123.123.123.55397 > 192.168.1.3.5060: SIP, length: 381
123.123.123.123.55397 > 192.168.1.3.5060: SIP, length: 4
123.123.123.123.55397 > 192.168.1.3.5060: SIP, length: 4
123.123.123.123.55397 > 192.168.1.3.5060: SIP, length: 4
123.123.123.123.55397 > 192.168.1.3.5060: SIP, length: 4

but no reply from sipwitch is being sent out.

Below is the startup configuration listing:
---------------------------------------------------------------
sipwitch: new realm 192.168.1.3
sipwitch: media proxy configured for 38 ports
sipwitch: scanning config from /home/DIR
sipwitch: adding policy loopback for 127.0.0.0/8
sipwitch: adding policy loopback for ::1
sipwitch: adding policy lo for 127.0.0.1/255.0.0.0
sipwitch: adding policy eth0 for 192.168.1.3/255.255.255.0
sipwitch: adding policy local for 192.168.1.0/24
sipwitch: adding user USER_A
sipwitch: adding user USER_B
sipwitch: adding user USER_C
sipwitch: scanning users and groups
sipwitch: adding admin root
sipwitch: adding admin USER_A
sipwitch: startup
sipwitch: starting registry; mapping 200 entries
sipwitch: starting sip stack v4; 200 maps
sipwitch: starting cdr thread
sipwitch: listening port 5060 for udp
sipwitch: listening port 5060 for tcp
sipwitch: starting event thread udp
sipwitch: starting event thread tcp
sipwitch: starting media proxy
sipwitch: logfile: server starting 2014-01-05 21:40:11
sipwitch: starting event dispatcher
sipwitch: notify watching /home/DIR
sipwitch: starting signal handler
sipwitch: starting media thread
sipwitch: starting background thread
sipwitch: registry cleanup; no entries expired
sipwitch: registry cleanup; no entries expired
sipwitch: registry cleanup; no entries expired
sipwitch: registry cleanup; no entries expired
sipwitch: registry cleanup; no entries expired

================================================================================

I would highly appreciate it, if someone could point me to where to look
next or which part of the configuration to change.

Regards,
Arthur