I have anEX90on the internal networkregisteredvcs-cthroughprovisioningcorrectly,have anotherregisteredEX90-evcsmanually,howeverwhen I try todo itviaprovisioningtakes the databut the serverit takes toregisteringviasipandh323is thevcs-control andsodoes not registerwhenI checkthetemplatein thetmshavethe following:
Myquestion is howdoto have atemplatethat works forbothregisteredinthe internal network,asI wantto registeredin-vcsexpresswayviainternet??
I also happen tomeonceandthe endpoint registeredviavcs-expresswaydo not knowhow to add"addsystem"in TMS, sincetmsis onmy internal networkand theendpoint on internet,but thephonebookworking properlyfromthe endpoints registered onexpressway...and I wouldaddin thesystem howshould I do?
The reason is because the EX90 will always request the internal configuration settings within the template unless it is told otherwise to use the public settings, this can be done by one of the following:
For the domain you are using with your EX90, you must have a DNS NAPTR entry that uses an "se" flag. If this DNS record exists, the EX90 will request the public template settings from the VCS. Note the "se" flag is only supported with Linux DNS, Windows DNS doesn't support a two character NAPTR flag.
Configure the EX90 to use the public template settings by doing the following on the codec, this is the same as option 1 above, but instead of DNS doing it for you, you're doing it yourself. xConfiguration Provisioning Connectivity: External
The administrator guide, pg 70 explains the provisioning connectivity setting, as well as the NAPTR record. Note, the admin guide speaks of an "e" flag for the NAPTR record, however this is incorrect and I've already brought this up to TAC earlier this year to fix the typo, as it really looks for an "se" flag.
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.