Meridian Link

[David]

Hello,

I have problem with meridian Link Rls 25.
Once a day, TServer lose the connection with the Pbx Link. I can read the following error in Tserver Logs :

Could you please help me, and tell me what should I have configured.
I have to to reboot Symposium server 2 or 3 times before having the 'link connected' message.

Thanks

David

(link_start) link [1] 'link1 ame' start
(tcp_start) connecting to 128.6.1.171:3000... contacted on socket [592]
@ 00:30:37.5570
L+ 1 start link 'link1 ame' 592
(tcp_connect_handler) 128.6.1.171:3000 is connected on socket [592]
@ 00:30:37.7130
L^ 1 UP link 'link1 ame'
e< 1 01000000:02ff0000:03ff0000:04ff0000 01110000
e+ 01010000 01110000
e+ 02ff0000 01010000
@ 00:30:37.7130
>> 1 ff 0a 00 36 00 00 00 01 01 00 01 03 01 04 0e 54 53 65 72 76 65 72 2d 31 30 30 31 05 09 4c 61 6e 6c 69 6e 6b 09 09 03 01 61 01 62 01 64 0b 06 53 4c 31 36 0d 03 00
s> 1 Application Registration
Application Protocol:1
Application ID:TServer1001
Host ID:Lanlink
Service ID List:97, 98, 100
Meridian 1 Machine Name:SL16
Meridian 1 Customer Number:0

e> 1 01010000:02ff0000:03ff0000:04ff0000
@ 00:30:37.7130
<< 1 ff 0a 00 11 00 80 00 01 02 00 71 03 01 78 04 05 04
s< 1 Application Registration Response
Result:Fail
Cause:504

?? Application exists... associd 00
L! 1 restart link 'link1 ame' apprel:close:open 1:0:2000 associd 00 sip 0
@ 00:30:37.7130
>> 1 ff 0a 00 0a 00 00 00 01 03 00
s> 1 Application Release

e< 1 01010000:02ff0000:03ff0000:04ff0000 02550000
e> 1 01010000:02ff0000:03ff0000:04ff0000
e< 1 01010000:02ff0000:03ff0000:04ff0000 01220000
e+ 01000000 01220000
e> 1 01000000:02ff0000:03ff0000:04ff0000
(link_stop) link [1] 'link1 ame' stop
(tcp_stop) closed on [592]
@ 00:30:37.7130
L 1 stop link 'link1 ame' 0
e< 1 01000000:02ff0000:03ff0000:04ff0000 01330000
e> 1 01000000:02ff0000:03ff0000:04ff0000
@ 00:30:39.7130
c* 1 timer 04d00002

[Vic]

David,

we started ot have a similar problem recently, and we are still looking into it. We laso have to reboot the link to get TServer connected to it again.

0x507 error means "service not available" let me ask PBX people if they know more and get back to you.
Vic

[David]

Thanks for your answer. On my side, I have ask Genesys and Nortel about this pb. I still wait for their answer. I come back to you if I have some news

David

[Ed]

Are you using Meridian Link or Symposium?

[Vic]

Service ID of 97, 98, 100 is Symposium Link.
MLink has an additional 101 service as well.
I do not know what the cause of this problem is, but usually rebooting the link fixes it.

What our PBX people dop, usually, is reinstall the link if the problem persists... But, this is kept as last resort only.
Have your PBX people check the link. Obviously, one of the services is not working; however, it is impossible to tell which from CTI side using TServer

[Johnny Chua]

Hi,
The problem might be cause by the delay in response from Genesys pertaining to the Call Messages.
You could ask the PABX vendor to set the response to suit Genesys. This take some trial an error kind of stuff.
The above can either be implemented through creating Dummy CDN or directly through MLink via disttech api_tool.
Hope the mentioned can help you. Cheers.

[David]

I am using Symposium

[Ed]

If you are using Symposium then Meridian Link ( on the switch ) should not be enabled. On the Symposium server verify that the MLSM service is active ( but check for Dr. Watsons and also verify the service is actually running ). There is a max register setting on the switch somewhere ( I'll have to look to find it ) that is defaulted to low. It needs to be set high ( like 254 total ) I'll look for my info on this. Hope this helps.

[Vic]

Ed,

I am having a similar problem we have both Symposium and MLink running on the same PBX and recently MLink would just return fail with cause 0x507 when TServer attempted to connect to it. Needless to say, Symposium was fine.

Any ideas?

[Ed]

Vic

With David it appears he is trying to run MLink and Symposium for one Tserver which will not work. Technically you should be able to have MLink and Symposium Link ( or MLSM for vs 4 ) together as long as Tserver is only accessing one or the other. If using Mlink and CDN's, DN's etc are acquired by Symposium it will not work as desired. You have to use one or the other. I will get more information on this. Ed

[Vic]

Ed,

thanks for the info! Actually, I am able to run both Symposium and MLink TServers together (each accessing their own link). As long as you have different DNs for MLink and Symposium to use, you are SAFE. You will need to start the Symposium first, because it registers DNs it wants one by one and MLink TServer would get the rest of DNs with REgisterAll. DN's acquired by Symposium would just return an error, thus as long as you do not use them, you should be safe. ... I think...

[Ed]

That is true, but unless you totally seperate CDN's, DN's for each link you will experience problems. Just be sure that your objects are not referenced by both links. Hope this is helpful.

[David]

Hi All,

I have asked Genesys & Nortel about this Pb. Genesys sent me a new version of TServer, and Nortel patched the Sympo Server. They did not explain me was it has changed exactly, but now it works. Obvioursly, it was a nortel PB

Thanks all for your help

David

[KM]

Can you find out the patch number that you used?
Maybe we will need to do the same as well. What version of symposium are you running?

[The Greatest]

This problem is experienced when the T server installed is not right. ie using the incorrect template to build the T server application. The T server needs to be TServer_Symposium while the Switch is Nortel Meridian CallCentreSyposium.