Re: alternate GKs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It means if we r defining more tahn ONE gk in alternateGKs then we shud also define more than one IP in sendTO varibale. i read this alreday in manual.
 
----- Original Message -----
From: Finny
Sent: Thursday, September 09, 2004 04:20 PM
Subject: RE: alternate GKs

Please see the following line which is taken from the manual
 

AlternateGKs=1.2.3.4:1719:false:120:OpenH323GK
Default: N/A

We allow for existence of another gatekeeper to provide redundancy. This is implemented in a active-active manner. Actually, you might get into a (valid !) situation where some endpoints are registered with the first and some are registered with the second gatekeeper. You should even be able use the two gatekeepers in a round_robin fashion for load-sharing (that's untested, though :-)). If you read on, "primary GK" refers to the gatekeeper you're currently configuring and "alternate GK" means the other one. The primary GK includes a field in the RCF to tell endpoints which alternate IP and gatekeeper identifier to use. But the alternate GK needs to know about every registration with the primary GK or else it would reject calls. Therefore our gatekeeper can forward every RRQ to an alternate IP address.

The AlternateGKs config option specifies the fields contained in the primary GK's RCF. The first and second fields of this string define where (IP, port) to forward to. The third tells endpoints whether they need to register with the alternate GK before placing calls. They usually don't because we forward their RRQs, so they get registered with the alternate GK, too. The fourth field specified the priority for this GK. Lower is better, usually the primary GK is considered to have priority 1. The last field specifies the alternate gatekeeper's identifier.

SendTo=1.2.3.4:1719
Default: N/A

Although this information is contained in AlternateGKs, you must still specify which address to forward RRQs to. This might differ from AlternateGK's address, so it's a separate config option (think of multihomed machines).

-Finny

-----Original Message-----
From: openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx]On Behalf Of Rafat Subhan
Sent: Thursday, September 09, 2004 4:25 PM
To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: alternate GKs

then what IP i shud send in sendTO variable..?in case of diff IPs
 
 
----- Original Message -----
From: Finny
Sent: Thursday, September 09, 2004 03:47 PM
Subject: RE: alternate GKs

Hi
   You Can see the example
 
AlternateGKs=192.168.105.92:1719:true:120:H323GK;192.168.105.10:1719:true:100:GnuGK
                       Ip Address       Port Need to Register Flag Priority GK Identifier
 
You can have more than one GK separated by semicolan.
 
-----Original Message-----
From: openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx]On Behalf Of Rafat Subhan
Sent: Thursday, September 09, 2004 3:55 PM
To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: alternate GKs

Ok silence from all.it means we can define only one GK in it. thanx
----- Original Message -----
Sent: Thursday, September 09, 2004 10:10 AM
Subject: Re: alternate GKs

 
because wen i read manual, it only discuss one GK. Am I right?
----- Original Message -----
Sent: Wednesday, September 08, 2004 04:18 PM
Subject: alternate GKs

can we define more than one GK in alternateGks field, If so then how will they manage in round robin or priority wise.

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux