Re: Invalid call signalling address

["ian" <ian@xxxxxxxxxxx>]

Hi,

 

Thanks for your suggestion but the GW is not registered to my Gatekeeper. The GW is owned by a telco and the only way to connect is via public interface. Once the telco gateway receives the Setup with a local callSourceSignalAddress, it wont be able to route the signalling messages back to me, thus rejecting the call.

 

regards,

 

ian

----- Original Message -----

From: Prashant Samant

To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx

Sent: Tuesday, August 23, 2005 7:52 PM

Subject: Re: Invalid call signalling address

Hi,

You can do this by external routing. You can add a static route to GW2 via public interface (assuming the GW2 is available via public interface).

 

Regards,

Prashant

----- Original Message -----

From: ian

To: OpenH323Support

Sent: Tuesday, August 23, 2005 4:31 PM

Subject: Invalid call signalling address

Hi guys,

 

My gatekeeper server has two network interface, one public and one local. My gatekeeper is configured as gatekeeper routed (GKRouted = 1) with proxy disabled (Enable=0). Call setup is like below:

 

 

    TERMINAL ==(Setup1)==>>> GATEKEEPER ==(Setup2)==>>> GATEWAY

 

My problem is that the sourceCallSignalAddress in Setup2 sent by the Gatekeeper to Gateway is the local ip address which causes the GW to reject the call. But Setup1 entered the gatekeeper via public IP. Is there a way to specify to the gatekeeper which network interface to use? I also dont want to set Home and NetworkInterfaces to just the public interface.

 

Thanks!

 

ian