TServer Hot standby

[sreeschand]

Hi,

We have two TServers primary and backup configured in HA.

Issue :

All Calls in Queue are defaulting when TServer swaps.

Since TServers are in HA calls should not default right? backup TServer should pickup these calls right?

Greatly appreciate any help on this.

Thanks

[cavagnaro]

Are they in Hot or Warm standby?
Some logs would help to determine the issue, if any.

[sreeschand]

It's in Hot standby

[ecki]

Hi,

TS in hot standby means that both are tracking everything what's happening in Switch, but just only one is driving switch. The defaulting stuff is more URS stuff. You should therefore check your URS options, for example whether it is instructed to pickup the calls from RPs.

Cheers.

e.

[sreeschand]

Please let me know what option in URS determines this ??

[ecki]

Well, hopefully this helps, but no guaranties,

pickup_calls = true

Try to set this first on the main URS app and then try to put it in ot annex tab of particular route point you wan to have this feature.

e.

[catanirex]

Hi

It is depending on the switch you are using... For instance, on Nortel, the link only supports one application (TServer) that aqquires the DNs, which means that the backup TServer needs to register all DNs when it becomes primary TServer. So using Nortel Symposium link and Genesys Tserver Hot standby unfortunately means that all queueing calls will be default routed.

The URS option pickup_calls works fine when primary URS goes down, then backup URS continues to handle the queueing calls.

[sreeschand]

Thank you very much for the reply, we are using Nortel symposium link.

So there is no other way call will default?? when TServer swaps?

So whats with Avaya?

[rubic123]

This article is very initiative and I m satisfied with your article.
Rubic
[url=http://www.tnsc.co.uk]Outsource IT Support UK[/url]

[KBS]

sreeschand 

What version of TServer for Nortel are you using?

According to the release notes, there are known issues with certain 7.6 versions (which were corrected in later 7.6 releases) where the primary TServer does not release control of CDNs during a failover, so the backup TServer cannot take control of these CDNs. In this case, I have found I have to stop BOTH TServers to free them up, then restart the primary to regain control.

You may want to review the release notes for TServer Nortel CS1000 and see if the fixes address the issue you are encountering.

[sreeschand]

Thank you all for the reply...

KBS, when backup TServer becomes primary it's registering all CDN's it means it's getting control of the CDN's.New call coming to the route point are getting routed properly.

Thanks...

[bogdan]

[quote]It is depending on the switch you are using... For instance, on Nortel, the link only supports one application (TServer) that aqquires the DNs, which means that the backup TServer needs to register all DNs when it becomes primary TServer. So using Nortel Symposium link and Genesys Tserver Hot standby unfortunately means that all queueing calls will be default routed.[/quote]

Are you sure of this? Because I have tickets raised for quite a while at genesys support for this exact problem and they didn't solved it, they didn't even gave me an explanatory answer - finally I gave up at them.

Regards

[catanirex]

Hi,

Yes, I'm sure of the Nortel / link/ TServer HA functionality. It is even documented in the Genesys TServer deployment pdf under Known Limitations:
"In an HA environment, all calls with treatments applied to CDNs at the time of a T-Server switchover will be routed by the switch to a default
destination."

Haven't worked with Genesys HA on other switches yet.