Forum Discussion
Two SBC lookin on the same IP adress. First SBC is working, second SBC is not.
- It is okay to use a wildcard certificate on the SBC.
It sounds strange that Teams sends calls to a SBC that it says is inactive, should not be possible. I guess there is something wrong with the "SIP Gateway", you should check with the partner that deployed these for you.
Each SBC should have a public routable IP address.
Did you setup two SBCs with the same IP address? Then it sound like you have an active/passive setup, so all traffic will be sent to the active SBC until that SBC fail and the passive SBC becomes the active one.
- Actually, I wanted to use a different SBS, not active/passive. I planet separate calls inside my sip router. Is it possible? For example, if I separate SBS by different port?
- You will need one public IP for each SBC. Add both SBCs in the Teams Admin Center and add both to the same Voice Routing, then Teams will send calls to both of them.
LinusCansby small clarification. Calls from teams to our SIP router work for both SBC. Outgoing from the SIP router to the teams work only for the first SBC.
In the teams administration console, the second SBC displays TLS inactive, and SIP options - No SIP OPTIONS.
Everything is fine with the first SBC. I tried deleting the SBC and adding a new one but in the opposite order. First after the second. Nothing has changed, the second SBC continued to be in such a state (inactive). As soon as I added the first one, it (first what have no problems) immediately assumed the active state.
In the logs of the SIP router, we do not see anything to the second SBC. But we see constant requests to the first SBC.
Yesterday we tried to split the SBC into different ports, but it was unsuccessful.
As I wrote above, the certificate for both SBCs is the same wildcard.
