Forum Discussion
Solved
Two SBC lookin on the same IP adress. First SBC is working, second SBC is not.
I have a Microsoft tenant, Added the main domain. Created SBC for sip router. All working.
I added a second SBC on the same sip router. But at this time incoming calls to the second SBS don't work. I use a wildcard certificate for both SBC on the sip routers. But I can't see any logs about the second SBC, but I see logs about the first. Looks like teams don't send options to the second SBC.
- 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.
12 Replies
- hello
- Hi,
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.
