Re: [reSIProcate] repro doesn't react to sip INVITE in a remote server, but works correctly in LAN

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

FYI - Allen's problem was the Windows Firewall.

Scott

On Fri, Nov 4, 2011 at 8:46 PM, Allen <allenguan@xxxxxxxxx> wrote:

Hi, Scott,

Sorry for my unclear wording.

my conference server which is written with RESIP uses the default 5060
udp/tcp port.

it uses the SipStack class' function:

sipstack.addTransport(UDP, 5060, V4, StunEnabled);
sipstack.addTransport(TCP, 5060, V4, StunEnabled);

this code is the same as the code in repro. both program run in the same
machine, my conference server works, the repro doesn't work.

but eventually I figured it out, it's the Windows Firewall blocked the
traffic, the Windows Firewall need to add repro into a list to let the
traffic go through. Even I can use Microsoft Network Monitor to observe
the arrival of the sip INVITE message, it didn't reach to repro.

For #2, I use tcpview which is freely available from Microsoft, I can
see no other application is making use of 5060, sure I tried the netstat
-ab as you suggested as well.

Thanks!

-Allen

On 11/4/2011 5:23 PM, Scott Godin wrote:
> Your wording is unclear. I don't understand what you are saying about
> the checks I asked of you. For #1 - what port is your app listening on?
> What port does the network trace show the sip message is arriving on?
> For #2 why can't you run netstat -ab without your app running?
>
> Sent from my Windows Phone From: Allen
> Sent: Friday, November 04, 2011 7:19 PM
> To: Scott Godin
> Subject: Re: [reSIProcate] repro doesn't react to sip INVITE in a
> remote server, but works correctly in LAN
> Hi, Scott,
>
> Thanks a lot for your prompt reply.
>
> my conference sever which is built with RESIP, and exactly same code to
> set up the SipStack class instance, can work correctly on this machine.
> So I can't see check 1& check 2 should have problem.
>
> I ran a sip client in this machine to send the sip INVITE to the repro,
> the repro can capture the sip INVITE.
>
> I put a log line in UdpTransport::processRxRecv() to see if it can
> receive anything, if I sent the sip INVITE from my office to this
> machine running in data center, the recvfrom() doesn't return. but if I
> send the sip INVITE from the same machine, it prints out the size of the
> data received by recvfrom().
>
> Is there any way to narrow down this issue?
>
> Thanks a lot for your help!
>
> -Allen
>
> On 11/4/2011 2:35 PM, Scott Godin wrote:
>> A couple of things to check:
>> 1 - resip transports are listening on the same interface and port that
>> the messages are arriving on.
>> 2 - no other application is also listening on this port. With your
>> resip app shutdown - try running netstat -ab to check. I have seen
>> cases where SQL server will use UDP port 5060.
>>
>> Scott
>>
>> Sent from my Windows Phone From: Allen Guan
>> Sent: Friday, November 04, 2011 3:02 PM
>> To: resiprocate-devel
>> Subject: [reSIProcate] repro doesn't react to sip INVITE in a remote
>> server, but works correctly in LAN
>> Hi, all,
>>
>> I am testing repro, first I test it in LAN, it works correctly and
>> forward the sip INVITE to the conference server. then I install repro
>> in a remote server running windows small business server 2011 which is
>> running behind a router, port forwarding is set up correctly. My
>> conference server written with resip can correctly response to a sip
>> INVITE when running in this server, then I stop my conference server
>> and start the repro, to my surprise, the repro seems can't detect the
>> sip INVITE. I check the code in Proxy::thread(), enable the following
>> line at line 104:
>>
>> DebugLog (<< "TransactionUser::postToTransactionUser " << " &=" <<
>> &mFifo << " size=" << mFifo.size());
>>
>> all I can see is ".. size = 0 ...", it doesn't capture the sip INVITE.
>>
>> I use Microsoft Network Monitor to capture the traffic, I can see the
>> sip INVITE does arrive this server, just the repro could not capture
>> it, would any one please give me any suggestion for this?
>>
>> Thanks a lot in advance.
>>
>> -Allen
>> _______________________________________________
>> resiprocate-devel mailing list
>> resiprocate-devel@xxxxxxxxxxxxxxx
>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel