Cisco Cisco IOS Software Release 12.2(8)T

SIP Media Inactivity Timer

Configuration Examples

Cisco IOS Release 12.2(8)T and 12.2(11)T

Verifying the SIP Media Inactivity Timer

To verify that the SIP Media Inactivity Timer feature is enabled, follow these steps:

Step 1

Enter the show running-config command to verify the configuration.

Step 2

Enter the debug ccsip events command to verify that the timer is enabled.

Troubleshooting Tips

To troubleshoot the SIP Media Inactivity Timer feature, perform the following tasks:

•

Make sure that you can make a voice call.

•

Use the debug ccsip all command to enable all SIP debugging capabilities, or use one of the
following more specific SIP debug commands:

–

debug ccsip calls

–

debug ccsip error

–

debug ccsip messages

•

Use the debug ccsip events command, which includes new output specific to the SIP Media
Inactivity Timer feature. The following example trace shows a timer being set:

Router# debug ccsip events

00:04:29: sipSPICreateAndStartRtpTimer: Valid RTP/RTCP session found and CLI ena

bled to create and start the inactivity timer

00:04:29: sipSPICreateAndStartRtpTimer:Media Inactivity timer created for call.

Mfactor(from CLI): 5 RTCP bandwidth: 500

RTCP Interval(in ms): 5000

Normalized RTCP interval (in ms):25000

The following example trace shows a timer expiring:

Router# debug ccsip events

02:41:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed state to

down

*Jan 1 02:41:34.107: sipSPIRtpDiscTimerExpired:RTP/RTCP receive timer expired.

Disconnect the call.

*Jan 1 02:41:34.107: Queued event From SIP SPI to CCAPI/DNS :

SIPSPI_EV_CC_CALL_DISCONNECT

*Jan 1 02:41:34.107: CCSIP-SPI-CONTROL: act_active_disconnect

Note

The timer receive-rtcp command configures a media activity timer that is common to both H.323 and
SIP. If set, it affects both H.323 and SIP calls.

Configuration Examples

This section provides the following configuration example:

•

Configuring the SIP Media Inactivity Timer Feature Example