Questions regarding SymposiumTserver

[Mark Cupps]

Does Symposium TServer care about the VSID programming in the switch? When I cutover to Symposium my concern is with the Switch programming in LD 23 CDN CNTL yes VSID 2
(VSID 2 is the aml to the existing Meridian Link 5C module). I will eventually retire Link 5C and at that point will I need remove VSID 2 or does Symposium TServer even care? I noticed in the reference document on Symposium TServer all you need is CNTL yes for the CDN. If I register the existing CDN's in Genesys with Symposium then Symposium will have control of the call and not Genesys. Anyone else out there done this replacement?

[Bill Boga]

I've noticed the Genesys documentation for Symposium Tserver is wrong. You do not set CNTL to yes with Symposium TS. Even if you did, unlike with Meridian Link, you can not define the VSID. CNTL is set to YES and VSID is defined when the TServer succesfully registers a CDN. If you did manually set CNTL to yes, TS will be sent messages, but it still may not be able to control the call. Best to keep it at NO, this helps in troubleshooting.

Another reason not to manually set the VSID is it may actually be different the next time Symposium is restarted if you have multiple applications such as a CallPilot. The VSID is dynamically assigned based on which application registers with the PBX first. They do try to retain the same VAS ID they used the last time they registered, but the possiblity is there that a different ID will be assigned.

For this reason, it is important that you set the SECU setting correctly on all VAS IDs. The description, DES, should be set to a value that does not describe the application, but perhaps the ELAN number. Additionally, the MCNT (message count) and INTL (interval) should not be left at default, 9999 and 1 respectively, which may adversely affect the PBX. The default setting means that up to 9999 unaknowledged messages may be received every 5 seconds. The Nortel recommendation was MCNT 400 and INTL 4, which equates to 400 message in 20 seconds (INTL is in 5 second increments). I think you can actually increase this with the increased processing power of the new switches, but, if your PBX is not answering 400 messages in 20 seconds, there is a problem. Keep in mind, these are unaknowledged messages, if the switch answers, TS will keep going.

Set configuration documentation is also vague, but to help keep the TServer and the PBX synchronized, it is a good idea to set IAPG of all sets to 1, instead of the default 0. The value of 1 will send all unsolicited messages to TServer, 0 sends none. By sending all messages to TS, the TServer can keep track of the set even if someone touches the phone instead of use the 'softphone'. You might already have done this with MLink.

Good Luck