Class Snap

Class Snap

Monday, March 31, 2014

Incoming call to CUCM from Router (registered as H.323) fails with the following "debug voice ccapi inout" output (Disconnect Cause Value = 38)

Outgoing Dial-peer=2001 
Mar 17 21:30:36.011: //48/B5B294ED8093/CCAPI/cc_api_event_indication: 
Event=92, Call Id=48 
Mar 17 21:30:36.011: //48/B5B294ED8093/CCAPI/cc_api_event_indication: 
Event Is Sent To Conferenced SPI(s) Directly 
Mar 17 21:30:36.015: //48/B5B294ED8093/CCAPI/cc_api_call_disconnected: 
Cause Value=38, Interface=0x48C65898, Call Id=48 
Mar 17 21:30:36.015: //48/B5B294ED8093/CCAPI/cc_api_call_disconnected: 
Call Entry(Responsed=TRUE, Cause Value=38, Retry Count=0) 
Mar 17 21:30:36.015: //47/xxxxxxxxxxxx/CCAPI/ccCallReleaseResources: 
release reserved xcoding resource. 
Mar 17 21:30:36.015: //48/B5B294ED8093/CCAPI/ccCallSetAAA_Accounting: 
Accounting=0, Call Id=48 
Mar 17 21:30:36.015: //48/B5B294ED8093/CCAPI/ccCallDisconnect: 
Cause Value=38, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect C 
ause=38) 



Things to check that might rectify the issue: 

Once you run the debug and you get a "Disconnect Cause Value of 38", run a "show dialplan number xxxx (where xxxx is the number that you are sending to cucm)" and it will give you a description of the last Disconnect Cause Value (so in this case 38 which shows us "network out of order").... 

Basically make sure you have bound your h323 to an interface on the router 

interface fastethernet 0/0.102 
h323-gateway voip bind srcaddr x.x.x.x (interface of the router, should be the same interfafce ip that you registered your router in cucm with)

3 comments:

  1. what about when you are getting this error and are using MGCP for call manager registration?
    mgcp bind control source-interface GigabitEthernet0/1.300
    russellstrei@gmail.com

    ReplyDelete
  2. I'd remove the bind for MGCP, say no mgcp; mgcp and then try the call and then bind back... also remove the "isdn bind l3 ccm-manager" and put it back ... sorry I don't frequent my blog too often.

    ReplyDelete
  3. I'd remove the bind for MGCP, say no mgcp; mgcp and then try the call and then bind back... also remove the "isdn bind l3 ccm-manager" and put it back ... sorry I don't frequent my blog too often.

    ReplyDelete