cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1104
Views
0
Helpful
9
Replies

878 isdn problem

omulete
Level 1
Level 1

hi guys,

i have an 878 shdsl router with a built-in ISDN S/T interface. i try to use the isdn interface but it seems that nothing it's working.

System image file is "flash:c870-advsecurityk9-mz.123-14.YT1.bin"

isdn test call interface brI 0 3121686

000094: Oct 3 16:56:34.520 buc: ISDN BR0 **ERROR**: process_bri_call: Outgoing call id 0x8004 blocked

000095: Oct 3 16:56:34.520 buc: ISDN BR0 **ERROR**: UserIdle: process_bri_call failed on call to 3121686

the isdn line it's very ok.

9 Replies 9

thisisshanky
Level 11
Level 11

Can you paste a sh isdn status.

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus

Global ISDN Switchtype = basic-net3

ISDN BRI0 interface

dsl 0, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 113, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 0

interface BRI0

ip address negotiated

no ip redirects

no ip unreachables

no ip proxy-arp

encapsulation ppp

ip route-cache flow

dialer string xxxx

dialer-group 1

isdn switch-type basic-net3

isdn point-to-point-setup

ppp authentication chap

ppp chap hostname xxxx

ppp chap password 7 xxxxx

I do not see problems in the ISDN status since the layer 1 status is active and the layer 2 state is MULTIPLE_FRAME_ESTABLISHED.

I do not see any particular problem inn the interface configuration. It would be helpful to see what dialer list is associated with dialer-group 1. Perhaps the output of debug isdn q931 might be helpful.

HTH

Rick

HTH

Rick

hi guys,

The following ISDN debugs are enabled on all DSLs:

debug isdn error is ON.

debug isdn q931 is ON. (filter is OFF)

dialer-list 1 protocol ip permit

hostname#sh isdn status

Global ISDN Switchtype = basic-net3

ISDN BRI0 interface

dsl 0, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 113, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 0

hostname#isdn test l2 disconnect interface bRI 0

878_Teste#

000141: Oct 4 09:01:41.135 buc: %ISDN-3-LAYER2_DOWN: Layer 2 for Interface BR0, TEI 113 changed to down

000142: Oct 4 09:01:42.319 buc: ISDN BR0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

000143: Oct 4 09:01:42.319 buc: ISDN BR0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

hostname#sh isdn status

Global ISDN Switchtype = basic-net3

ISDN BRI0 interface

dsl 0, interface ISDN Switchtype = basic-net3

Layer 1 Status:

DEACTIVATED

Layer 2 Status:

Layer 2 NOT Activated

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 0

hostname#isdn test call interface brI 0 3121686

000146: Oct 4 09:03:25.978 buc: ISDN BR0 **ERROR**: process_bri_call: Outgoing call id 0x8006 blocked

000147: Oct 4 09:03:25.978 buc: ISDN BR0 **ERROR**: UserIdle: process_bri_call failed on call to 3121686

000149: Oct 4 09:03:55.970 buc: ISDN BR0 **ERROR**: CCBRI_Go: NO CCB Src->HOST call id 0x8006, event 0x5 ces 1

Hello, anything new at this ?

I have the same problem. Maybe it's the wrong feature set.

In the datasheet http://www.cisco.com/en/US/products/hw/routers/ps380/products_data_sheet0900aecd8028a976.html

you can see that only in the Advanced Enterprise Services IOS you can use the BRI as BackupInterface.

Maybe Cisco deactivated the BRI for outgoing calls in the other featuresets

Christian

I do not have direct experience with this particular model so I can not speak directly to this from experience. But I think it is very unlikely that Cisco deactivated the BRI for outgoing calls in your feature set.

I had not considered in the original post the possibility that the BRI might be functioning as backup interface. But this behavior might be consistent with configuration as backup interface. Perhaps you could post the relevant parts of the router config and also post the output of show interface for the BRI.

One thing about backup interface is that if the BRI is configured as backup interface for some other interface then the BRI will neither make a call or receive a call unless the primary interface is down (and shutdown of the primary does not allow the BRI to function).

Post the requested output and we will see if we can find answers to your issue.

HTH

Rick

HTH

Rick

(Sorry if this is a double post, I think my previous post didn't get submitted properly)

I'm having the same problem as described above, also with an 878. I simply cannot get it to dial out on a BRI channel (I get the same "Outgoing call id 0xXXXX blocked" error). Even "isdn test call" won't do it.

Is there any way I can find out for certain if this is in fact possible? Or if dialout has actually been disabled on the 878?

Help greatly appreciated, this has been driving me nuts for the last 2 days :(

Has anyone found a solution or a reason for this problem.

I have the ame problems as described in this thread and am REALLY in need for some suggestions.

Thanks for all suggestions

Bas

We have asked several of the people who have posted with this problem for the output of debug isdn q931 and so far no one has posted this information. Can you run the debug, attempt the test, and post the debug output.

It would also be helpful is you would post the router config.

HTH

Rick

HTH

Rick
Review Cisco Networking products for a $25 gift card