Endpoint prefix and GatewayPriority

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

 



Hello,
 
There's an easy feature that you might want to keep in mind to program for the next version of gnugk (If I'll have the time I'll do it, but first I have to study the code).
 
The problem is like this:
 
-------------------------------------------------------
[RasSrv::PermanentEndpoints]
1.1.1.9=ger;0049,004933
1.1.1.170=ger2;0049,004931
[EP::ger2]
Capacity=30
GatewayPriority=1
 

[EP::ger]
Capacity=30
GatewayPriority=2
-------------------------------------------------------------
 
In this scenario, a call to 004931555555 goes to ger2. If ger2 is full, calls will be rejected with "resourceUnavailable".
A call to 004933555555 goes to "ger" and if "ger" is full it doesn't goes to ger2.
 
What I'm sugesting for the next version is for you guys to keep in mind 2 things: 
 
1. Prefix 004933 is more specific than 0049, but if 004933 fails because of capacity, route to the next gateway that has a less specific prefix (0049).
 
2. This is a more important feature. It would be nice to have endpoint priority for each supported prefixes.
        For the scenario above, the "ger" endpoint to have priority 1 for 004933 and priority 2 for 0049 and endpoint "ger2" to have priority 1 for 004931 and priority 1 for 0049. Anyway, you get the ideea.
 
P.S.: Don't take the example for granted. If it's not complicated enough, add another endpoint for 0049 only with priority 1 and 60 calls capacity. In this case you have a total of 120 calls capacity for 0049, but you can't have more than 30 calls to 004933 or 004931.
 
P.S.2: If I get the time to read the code and do this myself, where should I send the patch ? :)
 
Kind Regards,
Lucian
 

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

  Powered by Linux