sipwitch-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sipwitch-devel] My testing setup


From: Earl
Subject: Re: [Sipwitch-devel] My testing setup
Date: Tue, 28 Feb 2012 12:43:11 +0100
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0) Gecko/20120129 Thunderbird/10.0

@ Gernot

if you have a server, either in the DMZ, or with port forwarding, you can test if
packets are getting to your server by using the following generic service:

http://www.canyouseeme.org/

put in each port you wish to test and it will tell you if your port can be seen from
outside.

Please let the list know some feedback how this test functions.

Earl

On 28/02/2012 9:39, David Sugar wrote:
Since you are attempting to "connect" to the publicly appearing routing
address, sip.dyndns.org, from the external pc, where will it attempt to
connect to?  It sounds like it would try to connect to the public
appearing address of your nat/router box.  SIP Witch sits inside your
network.  The fact that sipwitch shows no activity I think indicates
indeed no sip packets were received by it, though this can be confirmed
with wireshark.  The question is what happened at the router, did they
even arrive there?  Does it indeed forward UDP ports successfully?

On 02/27/2012 09:35 AM, Gernot Super wrote:
System: Debian Squeeze with the latest sipwitch behind router(ports
5060,5061 forwarded), sip.dyndns.org, user1 running on local pc where
sipwitch server is installed, user2 external, Clients: Jitsi (latest
beta nightly)


/etc/sipwitch.conf:

<?xml version="1.0"?>
<sipwitch>
<provision>
<user id="user1">
<secret>user1</secret>  <extension>201</extension>  <display>USER1 - Jitsi
at local pc where sipwitch server is running</display>
</user>
<user id="user2">
<secret>user2</secret>  <extension>202</extension>  <display>USER2 - Jitsi
- external via usb-key</display>
</user>
</provision>
<access>
<local>192.168.0.0/24</local>
</access>
<stack>
<!--
<localnames>sip.dyndns.org</localnames>
-->
<!--
<restricted>local</restricted>
<trusted>local</trusted>
-->
<mapped>200</mapped>
<threading>2</threading>
<interface>*</interface>
<dumping>false</dumping>
<!--
<peering>sip.dyndns.org</peering>
-->
<system>system</system>
<anon>anonymous</anon>
</stack>
<timers>
<!-- ring every 4 seconds -->
<ring>4</ring>
<!-- call forward no answer after x rings -->
<cfna>4</cfna>
<!-- call reset to clear cid in stack, 6 seconds -->
<reset>6</reset>
</timers>
<registry>
<prefix>200</prefix>
<range>100</range>
<keysize>77</keysize>
<mapped>200</mapped>
<realm>output from 'sipwitch realm'</realm>
</registry>
<!--
<templates>
<user>
<secret>123</secret>
<forwarding>
<busy>voicemail</busy>
<na>voicemail</na>
</forwarding>
</user>
<admin>
<forwarding>
<busy>operator</busy>
<na>operator</na>
</forwarding>
</admin>
</templates>
-->
<routing>
</routing>
</sipwitch>

Since debian started sipwitch after installation i had to stop it first.
Afterwards i edited the configuration file and started sipwitch with
sipw -x9 -f.
Then executed jitsi on the same pc, added address@hidden and
password - user1 was recognised from the server with the external
dyndns-IP, registered and activated. Jitsi says user1 is online.

So far so good. Fired up another pc, internet-connection with usb-key,
started jisti, added address@hidden -->  Jitsi: Could  not connect.
-->  sipwitch: no sign of connection
Both logfiles not informative :-(

ANY help would be very appreciated.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]