Skip to end of metadata
Go to start of metadata

Follow the instructions below to connect a BCM v3.7 or below with NetPBX:

  1. Make sure the CDRServer.EXE and Interop.CDRSERVERLib.dll files are placed in the same folder as NetPBX.EXE, usually located in {pf}\Tri-Line\NetPBX.

  2. Register CDRServer.EXE by running the command line with administrator privileges and typing the following command under the directory path of the NetPBX folder: CDRServer.EXE/regserver.
  3. Open the computer's local security policies: Start -> Control Panel -> Administrative Tools -> Local Security Policy.

  4. Within the Security Settings\Local Policies\Security Options tree, change the following items as highlighted in the screenshot below:


    1. Network Access: Let Everyone permissions apply to anonymous users. Set this to Enabled.
    2. Network Access: Sharing security model for local accounts. Set this to Classic.
    3. DCOM: Machine Access Restrictions: Click on Edit Security and add the following user accounts: Anonymous, Everyone, Interactive, Network, System. Set each one to have full access rights.

  5. Next step is to modify the way DCOM behaves on the computer by executing the DCOM configuration program: Start -> Run -> DCOMCNFG [enter]. Browse the tree to the following location: Console Root -> Component Services -> Computers -> My Computer. Righ-click on My Computer for Properties and amend or update the following options:


    1. On the Default Properties tab:
      Enable Distributed COM on this computer: tick the box for his option
      Default Authentication Level: set this to Connect
      Default Impersonation Level: set this to Identify

    2. On the COM Security tab:
      Go to the Access Permissions section and select Edit default.
      Add the following accounts and set both local and remote access permissions: Anonymous, Everyone, Interactive, Network, Local Service and System.


      Go to the Launch and Activation Permissions section and click on Edit default tab.
      Add or update the following accounts to give them all local and remote access permissions: Anonymous, Everyone, Interactive, Network, Local Service  and System.

 

Labels: