Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Richard on January 01, 1970, 12:00:00 AM

Title: Two Tservers connected to Symposium
Post by: Richard on January 01, 1970, 12:00:00 AM
Does anyone have an answer to configuring two Tservers to talk to one Symposium. I have been successful in connecting two applications but only the first one can register properly. Any assistance would be greatly appreciated. Running SCCS 4.0 against G6 on Nortel Option 61c rls 25.

Here is Nortel's comments:

There is no "special" configuration on the Link end (SCCS or Meridian Link). Instead, on your application, TServer, CallPath, TAPI, etc. you just need to define the ApplicationID to be different for each different host. The Link interface supports up to 16 different simultaneous hosts. This has been the case since Meridian Link 5's TCP/IP interface was introduced a few years ago.

I registered the second link through the Mlink_tool and I was able to connect successfully but I got the following errors on this link:

Registration failed: DN 4003, type 0x1a, cause 0x2033: Internal error
@18:18:32.3705 [0] 6.1.00115 send_to 0x00030002: message EventError
(Internal error)
AttributeCustomerID 'RHB_CCC_Production'
AttributeTimeinuSecs 370560
AttributeTimeinSecs 990613112
AttributeReferenceID 123
AttributeThisDN '4003'
AttributeErrorCode 218
This number is not controlled or registered by the other TServer. Any suggestions greatly appreciated.
Title: Two Tservers connected to Symposium
Post by: Ed on January 01, 1970, 12:00:00 AM
Can't monitor same DN's, agents etc, but 2 tservers do fine. Be sure license can handle because you can't run to license mgr's on same box. be sure Tserver ports are different ( these are the ports tserver opens as 'LISTENING'.
Title: Two Tservers connected to Symposium
Post by: Richard on January 01, 1970, 12:00:00 AM
FYI,

We have successfully connected to two Tservers with SCCS 4.0 running G6.1. To do this you need unique hostnames and IP addresses and to make sure appliation ids and port numbers for each Tserver are unique as well. To confirm connections on the Symposium server do netstat and look for multple occurrences of port 3000 for the links.

regards,

Richard
Title: Two Tservers connected to Symposium
Post by: Ed on January 01, 1970, 12:00:00 AM
Richard

How long have you had 6.1 up and running? Did you convert from 6.0 ( or 5.1 ) or clean install?

thanks
Title: Two Tservers connected to Symposium
Post by: Ed on January 01, 1970, 12:00:00 AM
FYI

You don't need 2 host's and IP's, Just ports.
Title: Two Tservers connected to Symposium
Post by: Suleyman Kundak on January 01, 1970, 12:00:00 AM
CFG of the first TServer

[extrouter]
defaultdn=
reconnect out=5
register out=60
request out=10
routedn=
timeout=30

[logcontrol]
loguffering=false
logcheckinterval=60
logfile ame=e:\gcti\logs\tserver.txt
logfilesize=10000000
log emoveoldfiles=false

[tcpoptions]
hostname=Meridian
port=3000
protocol=tcp

[TServer]
attachcdninfo=on
check enantprofile=false
compatibilityport=3010
completexferondisc=on
hexdump=yes
internaladdrlength=
licensefile=7260@10.6.100.193
link1 ame=tcpoptions
link imeout=
log raceflags=on
mail ame=MeridianMail
managementport=3001
max runk umber=
mlinkapplicationid=Meridian
mlinkcustomer umber=0
mlinkhostid=Lanlink
mlinkpollinterval=0
mutexfermethod=2step
nocalldisconnect=3
nocallid elease=on
nrdyafterlogin=off
numoflicenses=210
origcallxferinit=xfer
rlsextconsult=on
serverid=2
setdnisfromdest=off
verbose=true
version=5
wrongcallid elease=off

[x25options]
comport=
mode=svc
protocol=x25
restartdelay=
template=
userdata=
x25address=
x25device=
x25localaddr=

CFG of the second TServer
[extrouter]
defaultdn=
reconnect out=5
register out=60
request out=10
routedn=
timeout=30

[logcontrol]
loguffering=false
logcheckinterval=60
logfile ame=d:\gcti\logs\tserver.txt
logfilesize=10000000
log emoveoldfiles=false

[tcpoptions]
hostname=Meridian
link umber=0
port=3000
protocol=tcp

[TServer]
attachcdninfo=off
check enantprofile=false
compatibilityport=3010
completexferondisc=off
hexdump=yes
internaladdrlength=
licensefile=c:\flexlm\license.dat
link1 ame=tcpoptions
link imeout=
log raceflags=on
mail ame=MeridianMail
managementport=3001
max runk umber=
mlinkapplicationid=Meridian1
mlinkcustomer umber=0
mlinkhostid=Lanlink
mlinkpollinterval=0
mutexfermethod=fast
nocalldisconnect=3
nocallid elease=on
nrdyafterlogin=off
numoflicenses=210
origcallxferinit=xfer
rlsextconsult=on
serverid=1
setdnisfromdest=off
verbose=true
version=5
wrongcallid elease=off

[x25options]
comport=
mode=svc
protocol=x25
restartdelay=
template=
userdata=
x25address=
x25device=
x25localaddr=

Hope it helps
Title: Two Tservers connected to Symposium
Post by: Victor on January 01, 1970, 12:00:00 AM
I have never seen this:
licensefile=7260@10.6.100.193

In other words you can just specify a port where license manager is running instead of a path to a license file??? That would be REALLY great! Does it work on 5.xxx?
Title: Two Tservers connected to Symposium
Post by: Ed on January 01, 1970, 12:00:00 AM
Just wondering what the 2 cfg's are showing other than server id being different and link number under switch ( which implies seperate links ). With Symposium you can run 2 tservers against same link ( listens on port 3000 ) as long as Monitored DN's etc are different ( otherwise why run 2 tservers ) and under server info tab in cme for tserver(s) the ports are different. Just wondering? good info though.
Title: Two Tservers connected to Symposium
Post by: Suleyman Kundak on January 01, 1970, 12:00:00 AM
yes it works without a problem.