It wont. On 07/05/2011 12:53 PM, Roman Gelfand wrote:
Are you saying that port 30400, in this case, will not change for the life of this call? On Mon, Jul 4, 2011 at 9:20 PM, Joegen Baclor <jbac...@ezuce.com <mailto:jbac...@ezuce.com>> wrote:Here is what is happening based on the pcap you sent. 1. Your soft phone (XLITE) sends an INVITE with private IP and port 59926. offered in SDP. 2. Karoo Bridge sends the offer to sipX via the internal interface. 3. destination starts sending RTP packets. 4. Karoo relays the packets to your Softphone public address on port 59926 (Take note that this port may change as soon as a first RTP packet is received from XLite). Karoo local port is 30400. the same port given in SDP answer. 5. Xlite sends first RTP packet (Datagram #149 in pcap) from port 24705 6. Firewall or whatever beast running on your edge device blocks the packet and responding with an ICMP error. Item number 5 (if it successfully makes it to Karoo) would have completed the far-end-nat traversal requirements and everyone lives happily ever after. I think your edge device tries to map port 30400->59926 permanently and packets coming from a different port going to 30400 are automatically blocked. Defintely a bad situation for far-end-nat. On 07/05/2011 04:35 AM, Roman Gelfand wrote:Hi Joegen, After trying to analyze this with my limitted knowledge, I am running into a wall. I had, since, taken away the firewall between wan and Karoo Bridge. The symptoms are the same. I have generated a tcpdump and was wondering if you see a problem. I have attached the tcpdump. Thanks, Roman On Sun, Jul 3, 2011 at 11:49 AM, Joegen Baclor <jbac...@ezuce.com <mailto:jbac...@ezuce.com>> wrote: Karoo or which ever application binding to a UDP port is beyond ICMP. The rule is if you see an error which says ICMP error, the culprit is always a firewall app or an application talking directly to the kernel. I am going to be a bit unhelpful here but the only thing I could advice is to make sure your firewall is not getting in the way. On 07/03/2011 08:02 PM, Roman Gelfand wrote:I had since put a sniffer on my firewall and this was the result 146.939239 [my firewall wan ip] -> [remote client's firewall wan ip]: icmp: [my firewall wan ip] udp port 30944 unreachable On Sun, Jul 3, 2011 at 7:06 AM, Roman Gelfand <rgelfa...@gmail.com <mailto:rgelfa...@gmail.com>> wrote: also, If I call pstn number from x-lite, it works. On Sun, Jul 3, 2011 at 6:47 AM, Roman Gelfand <rgelfa...@gmail.com <mailto:rgelfa...@gmail.com>> wrote: The firewall on the pc is off. On Sun, Jul 3, 2011 at 5:28 AM, Tony Graziano <tgrazi...@myitdepartment.net <mailto:tgrazi...@myitdepartment.net>> wrote: is there a firewall on the pc? if so does it have icmp blocked? On Jul 3, 2011 1:26 AM, "Roman Gelfand" <rgelfa...@gmail.com <mailto:rgelfa...@gmail.com>> wrote: > I am using x-lite softphone to register to SIPX via Karoo Bridge over WAN. > There is a firewall (transparent mode) between Karoo Bridge and WAN There > is a firewall betweet x-lite and WAN. The registration to sipx is > successfull. Calls from within sipx's local network to the x-lite softphone > are successfull. Calls from x-lite softphone to sipx's local network die on > invite. After looking at tcpdump, I found a message stating > > 15618 38.709230 "src IP" "dst IP" ICMP Destination unreachable (Port > unreachable) > > I suppose that this is the problem. > > What I am not sure about is src IP or dst IP is unreachable? > > > Thanks in advance _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org <mailto:sipx-users@list.sipfoundry.org> List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org <mailto:sipx-users@list.sipfoundry.org> List Archive:http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
