Stream Manager

[Nirgal]

Hi Guys, I have a problem were if Stream Manager is down T-Server appears not to know about this and continue to try to apply an announcement treatments to the call. But if an agent becomes available the call will not route to the agent.  The reason appears to be because Genesys is still attempting to apply the announcement.  Any ideas how I could prevent this happening?

SM 7.6.002.30
T-Server 7.6.008.01
URS 7.6.100.05

[victor]

Hi,

what we do is have several SMs assigned, thus if one SM is down, T-Server just send the call to a different SM. We have not tried to see what happens if all SMs are down though. I would strongly suggest looking into having multiple SMs available since we had quite a few problems with SMs, shall we say..."misbehaving"?

Best regards,
Vic

[Nirgal]

Thanks mate.  We have two SM at present but think we will add a third.  :-)  Think I may have worked out a work around as well so hopefuly the the problems is sorted.

[René]

Hi Nirgal,

SIP Server has no chance to detect SM is down unless you enable Out Of Service checking. However, SIP Server should be able to route call to an agent even all SMs are down. Could you post here a log showing your issue?

Last note - it is definitely good idea to have multiple SMs deployed. Not even from availability perspective but from load sharing perspective as well.

R.