the truth is that I don't have any gk configuration. The GK is a polycom pathnavigator. I don't know if this is the problem but, I think that al least I must to see a rrq from the gw. there is nothing. In theory with the comand gateway, the gw must to start sending rrq messages
I have tried with the ip address of the gk and with the option multicast for gk discovery, but nothing happens.
The only time you use RAS and H323 registration is between Cisco GW and GKs.. i dont think it will work at all with other vendors equipment. The RAS messages are proprietary I believe.
The only reason to use GW to GK registration is for call admissions control and signaling. Im not really familar with the pathnavigator.
For example with the Cisco GW and GK, it behaves as follows:
Local H323 receives an incoming message or request... example, dial pattern 8* Dial Peer 1 has patter 8* pointed to RAS.
RAS is regisreted with designated GK from the Loopback or Ethernet interface on the GW.
GK receives the signal or request for connection, looks up on it's table for 8*, which zone local or remote and then sends the call off to the next device (GK or GW)
Once the signal is established, the RAS connection simply monitors the connection status. The actual RTP packets are from GW to GW.
So if your polycomnavigor is doing RTP packets as well, you are better off not trying to use registration and send the call to the polycom as a Dial peer, IP xxx.xxx.xxx. h323, codec, etc. The RAS is not doing any good for you.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...