Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Incoming call not working

Hello Guys,

I have an issue with the incoming calls. We I dial the 10 digitss number using my Cell phone, it doesn't go through. I receive a message stating "the call can't go through". But we can call from inside to outside and within the company.

Also when I try to add a dial-peer, an error message stating "Could not add peer" appears.

Could you please help me out?

The gateway is a 3640 H.323.

This is the output of the debug isdn q931. I am dialing 617-717-7982.

Oct 26 2006 02:23:56.129: ISDN Se1/0:23 Q931: RX <- SETUP pd = 8 callref = 0x00E1

Bearer Capability i = 0x8090

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xE1808386

Preferred, Interface 0, Channel 6

Net Specific Fac i = 0x00E7

Calling Party Number i = 0x2181, '6178692545'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '7982'

Plan:ISDN, Type:National

Oct 26 2006 02:23:56.169: ISDN Se1/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x80E1

Channel ID i = 0xA98386

Exclusive, Channel 6

Oct 26 2006 02:23:56.253: ISDN Se1/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x80E1

Cause i = 0x80A6 - Network out of order

Oct 26 2006 02:23:56.301: ISDN Se1/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x00E1

Oct 26 2006 02:23:56.309: ISDN Se1/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x80E1

Thanks,

12 REPLIES
New Member

Re: Incoming call not working

The output of ccapi inout is in attach.

Thanks,

New Member

Re: Incoming call not working

From your output it would seem that your striping digits off.

If your dialing 617-717-7982, but the ISDN is presented with only the last 4 digits, "Called Party Number i = 0xA1, '7982'"

Can you provide the configuration?

New Member

Re: Incoming call not working

Thanks for your help,

Attached is the config

Thanks again,

New Member

Re: Incoming call not working

Sorry, I miss read the initial problem, I thought that you where having problems without bound calls.

I can see from the configuration that there are two matching dial-peers, 7100 and 7200.

I've noticed that the interface F0/0 is missing the command 'h323-gateway voip interface'

The error is in the debug is 'Disconnect Cause=38' this is typically casued by connection issues.

The gateway is not able to make a TCP connection to the CallManager. In the debugs see the gateway trying dial peer 7100 then dial peer 7200. This indicates to me the GW is not able to make a TCP connection to the CCM.

How has the gateway been setup in CallManager, DNS name or IP Address, make sure that Callmanager can resolve the gateway and ping etc.

New Member

Re: Incoming call not working

Thanks for the reply,

Please note that we're able to make outbound calls for any number. 4 digits dialing working fine as well.

May be the h323-gatway command was missing in the config that I posted but I do have that command under the F0/0 Interface. Here's the config for the F0/0 Interface:

interface FastEthernet0/0

ip address 172.16.XXX.1 255.255.255.0

ip route-cache flow

speed 100

full-duplex

h323-gateway voip bind srcaddr 172.16.XXX.1

I See the GW is registered with CCM. As I said the only issue is that I can't receive any calls comming from PSTN network.

Thanks,

New Member

Re: Incoming call not working

I've always used the addtional command "h323-gateway voip interface"

But as you say you can make outbound calls.

Have you tried using the hidden command 'csim start ' to see if the gateway can make the call?

Sorry I can't be anymore help.

New Member

Re: Incoming call not working

I am in desprate need of help for this issue, can someone please help?

Thanks,

New Member

Re: Incoming call not working

sounds like possibly a naming / IP address reference issue with the CallManager and H.323 GW. (I am assuming this is CCM from your session target...) I would try deleting the H.323 entry for this gateway and re-adding it, or, better yet, just Stop and Start CCM service, if you can.....

New Member

Re: Incoming call not working

Thanks for the reply,

My question is why are we able to make outbound call if the session-targat address is wrong. Please consider the following two Dial-peer. For a call coming in from PSTN, which Dial-peer is going to be used? Accroding to me the Dial-peer voice 1001 will be used because the call is coming from PSTN therefore it going to use the PRI. Am I right?

dial-peer voice 7000 voip

preference 1

destination-pattern 7577

session target ipv4:172.16.165.10

incoming called-number .

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

dial-peer voice 1001 pots

preference 1

destination-pattern [2-9].........

direct-inward-dial

port 1/0:23

forward-digits all

Thanks,

New Member

Re: Incoming call not working

Could someone please respond to this posting?

Thanks,

New Member

Re: Incoming call not working

Nobody can help?

New Member

Re: Incoming call not working

Hi,

Outbound calls use the dial-peer pots and incoming calls use the dial-peer voip. Thats why you can make outboud calls even the CCM addres is wrong..

415
Views
6
Helpful
12
Replies
CreatePlease login to create content