You
are correct. I unregistered my endpoint and then was able to dial it via IP.
This doesn't seem right though. My test
endpoint has a public IP so I should be able to connect to it via
IP. It happens to be registered directly to the state gatekeeper so anyone who
is also registered to the state GK can connect via E.164 extension OR public IP.
In our state most (if not all) K12 end points have public IPs and are registered
to the state GK. It is common when there are point to point calls to use IP's
for dialing versus E.164 extensions. That very scenario happened to us a few
weeks ago and that is how I discovered the problem. We finally had to ask them
to give us their extension and then we were able to
connect.
Here are the results of my testing. Note that EP1 is on
a LAN and EP2 has a WAN connection and all dialing is done from
EP1.
Case 1
EP1-->Polycom V2IU-->State
GnuGK
EP2-->State GnuGK
dial by IP: succeeds
dial by E.164:
succeeds
Case 2
EP1-->proxy GnuGK-->State
GnuGK
EP2-->State GnuGK
dial by IP: fails
dial by E.164:
succeeds
Case 3
EP1-->proxy GnuGK-->State
GnuGK
EP2-->proxy GnuGK-->State
GnuGK
dial by IP:
succeeds
dial by E.164:
succeeds
Case
4
EP1-->proxy GnuGK-->State
GnuGK
EP2-->no GK
dial by IP:
succeeds
Case
5
EP1-->proxy GnuGK
EP2-->State
GnuGK
dial by IP:
fails
Case 6
EP1-->proxy GnuGK
EP2-->no
GK
dial by IP:
succeeds
Is
there a way with GnuGK to proxy all H.323 traffic (LAN <--> WAN), register
our E.164 extensions with the state GK and still be able to dial end points via
their public IP's? (The Polycom V2IU is able to do this)
Thanks,
Andrew
From: openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Simon Horne
Sent: Wednesday, July 16, 2008 9:02 PM
To: GNU Gatekeeper Users
Subject: Re: Dial by IP failsAndrewI suspect you are calling an endpoint at the IP address which is registered with a gatekeeper. You cannot call this directly you must call the gatekeeper it is registered with.Simon-----Original Message-----
From: openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx]On Behalf Of Andrew Struiksma
Sent: Thursday, 17 July 2008 9:31 AM
To: GNU Gatekeeper Users
Subject: Re: Dial by IP failsIt appears that my calls are failing because of "routeCallToGatekeeper." Does ArjReasonRouteCallToGatekeeper have anything to do with this?Andrew Struiksma
K20 Network Support Specialist - NW Regional Video ITU
Northwest Educational Service District
From: openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Andrew Struiksma
Sent: Monday, July 07, 2008 3:03 PM
To: GNU Gatekeeper Users
Subject: Dial by IP failsI just discovered that I cannot dial out through our proxy GK by IP address. We can only dial via E.164 extension. All my video end points are NATed behind the GK. Typically we dial via E.164 extension and our GK sends all the signal traffic to the state gatekeeper.What could be causing this problem?The typical signaling path for a call made using an E.164 extension is as follows:our video endpoint<-->our proxy GnuGK<-->state GnuGK<-->remote video endpointI've compared the log of a call to the same end point via IP address and E.164 extension. Here are the differences that I've discovered:IP--no ARQ is sent to state GKIP--no "IE: Called-Party-Number" in the section labeled "ProxyChannel.cxx(842) Q931 Received: {"IP--no message such as "ProxyChannel.cxx(1627) Q931s GWRewrite source for 10.2.5.127:1030: call record"IP--proxy channel "ProxyChannel.cxx(899) Q931d Received: Facility"Ext--proxy channel "ProxyChannel.cxx(899) Q931d Received: Alerting"IP--has this section:h323_uu_pdu = {
h323_message_body = facility {
protocolIdentifier = 0.0.8.2250.0.4
alternativeAddress = ipAddress {
ip = 4 octets {
<IP of state GK>}
port = 1720
}
conferenceID = 16 octets {
02 2a cf 3c 39 f7 19 17 2a 96 63 60 19 de bf 8d .*.<9...*.c`....
}
reason = routeCallToGatekeeper <<null>>IP--the call is cleared with this message:ProxyChannel.cxx(842) Q931 Received: {
q931pdu = {
protocolDiscriminator = 8
callReference = 21162
from = originator
messageType = ReleaseComplete
IE: Cause - Normal call clearing = {
80 90 ..
}
IE: User-User = {
25 c0 06 00 08 91 4a 00 04 80 01 00 11 18 11 00 %.....J.........
02 2a cf 3c 39 f7 19 17 2a 95 63 60 19 de bf 8d .*.<9...*.c`....
01 00 01 40 10 80 01 00 ...@....
}
}
h225pdu = {
h323_uu_pdu = {
h323_message_body = releaseComplete {
protocolIdentifier = 0.0.8.2250.0.4
reason = facilityCallDeflection <<null>>How can I correct this problem so that I can complete calls via IP address?Thanks!Here is my INI file:-----------------------------------------------------------------[Gatekeeper::Main]
Fortytwo=42
Name=NWESD-GK1
ExternalIP=<GK IP>[RoutedMode]
GKRouted=1
H245Routed=1
CallSignalPort=1720
EndpointSignalPort=1721
CallSignalHandlerNumber=5
AcceptNeighborsCalls=1
SupportNATedEndpoints=1
Q931PortRange=20000-20015
H245PortRange=30000-30015
AcceptUnregisteredCalls=1
SupportCallingNATedEndpoints=1[Proxy]
Enable=1
ProxyForNat=1
ProxyForSameNAT=0
T120PortRange=40000-40015
RTPPortRange=50000-50099[Endpoint]
Gatekeeper=<state GK IP>Type=Terminal
Vendor=GnuGK
H323ID=NWESD-GnuGK1
E164=00114790801488[RasSrv::ARQFeatures]
CallUnregisteredEndpoints=1[RasSrv::RRQFeatures]
SupportDynamicIP=1
OverwriteEPOnSameAddress=1
-----------------------------------------------------------------Andrew
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
