05-26-2008 01:34 PM - edited 03-15-2019 10:52 AM
Hello,
I need to configure the gw to use h323, i don't have problems with outgoing calls, however the incoming calls don't go through, the main number doesn't ring
this is what i see on thw GW
May 26 21:33:37.299: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x0169
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Called Party Number i = 0x80, '7070'
Plan:Unknown, Type:Unknown
*May 26 21:33:41.339: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x0169
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Called Party Number i = 0x80, '7070'
Plan:Unknown, Type:Unknown
dial-peer voice 900 pots
incoming called-number .
direct-inward-dial
!
dial-peer voice 16 voip
preference 1
destination-pattern ....
session target ipv4:10.2.100.16
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 15 voip
destination-pattern ....
session target ipv4:10.2.100.15
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
dial-peer voice 9 pots
destination-pattern 9[2-9]......
direct-inward-dial
port 0/0/0:23
forward-digits 7
!
dial-peer voice 91229 pots
destination-pattern 91[2-9]..[2-9]......
direct-inward-dial
port 0/0/0:23
forward-digits 11
!
dial-peer voice 911 pots
destination-pattern 9911
direct-inward-dial
port 0/0/0:23
forward-digits 3
what am I missing
thank you
05-26-2008 01:38 PM
Is 10.2.100.15 pingable from router? Is router address configured as GW in it ?
05-26-2008 01:40 PM
yes I can ping 10.2.100.15 (publisher) abd 10.2.100.16 (subscriber)
i didn't understand the second question
05-26-2008 01:50 PM
In the CM you need to configure an h.323 GW with the corresponding address. Then you can look at debug ccapi to see why CM is refusing the call.
05-26-2008 01:53 PM
I have the GW configured in CCM.
and I have the ccapi debug turned on, however on incoming calls the only thing I see is
*May 26 21:51:43.531: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x016A
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Called Party Number i = 0x80, '7070'
Plan:Unknown, Type:Unknown
*May 26 21:51:47.543: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x016A
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Called Party Number i = 0x80, '7070'
Plan:Unknown, Type:Unknown
however for outgoing calls i see the complete output from the ccapi debug
05-26-2008 02:00 PM
You can try debug cch323 but I'm afraid you will only see thta CM is not responding. Perhaps you need to restart something there.
Unfortunately I'm not an expert at CM, hope somebody else can help.
05-26-2008 02:07 PM
I see that the incoming number that telco is sending you is 7070. In the call manager, what do you have programmed as 7070? Do a route plan report in the CCM on DN 7070 and see what comes up. Is it a phone, a CTI Route Point, a translation pattern? If it is a phone, see if that phone that has the DN 7070 on it is registered. If the call hits a translation pattern in the CCM, see that the translation pattern is correctly configured in the CCM. Are you getting ringback when the number is dialed? If not, what message are you getting?
05-26-2008 02:28 PM
7070 is a translation pattern that will translate into 6001, 6001 is a shared line
I have the 2 protocols running on the GW; MGCP and H323, I turn off MGCP with the command "no mgcp" and then I try the call and nothing happens, however if I issue "mgcp" the call goes through
I listen to dead air and then fast busy
05-26-2008 02:33 PM
How is the gateway (PRI) configured in the CCM? Is it MGCP or H.323? If it is an MGCP gateway, under the MGCP PRI configuration, there is an place where you can enter the attendant DN. In the Attendant DN field, enter 7070. Therefore when the call hits the call manager, it will see the call being presented as 7070, which in turn will hit the translation pattern and send the call to the phones that are registered with DN 6001.
Hope that helped
05-27-2008 06:27 AM
If it works as MGCP but not H323, do you have h323-bind configured on the relevant interface?
05-27-2008 07:12 AM
yes
interface Gi0/0
description voice
h323-gateway voip interface
h323-gateway voip bind srcaddr 10.3.100.1
We want to get rid of MGCP due to a few delay issues that we are facing. But I just cannot get the incoming calls to work properly
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: