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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VoIP Trunking
- Thread starter randyb19
- Start date
hawaiitech
Technical User
The design considerations go far beyond my knowledge, but I think the first limitation you would run into would be how many simultaneous connections the Medpro would be able to handle. I think that can change depending on what codec you use.
To elaborate more, taking medpro resources out of the picture.. Your limiting point in theory other than the trunk group page is your CLAN.. I'm not sure on the exact number but the socket connections of a CLAN is around 300ish I think..
BuckWeet
BuckWeet
- Thread starter
- #5
I understand the hardware limitation of the CLANs and MEDPROs, but there must me a limit to how many channels a signaling group can govern. With a standard T1, your limited by how many channels can be included just by the nature of the circuit. But with a VoIP trunk, running over an OC-48, I could go hog wild adding channels. So, there has to be a maximum limit to how many channels a signaling group can handle in a VoIP trunk.
You're thinking in a different way.. IP is in no way like TDM technologies.. Its all logical thinking now, non circuit switched thinking now.
With IP it is now comes down to the limitation of the hardware in question. There are no D channels, its all IP signaling, which therefore it comes to an issue of the CLAN being the bottleneck if anything. If AVAYA ever comes up with a way of letting you group CLANs, then that theory itself is thrown out the door.. You're only limitations to my knowledge is how many trunks you can have in a trunk group and then how many connections a clan can support.
BuckWeet
With IP it is now comes down to the limitation of the hardware in question. There are no D channels, its all IP signaling, which therefore it comes to an issue of the CLAN being the bottleneck if anything. If AVAYA ever comes up with a way of letting you group CLANs, then that theory itself is thrown out the door.. You're only limitations to my knowledge is how many trunks you can have in a trunk group and then how many connections a clan can support.
BuckWeet
johnkeystone
Technical User
Hello, I am a newbie to VoIP but I have come across these numbers:
The MedPro handles 64 phones or trunks under G711, 32 with G729 or G723.
The number of sockets supported by the C-LAN is 442.
Where I am unclear is when resources are freed-up, for example, apparently they are when 2 IP trunks are connected?
And also, I think with the MedPro the formula based on that 64 number is 1 to 10 for normal users, and 1 to 1.5 for call center agents. If I understand that correctly, that means a MedPro is needed for every 96 agents?
If anyone can clarify, it'd be greatly appreciated!
The MedPro handles 64 phones or trunks under G711, 32 with G729 or G723.
The number of sockets supported by the C-LAN is 442.
Where I am unclear is when resources are freed-up, for example, apparently they are when 2 IP trunks are connected?
And also, I think with the MedPro the formula based on that 64 number is 1 to 10 for normal users, and 1 to 1.5 for call center agents. If I understand that correctly, that means a MedPro is needed for every 96 agents?
If anyone can clarify, it'd be greatly appreciated!
Hey--great question as I am setting up several IP phones in another State and the first phone that went out ---set to G.711 IP-Codec, produced a lot of excitement. The call was very clear and now the Call Center Director has control over call allocation and processing--plus data from CMS about that call. So more phones have been ordered----
The answer about which codec to use and how many total calls will be very interesting to me.
The answer about which codec to use and how many total calls will be very interesting to me.
- Status