Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.networking > #1905

Need a method to prove incoming connection.

From Bit Twister <BitTwister@mouse-potato.com>
Newsgroups comp.os.linux.networking
Subject Need a method to prove incoming connection.
Date 2013-01-17 04:27 +0000
Organization A noiseless patient Spider
Message-ID <slrnkfevcu.44v.BitTwister@wb.home.test> (permalink)

Show all headers | View raw


I am trying to get ekiga to register with ekiga.net and with
diamondcard.us for VoIP

Fault isolation is ineffective because I can not prove each player
in this who done it.

Isolation points are:
ekiga 4.0.0
Mageia Linux release 3
pc firewall, shorewall
ActionTech router firewall.
port forwarding rules
Verizon FiOS
stun ports udp 3478-3479
sip ports  udp 5000-5100
H.323 port tcp 1720
dns resolver, named
ekiga stun server
ekiga register server
diamondcard register server

Currently I have a network_ck script, which pings each failure point
in the network ending at a ping of yahoo.com.
When any point fails, it prints out what failed and what to verify
and who is responsible for fixing it.

I want to do the same thing in a voip_ck script.

I hoping there is something that I can launch on the pc to listen on
a port number for a udp or tcp packet and get a response.
Script would look something like

_wan_ip=$(get_wan_ip.pl)

   #** start listener
some_cmd tcp 1720 > listen.txt

   #*** send a packet
some_other_cmd tcp #_wan_ip 1720
if [ $? -ne 0 ] ; then
  echo some_other_cmd tcp 1720 failed
fi

_count=$(grep -c "some string" listen.txt)
if [ $_count -eq 0 ] ; then
  echo some_cmd tcp 1720 failed to receive packet.
fi

I am hoping for some handy commands rather than writing a program in C or
maybe perl if there are modules for port/socket access.

Any and all suggestions welcome.

Back to comp.os.linux.networking | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Need a method to prove incoming connection. Bit Twister <BitTwister@mouse-potato.com> - 2013-01-17 04:27 +0000
  Re: Need a method to prove incoming connection. Joe Beanfish <joebeanfish@nospam.duh> - 2013-01-17 14:15 +0000
    Re: Need a method to prove incoming connection. Bit Twister <BitTwister@mouse-potato.com> - 2013-01-17 16:26 +0000
      Re: Need a method to prove incoming connection. Bit Twister <BitTwister@mouse-potato.com> - 2013-01-17 16:46 +0000

csiph-web