09-17-2023 04:47 AM
Hi,
I have a problem with consult call transfer. I have SIP trunk with ITSP. When I want to transfer an external call from 7965 to 7945 it drops but from 7945 to 7965 is successful. Both phones can call to each other and outside and blind transfer works without problem. My CUCM version is 11.5.
How can I troubleshoot it? Is it signaling or codec problem?
Solved! Go to Solution.
10-12-2023 07:04 AM
Dear Carlo,
Only Cisco CallManager service logs?
10-12-2023 07:25 AM
Hi.
They could be enough but if you can, please select all services
Thanks a lot
Carlo
10-13-2023 09:12 AM
10-13-2023 09:49 AM
Hi,
As I suspected , there is a real capabiliies mismatch during the transfer:
PreCheckCapabilities, caps mismatch! Xcoder Reqd
and the call ended with no transcoder device configured message
To dig more, you could temporarly set to "detailed" level the CM Service trace goin on Cisco Unified Serviceability Menu -->Trace--> Configuration.
In the Output you sent I cannot see the incoming call.
Please send the complete SDL trace so we can find where to place the fix
Thanks again.
Regards
Carlo
10-14-2023 11:53 AM
10-15-2023 12:44 AM - edited 10-15-2023 12:45 AM
Hi,
On CUCM go to "System--> Enterprise Parameters" and set to "Disabled" the Advertise G.722 Codec option , reset both phones and try again.
If ther transfer fails again please attach a new SDL trace log.
Please let me know
Thanks
Regards
Carlo
10-16-2023 05:11 AM
Dear Carlo,
Thank you very very very much.
May I ask you to explain the problem and solution?
10-16-2023 01:30 PM
Hi,
You are most welcome!
While 7945 negotiated G711ulaw codec on the second call to 7965 before transfer, 7965 to 7945 negotiated G722 on second call and this caused the call drop due to a missing Transcoding resource needed to mix those 2 RTP flows. A Blind Transfer "forces" to use original negotiated Codec in original call. By Disabling the advertisement of G722 codec, all registered deviced on your Cucm Cluster will no longer advertise G722 as usable codec.
HTH
Carlo
11-19-2023 06:55 AM
Hi,
In which line of logs you found this?
11-20-2023 01:21 AM - edited 11-20-2023 01:48 AM
Hi
In the log we can find 2 CI (Call Identifier) that are the 2 call legs of the call: 31706028 which is the CI between CUCM and CUBE (SIP Trunk) and CI 31706034 between CUCM and SCCP Phone with Device Name SEPE84040A38306 which executes the call transfer.
Here you can see that the Call ID becomes a Conference ID because the user with 706 initiate a consult transfer to 710
PayloadType=6 CI=31706034 DiffServ=0xb8 (DSCP=0x2e) Silent=0 MaxFrms=0 G723BitRate=0 PartyId=0x1007569 RFC2833PayloadType=0 mixingMode=0 partyDir=0
09956474.001 |14:57:26.350 |AppInfo |StationD: (0000456) startMediaTransmission conferenceID=31706034 passThruPartyID=16807273 remoteIpAddress=IpAddr.type:0 ipAddr:0xc0a86120000000000000000000000000(<<<IP15>>>) remotePortNumber=31178 milliSecondPacketSize=20 compressType=6(Media_Payload_G722_64k) RFC2833PayloadType=0 qualifierOut=?. myIP: IpAddr.type:0 ipv4Addr:0xc0a8610d(<<<IP7>>>)
Here we can see that the CUCM searches for a transcoding resources but it cannot allocate one.
956995.029 |14:57:31.756 |AppInfo |DET-MediaManager-(12105)::sendMTPXcoderAllocationRequest, (CapCount,Region),SideA:(6,Default), SideB:(1,Default), supressMatchCap=0,MTPNeededForDTMF=0
09956995.030 |14:57:31.756 |AppInfo |SIG-MediaManager-(12105)::sendMTPXcoderAllocationRequest, allocate xcoder(ci=31706040), suppressMatchCap=0, mrgl=18dcfe5d-aab2-9e9e-f97b-5d919584ec56 DeviceCapsReqdMask=0x0
09956995.031 |14:57:31.756 |AppInfo |DET-MediaManager-(12105)::allocateProxies, j=2 XferMode(4 0) CI(31706034 0) mrid(0 0) resrcCI(0 31706040)
09956995.032 |14:57:31.756 |AppInfo |SIG-MediaManager-(12105)::allocateProxies, allocating resources(1), additional res(0)
09956996.000 |14:57:31.756 |SdlSig |MrmAllocateXcoderResourceReq |waiting |MediaResourceManager(1,100,140,1) |MediaManager(1,100,142,12105) |1,100,14,1.44026^*^* |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] CI=31706040 MRGLPkid=18dcfe5d-aab2-9e9e-f97b-5d919584ec56 Kpbs=0 RegionA=Default CapA=6 RegionB=Default CapB=1 SuppressFlag=0 Type=1 DeviceCapablity= [0x0]0 MandatoryCapabilties= [0x0]0 Count=1
09956996.001 |14:57:31.756 |AppInfo |MediaResourceManager::waiting_MrmAllocateXcoderResourceReq - CI=31706040, Count=1
09956996.002 |14:57:31.756 |AppInfo |MediaResourceManager::waiting_MrmAllocateXcoderResourceReq - CREATING CHILD USING MRGL LIST
09956996.003 |14:57:31.756 |AppInfo |MRM::convertScmStringToStdString MRG
09956996.004 |14:57:31.756 |AppInfo |MRM::getXcodeDeviceGivenMrgl
09956996.005 |14:57:31.756 |AppInfo |MRM::getXcodeDeviceGivenMrgl GETTING XCODE FROM DEFAULT LIST <<--Searching for Transcoding resource
09956996.006 |14:57:31.756 |AppInfo |MediaResourceManager::sendAllocationResourceErr - ERROR - no transcoder device configured
09956996.007 |14:57:31.756 |AppInfo |GenAlarm: AlarmName = MediaResourceListExhausted, subFac = CALLMANAGERKeyParam = , severity = 4, AlarmMsg = MediaResourceListName : MRGL
MediaResourceType : 2
MediaResourceTypeValue : Transcoder
AppID : Cisco CallManager
ClusterID : StandAloneCluster
NodeID : CUCM
And here sends the call disconnect.
09956996.008 |14:57:31.756 |AppInfo |GenAlarm: Push_back offset 680 seq 4684
09956996.009 |14:57:31.756 |AppInfo |GenAlarm: Pop offset 681 seq 3684
09956997.000 |14:57:31.756 |SdlSig |MrmAllocateMtpResourceErr |waitResourcesAllocated |MediaManager(1,100,142,12105) |MediaResourceManager(1,100,140,1) |1,100,14,1.44026^*^* |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] CI=31706040 MRGLPkid=
09956997.001 |14:57:31.756 |AppInfo |DET-MediaManager-(12105)::waitResourcesAllocated_AllocateMtpResourceErr, resCI=31706040, numRes=1, numPreRes=0
09956997.002 |14:57:31.756 |AppInfo |DET-MediaManager-(12105)::waitResourcesAllocated_AllocateMtpResourceErr, numRsrcRes=1, sizeRsrcList=1, failCall=1 resAllocationFailReason=Xcoder ipv6mtp=0
09956997.003 |14:57:31.756 |AppInfo |DET-MediaManager-(12105)::cleanUp, send MediaUpdateDisconnectStatus, reConnectType=0, sendErrIndToParent=0, failCall=1
Please let me know if you need further info.
HTH
Regards
Carlo
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