{"id":208,"date":"2018-05-25T11:34:45","date_gmt":"2018-05-25T09:34:45","guid":{"rendered":"https:\/\/am-itconsulting.de\/?p=208"},"modified":"2018-05-25T11:34:45","modified_gmt":"2018-05-25T09:34:45","slug":"sip-debugging-overview","status":"publish","type":"post","link":"https:\/\/am-itconsulting.de\/?p=208","title":{"rendered":"SIP debugging overview"},"content":{"rendered":"<h3 id=\"toc-hId-1053871152\"><strong>SIP debugging overview<\/strong><\/h3>\n<p><strong>debug ccsip<\/strong>: This has various options,<\/p>\n<ul>\n<li>debug ccsip all: \u00a0This command enables all ccsip type debugging. This debug command is very active, you should use it sparingly in a live network<\/li>\n<li>debug ccsip calls: This command displays all SIP call details as they are updated in the SIP call control block. You can use this debug command to monitor\u00a0call records for suspicious clearing causes.<\/li>\n<li>debug ccsip errors: This command traces all errors that are encountered by the SIP subsystem.<\/li>\n<li>debug ccsip events: this command traces event, such as call setups, connections and disconnections. An events version of a debug command is often the best place\u00a0to start because detailed debugs provide much useful information.<\/li>\n<li>debug ccsip info: This command enables tracing of general SIP security parameter index (SPI) information, including verification that call redirection is disabled.<\/li>\n<li>debug ccsip media: This command enables tracing of SIP media streams<\/li>\n<li>debug ccsip messages: This command shows the headers of SIP messages that are exchanged between a client and a server.<\/li>\n<li>debug ccsip preauth: This command enables diagnostic reporting of authentication, authorization, accounting (AAA) for SIP calls.<\/li>\n<li>debug ccsip states: This command displays the SIP states and state changes for sessions within the SIP subsytem.<\/li>\n<li>debug ccsip transport: This command enables tracing the SIP transport handler and the TCP or UDP process<\/li>\n<\/ul>\n<p><strong>debug voip ccapi inout<\/strong>: This command shows every interaction with the call control application programming interface (API) on both the telephone interface and on the VOIP side.\u00a0By monitoring the output, you can follow the progress of a call from the inbound interface or VOIP peer to the outbound side of the call. This debug command is very active.\u00a0you should use it sparingly in a live network.<\/p>\n<p><strong>debug voip ccpai protoheaders:<\/strong>\u00a0This command displays messages that are sent between the originating and terminating gateways. If no headers are being received by the terminating gateway,\u00a0verify that the header-passing command is enabled on the originating gateway.<\/p>\n<p><strong>Feature Design of SIP Debug Output Filtering Support<\/strong><\/p>\n<p>Prior to the SIP Debug Output Filtering Support feature, debugging and troubleshooting on the VoIP gateway was made more challenging by the extensive amounts of raw data generated by debug output.<\/p>\n<p>This feature allows the debug output for a SIP call to be filtered according to a variety of criteria. The SIP Debug Output Filtering Support feature provides a generic call filtering mechanism\u00a0that does the following:<\/p>\n<p>\u2022Allows you to define a set of matching conditions for filtering calls.<\/p>\n<p>\u2022Identifies the desired calls based on the configured matching conditions inside VoIP gateways.<\/p>\n<p>\u2022Coordinates the filtering effort on traced calls between multiple modules inside VoIP gateways.<\/p>\n<p>\u2022Displays the debugging trace for calls that match the specified conditions.<\/p>\n<p><strong>SIP Debug Commands that Support Output Filtering<\/strong><\/p>\n<p>\u2022debug ccsip all<\/p>\n<p>\u2022debug ccsip calls<\/p>\n<p>\u2022debug ccsip events<\/p>\n<p>\u2022debug ccsip messages<\/p>\n<p>\u2022debug ccsip preauth<\/p>\n<p>\u2022debug ccsip states<\/p>\n<p><strong>Configuring Call Filters<\/strong><\/p>\n<p>This task configures the conditions for filtering SIP calls.<\/p>\n<p>SUMMARY STEPS<\/p>\n<p>1. enable<\/p>\n<p>2. configure terminal<\/p>\n<p>3. call filter match-list number voice<\/p>\n<p>4. incoming calling-number string<\/p>\n<p>5. incoming called-number string<\/p>\n<p>6. incoming signaling {local | remote} ipv4 ip-address<\/p>\n<p>7. incoming media {local | remote} ipv4 ip-address<\/p>\n<p>8. incoming dialpeer tag<\/p>\n<p>9. outgoing calling-number string<\/p>\n<p>10. outgoing called-number string<\/p>\n<p>11. outgoing signaling {local | remote} ipv4 ip-address<\/p>\n<p>12. outgoing media {local | remote} ipv4 ip-address<\/p>\n<p>13. outgoing dialpeer tag<\/p>\n<p>14. end<\/p>\n<p><strong>Example:<\/strong><\/p>\n<p>call filter match-list 1 voice<br \/>\nincoming called-number 4085559876<br \/>\n!<br \/>\nvoice-port 0:D<br \/>\n!<br \/>\nvoice-port 1:D<br \/>\n!<br \/>\nvoice-port 2:D<br \/>\n!<br \/>\nvoice-port 3:D<\/p>\n<p><strong>Enabling SIP Debug Output Filtering: Example<\/strong><\/p>\n<p>Router# debug condition match-list 1 exact-match<br \/>\nRouter# debug ccsip all<\/p>\n<p>Router# show debug<\/p>\n<p>CCSIP SPI:SIP Call Statistics tracing is enabled \u00a0 \u00a0 \u00a0 (filter is ON)<br \/>\nCCSIP SPI:SIP Call Message tracing is enabled \u00a0(filter is ON)<br \/>\nCCSIP SPI:SIP Call State Machine tracing is enabled \u00a0 \u00a0(filter is ON)<br \/>\nCCSIP SPI:SIP Call Events tracing is enabled \u00a0 (filter is ON)<br \/>\nCCSIP SPI:SIP error debug tracing is enabled \u00a0 (filter is ON)<br \/>\nCCSIP SPI:SIP info debug tracing is enabled \u00a0 \u00a0(filter is ON)<br \/>\nCCSIP SPI:SIP media debug tracing is enabled \u00a0 (filter is ON)<br \/>\nCCSIP SPI:SIP Call preauth tracing is enabled \u00a0(filter is ON)<\/p>\n<p>Router# Debug filtering is now on<br \/>\nBuilding configuration&#8230;<br \/>\n!<br \/>\n!<br \/>\n!<br \/>\ncall filter match-list 1 voice<br \/>\nincoming called-number 4085551221<br \/>\n!<br \/>\nend<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SIP debugging overview debug ccsip: This has various options, debug ccsip all: \u00a0This command enables all ccsip type debugging. This debug command is very active, you should use it sparingly in a live network debug ccsip calls: This command displays all SIP call details as they are updated in the SIP call control block. You [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-208","post","type-post","status-publish","format-standard","hentry","category-unified-communications"],"_links":{"self":[{"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=\/wp\/v2\/posts\/208","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=208"}],"version-history":[{"count":1,"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=\/wp\/v2\/posts\/208\/revisions"}],"predecessor-version":[{"id":209,"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=\/wp\/v2\/posts\/208\/revisions\/209"}],"wp:attachment":[{"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=208"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=208"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/am-itconsulting.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=208"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}