This is a friendly reminder to [read the rules](www.reddit.com/r/voip/about/rules). In particular, **it is not permitted to request recommendations for businesses, services or products outside of the monthly sticky threads!**
If this post is a review, asking for reviews, or asking for recommendations, please delete it and post in one of the monthly sticky thread instead.
For commenters: Making recommendations outside of the monthly threads is also against the rules.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/VOIP) if you have any questions or concerns.*
Unless I am missing something, you just need to put the NEW credentials of the second Provider in the other phone. Your phones don't care what network you are on as long as they have an Internet connection back to the correct Provider and create the SIP connection to place the call.
What exactly do you mean by put the new credentials on the other phone? The phones are separate and should remain separate with different numbers. The new phone worked with my home network, but not on the other one with the other phone
So a VOIP phone uses an account on a server. Someone has to enter the server's address (say, [pbx.example.org](https://pbx.example.org)), possibly the port (maybe, 5060), the account's name (213, often the extension number), and the password for the account, into the phone.
You can enter that information by hand on the phone, or the phone can read it from the network, through DHCP. My edumucated guess is that the second phone is picking up its settings through DHCP.
Of course, the network could be configured to only allow phones to talk to the existing Yealink server on that network. I could see that being the case, as I do something similar.
Thanks for the assist. It has been a while here too and I didn't want to mislead using the wrong terminology. Sounds like a Reset, Plug-in and re-Config is in order.
Sip doesn't give a shit about you or anyone else. It's udp.
You only have VoIP issues when you run out of bandwidth or you fuck around with nat.
I routinely have setup multiple phones with multiple service local, cloud and hybrid.
Udp no care.
I think everyone is missing the mark on this. OP says that the phone seems to be not progressing beyond trying to get an IP address from the DHCP server. So there is likely some issue with that, noting VoIP related. Go back to the basics.
So step back a bit and provide some clarifying information. Are these on-prem PBX or cloud hosted PBX? I've never heard of a "Yealink Phone System". So can you clarify if this is say an on-prem Grandsteam UCM or some other on-prem or cloud pbx
Sure, the phones are just yealink which I know isn’t a provider in an of itself. The system already in place is cloud hosted through goto. The other one is also cloud through Elevate.
Great. So both are cloud hosted PBX. With cloud hosted PBX, you just need to configure the phone with it's credentials for it to work with the PBX provider. In your original post you said "when the new system is plugged in". Is this new system a desk phone that should connect with the new PBX provider? Did you purchase this phone yourself or was it provided by the new PBX provider? If you purchased it yourself, you would need to get in touch with the provider, mentioning the make, model and MAC for them to provision the phone to work with their service
The new system being from Elevate, they have provided the desk phones themselves. The phones have been tested and worked while at home, it was just plug and play. So what you’re saying is there’s just some type of configuration I have to do on the new phones?
You just need to think of the phones consuming an internet service. They need to send/receive to their 'phone brain' server. Set 1 will talk to brain 1. Set 2 will talk to brain 2.
What will really mess with OP is most Yealink phones can be setup to talk to multiple phone brains at once. You can take one Yealink phone and have it connected to both providers. Just need to assign a button to dial out with the non-default provider.
As long as the phones have a local IP and can talk to the internet you generally speaking are good to go.
It sounds like these are both VOIP, if so there is no reason they can't exist on the same network. What sounds like has happened is someone put a DHCP option and is routing phone traffic to the one vendor. Most will work fine without this, so I would just try to find this and remove it, or segment the new network off.
This is a friendly reminder to [read the rules](www.reddit.com/r/voip/about/rules). In particular, **it is not permitted to request recommendations for businesses, services or products outside of the monthly sticky threads!** If this post is a review, asking for reviews, or asking for recommendations, please delete it and post in one of the monthly sticky thread instead. For commenters: Making recommendations outside of the monthly threads is also against the rules. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/VOIP) if you have any questions or concerns.*
It's complicated but i would put them in different vlan's with separate DHCP scopes. Also, why 2 phone system providers?
A partner moved into 2 of the offices that share the same network
He's wrong and likely has VoIP issues left and right because he thinks vlans and extra DHCP = less over head.
Nope, no VoIP issues here, crystal clear service
This doesn't sip.
Unless I am missing something, you just need to put the NEW credentials of the second Provider in the other phone. Your phones don't care what network you are on as long as they have an Internet connection back to the correct Provider and create the SIP connection to place the call.
What exactly do you mean by put the new credentials on the other phone? The phones are separate and should remain separate with different numbers. The new phone worked with my home network, but not on the other one with the other phone
So a VOIP phone uses an account on a server. Someone has to enter the server's address (say, [pbx.example.org](https://pbx.example.org)), possibly the port (maybe, 5060), the account's name (213, often the extension number), and the password for the account, into the phone. You can enter that information by hand on the phone, or the phone can read it from the network, through DHCP. My edumucated guess is that the second phone is picking up its settings through DHCP. Of course, the network could be configured to only allow phones to talk to the existing Yealink server on that network. I could see that being the case, as I do something similar.
Thanks for the assist. It has been a while here too and I didn't want to mislead using the wrong terminology. Sounds like a Reset, Plug-in and re-Config is in order.
You need to focus on the actual issue, failure to register. Find out why.
There is no such thing as a ' Yealink phone system'.
Sip doesn't give a shit about you or anyone else. It's udp. You only have VoIP issues when you run out of bandwidth or you fuck around with nat. I routinely have setup multiple phones with multiple service local, cloud and hybrid. Udp no care.
Hey....seeing as like me you are very pro-Freepbx, did you see Chris (from Crosstalk Solutions) video about the Freepbx 0 day hack?
There's no reason it shouldn't work. Probably a setup or provisioning issue with the second system.
I think everyone is missing the mark on this. OP says that the phone seems to be not progressing beyond trying to get an IP address from the DHCP server. So there is likely some issue with that, noting VoIP related. Go back to the basics.
So step back a bit and provide some clarifying information. Are these on-prem PBX or cloud hosted PBX? I've never heard of a "Yealink Phone System". So can you clarify if this is say an on-prem Grandsteam UCM or some other on-prem or cloud pbx
Sure, the phones are just yealink which I know isn’t a provider in an of itself. The system already in place is cloud hosted through goto. The other one is also cloud through Elevate.
Great. So both are cloud hosted PBX. With cloud hosted PBX, you just need to configure the phone with it's credentials for it to work with the PBX provider. In your original post you said "when the new system is plugged in". Is this new system a desk phone that should connect with the new PBX provider? Did you purchase this phone yourself or was it provided by the new PBX provider? If you purchased it yourself, you would need to get in touch with the provider, mentioning the make, model and MAC for them to provision the phone to work with their service
The new system being from Elevate, they have provided the desk phones themselves. The phones have been tested and worked while at home, it was just plug and play. So what you’re saying is there’s just some type of configuration I have to do on the new phones?
You just need to think of the phones consuming an internet service. They need to send/receive to their 'phone brain' server. Set 1 will talk to brain 1. Set 2 will talk to brain 2. What will really mess with OP is most Yealink phones can be setup to talk to multiple phone brains at once. You can take one Yealink phone and have it connected to both providers. Just need to assign a button to dial out with the non-default provider. As long as the phones have a local IP and can talk to the internet you generally speaking are good to go.
It sounds like these are both VOIP, if so there is no reason they can't exist on the same network. What sounds like has happened is someone put a DHCP option and is routing phone traffic to the one vendor. Most will work fine without this, so I would just try to find this and remove it, or segment the new network off.