09-13-2017 06:33 AM - edited 03-18-2019 01:27 PM
Hi
I have a critical strange Issue in my VoIP network.
we have ISR 4351/K9 Router with ISO isr4300-universalk9.03.16.05.S.155-3.S5-ext.SPA.bin
we have CUCM 11.5 an we are using E1 line
the problem is 1st call is successfully establised but when we dial any other number from another ext. it gives buzy tone or disconnected.
Solved! Go to Solution.
09-25-2017 10:28 PM - edited 09-25-2017 10:29 PM
Hi There,
Failed calls happen when the HW-TRANS device is allocated instead of the HW-MTP device. When the calls try and connect when the HW-TRANS device is used, we get an error (in the failed call section below).
WORKING CALL - Resource Allocation:
27616400.004 |05:12:15.100 |AppInfo |MediaResourceCdpc(5330)::sendMtpAllocateRequestToDevice MtpResource=HW-MTP Cepn=ec22edcc-adc9-e399-491b-cf2fe909fb5b
FAILED CALL - Resource Allocation:
27618027.004 |05:13:21.598 |AppInfo |MediaResourceCdpc(5333)::sendMtpAllocateRequestToDevice MtpResource=HW-TRANS Cepn=03197a90-af35-9059-575b-b4f6ddb966a4
.... SOME OUTPUT OMMITED ...
27618198.001 |05:13:21.613 |AppInfo |StationInit: (0147068) OpenReceiveChannelAck Status=1 (Error: Endpoint failed to open receive channel), IpAddr=IpAddr.type:1 ipAddr:0x00000000000000000000000000000000(::), Port=0, PartyID=33570955
Since your HW-MTP and HW-TRANS are in the same MRG, CUCM is load balancing between them for calls made through your H.323 GW which has MTP required enabled. This is why some calls work, and some calls fail (I think this may be related to the fact that your HW-TRANS has passthrough enabled, but I am not 100% sure).
Can you first try removing HW-TRANS from the MRG which is assigned to the MRGL on the H.323 GW? You could also move the HW-TRANS resource to a new MRG which sits below the MRG which contains the HW-MTP inside of the MRGL.
This should correct your issue.
Please let us know if this helps!
*** Please mark answers as helpful and/or correct if appropriate.
09-19-2017 12:09 AM - edited 09-19-2017 07:00 PM
Hi There,
I started taking a look through the debugs, but you have a lot of output and no descriptions of which call is which.
On first glance it looks like it could be a codec issue. I see some cause code 47 messages in there, which usually indicate you have an issue requiring a transcoder, and there is no transcoder available.
It would be a lot easier if you could do the following:
1. Attach a copy of the running configuration of the VGW (remove sensitive info first)
2. Whenever you attach debugs for a test call, list the following info for each call:
a. Start Time
b. Called Number
c. Calling Number
d. Result of the call (failed or good)
3. Grab the following debugs for a working a failed call:
a. debug h225 asn1
b. debug h245 asn1
c. debug voip ccapi inout
Also, please configure "voice iec syslog" in your VGW running-config if you don't already have it. It can generate very useful output in troubleshooting scenarios.
09-19-2017 12:56 AM
09-19-2017 08:26 PM - edited 09-19-2017 08:28 PM
Hi There,
Thanks for sending those debugs.
I compared the 2 calls, Call A (Working - 050648xxx), to Call B (Non-Working 055421xxx).
Here is the comparison between the 2 calls:
Based on this I would suggest you check the following:
If you checked that the region configuration is good and calls still fail, we will need to review the CM trace from UCM in addition to a fresh set of VGW logs in order to continue troubleshooting.
09-20-2017 03:07 AM
09-20-2017 01:43 PM
09-21-2017 12:59 AM
Hi Jonathan,
all ip phones (caller) and gateway are in the same device pool (same region) and none of the devices are using the default region on their setting.
09-21-2017 09:44 AM
Hi there,
Yes, but can you confirm which location the media resources are located?
Can you post a screenshot of "Media Resources > Transcoder" and "Media Resources > Media Termination Point"?
In order to continue troubleshooting past this point, you would need to post the CM trace for the working/failed call.
09-25-2017 03:48 AM
Hi Jonathan,
Find the attached required logs
https://drive.google.com/open?id=0B5PZdkvYVavpTFpnNTQ1NFhYanM
09-25-2017 10:28 PM - edited 09-25-2017 10:29 PM
Hi There,
Failed calls happen when the HW-TRANS device is allocated instead of the HW-MTP device. When the calls try and connect when the HW-TRANS device is used, we get an error (in the failed call section below).
WORKING CALL - Resource Allocation:
27616400.004 |05:12:15.100 |AppInfo |MediaResourceCdpc(5330)::sendMtpAllocateRequestToDevice MtpResource=HW-MTP Cepn=ec22edcc-adc9-e399-491b-cf2fe909fb5b
FAILED CALL - Resource Allocation:
27618027.004 |05:13:21.598 |AppInfo |MediaResourceCdpc(5333)::sendMtpAllocateRequestToDevice MtpResource=HW-TRANS Cepn=03197a90-af35-9059-575b-b4f6ddb966a4
.... SOME OUTPUT OMMITED ...
27618198.001 |05:13:21.613 |AppInfo |StationInit: (0147068) OpenReceiveChannelAck Status=1 (Error: Endpoint failed to open receive channel), IpAddr=IpAddr.type:1 ipAddr:0x00000000000000000000000000000000(::), Port=0, PartyID=33570955
Since your HW-MTP and HW-TRANS are in the same MRG, CUCM is load balancing between them for calls made through your H.323 GW which has MTP required enabled. This is why some calls work, and some calls fail (I think this may be related to the fact that your HW-TRANS has passthrough enabled, but I am not 100% sure).
Can you first try removing HW-TRANS from the MRG which is assigned to the MRGL on the H.323 GW? You could also move the HW-TRANS resource to a new MRG which sits below the MRG which contains the HW-MTP inside of the MRGL.
This should correct your issue.
Please let us know if this helps!
*** Please mark answers as helpful and/or correct if appropriate.
09-26-2017 05:42 AM
09-26-2017 09:20 AM
That is good news, thanks for following up with the results!
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