12-21-2012 06:09 PM - edited 03-16-2019 02:50 PM
I've a cucm 8.6. configured to see a voice-gw in h323 mode.
the outgoing calls works quell but the incoming calls arrive on. the voice gw but are not correcly routed
eachone can help me?
12-21-2012 06:22 PM
Please post the output of below:
sh run | s dial-peer
sh run | s translation
also post the below debug for the incoming call:
debug voip dialpeer inout
12-21-2012 06:51 PM
hi thanks for help .
Now I'm noT a le to send the requie ed traces because the customer it's closed.
can I send you All at 27 oc december?
12-21-2012 06:56 PM
hi thanks for help .
Now I'm noT able to send the required traces because the customer it's closed.
can I send you All at 27 of december?
12-21-2012 07:18 PM
No problems. You can post it whenever you get chance, I will or anyone here in the forum will look and help with you that.
12-27-2012 01:38 AM
12-27-2012 01:56 AM
Hi Giancarlo,
Looking at the debugs and the dialpeer config, here is what I see:
Calling Number=000393400971266
Called Number=500
Incoming Dial-peer=50
dial-peer voice 50 pots
tone ringback alert-no-PI
description DIAL-PEER PER CHIAMATE USCENTI VERSO LA PSTN
destination-pattern 0T
progress_ind alert enable 8
progress_ind progress enable 8
progress_ind connect enable 8
incoming called-number .
direct-inward-dial
port 0/0/0
no sip-register
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=1
2: Dial-peer Tag=2
dial-peer voice 1 voip
description chiamata in ingresso su GFLUCM1
destination-pattern 96075..
session target ipv4:172.16.41.240
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
fax rate disable
no vad
dial-peer voice 2 voip
description Chiamata in ingresso su UCM 11
preference 1
shutdown
destination-pattern 5..
session protocol sipv2
session target ipv4:172.16.41.240
dtmf-relay sip-notify
codec g711ulaw
no vad
Looks like the called party is a 3 digit number of 5.. pattern. Dialpeer 2 is in shutdown mode. Is there a reason why it's shutdown? I dont see any voice translation profile applied to dialpeer 1 to strip off the leading digits and to see only 5.. ahead to the CUCM (assuming that you want to send only the last 3 digits 5..). Shut dialpeer 1 and do a no shut on dialpeer 2. That should ideally take care of this issue.
HTH.
Regards,
Harmit.
12-28-2012 08:25 AM
Hi Harmit,
the dial-peer was in shutdown for test.
But I've checked alla configurations and they are ok.
For that I thinked that the problem could be an IOS bug.
I've downgraded the IOS to version 15.1.2 and now all works well!!!!!
Many thanks for your help
Have an Hppy new year
Giancarlo
12-28-2012 10:21 AM
Hi Giancarlo,
Glad to hear that! :-) Wish you a happy new year as well!!
Regards,
Harmit.
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