Kevin,<br><br>Removing the condition cleared that up, i'm now seeing q931 debugs on that router. Thanks a bunch! I'll read through that document to try to understand what that was for and how it got set (not something I did knowingly)
<br><br>Have a good weekend<br>Ed<br><br><div><span class="gmail_quote">On 6/16/06, <b class="gmail_sendername">Kevin Thorngren</b> <<a href="mailto:kthorngr@cisco.com">kthorngr@cisco.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Interesting, I just tried this in the lab. Per the documentation you<br>would expect to see debug traffic for only the specified interface(s)<br>in the condition. But I see that having a condition on the serial<br>interface seems to filter out the isdn debugs for all interfaces. Not
<br>sure if this is a bug or if there are good reasons why this is not<br>working. Maybe other conditions need to apply for the filter to work.<br><br>You can type "no debug condition 1" to remove the condition. You will
<br>see a warning message if this is the last condition you have. You can<br>type yes to the answer to remove the last condition.<br><br>Here is the docs describing this:<br><a href="http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/">
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/</a><br>products_command_reference_chapter09186a008017cfa1.html<br><br>Kevin<br>On Jun 16, 2006, at 10:27 AM, Ed Leatherman wrote:<br><br>> sh debug shows this, I dont see the message about "condition 1" on the
<br>> router that will properly displaying debug messages.<br>><br>> The following ISDN debugs are enabled on all DSLs:<br>><br>> debug isdn error is ON.<br>> debug isdn q931 is ON. (filter is ON)<br>>
<br>><br>><br>> Condition 1: interface Se0/0/0:23 (1 flags triggered)<br>> Flags: Se0/0/0:23<br>><br>><br>><br>> On 6/15/06, Ed Leatherman <<a href="mailto:ealeatherman@gmail.com">ealeatherman@gmail.com
</a>> wrote:debug MGCP<br>> packet appears to work fine.<br>>><br>>><br>>> On 6/15/06, Ryan Ratliff < <a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote:<br>>>> chan.Definitely
not supported with MGCP though.<br>>>><br>>>> How about if you turn on 'deb mgcp packet' along with your q931<br>>>> debug?<br>>>><br>>>> -Ryan<br>>>><br>>>> On Jun 15, 2006, at 2:02 PM, Ed Leatherman wrote:
<br>>>><br>>>> They are definately both PRI<br>>>><br>>>> Isnt there some configuration that allows multiple PRI's to share a<br>>>> D-<br>>>> channel? I specifically told the telco we didnt want this, and i'd be
<br>>>> surprised if it would work without any extra configuration on my<br>>>> side, but thats the only other thing I could think of.<br>>>><br>>>> #sh isdn status<br>>>> Global ISDN Switchtype = primary-4ess
<br>>>><br>>>> %Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 1. Layer 3 output<br>>>> may not apply<br>>>><br>>>> ISDN Serial0/0/0:23 interface<br>>>> dsl 1, interface ISDN Switchtype = primary-ni
<br>>>> L2 Protocol = Q.921 0x0000L3 Protocol(s) = CCM MANAGER<br>>>> 0x0003<br>>>> Layer 1 Status:<br>>>> ACTIVE<br>>>> Layer 2 Status:<br>>>> TEI = 0, Ces = 1, SAPI = 0, State =
<br>>>> MULTIPLE_FRAME_ESTABLISHED<br>>>> Layer 3 Status:<br>>>> 0 Active Layer 3 Call(s)<br>>>> Active dsl 1 CCBs = 0<br>>>> The Free Channel Mask:0x807FFFFF<br>>>> Number of L2 Discards = 0, L2 Session ID = 203
<br>>>> Total Allocated ISDN CCBs = 0<br>>>><br>>>> On 6/15/06, Ryan Ratliff <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote: Are both of them<br>>>> PRIs for sure?Perhaps the one not showing q931
<br>>>> debugs is actually a channel-group (CAS) and not a PRI?<br>>>><br>>>> -Ryan<br>>>><br>>>> On Jun 15, 2006, at 11:37 AM, Ed Leatherman wrote:<br>>>><br>>>> Just had the defaults on both routers, however I tried the "logging
<br>>>> console 7" on the problem router, which looks like it should display<br>>>> debuging messages and it still shows nothing.<br>>>><br>>>> Just for grins and giggles I turned on debug cdp packets, and i am
<br>>>> getting debug messages on both routers.. so its something with the<br>>>> ISDN that is causing it to not display.<br>>>><br>>>> On 6/15/06, Mark Borchers <<a href="mailto:mborchers@igillc.com">
mborchers@igillc.com</a>> wrote:<br>>>> Have you set your logging level high enough to show debug traffic?<br>>>> See the logging console command args.<br>>>> -----Original Message-----<br>>>> From:
<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto: cisco-voip-<br>>>> <a href="mailto:bounces@puck.nether.net">bounces@puck.nether.net</a> ] On Behalf Of Ed Leatherman
<br>>>> Sent: Thursday, June 15, 2006 10:26 AM<br>>>> To: ciscovoip<br>>>> Cc: <a href="mailto:jeff.davis@mail.wvu.edu">jeff.davis@mail.wvu.edu</a><br>>>> Subject: [cisco-voip] debug isdn q931
<br>>>><br>>>> I'm fairly certain this is something I am doing wrong but I cant find<br>>>> it for the life of me..<br>>>><br>>>> I have 2 ISR routers, 3825 with some T1 interfaces and DSPs for
<br>>>> conferencing. identical firmware loads and configurations, other than<br>>>> 1 has an FXO card that the other doesn't.<br>>>><br>>>> I'm executing on both routers from seperate SSH sessions:
<br>>>> # term mon<br>>>> # debug isdn q931<br>>>><br>>>> On router A, I can see all the Q931 debug messages go by. On router<br>>>> B, I see nothing on the SSH session however I know calls are being
<br>>>> placed on it ( I can see the channels going in service etc from<br>>>> RTMT). Could I have something turned off on router B that doesnt show<br>>>> up in the config?<br>>>><br>>>> --
<br>>>> Ed Leatherman<br>>>> IP Telephony Coordinator<br>>>> West Virginia University<br>>>> Telecommunications and Network Operations<br>>>><br>>>><br>>>><br>
>>> --<br>>>> Ed Leatherman<br>>>> IP Telephony Coordinator<br>>>> West Virginia University<br>>>> Telecommunications and Network Operations<br>>>> _______________________________________________
<br>>>> cisco-voip mailing list<br>>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>>>><br>>>><br>>>><br>>>><br>>>> --<br>>>> Ed Leatherman<br>>>> IP Telephony Coordinator<br>>>> West Virginia University<br>>>> Telecommunications and Network Operations
<br>>>><br>>><br>>><br>>><br>>> --<br>>><br>>> Ed Leatherman<br>>> IP Telephony Coordinator<br>>> West Virginia University<br>>> Telecommunications and Network Operations
<br>><br>><br>> --<br>> Ed Leatherman<br>> IP Telephony Coordinator<br>> West Virginia University<br>> Telecommunications and Network<br>> Operations_______________________________________________<br>
> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>IP Telephony Coordinator<br>West Virginia University<br>Telecommunications and Network Operations