09-30-2021 10:37 AM
We have configured a cucm with h323 gateway has fxo ports, the outgoing call is working fine, but the incoming disconnects before ring to IP phone.
PSTN>FXO>h323 gateway>CUCM>IP Phone
09-30-2021 11:15 AM
Is it by choice that the call uses dial peer 100 for both inbound and outbound destinations?
09-30-2021 12:43 PM
Line 53 of the debug shows the original call accepted on dial-peer 1. On Line 164 it starts an inbound dial-peer selection again (after having found 100 as the outbound dial-peer) showing the inbound dial-peer of 100. Why? I'm not sure but am researching.
Maren
10-01-2021 03:06 AM
Looking at the debug on a PC in N++ I see that I missed that line <blush>, not all easy to read debugs on a cell phone.
The debugs are however quite thin in the output of what happens between dial peer 1 is selected as the inbound and dial peer 100 is selected as the outbound and then as the inbound also.
In general the debug provided does not really reveal what is going on. I would recommend you to turn of these debugs and re-post the output from this.
09-30-2021 12:26 PM
Your problem description says that the router is an H323 gateway, and I presume that is how it is configured in CUCM. But your dial-peer 100 has the command "session protocol sipv2" which means the router will attempt to signal out to CUCM using SIP and not H323. The two ends must agree for the call to be successful.
Once you have that fixed another issue might be caller-id. The ANI/DNIS indicated in the call leg going up to CUCM the ANI field is blank. If the gateway is set to reject anonymous calls, that might also interfere.
Maren
09-30-2021 02:10 PM
Thanks @Maren Mahoney
I will shutdown all dial-peers pots or voip, then will configure below for incoming call from pstn
dial-peer voice 100 voip
destination-pattern 1015
session target ipv4:10.20.0.70
codec g711ulaw
!
dial-peer voice 202 pots
incoming called-number .
direct-inward-dial
that those are enough in mu configuration or there is another issue?
and why we should delete this command " session protocol sipv2"?
Thanks
09-30-2021 02:58 PM
I'd have to take a deeper look to help writing the dialpeers. @Roger Kallberg is pretty good at that and can hopefully get to it before I do.
As for removing the "session protocol sipv2":
H.323 and SIP are two different signaling protocols that can be used to set up a call. (Two others in the Cisco Collaboration environment are SCCP an MGCP.) If one system (like CUCM) is expecting incoming signaling using H.323, then the router would need to be sending H.323. Similarly, if one end is sending SIP then the other end needs to be expecting SIP.
You wrote that you set up the CUCM-end of the connection as an H323 gateway (Device > Gateway and select H323) and that makes CUCM speak H323. The command "session protocol sipv2" on the router tells the router to use SIP signaling when sending information up to CUCM. By taking that command off of that dial-peer, you are telling the router to return to the default (for the router) protocol of H323.
Maren
10-01-2021 02:25 AM - edited 10-01-2021 04:40 AM
This would be my recommendation for configuration. @Maren Mahoney thanks for the vote of confidence. ':-)'
voice class uri CUCM sip host ipv4:<CM CPE 1> ;CPE Subscriber host ipv4:<CM CPE 2> ;CPE Subscriber host ipv4:<CM CPE 3> ;CPE Subscriber ;add as many line as there are CPE nodes in the CM cluster ! voice class e164-pattern-map 1 description E164 Pattern Map for called number to CUCM e164 +<start of DID number range>T ! voice class server-group 1 ipv4 <CM CPE 1> preference 1 ipv4 <CM CPE 2> preference 2 ipv4 <CM CPE 3> preference 3 description Inbound calls from PSTN to CUCM ! voice class sip-options-keepalive 1 description Used for Server Group SIP OPTIONS PING ! trunk group FXO hunt-scheme round-robin both translation-profile incoming PSTN-IN translation-profile outgoing PSTN-OUT ! voice-port 0/0/3 trunk-group FXO input gain 7 !set to match your region output attenuation -4 cptone SA !set to match your region timeouts call-disconnect 1 timeouts wait-release 1 timing hookflash-out 50 !set to match your region description *** local PTT <number> *** bearer-cap Speech caller-id enable ! voice-port 0/1/0 trunk-group FXO input gain 7 !set to match your region output attenuation -4 cptone SA !set to match your region timeouts call-disconnect 1 timeouts wait-release 1 timing hookflash-out 50 !set to match your region description *** local PTT <number> *** bearer-cap Speech caller-id enable ! dial-peer voice 1000 voip description Outbound calls from CUCM translation-profile incoming NOPLUS-IN voice-class codec 1 session protocol sipv2 incoming uri via CUCM dtmf-relay rtp-nte sip-kpml no vad ! dial-peer voice 1010 voip description Inbound calls to CUCM subscribers modem passthrough nse codec g711ulaw session protocol sipv2 session server-group 1 destination e164-pattern-map 1 voice-class codec 1 voice-class sip options-keepalive profile 1 dtmf-relay rtp-nte sip-kpml no vad ! dial-peer voice 100 pots tone ringback alert-no-PI description Inbound calls from PSTN incoming called-number . direct-inward-dial ! dial-peer voice 110 pots trunkgroup FXO tone ringback alert-no-PI description Outbound calls to PSTN destination-pattern 0T !set to match what you use as the breakout number progress_ind setup enable 3 progress_ind alert enable 8 progress_ind progress enable 8 progress_ind connect enable 8 progress_ind disconnect enable 8 no digit-strip no sip-register !
Please note that this configuration is for using SIP as the control protocol for your voice gateway in CM. Frankly that is a much better option these days than using H.323.
If you anyway want to stick with H.323 this would be the configuration for that.
voice class e164-pattern-map 1 description E164 Pattern Map for called number to CUCM e164 +<start of DID number range>T ! trunk group FXO hunt-scheme round-robin both translation-profile incoming PSTN-IN translation-profile outgoing PSTN-OUT ! voice-port 0/0/3 trunk-group FXO input gain 7 !set to match your region output attenuation -4 cptone SA !set to match your region timeouts call-disconnect 1 timeouts wait-release 1 timing hookflash-out 50 !set to match your region description *** local PTT <number> *** bearer-cap Speech caller-id enable ! voice-port 0/1/0 trunk-group FXO input gain 7 !set to match your region output attenuation -4 cptone SA !set to match your region timeouts call-disconnect 1 timeouts wait-release 1 timing hookflash-out 50 !set to match your region description *** local PTT <number> *** bearer-cap Speech caller-id enable ! dial-peer voice 1000 voip description Outbound calls from CUCM translation-profile incoming NOPLUS-IN voice-class codec 1 incoming called-number . dtmf-relay h245-alphanumeric rtp-nte no vad ! dial-peer voice 1010 voip description Inbound calls to CUCM subscriber 1 preference 1 modem passthrough nse codec g711ulaw session target <CM CPE 1> destination e164-pattern-map 1 voice-class codec 1 dtmf-relay h245-alphanumeric rtp-nte no vad ! ! dial-peer voice 1011 voip description Inbound calls to CUCM subscriber 2 preference 2 modem passthrough nse codec g711ulaw session target <CM CPE 2> destination e164-pattern-map 1 voice-class codec 1 dtmf-relay h245-alphanumeric rtp-nte no vad ! dial-peer voice 1012 voip description Inbound calls to CUCM subscriber 3 preference 3 modem passthrough nse codec g711ulaw session target <CM CPE 3> destination e164-pattern-map 1 voice-class codec 1 dtmf-relay h245-alphanumeric rtp-nte no vad ! dial-peer voice 100 pots tone ringback alert-no-PI description Inbound calls from PSTN incoming called-number . direct-inward-dial ! dial-peer voice 110 pots trunkgroup FXO tone ringback alert-no-PI description Outbound calls to PSTN destination-pattern 0T !set to match what you use as the breakout number progress_ind setup enable 3 progress_ind alert enable 8 progress_ind progress enable 8 progress_ind connect enable 8 progress_ind disconnect enable 8 no digit-strip no sip-register !
There are other part of the config that is not shown, like translations as such, as these are very specific to your needs. So you'd need to adapt the suggested configurations to match your specific needs.
10-01-2021 09:00 AM
Wow, @Roger Kallberg! Once again hitting it out of the park. -- Maren
10-01-2021 11:25 AM
Now you will make me blush.
10-01-2021 02:16 PM - edited 10-01-2021 02:18 PM
<never mind....>
Maren
10-05-2021 07:20 AM
Hi Faisal,
You've got a lot of great advice here from Roger and Maren and I'd say between the two of them they've more than answered your question.
Only small suggestion (and it's very small) would be to add in H225 timeout values if sticking with H.323. This will ensure CUCM node redudancy in the event of a failure
So basically apply the config Roger suggested, but add the following config to your dial-peers facing CUCM:
voice-class h323 1
h225 timeout tcp establish 3
dial-peer voice 100 voip
description ***To CUCM Node 1***
voice-class h323 1
dial-peer voice 101 voip
description ***To CUCM Node 2***
preference 1
voice-class h323 1
Note this is only if you have more than one CM node. If you've got a single node, then it doesn't matter.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide