Forum Discussion
Hello Steve,
Based on our previous discussion i suggested to do following scenarios:
1) to leave only one SIP monitor(on LB) and change existing one on MSS (tcp monitor).
2) On LB I will mark both Rhino servers to be "down" and see what happens. Maybe to check if LB would throw alarm on MSS...
I will give you part of discussion we had. (Person A is me, person B is MSS guy).
B: I guess option 2 would mean that we get no response to INVITE's and thus cause calls to fail with CC920 (SIP control Plane failure)
A: yea, something like this would be expected
B: we have to send the SIP OPTION's message to the same address that we send the INVITE .. so is Option 1 feasible ?
A: so basically without SIP monitor on your side, you are unable to send any traffic to LB, right?
B: no .. we can disable SIP OPTION's completely if required .. it just means we would have no prior knowledge that the SIP endpoint is down (and no way of alarming this)
A: so you don't have any other way, except SIP OPTIONS, to interogate LB availability?
B: no... unless we use SIP over SCTP ?
B: we would just get clear codes showing that SIP calls are failing
I think our BIG-IP 1600 on 10.2.4 supports SIP over SCTP, but i have to see how this will affect our config and whether we will be able to achieve.
For time being i switched SIP monitor on LB with tcp check, just not to duplicate SIP traffic on Rhino servers.
Any comments on this?
Regards,
Zvone