Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Status of SIP trunks

I have a large number of Cube routers running 15.1.x.  They connect have a SIP trunk to our ITSP.  I'm trying to find a way to monitor that SIP trunk.  Documentation/posts I've found reference "show sip-ua register status".  However that returns nothing, even for our working SIP trunks

Router#show sip-ua register status

Line                             peer       expires(sec) registered P-Associ-URI

================================ ========== ============ ========== ============

Router#

Any other ideas? Thanks

Everyone's tags (2)
4 REPLIES
Cisco Employee

Status of SIP trunks

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.
New Member

Hi Nadeem, thanks for the

Hi Nadeem, thanks for the detailed answer. But according to the book, Network Warriar 2nd Edition, in page number 560, they are mentioning about this command "show sip-ua register status" and it will display the SIP trunk lines too. Here is the output from that book.

 

R1-PBX#sho sip-ua register status
Line                    peer                     expires(sec)      registered        P-Associated-URI
============ ============= ============ =========== ================
101                     20001                  1857                   yes
102                     20002                  1857                    yes
103                     20003                  1857                   yes
104                     20004                  1857                   yes
557333333         −1                         2340                   yes
608222222         −1                        2145                   yes

 

The author mentions that the last two lines with "-1" as peer are sip trunks. Could you please guide me on this?

Thanks,

Pandi

New Member

Hi Nadeem,Will this work in

Hi Nadeem,

Will this work in without CUBE environment? I have a voip gateway without CUBE.

 

Thanks,

Pandi

VIP Super Bronze

Re: Status of SIP trunks

Bill,

SIP trunks do not register as other sip endpoints do, hence you will not find any information using the show sip-ua status. As Nadeem suggested (+5), OPTIONs PING is the only option to use to monitor the status of a sip trunk..What you need to do is to check the status of the dial-peer to the ITSP using the command below:

sh dial-peer voice summary

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
1303
Views
15
Helpful
4
Replies