Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Calls on Second BRI Channel Fail

Hi everyone, we have two ISDN BRIs configured for incoming voice calls coming into a 2811 router. If you place a call to one channel of the bri the call is successful. If you place another call to the second channel while the first call is active, the caller hears ringing for about a minute and then is disconnected. The called phone rings for a brief second and then disconnects. Debugs on the router show that a Call Release is being received by the telco. We had the telco in to test and when the second call is placed their debugs show no response from the router once the call setup is sent. Here is the bri config:

interface BRI0/3/0

no ip address

isdn switch-type basic-ni

isdn incoming-voice voice

!

interface BRI0/3/1

no ip address

isdn switch-type basic-ni

isdn incoming-voice voice

Here is the debug from the router that shows the call release:

Dec 23 20:57:18.751: ISDN BR0/3/1 Q931: RX <- SETUP pd = 8 callref = 0x1F

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x8A

Signal i = 0x40 - Alerting on - pattern 0

Calling Party Number i = 0x2081, '9199915607'

Plan:Unknown, Type:National

Called Party Number i = 0xC1, '6137825'

Plan:ISDN, Type:Subscriber(local)

Locking Shift to Codeset 5

Codeset 5 IE 0x2A i = 0x808001039E05, 'From ', 0x8B0C, '919 991-5607', 0x9E04, 'For ', 0x950C, '860 613-7824', 0x8001018C03, 'cfb', 0x8001018C0E, 'Forw arded-busy', 0x800105800114 .Dec 23 20:57:18.767: ISDN BR0/3/1 Q931: TX -> CALL_PROC pd = 8 callref = 0x9F

Channel ID i = 0x8A

.Dec 23 20:57:18.787: ISDN BR0/3/1 Q931: TX -> ALERTING pd = 8 callref = 0x9F

Channel ID i = 0x8A

.Dec 23 20:57:18.823: ISDN BR0/3/1 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x 1F

Cause i = 0x8295 - Call rejected

.Dec 23 20:57:18.839: ISDN BR0/3/1 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x 1F

Cause i = 0x8295 - Call rejected

Does anyone have any ideas?

1 REPLY

Re: Calls on Second BRI Channel Fail

Hello,

The cause code for the call release is 0x8295, which can be found and explained at

http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a008012e95f.shtml

The least Byte has the meaning:

95 Call rejected The destination is capable of accepting the call, but it rejected the call for an unknown reason.

This cause indicates that the equipment that sends this cause does not want to accept this call.

Note: The equipment is able to accept the call because the equipment that sends this cause is neither busy nor incompatible. However, the equipment rejects the call.

So there seems to be an issue with the end device and the router. What is connected and is this device working in case only one call is in place to it?

Hope this helps! Please rate all posts.

regards, Martin

271
Views
5
Helpful
1
Replies
CreatePlease login to create content