RUBY installation and configurtion with Samsung and Tapi

[John Richard Procter]

RUBY installation and configurtion with Samsung and Tapi Officeserv multiple group info.PLEASE KEEP IN MIND ALL AGENTS MUST LOG OUT AND BACK IN WITH THEIR CODE AFTER CONFIGURATION
HAS BEEN CHANGED.

Requirements

• Samsung recommend a Duel core processor Intel, 2-4gig memory and 200gig hd
  
• Samsung Tapi OfficeServOpenTSP-V3127-20070810.exe
  
• Samsung Office Serve Link OfficeServLinkV3-V3001-20070124.exe
  
• RUBYtapi rby-rubytapi-update-2_3_13_0.exe
  
• RUBY server update rby-server-update-2_3_12_4.exe
  
• PABX3 receiving UCD data on port 5105 for queue data.
  PABX3 receieving data on port 5100 for login and out.

All the above is available on request from support@datatex.co.za and only the above version are compatible


PABX3 installation

• Install the PABX3 interface.
  
• Right click on the telephone icon on your system tray and select "show".
  
• Click on Options -> Filepaths.
  
• For PABX.dll use the 7400 Samsung plugin.
  
• For ACD dll use the 7400 Samsung UCD plugin for UCD data.
  
• Once these plugins are selected, click on the Network tab and tick "Send Call center data"
  
• This PABX3 receives data from port 5105 of the PABX.
  OPTIONS -> Remote PABX, Tick "TCP Connect" and enter "PABX IP" and "Port".
  
• Click on the RUBY call center tab and configure the following:
  
  If you had 2 Group numbers, 1 and 511 for example your configuration would be similair to below:
  
  ruby.PNG
  
  Second PABX 3:
  
  ruby 2.PNG
  
  
  Sample of output data:
  
  

  Code: Select all

  ~5014=0=0=0=0=0=0=0=0=0=0
~5015=2651=458=1199=6=44=28776=0=0=24=180
~5016=23=40=8=5=7=184=0=0=23=158
~5017=0=0=1=5=0=10=0=0=10=20
~5018=7402=23494=33448=11=31=38080=0=0=56=420
~5019=0=0=0=0=0=0=0=0=0=0
~5010=0=0=2=5=0=0=0=0=0=0
~5011=0=3=0=6=0=0=0=0=6=12
~5012=0=1=0=2=0=0=0=0=2=2

  
  
  
  1. UCD PABX3:
     
     • This PABX receive UCD data from port 5105 of the PABX
       (call data per call group), the groups needs to be configured
       in OPTION -> RUBY CALL CENTRE.
       ruby 3.PNG
       
       
       PABX 3 UCD data (port 5105):
       
       
       • UCD PABX3 receives the UCD data from port 5105 on the PABX.
         
         
       • PABX3 -> OPTIONS -> NETWORKS, tick 'Network Enabled'.
         
       • Change the 'Listen Port' of TOPAZ to 35005.
       • Tick "Send Call Centre Data".
       • This PABX3 receive SMDR data from port 5105 of the PABX.
         OPTIONS -> Remote PABX, Tick "TCP Connect" and enter "PABX IP" and "Port".
       • The SMDR and UCD plugin must be loaded in PABX3,
         OPTIONS -> FILE PATHS, PABX DLL and ACD DLL.
         
       • The queue information is send to RUBY from the UCD PABX3.
       
       Samsung Tapi Installation
       
       
       • To install the Open TSP, run the executable file and click 'Next' on all prompts until it's installed.
       • Enter the IP address of the local machine on which its installed and the port it connects to (6000 or 5200) if prompted.
       • If you are not prompted for the IP and port,proceed to:
         'START -> PROGRAMS -> OfficeSERV Open TSP Driver -> Open TSP Config tool and configure the IP and Port there.
       
       Installation of RUBYtapi
       
       
       • Run the rby-rubytapi-update-2_3_13_0.exe.
       • Once intsalled, Right click on the icon and select "Configure".
       
       RUBY TAB
       
       1. RUBY Host = 127.0.0.1 or Server IP.
       2. RUBY Port = 20000
       3. PABX = SamsungOfficeServ 7200/7400
       4. On the RUBYtapi configuration, the PABX must be set as the Samsung Officeserv 7200/7400.
       "Send Login info" and "Send Queue info" must be disabled as we use PABX3 for this.
       
       EXTENSIONS TAB
       
       1. Enter the number of extension digits.
       2. Tapi Devices must contain a list of all extensions\devices which we receive from SAMSUNG TAPI.
       3. All the RUBY extensions must be carried over from "Available Devices" to "Monitored Devices".
       
       If at this point you do not rceive any TAPI devices in RUBYtapi, please run the MONITOR programme on the TOPAZ
       CD and make sure that we are receiving data from SAMSUNG TAPI, once we are receiving devices we can continue.
       
       
       RUBY server Configuration
       
       Run the RUBY server update rby-server-update-2_3_12_4.exe
       Open RUBY and click on "Configure"
       
       AGENT CONFIGURATION
       
       1. All Agents Default Physical extensions must be configured in the Default extension Field.
       2. If they are using codes to log into the phone these must be added as the "Agent Code". (These are unique codes for an agent
       to use to lgin via the phone into a group).
       3. The RUBY group number must be used instead of the actual ACD number for the AGENT configuration.
       4. The agent must log onto the physical device (EXTENSION) associated to them with the code associated to them.
       
       
       
       SUMMARY OF INSTALLATION
       
       
       • PABX3 is receiving UCD data from a TCP connection to the samsung PABX, this contains our queue stats.
       • PABX3 is sending this straight to RUBY, with the "Send Call center Data" option enabled.
       • Samsung TAPI is sending staright to RUBYtapi which is sending to RUBY server.
       • ALL tapi application need to be running at all times.

Flow of data
SAMSUNG pabx -> Samsung Tapi on port 6000 -> RUBY Tapi -> RUBY.
SAMSUNG pabx -> Pabx3 via TCP on port 5105 -> RUBY

After the Samsung tapi applications are installed, please use the monitor programme to test whether you are receiving data
before continuing.