Author Topic: Stream Manager Load sharing with SIP Server 8  (Read 4709 times)

Painful

  • Guest
Stream Manager Load sharing with SIP Server 8
« on: December 10, 2009, 01:03:31 PM »
HI ,

I have SIP Server configured find with windows NLB, but currently I only have one stream manager....so I want to add one more stream manager, how do i make sm load sharing work so that it can work redundantely (sort of).
I want to handle a failure of a stream manager or combo of stream manager and sip server to use another sip server and stream manager.

So my options
1. use windows nlb - not supported by genesys but solution is out there.
2. configure multiple stream managers - voip dn

With item 2 is it as simple as configuring another MOH voip dn and change the contact settings in the annex tab?
If so, when I did this and switched over the sip servers, the next call gets dead air..remove the dn everything works fine.

Currently the stream managers are installed on the same hosts as SIP Server( yes i know genesys doesnt like this) but the contact is the NIC IP not the NLB port
Are there any other options and does the configuration sound correct.

Offline borkokrz

  • Full Member
  • ***
  • Posts: 154
  • Karma: 6
Re: Stream Manager Load sharing with SIP Server 8
« Reply #1 on: December 10, 2009, 01:50:04 PM »
The configuration sounds correct. I have similar environment with Warm-Standby Sip Server 8.0 on 2 Linux boxes with virtual IP and 2 SM installed on the same hosts using unique IP addresses. Everything works smoothly for few months.

The configuration is simple - configure multiple SM and multiple moh, mcu etc DN's.

Could you describe the situation after switch-over ? When the call gets dead ? Maybe you can post some logs ?

Marked as best answer by on Today at 09:23:57 AM

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: Stream Manager Load sharing with SIP Server 8
« Reply #2 on: December 10, 2009, 04:11:43 PM »
  • Undo Best Answer
  • Hi,

    Configuration with Stream Managers being deployed on NLB hosts together with SIP Server is not supported [s]until release 8.0.2[/s]. It's possible to make it working by modifying Windows TCP/IP routing table but it isn't recommended.

    If you need multiple Stream Managers just deploy another instances and configure corresponding VoIP Services in Genesys configuration. Load-balancing is the only supported configuration.

    [i]Edit: see my post(s) below[/i]

    R.
    « Last Edit: December 14, 2009, 10:12:56 AM by René »

    Offline borkokrz

    • Full Member
    • ***
    • Posts: 154
    • Karma: 6
    Re: Stream Manager Load sharing with SIP Server 8
    « Reply #3 on: December 11, 2009, 11:09:00 AM »
    Official support is one thing and working solution is the other thing. Per example officially you can't install several SIP instances on one server. In practice it is possible. The same thing correspond to SM on the same host as SIP Server.

    Offline René

    • Administrator
    • Hero Member
    • *****
    • Posts: 1832
    • Karma: 62
    Re: Stream Manager Load sharing with SIP Server 8
    « Reply #4 on: December 11, 2009, 02:24:07 PM »
    Hi Borkokrz,

    I don't agree with you. The fact something not officially supported work for you doesn't mean it will work for other customer using different features, architecture etc. It's not that easy... For example, Stream Managers deployed on the same SIP Server boxes when Windows NLB is used don't work correctly. It's possible this issue is not present when using Linux boxes...

    R.

    Painful

    • Guest
    Re: Stream Manager Load sharing with SIP Server 8
    « Reply #5 on: December 13, 2009, 07:44:00 AM »
    Hi Rene,

    I have SIPServer v8.0.2 and cant spot anything around sip server / stream manager nlb stuff in the release notes.

    Have you got any other info?

    Thx

    Offline René

    • Administrator
    • Hero Member
    • *****
    • Posts: 1832
    • Karma: 62
    Re: Stream Manager Load sharing with SIP Server 8
    « Reply #6 on: December 14, 2009, 10:14:24 AM »
    Hi,

    I'm sorry but I mixed up this issue with other one that is solved in 8.0.2. It means that it isn't supported and won't work even in 8.0.2.

    Sorry again for confusion.

    R.