We got this working in the lab for inwards and outwards video calling. Attached are the configs that may help.
The ISDN D channel needs the command 'isdn integrate calltype all' to allow the data/video bearer cap to be handled. You also need a 'voice class codec' that includes video codecs, and a 'voice class called number inbound/outbound' command that has the individual numbers used for the video calls.
The attached configs were for a back to back ISDN connection between the two routers. One router (2821) was runing as a H323 gatekeeper that all the H323 devices were registered to. The video calls were done using the Polycom PVX application (demo copy downloaded from here - http://www.polycom.com/apac/en/support/video/pvx.html). The other router was emulating the PSTN and also had the Polycom PVX application working through it. The calls worked fine at 384K.
The information is really helpful. Could you please explain how the "voice class called number inbound/outbound" works? Do the range of the numbers have to be in valid DDIs? I looked at the attached document but couldn't work out how these numbers are allocated.
If you have problems with higher speeds, it could also be caused by media negotiation timers.
Quite frequently when there is a CUCM involved, speeds about 64/128 will not consistently connect.
It is suggested to go into the service parameters and change the Media Exchange Timer and H245 Timeout timers to 30 seconds. As well, if these values, or their equivalent, are available on the endpoints interacting with the gateway it is suggested to change them to 30 seconds.
When you do H320 video, the H245 media negotiation does not happen until the last channel has sync'd up, which is quite a bit later than when you do 64 kpbs.
As well, by default all dial peers allow all video codecs through by default. By specifying a video class codec you are only filtering out possibilities. You should be able to get this to work without adding video codecs to your dial peers.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.