I found several ways monitoring SIP calls in PRTG using SNMP.
- Monitor active calls using SIP legs/2
- Monitor each dial-peer separately and combine them in the Sensor Factory
- Just monitor multiple OIDs in one Sensor
Enable SNMP on the CUBE:
conf t snmp-server community <community> ro snmp-server location <location> snmp-server contact <contact info>
1. Monitor active calls using SIP legs
Idea: check how many SIP legs on the voice gateways (show call active voice brief). Use it in the Total SIP call Sensor Factory by dividing “SIP call-legs” /2:
SNMP Custom OID: 188.8.131.52.184.108.40.206.220.127.116.11.18.104.22.168
Get the sensor ID and use it in the Sensor Factory:
2. Monitor each dial-peer separately and combine them in the Sensor Factory
Check the dial-peer voice numbers for the inbound and outbound calls. Dial-peer’s number will be used in OIDs:
###### OUTBOUND Dial-peers to SIP Provider = Outbound calls ###### dial-peer voice 100 voip description ***SIP_OUTBOUND*** [...] dial-peer voice 101 voip description ***SIP_OUTBOUND_BACKUP*** [...] dial-peer voice 105 voip description ***SIP_OUTBOUND_INTL*** [...] dial-peer voice 106 voip description ***SIP_OUTBOUND_INTL*** [...] ###### OUTBOUND Dial-peers to CUCM = Incoming calls ###### dial-peer voice 102 voip description ***SIP_OUTBOUND_TO_CUCM*** [...] dial-peer voice 103 voip description ***SIP_OUTBOUND_TO_CUCM*** [...]
An SNMP walk against the OID 22.214.171.124.126.96.36.199.188.8.131.52.4.1.2 will show all dial-peers configured and it’s usage:
Add a SNMP Custom sensors. Based on the number of dial-peers, add some or all of them (for both inbound and outbound):
Check Sensor’s ID for each dial-peer and use them in the Sensor Factories for Total Outbound and Total Inbound calls.
Total Outbound Calls ( Sensor Factory) – a sum of all outbound dial-peers:
Total Inbound Calls ( Sensor Factory) – a sum of all “inbound” dial-peers (to CUCM):
3. Just monitor multiple OIDs in one Sensor
Just add all Outbound OIDs into the SNMP Custom Advanced (up to 10):
Because the update interval is 30 sec, there could be some mismatches between individual deal-peer outputs and total calls. Overall these methods should be pretty accurate and gives you an idea for SIP utilization.