After some head bashing, and other bashing (beer mostly), I've come to the following
assumptions about Virtual Queues:
1. Virtual Queues can be routed according to alias names given by a RouteToAlias command
via the status port.
2. In order for a call to find it self in a specific virtual queue, it needs to be routed
into it, via a line in RasSrv::GWPrefixes
Lets say my configuration looks something like this:
[RoutedMode] GKRouted=1 H245Routed=1 CallSignalPort=1720 CallSignalHandlerNumber=2 AcceptNeighborsCalls=1 AcceptUnregisteredCalls=1 RemoveH245AddressOnTunneling=1 DropCallsByReleaseComplete=1 SendReleaseCompleteOnDRQ=1 SupportNATedEndpoints=1 Q931PortRange=30000-39999 H245PortRange=40000-49999 AllowNeighborsCalls=1
[Proxy] Enable=0
[RasSrv::PermanentEndpoints] 192.168.1.1=remote;80000 192.168.2.1=origin;80001
[RasSrv::GWPrefixes] nirs1=12345 nirs2=12346
[CTI::Agents] VirutalQueue=nirs1,nirs2
Now, lets say a call is issued from "origin", bear in mind that "origin" isn't registered
with the GateKeeper, it's a permanent EndPoint, and sends in a prefix of "12345". If I
understood the mechanism correctly, the call should be routed to the "nirs" Virtual
Queue. I've tried using this configuration, but I didn't see any "RouteRequest" posts
to the status port, which means that most probably I'm doing something wrong.
Questions that arose for me are these:
1. Will routing to VQ's work only for registered endpoints?
2. If 1 is Yes, is there a way to bypass this issue, and make it work for permanent endpoints?
Regards, Nir S
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
