[cisco-voip] Inbound calls to H323 using CCD over SAF fail with dead air
Jeffrey Girard
jeffrey.girard at girardinc.com
Fri Mar 1 08:18:31 EST 2013
Just for completeness, I solved the problem.
On the config below (on the H323 GW) I had fatfingered the SIP trunk port. I had 5050 and it should have been 5060
All is well now
Jeff
________________________________
From: Ryan Ratliff [rratliff at cisco.com]
Sent: Thursday, February 28, 2013 2:43 PM
To: Jeffrey Girard
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Inbound calls to H323 using CCD over SAF fail with dead air
Too bad DNA is no help. You're going to have to crack open the ccm traces to see what's going on then.
-Ryan
On Feb 28, 2013, at 2:36 PM, Jeffrey Girard <jeffrey.girard at girardinc.com<mailto:jeffrey.girard at girardinc.com>> wrote:
Yeah, DNA does not work with CCD.
Give a block reason of unallocated number.
To confirm, I ran DNA against a number in cluster 2 and it gives the same result, though the call completes correctly.
RTMT shows the pattern 51XX as reachable via SIP to the correct loopback address of the H323.
________________________________
From: Ryan Ratliff [rratliff at cisco.com<mailto:rratliff at cisco.com>]
Sent: Thursday, February 28, 2013 2:28 PM
To: Jeffrey Girard
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Inbound calls to H323 using CCD over SAF fail with dead air
What does Dialed Number Analyzer show for that call? It will indicate if there are alternate matches and tell you what they are.
If you wait for 15 seconds or so what happens to the call?
-Ryan
On Feb 28, 2013, at 2:06 PM, Jeffrey Girard <jeffrey.girard at girardinc.com<mailto:jeffrey.girard at girardinc.com>> wrote:
Ryan -
Thanks for the response.
To be more specific:
From Cluster 1, I pick up a handset and dial 5100. That is a phone registered to the CUCME. Nothing happens. No progress tones, no drops. Just dead air. 5100 never rings. Almost like it was waiting for interdigit timeout.
Replace the handset and then dial 5101 (another phone registered to the CUCME). Same thing.
However, from the CUCME, phone 5100, I can place a call to the Cluster 1 handset. I can also place the call from the 5101 handset.
Repeat the procedure for Cluster 2 with the exact same results both ways.
________________________________
From: Ryan Ratliff [rratliff at cisco.com<mailto:rratliff at cisco.com>]
Sent: Thursday, February 28, 2013 1:28 PM
To: Jeffrey Girard
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Inbound calls to H323 using CCD over SAF fail with dead air
Can you be more specific in how the calls fail? Do they complete (both phones ring, answer and go to connected state) but you get no audio or does the call not complete or just drop?
Audio issues are not typically related to call signaling unless the call drops to reorder after ~15 seconds. They are more commonly simple routing issues between endpoints.
-Ryan
On Feb 28, 2013, at 12:22 PM, Jeffrey Girard <jeffrey.girard at girardinc.com<mailto:jeffrey.girard at girardinc.com>> wrote:
This is a lab network.
I have two CUCM 8.6 clusters using CCD over SAF. Phones attached to both clusters are able to call back and forth.
I just added a H323 gateway into the mix - running CCD over SAF. Two phones registered to the CUCME.
Outbound calls from the CUCME to anywhere all succeed.
Inbound calls from anywhere (both clusters) all fail with dead air.
Both RTMTs show that the pattern (51XX) is reachable.
SAF neighbors are all present as they should be.
A debug voice dialpeer on the CUCME shows no activity when a call is placed inbound to the CUCME.
Stripped CUCME config is below.
Any thoughts?
Jeff
voice service voip
no ip address trusted authenticate
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
sip
bind control source-interface Loopback0
bind media source-interface Loopback0
!
router eigrp SAF_FORWARDER
!
service-family ipv4 autonomous-system 10
!
topology base
exit-sf-topology
exit-service-family
!
!
!
dial-peer voice 1 pots
description Incoming Call Routing
incoming called-number .
direct-inward-dial
!
dial-peer voice 2 voip
description Incoming Call Routing
incoming called-number .
voice-class codec 1
dtmf-relay h245-alphanumeric
no vad
!
dial-peer voice 998 voip
description test dial peer
destination-pattern ....
session target saf
voice-class codec 1
no vad
!
!
voice service saf
profile trunk-route 10
session protocol sip interface Loopback0 transport udp port 5050
!
profile dn-block 10
pattern 1 type extension 51XX
!
profile callcontrol 10
dn-service name CCD
description CCD over SAF
trunk-route 10
dn-block 10
!
!
call
!
channel 10 vrouter SAF_FORWARDER asystem 10
subscribe callcontrol wildcarded
publish callcontrol 10
!
!
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130301/100153a1/attachment.html>
More information about the cisco-voip
mailing list