Hi,
we have an Cisco 2911 voice gateway configured with 6 BRI Interfaces and connected to an CUCM 8.0.3
Incoming calls from PSTN are delayed in call proceeding by round about 14 seconds! Here is a debug of this:
Jun 10 09:00:41.317: ISDN BR0/1/1 Q931: RX <- SETUP pd = 8 callref = 0x55
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Exclusive, B1
Calling Party Number i = 0x2181, '39982XXXXX'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, 'XXXX142'
Plan:ISDN, Type:Subscriber(local)
High Layer Compat i = 0x9181
Jun 10 09:00:41.317: ISDN BR0/1/1 Q931: TX -> SETUP_ACK pd = 8 callref = 0xD5
Channel ID i = 0x89
Exclusive, B1
Jun 10 09:00:56.321: ISDN BR0/1/1 Q931: TX -> CALL_PROC pd = 8 callref = 0xD5
Jun 10 09:00:56.337: ISDN BR0/1/1 Q931: TX -> ALERTING pd = 8 callref = 0xD5
You can see the delay between TX -> SETUP_ACK and TX -> CALL_PROC. There a 15 Seconds while the caller no hear ringback tone.
What can be the reason of this?
Here is a sample of BRI Interface configuration:
interface BRI0/0/0
no ip address
isdn switch-type basic-net3
isdn overlap-receiving
isdn point-to-point-setup
isdn incoming-voice voice
isdn send-alerting
isdn static-tei 0
Can somebody help?
Which exact IOS are you using?
DP config ?
IOS is
(C2900-UNIVERSALK9-M), Version 15.1(4)M
Dial-Peer:
dial-peer voice 1 pots
description incoming from PSTN
incoming called-number .
direct-inward-dial
!
dial-peer voice 10 voip
description to CUCM
destination-pattern 12345T
modem passthrough nse codec g711alaw
session target ipv4:192.168.161.240
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
fax-relay ecm disable
fax protocol pass-through g711alaw
no vad
no supplementary-service h225-notify cid-update
!
On the voip dial peer make it a pattern match, something like:-
destination-pattern 12345...
Hope this helps,
Craig
(PLEASE RATE HELPFUL POSTS)
Craig Dyer wrote:
On the voip dial peer make it a pattern match, something like:-
destination-pattern 12345...
I think they used T believing it is needed to support different lenght called numbers and presence overlap-receiving.
In reality, what is needed, in these cases is avoid overlapping numbers, and use separate DPs.
Hi,
Had this issue resolved? We have same problem in our network.
Please help me with the resolution if you have already got it.
Appreciate your help.
Regards,
Sanadh
Can you send you sh run here and a
debug voip ccapi inout
Hi,
Thanks for your immediate response.
Issue resolved now. It was dial-peer issue. Our subscriber CUCM 10.99.4.1 is down and not in cluster.
So going to next dial-peer (dial-peer voice 8 voip) was taking 15 seconds.
dial-peer voice 7 voip
destination-pattern 3096....
progress_ind setup enable 1
progress_ind progress enable 1
progress_ind connect enable 1
progress_ind disconnect enable 8
session target ipv4:10.99.4.1
incoming called-number .
dtmf-relay h245-alphanumeric
codec g711ulaw
!
dial-peer voice 8 voip
preference 1
destination-pattern 3096....
progress_ind setup enable 1
progress_ind progress enable 1
progress_ind connect enable 1
progress_ind disconnect enable 8
session target ipv4:10.99.4.2
incoming called-number .
dtmf-relay h245-alphanumeric
codec g711ulaw
!
Thanks & Regards,
Sanadh
Sanadh,
To avoid this in the future configure the following
voice class h323 1
h225 timeout tcp establish 3
dial-peer voice 7 voip
voice-class h323 1
WIth this command when the primary callmanager on dial-peer 7 is down, the next callmanager on dial-peer 8 will be tried within 3 secs.
Pls rate useful posts
Thank you for the valuable input, i will configure the same in voice gateway.
This will help us to avoid delay in calls, if the primary dial-peer is not matched.
Thanks & Regards,
Sanadh