Configured gatekeeper per MS support article "How to Configure the Gatekeeper Service in ISA Server to Allow Inbound Netmeeting Calls (Q288206)". Works for the most part - external netmeeting client can establish session with internal netmeeting client. However, no video. Chat, app sharing, etc work, but camera stream from internal client not making it to external client. Any thoughts?
Using the default H.323 app filter, set up the params to allow video, data, DNS. Created basic protocol rule using default H.323 protocol defn.
Check out the H.323 filter (not gatekeeper) configuration and make sure you have all options selected, esp. the video option.
If the data connection is working, you know that your setup is correct. I've found that when the video doesn't work, but everything else does, its probably a NetMeeting client config issue. But check out the filter configuration first.
H.323 filter has every checkbox checked on Call Control tab, and using the internal IP address of the ISA server for Gatekeeper location.
The Netmeeting clients set up as they were before ISA, except that the internal clients now register with the Gatekeeper, and the external clients use the ISA box as the Gateway. The internal client shows "Send Video", the external "Receive Video" in their menus, but no video goes through.
When I do a Netstat -na on the public IP for the ISA, I only see 1720. Shouldn't I see 522, 1731, 1503 etc?
The gatekeeper will handle the connections required, so only 1720 is opened statically by the gatekeeper.
It sounds like you have everything set up correctly. Just a couple of other ideas:
1. Try *not* using a secure connection. Disable the secure connection option on the NetMeeting clients. I've had problems with that, which isn't to say that it doesn't work, its just that the one time I worked with secure connections, it didn't work right, but I haven't followed up on the problem.
2. Try disabling fragment filtering and see if that helps.
Are you using a DSL line? If so, there might be an MTU problem as well.
Are you using PPPoE? [No, fortunately. Neither at my lab, nor my associates' lab, both of which are having the same behavior.]
In the H.323 Filter properties dialog box, have you confiured it to use the internal interface of the ISA Server? [Yes]
In the Gatekeeper dialog box, Network tab, have you selected *only* the internal network adapter? [yes]
Are you allowing anonymous access for all protocols? [Site and content rules set to All destinations, all content, applies to any request. Protocol rule set to Any Request.]
One further datum. Don't have a camera at my external client end, only at internal client. However, audio from external client is going to internal client, whereas audio from internal to external is not. So it looks like the problem relates to outbound A/V. Is there something in the protocol rule that should be added???
Finally, under H.323 Gatekeepers/server/call routing/destinations, I see an entry in the details pane for the internal IP address. If I double click on that, I see options for destination types. I don't remember setting that up. Right now it shows Gateway or proxy selected - I tried moving to Gatekeeper, but that did not work either. What should this be set at?
Finally, when the call is in progress (and chat working, for example,), when I look a the gatekeeper it shows my internal client as an "Active Terminal", but shows NO Active Calls. Is that right? Or wierd?
The "Active Sessions" thing was a distraction - apparently a refresh issue on the screen. Everything appears to be working perfectly, without any change of settings from before... provided the external client is not at my desktop at the office. My associate and I were both able this weekend to establish sessions external netmeeting client <--> netmeeting client behind ISA (our respective home offices) when that external client is generically "on the Internet". It seems that something at our corporate office prevents this communication. On the other hand, it worked for both of us when we simply used Linksys routers at the home offices and not ISA boxes. Interesting feature, huh?
For my part, I'm able to do what I need, so I'm logging off this conversation. However, happy to continue the discussion 'for academic purposes', or to test configs further if it would help anyone else. Tom - thanks for all your suggestions!
Good to hear you got it working! Would be nice to know exactly what the problem was with the Cisco 'gateways' and what they mean by gateway. I wonder if they just meant gateway as in router, or perhaps a NAT device, or something else?