05-05-2011 02:31 PM - edited 03-16-2019 04:50 AM
Hi,
We see lots of cause code 47 errors in CDR records for several of our customers 7.1.3 clusters. Customor uses GK controller trunks for intercluster calls and H323 gateways for PSTN calls. No complaints about call drops or anything. Could these be false alarms (e.g. someone calls a number in the DID range that is not configured)?
Below is output from one of the PSTN h323 gateway:
#show h323 gateway cause-codes
CAUSE CODE STATISTICS AT 9w0d
DISC CAUSE CODE FROM OTHER PEER FROM H323 PEER
0 1 0
1 unassigned number (1) 20 483
3 no route to destinatio 126 31
16 normal call clearing ( 5590 24979
17 user busy (17) 32 858
18 no user response (18) 0 5
19 no user answer (19) 1249 55
21 call rejected (21) 1 39
27 destination out of ord 1 283
28 invalid number (28) 0 193
31 normal, unspecified (3 42 553
34 no circuit (34) 0 187
38 network out of order ( 14 13
41 temporary failure (41) 30 29
42 switch congestion (42) 1 4
44 no requested circuit ( 0 13
47 no resource (47) 65 2
63 service or option not 0 8
79 service not implemente 0 4
88 incompatible destinati 0 2
99 ie not implemented (99 0 294
102 recovery on timer expi 14 14
111 protocol error (111) 3 2
127 interworking (127) 0 4
Thanks!
-Mike
Solved! Go to Solution.
05-10-2011 09:26 AM
Typically, 47 cause code is due to a media resource that is a transcoder, MTP, etc... not being available. You should start by looking at CUCM traces for media resource allocation errors and verify that your codecs and regions settings are all correct.
05-10-2011 09:28 AM
Mike -
Cause code 47 typically indicates a problem with negotiating media. Some scenarios where this can arise:
- Allocation of transcoder due to regions/codec.
- Allocation of CFB when attempting to conference.
- Allocation of MTP for DTMF (won't fail a call unless Service Parameter is set to fail call if MTP allocation fails).
If CM is sending the disconnect w/ cause 47, it typically means that CM could not allocate a media resource that is required in order for the call to connect. Or, the media negotiation for the call might have timed out, ie. MxTimeout.
Detailed CM traces for a call which disconnects with cause 47 would help confirm what is happening.
-jt
05-10-2011 09:26 AM
Typically, 47 cause code is due to a media resource that is a transcoder, MTP, etc... not being available. You should start by looking at CUCM traces for media resource allocation errors and verify that your codecs and regions settings are all correct.
05-10-2011 09:31 AM
Thanks! I'll have to track down a specific example of this in a CUCM trace.
05-10-2011 09:28 AM
Mike -
Cause code 47 typically indicates a problem with negotiating media. Some scenarios where this can arise:
- Allocation of transcoder due to regions/codec.
- Allocation of CFB when attempting to conference.
- Allocation of MTP for DTMF (won't fail a call unless Service Parameter is set to fail call if MTP allocation fails).
If CM is sending the disconnect w/ cause 47, it typically means that CM could not allocate a media resource that is required in order for the call to connect. Or, the media negotiation for the call might have timed out, ie. MxTimeout.
Detailed CM traces for a call which disconnects with cause 47 would help confirm what is happening.
-jt
05-10-2011 09:32 AM
Thanks Jtesar. Time to track down a specific trace for this!
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