<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Michael and other FreeSWITCH gurus:<br>
<br>
As per your instruction, I have created logs. <a
href="http://pastebin.freeswitch.org/14479">Please take a look</a>.
It includes FS's messages while it initializes itself. The VoIP
adapter (SIP gateway, which also works as a router)'s IP address is
<b>192.168.11.250</b> on the LAN side. That of the PC which is
running FS is <b>192.168.11.11</b>. Its firewall function was
turned off during this testing. The summary of packet exchange
between the two during this same period is <a
href="http://pastebin.freeswitch.org/14480">here</a>. Please see
my original posting (which is included at the end of this message)
for the setup of my home LAN.<br>
<br>
~250 is sending RTCP receiver report before ~11 starts RTP
communication. I am wondering if the former is giving up on the call
because of time out; and, if it is true, if there is any way to have
it wait longer.<br>
<br>
I am completely stuck about this issue and I'll welcome any input
you have. <br>
<br>
Thanks!<br>
<br>
Yasuro<br>
<br>
Michael Collins wrote (11/12/2010 4:43 AM):
<blockquote
cite="mid:AANLkTimABv33uCx8eZr=vD=++sVjZty-dgUn5xwNnJSg@mail.gmail.com"
type="cite">Run your same test on FreeSWITCH but turn on sip
debugging at the fs_cli:<br>
sofia global siptrace on<br>
<br>
Then make the call and capture the output and put into new
pastebin. Hopefully you'll see why the channel is already hungup
when it goes to play music.<br>
-MC<br>
<br>
<div class="gmail_quote">2010/11/10 Yasuro <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:yasuro@yasuro.com">yasuro@yasuro.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"> Hi, FreeSWITCH gurus! I
need your help!<br>
<br>
First off, I am new to FS and I am new to Internet telephony
as well. Heck, I am new to the concept of NAT, UPnP, etc.,
so please bear with my ignorance.<br>
<br>
I subscribe to a VoIP service at home, with which I get one
DID. They supply me a VoIP adapter. Their expected usage is
for you to plug in analog phones to the analog phone jacks
in the VoIP adapter. However, It also has four Ethernet LAN
ports and it acts as a router. You can also access it from
the LAN side and register with its built-in SIP gateway. <br>
<br>
What I would like to do is to run FS (Windows version) on
one of the Windows PCs, have it register with the SIP
gateway, and have it act as an AA or IVR. For testing, I am
having it just play music.<br>
<br>
When I tried the same idea with AsterikWin32, it worked just
as I had hoped; it answered incoming calls automatically.
However, I somehow cannot make it work with FS. I simulate
incoming calls to my DID number with Skype's Sypeout. It
fails after a short while with such error messages as
"network error." It appears the call was never answered.<br>
<br>
FS is assigned an extension number 7 at the gateway. When I
call extension 7 from a different extension (at the gateway
level, not an extension inside FS), FS does answer the call
and I hear music. FS fails to answer only incoming calls
from outside.<br>
<br>
I think my FS configuration is fairly standard. I created an
external SIP profile for the gateway under
conf/sip_profiles/external/ and modified
conf/dialplan/public/00_inbound_did.xml so incoming calls to
the gateway will be transferred to an extension within FS.<br>
<br>
FS's messages and logs, plus the result of packet captures
indicate that FS <i>thinks </i>it has answered the call,
and goes on to initiate media communication. I see RTP
packets going from FS to the SIP gateway. What's different
from AsteriskWin32's case is that there are no RTP packets
coming back from the SIP gateway to FS. Turning of the
firewall of the PC does not seem to change the result in any
way.<br>
<br>
For your perusal, I have created the following logs of
communication between FS/AsteriskWin32 and the SIP gateway:<br>
<ul>
<li>AsteriskWin32's case</li>
<ul>
<li>Summary: <a moz-do-not-send="true"
href="http://pastebin.freeswitch.org/14457"
target="_blank">http://pastebin.freeswitch.org/14457</a><br>
</li>
<li>Details: <a moz-do-not-send="true"
href="http://pastebin.freeswitch.org/14460"
target="_blank">http://pastebin.freeswitch.org/14460</a></li>
</ul>
<li>FreeSWITCh's case</li>
<ul>
<li>Summary: <a moz-do-not-send="true"
href="http://pastebin.freeswitch.org/14462"
target="_blank">http://pastebin.freeswitch.org/14462</a></li>
<li>Details: <a moz-do-not-send="true"
href="http://pastebin.freeswitch.org/14463"
target="_blank">http://pastebin.freeswitch.org/14463</a></li>
<li>Log: <a moz-do-not-send="true"
href="http://pastebin.freeswitch.org/14465"
target="_blank">http://pastebin.freeswitch.org/14465</a><br>
</li>
</ul>
</ul>
The IP address of the SIP gateway is <b>192.168.11.250</b>,
and that of the PC FS/AsteriskWin32 resides in is <b>192.168.11.11</b>.
My DID number is masked as ABCDEFGHIJ. I do not know if it
gives you any useful information, but those files include
the registration phase. <i>FS's log was taken at a
different time</i>, so it does not entirely match the
packet captures. <br>
<br>
I also have the corresponding Pcap files. Please let me know
if you need them.<br>
<br>
I am not entirely sure, but I think as far as what I'd like
to do is concerned, NAT is not going to be an issue, because
the FS/AsteriskWin32 PC and the SIP gateway (its LAN side IP
address) are on the same subnet (192.168.11/24). At this
time, I do not need to access FS from the Internet.<br>
<br>
Finally, I will give you more details about my setup, which
may or may not be relevant to this issue.<br>
<br>
My home LAN is set up this way: <br>
<a moz-do-not-send="true"
href="http://i139.photobucket.com/albums/q302/starplatina/For%20Blogs/HomeLANSetup.jpg"
target="_blank">http://i139.photobucket.com/albums/q302/starplatina/For%20Blogs/HomeLANSetup.jpg</a><br>
Please note that there are <i>two layers</i> of NAT, and
that in the inner layer, two NAT devices exist. I know it
looks convoluted, but there are logical reasons for this
setup. <br>
<br>
The VoIP service provider only supports the PCMU codec. The
music file I prepared for this testing is encoded in PCMU,
so codecs will not be an issue.<br>
<br>
Please do not hesitate to ask if you have any questions.
Thanks for your help in advance!<br>
<br>
Yasuro<br>
<br>
<br>
</div>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a moz-do-not-send="true"
href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a moz-do-not-send="true"
href="http://lists.freeswitch.org/mailman/options/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a moz-do-not-send="true" href="http://www.freeswitch.org"
target="_blank">http://www.freeswitch.org</a><br>
<br>
</blockquote>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
FreeSWITCH-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre>
</blockquote>
<br>
</body>
</html>