IP Telephony - VCX
1752618 Members
4514 Online
108788 Solutions
New Discussion

VCXData error

 
Gareth.Coley
Advisor

VCXData error

Hello all. I am installing a new branch office in to our vcx estate and have come up with a problem.  Whilst configuring vcxdata the system comes up with "error 3", looking at the var/log files it tells me nothing more than vcx data is halting because of this error. Has anyone come across this error before? I have checked that the schema is built at the region and the addresses have been allowed through both firewalls.

3 REPLIES 3
sang-su
Occasional Visitor

Re: VCXData error

did you check branch's host name and site ID?

 

how about ping test  to verify network connectivity?

 

 * Regional office's primary VCX

 

  • On the VCX Regional Primary server, login as root from system console or ssh
  • Modify Regional office firewall software to permit traffic from the branch office server
    • Type: “modfw –p oracle allow <IP address of branch office server>”
  • Setup a database schema on the Regional office Auth & Dir server. This schema acts as a replica of the branch office server’s database schema and must be setup prior to the installation of the branch office server
    • Login as cworks from system console or ssh
    • Create database schema:
      • Type: “cd /opt/3com/VCX/vcxdata/bin”
      • Type: “./installVcxdata”
        • Select option 1 – Create a Backup Database Schema for a Branch Office
        • Enter the SiteID for the branch office: 2
        • Enter the Site Name for the branch office: (for example: demobr1)
          • Use this same Site ID/Name when you install the branch office server, as indicated below
        • Enter IP address of the primary IPM server at branch office site: <enter IP address of V6x00 or eth0 of 306 branch office server>
        • Enter IP address of the primary CallP server at branch office site: <enter IP address of V6x00 or eth1 of 306 branch office server>
        • Continue? y
    • Before you begin the installation process on the branch office server, first verify that the regional office Auth & Dir server is running properly and accessible via the network.
      • Login to the VCX Central Management Console and access VCX menus
      • Use ping to verify network connectivity from branch office server to the regional office server

 

 

  • On the VCX Branch Office server, login as root from system console or ssh
  • Type: “vcx-setup”
    • Networking is already configured – skipping
    • Which services will this system provide? 1 (IPT and IPM)
    • Confirm selection? yes
    • Do you wish to configure services? y
    • Role of system: 3 (branch office)
    • Global Parameters
      • Unique Identifier: 2 <-- branch office's site ID
      • Description for this site: demobr1

Customer name: 3Com Customer

 

 

thank you.

 

 

 

 

John_Katzmaier
Valued Contributor

Re: VCXData error

Hi,

 

I suggest that you open a case with Technical Support. They can collect logs from the system to determine why vcxdata is failing to configure.

jwhitley
Advisor

Re: VCXData error

Which firewalls are you using? If it's a SonicWall, Juniper (or many others) make sure that the SIP and SQL "application helpers" or ALGs are turned off on the firewalls at BOTH ends. Juniper firewalls by default pretty much ALWAYS kill a branch install (because they try to "help" the oracle data and do the exact opposite).

Many firewalls block (more accurately they corrupt) SIP FEATURE traffic from a VCX, so normal calls will work but transfer / CFU / hold / lots of other things will not.

If the install has already failed, make sure you clean up the Region server before trying again. Personally I remove the empty branch schema on the Region and reinstall it again, potentiall running ./dropReplication --continue-on-error on both the region and the branch, depending on how far the original install got.

Also make sure that the new Branch is not already listed in the LOCSA list on the region's global directory. If it is, this will cause the install to fail again (straight after the main parts of vcxdata are successfully installed.... really annoying).