[cisco-voip] debug isdn q931

Fri Jun 16 11:08:17 EDT 2006

Interesting, I just tried this in the lab.  Per the documentation you  
would expect to see debug traffic for only the specified interface(s)  
in the condition.  But I see that having a condition on the serial  
interface seems to filter out the isdn debugs for all interfaces.  Not  
sure if this is a bug or if there are good reasons why this is not  
working.  Maybe other conditions need to apply for the filter to work.

You can type "no debug condition 1" to remove the condition.  You will  
see a warning message if this is the last condition you have.   You can  
type yes to the answer to remove the last condition.

Here is the docs describing this:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/ 
products_command_reference_chapter09186a008017cfa1.html

Kevin
On Jun 16, 2006, at 10:27 AM, Ed Leatherman wrote:

> sh debug shows this, I dont see the message about "condition 1" on the  
> router that will properly displaying debug messages.
>
> The following ISDN debugs are enabled on all DSLs:
>
> debug isdn error is             ON.
> debug isdn q931 is              ON.   (filter is ON)
>
>
>
> Condition 1: interface Se0/0/0:23 (1 flags triggered)
>         Flags: Se0/0/0:23
>
>
>
> On 6/15/06, Ed Leatherman <ealeatherman at gmail.com> wrote:debug MGCP  
> packet appears to work fine.
>>
>>
>> On 6/15/06, Ryan Ratliff < rratliff at cisco.com> wrote:
>>> chan.  Definitely not supported with MGCP though.
>>>
>>> How about if you turn on 'deb mgcp packet' along with your q931  
>>> debug?
>>>
>>> -Ryan
>>>
>>>  On Jun 15, 2006, at 2:02 PM, Ed Leatherman wrote:
>>>
>>> They are definately both PRI
>>>
>>> Isnt there some configuration that allows multiple PRI's to share a  
>>> D-
>>> channel? I specifically told the telco we didnt want this, and i'd be
>>> surprised if it would work without any extra configuration on my
>>> side, but thats the only other thing I could think of.
>>>
>>> #sh isdn status
>>> Global ISDN Switchtype = primary-4ess
>>>
>>> %Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 1. Layer 3 output
>>> may not apply
>>>
>>>  ISDN Serial0/0/0:23 interface
>>>          dsl 1, interface ISDN Switchtype = primary-ni
>>>          L2 Protocol = Q.921 0x0000  L3 Protocol(s) = CCM MANAGER  
>>> 0x0003
>>>      Layer 1 Status:
>>>          ACTIVE
>>>      Layer 2 Status:
>>>          TEI = 0, Ces = 1, SAPI = 0, State =  
>>> MULTIPLE_FRAME_ESTABLISHED
>>>      Layer 3 Status:
>>>          0 Active Layer 3 Call(s)
>>>      Active dsl 1 CCBs = 0
>>>      The Free Channel Mask:  0x807FFFFF
>>>      Number of L2 Discards = 0, L2 Session ID = 203
>>>      Total Allocated ISDN CCBs = 0
>>>
>>> On 6/15/06, Ryan Ratliff <rratliff at cisco.com> wrote: Are both of them
>>> PRIs for sure?  Perhaps the one not showing q931
>>> debugs is actually a channel-group (CAS) and not a PRI?
>>>
>>> -Ryan
>>>
>>> On Jun 15, 2006, at 11:37 AM, Ed Leatherman wrote:
>>>
>>> Just had the defaults on both routers, however I tried the "logging
>>> console 7" on the problem router, which looks like it should display
>>> debuging messages and it still shows nothing.
>>>
>>> Just for grins and giggles I turned on debug cdp packets, and i am
>>> getting debug messages on both routers.. so its something with the
>>> ISDN that is causing it to not display.
>>>
>>> On 6/15/06, Mark Borchers <mborchers at igillc.com> wrote:
>>> Have you set your logging level high enough to show debug traffic?
>>> See the logging console command args.
>>> -----Original Message-----
>>> From: cisco-voip-bounces at puck.nether.net [mailto: cisco-voip-
>>> bounces at puck.nether.net ] On Behalf Of Ed Leatherman
>>> Sent: Thursday, June 15, 2006 10:26 AM
>>> To: ciscovoip
>>> Cc: jeff.davis at mail.wvu.edu
>>> Subject: [cisco-voip] debug isdn q931
>>>
>>> I'm fairly certain this is something I am doing wrong but I cant find
>>> it for the life of me..
>>>
>>> I have 2 ISR routers, 3825 with some T1 interfaces and DSPs for
>>> conferencing. identical firmware loads and configurations, other than
>>> 1 has an FXO card that the other doesn't.
>>>
>>>  I'm executing on both routers from seperate SSH sessions:
>>> # term mon
>>> # debug isdn q931
>>>
>>> On router A, I can see all the Q931 debug messages go by. On router
>>> B, I see nothing on the SSH session however I know calls are being
>>> placed on it ( I can see the channels going in service etc from
>>> RTMT). Could I have something turned off on router B that doesnt show
>>> up in the config?
>>>
>>> --
>>> Ed Leatherman
>>> IP Telephony Coordinator
>>>  West Virginia University
>>> Telecommunications and Network Operations
>>>
>>>
>>>
>>> --
>>> Ed Leatherman
>>> IP Telephony Coordinator
>>> West Virginia University
>>> Telecommunications and Network Operations
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>>  https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>>
>>>
>>> --
>>> Ed Leatherman
>>> IP Telephony Coordinator
>>> West Virginia University
>>> Telecommunications and Network Operations
>>>
>>
>>
>>
>> --
>>
>> Ed Leatherman
>> IP Telephony Coordinator
>> West Virginia University
>> Telecommunications and Network Operations
>
>
> -- 
> Ed Leatherman
> IP Telephony Coordinator
> West Virginia University
> Telecommunications and Network  
> Operations_______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 5570 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20060616/f42709c4/attachment-0001.bin 