cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1340
Views
0
Helpful
7
Replies

voip call connected and other side ring out

Mohamed Gaber
Level 1
Level 1

I have CallManager connected to a gateway at one site. On the other site I have CME. When I do a call from an IP Phone on the CM to an IP Phone on CME, the call rings out at the other side. But when it answers and the phone displaye connected. The IP Phone on the CM still ring out and not get connected.

Calls from CME to CM works well when it is answered.

It seems to me a signaling problem, but I could not solve.

Need Support.

1 Accepted Solution

Accepted Solutions

Looking at the latest file with debugs and config, I am able

to piece together following for call flow/setup:

ip phone---CCM----h323------R1----h323------PSTN/CME

If the above is correct then R1 is basically acting as a CUBE/IPIPGW

for h323 to h323.

Debugs from R1 show that its the incoming IP leg that's dropping first

with cause 47 (no resource)

Have u checked that Region setting between the calling ip phone and

h323 trunk/GW to R1 is set for g729 codec ?

Also add following on R1:

voice service voip
allow-connections h323 to h323
h323
  h225 connect-passthru  <--------

DK

View solution in original post

7 Replies 7

Nathan Compton
Level 4
Level 4

Sounds like a registration issue.  Is the CME registered as a H323 Gateway to the CUCM?  Is it SIP? Check source interfaces and source IP addresses to make sure everything is registering with the correct CME IP address. 

Assuming you are using h323 between CCM and CME ?

Is there any other device (like a FW/PIX/NAT router etc.) between the two?

It does sound like a signaling issue...can u provide following debugs for one

failed call ?

deb voip ccapi inout

deb h225 asn1

deb h245 asn1

Pl. include CME config along with ANI/DNIS for the test call and flow.

Thx.

DK

Thanks Dilib

Requested debug is attached.

Note that calls initiated from CME works well.

Thanks Adam.

CME is not registered to CM. CM is using local GW which is configured as H323 GW for outgoing calls. On the local GW two VOIP dial-peers are configured. On pointing to CM and other pointing to CME. Allow connection H323 to H323 is configured. CME has VOIP dial-peer pointing to the GW at CM side.

When I configure CME as H323 GW on CM it works well. The problem is when using the GW in the middel.

Looking at the latest file with debugs and config, I am able

to piece together following for call flow/setup:

ip phone---CCM----h323------R1----h323------PSTN/CME

If the above is correct then R1 is basically acting as a CUBE/IPIPGW

for h323 to h323.

Debugs from R1 show that its the incoming IP leg that's dropping first

with cause 47 (no resource)

Have u checked that Region setting between the calling ip phone and

h323 trunk/GW to R1 is set for g729 codec ?

Also add following on R1:

voice service voip
allow-connections h323 to h323
h323
  h225 connect-passthru  <--------

DK

Thanks so much Dilip

It works now. The IP Phone get connected at both sides after the IP Phone at CME answers the call.

I have a new problem now. After seconds the call disconnected. Before this I hear a hold tone.

Note that I'm using IP Communicator (on PC) and IP Blue (on Virtual PC) softphones, so I could not test by speaking.

Also, I don't have this problem when calls initiate from CME side.

New debugs at both sides are attached.

I have more question. Why I see gatekeeper messages, while I'm not doing any gatekeeper configuration?