Mailing List Archive: FX0 pool exhuastion

There isn?t any great ?baked in? way to monitor aggregate usage, however, some things that might help:

* Log the output of ?debug vpm signal? to the syslog. If you?re time stamping the syslog entries then you could reasonably piece together the times the FXO port?s experience a fxols_onhook_ringing or fxols_proc_voice event.

* Use some sort of a traffic grapher like Paessier (PRTG). These platforms tend to have a knack for being able to login to CLIs and execute command structures. If you can do that (one way or the other), frequently capture the output of "show voice port summary" which gives you a real-time / at-the-moment state of each FXO/S voice port

Absent that, you'd likely be relegated to the above, in an "on demand / manual" way.

Thanks,

Ryan

Thanks,

Ryan Huff
________________________________
From: cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of harbor235 <harbor235@gmail.com>
Sent: Monday, April 17, 2023 11:15:06 AM
To: Cisco VOIP <cisco-voip@puck.nether.net>
Subject: [cisco-voip] FX0 pool exhuastion

Hi,

I have a CISCO ISR4331 voice bundle (CME) setup with a 4FX0 using 4 analog lines. The number of phones and users have increased and would like to verify justification to add SIP trunks. If we are experiencing no free FX0 lines for inbound or outbound calls does a log message get generated to observe the need to augment the analog line pool or add a sip trunk? I would like an observable data point to justify adding more capacity?

thanks in advance,

Mike