|
Thank you Simon, I haven’t tried this yet, but I will. My current config looks like this: [RoutingPolicy] h323_ID=ldap,dns,internal default=ldap,dns,internal Would I then change it to: [RoutingPolicy] h323_ID=ldap,dns,explicit,internal default=ldap,dns,explicit,internal If I do this, will I be able to dial both alisas and IP Address depending on whichever I feel like dialing? Do I understand this correctly? From: Simon Horne [mailto:s.horne@xxxxxxxxxxxxxx] Josh Use the explicit routing policy http://www.gnugk.org/gnugk-manual-6.html And add the following to the INI [RoutingPolicy] default=explicit,internal, … Simon From: Josh Rogalski [mailto:rogalskij@xxxxxxxxxxxxx]
I have a successfully running gnugk server acting as a gatekeeper for h323 video conference calls. One of the quirks I find is that when I configure it on a video client endpoint, I can ONLY call to h323 alias’s, and no longer can I call
directly to IP addresses. Is there a way to use the gatekeeper on a video endpoint, and use either the username OR the ip address for dialing? I can provide my config if necessary.
|
------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
