- Joined
- Aug 4, 2009
- Messages
- 404
- Reaction score
- 52
Long story short, I had a customer replace a router and I couldn't get 8 yealinks to register at the same time. SIP ALG off, all the usual tricks failed. So I spun up an SBC on an old machine and got everything registered through the SBC. I'm going to replace this with a raspberry pi SBC.
I'm not sure of the mechanics here. When I configure an SBC, does that just become a generic path for calls? ie, when I set a phone to provision through an SBC the only think 'locking' it to that particular one is provisioning setting the sip proxy? If I were to manually change the proxy ip on the phone to a second SBC that should basically just work?
I'm hoping I can drop the replacement in and all I have to do is update the SBC address in provisioning and the phone will update. I don't want to take the site down. Already had this NAT nightmare and don't want the customer feeling any more issues.
I'm not sure of the mechanics here. When I configure an SBC, does that just become a generic path for calls? ie, when I set a phone to provision through an SBC the only think 'locking' it to that particular one is provisioning setting the sip proxy? If I were to manually change the proxy ip on the phone to a second SBC that should basically just work?
I'm hoping I can drop the replacement in and all I have to do is update the SBC address in provisioning and the phone will update. I don't want to take the site down. Already had this NAT nightmare and don't want the customer feeling any more issues.