Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What is the benefit to have your IP phone register to procr over a CLAN card? 2
- Thread starter HBcity
- Start date
-
2
- #2
Not so much benefit to one over the other as much as being aware of the differences and planning for it.
Processor ethernet was previously only supported on simplex servers (S8300/S8500) and never on duplex servers. That eventually changed. With the phasing out of G650s, you won't be registering to CLANs for much longer.
CLANs have a limit of 400 sockets each, you've got to keep track of each one's firmware, data network connection, and you'd typically want to have 1 CLAN dedicated for a particular adjunct - like CMS or Intuity AUDIX. I know that sounds simple, but you wouldn't believe how often customers screw that up. When you can have many CLANs, and you can consequently have as many ethernet interfaces as you'd like in the PBX, and they're cheap, "list node-names all" is a mess of CLANs in 192.x, 10.x, 172.x, private networks, etc. Every one winds up on a different VLAN and its a mess to fix when it breaks.
Procr socket limits are based only by the server type, and will accommodate what you need, and has the benefit of being just 1 thing.
You'd be good to review your IP-network-map as well. Subnets for phones that are not assigned as belonging to a particular region will have the phone assume the region of the gatekeeper it registered to. That means it is possible to have a CLAN in region 5, overlook adding any IPs for phones to region 5, but by pointing a subnets DHCP to that CLAN, the phones inherit region 5. If you move to procr, the phones will inherit procr's network region and location. That means your network map must be solid.
Another interesting point related to design, is that best practices are for procr to be in its own network region without DSPs, usually 200 or 250. Every network region connects directly to procr. Every network region connects to every other network region through the intervening region of procr. It lends itself to more of a "hub and spoke" topology more than a free-for-all topology where you have unpredictable DSP selection. That helps you avoid problems like:
Processor ethernet was previously only supported on simplex servers (S8300/S8500) and never on duplex servers. That eventually changed. With the phasing out of G650s, you won't be registering to CLANs for much longer.
CLANs have a limit of 400 sockets each, you've got to keep track of each one's firmware, data network connection, and you'd typically want to have 1 CLAN dedicated for a particular adjunct - like CMS or Intuity AUDIX. I know that sounds simple, but you wouldn't believe how often customers screw that up. When you can have many CLANs, and you can consequently have as many ethernet interfaces as you'd like in the PBX, and they're cheap, "list node-names all" is a mess of CLANs in 192.x, 10.x, 172.x, private networks, etc. Every one winds up on a different VLAN and its a mess to fix when it breaks.
Procr socket limits are based only by the server type, and will accommodate what you need, and has the benefit of being just 1 thing.
You'd be good to review your IP-network-map as well. Subnets for phones that are not assigned as belonging to a particular region will have the phone assume the region of the gatekeeper it registered to. That means it is possible to have a CLAN in region 5, overlook adding any IPs for phones to region 5, but by pointing a subnets DHCP to that CLAN, the phones inherit region 5. If you move to procr, the phones will inherit procr's network region and location. That means your network map must be solid.
Another interesting point related to design, is that best practices are for procr to be in its own network region without DSPs, usually 200 or 250. Every network region connects directly to procr. Every network region connects to every other network region through the intervening region of procr. It lends itself to more of a "hub and spoke" topology more than a free-for-all topology where you have unpredictable DSP selection. That helps you avoid problems like:
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question
- Question