Hello Bill
There is one method while reading white paper, let me know if if this suits you or in the enviorment
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/gatecont/ps5640/white_paper_c11-613550_ps10536_Products_White_Paper.html
2.2 CLI-Status
2.2.1 SIP Trunk Status
SIP trunk status is an important element of CUBE monitoring. SIP Trunk status can be monitored by configuring an out-of-dialog (OOD) SIP Options PING as a keepalive mechanism on the dial-peer(s) pointing towards the SIP Trunk, using the CLI example below.
dial-peer voice 100 voip
destination-pattern .T
voice-class sip options-keepalive up-interval 100 down-interval 50 retry 6
session protocol sipv2
session target ipv4:x.x.x.x
When calls to the SIP trunk are successful, the dial-peer is in "active" state. If SIP PING timeouts occur, the dial-peer changes to "busyout" status. Calls to the dial-peer during "busyout" will be rejected immediately to the originator for call rerouting.
• CUBE 1.3 (Cisco IOS 15.0.1M) returns an unconfigurable SIP "404 Not Found" error code
• CUBE 1.4 (15.1.1T) or later allows a configurable SIP error code in the 400-699 range. The default is "503 Service Unavailable"
Dial-peer state changes are as follows:
• Dial-peer is marked as "active" when a valid response to an Options PING is received
• Dial-peer is marked as "busyout" when no response to an Options PING is received
• Dial-peer status changes from "active" to "busyout" when:
– A "503 Service Unavailable" response is received
– No response is received, i.e. request timeout (configurable number of retries)
– A "505 Version not supported" response is received
• Dial-peer status changes from "busyout" to "active" after a configurable number of consecutive positive responses (i.e. anything except 503, 505 and t/o)
• On router reboot, all dial-peers start in the "active" state
The CLI to configure a SIP OOD Options PING is:
voice service voip
sip
error-code-override options-keepalive failure 500
dial-peer voice 10 voip
voice-class sip error-code-override options-keepalive failure 500
The dial-peer status based on the SIP OOD Options PING can be displayed with the following "show" commands:
router# show dial-peer voice summary
AD PRE PASS OUT
TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET STAT PORT KEEPALIVE
1 voip up up 1000 0 syst ipv4:x.x.x.10 active
2 voip up up 2000 0 syst ipv4:x.x.x.11 busyout
3 voip up up 3000 0 syst ipv4:x.x.x.12
router# show dial-peer voice | include options
voice class sip options-keepalive up-interval 100 down-interval 50 retry 6
voice class sip options-keepalive dial-peer action = active,
voice class sip options-keepalive up-interval 100 down-interval 50 retry 6
voice class sip options-keepalive dial-peer action = busyout,
SNMP would be best but AFAIK its currently not available.
2.4.2 SIP Trunk Status
SIP trunk status is an important element of CUBE monitoring. This status is not currently available via SNMP (only via CLI as covered in the previous section).
Br,
Nadeem
Please rate all useful post.
Br,
Nadeem
Please rate all useful post.
