[cisco-voip] T321 timer on BRI channel
James Jung
James.Jung at telecom.co.nz
Thu Nov 20 21:36:31 EST 2008
Sorry, the below configuration might be related to the previous email or
not.
The question is I have problem understanding this "isdn timer T321 0"
!
interface BRI0/0/0
no ip address
isdn switch-type basic-net3
isdn timer T321 0
isdn point-to-point-setup
isdn incoming-voice voice
isdn map address .* plan national type unknown
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
!
interface BRI0/0/1
no ip address
isdn switch-type basic-net3
isdn timer T321 0
isdn point-to-point-setup
isdn incoming-voice voice
isdn map address .* plan national type unknown
isdn bind-l3 ccm-manager service mgcp
isdn send-alerting
isdn sending-complete
!
Cisco document says setting the timer to 0 causes the timer expiry to
become infinite so that it will never expire.
What does the above configuration actually do for this "isnd timer t321
0" configuration?
Can anyone give me a detailed explanation with actual example?
Many thanks.
________________________________
From: James Jung
Sent: Friday, 21 November 2008 14:14
To: cisco-voip at puck.nether.net
Subject: T321 timer on BRI channel
Hi all
I have a problem and it has happened 7 times already this year.
A remote office use 2 BRI circuits controlled by CCM (4.1.3) using MGCP.
No one can make inbound and outbound call when it happens, and the isdn
status shows "Multiple-Frame.... Established" but when I make a test
call from PSTN, the q931 shows
*Nov 21 10:10:54: ISDN BR0/0/0 Q931: RX <- SETUP pd = 8 callref = 0x1A
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Signal i = 0x40 - Alerting on - pattern 0
Called Party Number i = 0x80, '2551694'
Plan:Unknown, Type:Unknown
High Layer Compat i = 0x9181
*Nov 21 10:10:54: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref
= 0x9A
Cause i = 0x80AC - Requested circuit/channel not available
And after bouncing the bri interface or no mgcp and mgcp command, it
works fine.
Anyone can tell me what would be the cause and how to avoid this
problem?
Thank you very much for your help in advance.
JJ.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081121/aeae5f23/attachment-0001.html>
More information about the cisco-voip
mailing list