Avaya PBX T1 Trunk to UM at Capacity?

[AuraTechie]

Thanks for any insight you can provide.

We have an Avaya PBX running CM 3.1.2 connected to an Exchange 2010 Unified Messaging server for voice mail (via an Audiocodes T1-to-SIP gateway). We have provisioned a 23-channel T1 trunk on the PBX.
Our users have had a very good experience so far with the trasition off Audix, including no busy signals.

However, on Monday mornings lately, we think we might be reaching capacity on that 23-channel link, since a few UM busy signals have been reported in that 8am-9am time period.

Is there anyway for us to pull capacity history metrics off the Avaya PBX? Or do some realtime monitoring of the T1 trunk side of the gateway to confirm our suspicians? And if you want to add your 2 cents for a long-term solution (i.e. adding SIP trunk to the equation?) that would be good to know too.

Thank you.

 

[cajuntank]

Your best bet would be to pose this question to the Avaya group on this forum

http://www.tek-tips.com/threadminder.cfm?pid=690

as your question deals more from the PBX side than the Exchange side. You can also check on

http://www.iaug.org/avayausers

for Avaya side questions and answers as well. With you having an older CM like that, I don't know if it has SES so that SIP connections could be done between the AVAYA and Exchange, but if I'm not mistaken, the only certified connectivity (outside of using a certied external codec like AudioCodes, NET, etc...) between CM and Exchange UM is either over Session Manager or SIP Enabled Services (SES) using CM 5.X.

 

[texeric]

AuraTechie - a busy signal may be a capacity issue, but could also be other issues as well. First check during that time frame if the trunk on the Avaya side shows all (or most) channels in use. If so, then it is most likely a capacity issue. If not, then it could be something else in the SIP gateway or even something on the UM side.

If it is a capacity issue, you may be able to add additional T1(s), depending on slot availability in your PBX and model of AudioCodes gateway. A single (properly sized) UM server can handle 100 or more concurrent calls. So unless you're planning to handle 200+ calls simultaniously you should be ok on the UM server side if you plan to add additional channels to the integration.