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

Cisco CUCM MEDIA_TIMER_ACK expiration

jsheppard22
Beginner
Beginner

Cisco CUCM with CallRex QMS integration. Users configured with BIB, phone preferred recording method, and recording profile accepts calls (internal and external) callers, but only one of the audio streams gets recorded. Cisco CUCM call signaling looks correct for the setup, but a SIP_MEDIA_ACK timer expires after 36 seconds and the recording stream gets terminated. CUCM sends a bye in both the direction of the recording server and the end user phone.


25198661.000 |14:16:04.774 |SdlSig |SsDataInd |await_recordingCall_connect |Recording(1,100,162,5216) |RecordManager(1,100,161,1) |1,100,251,3910.6928^10.108.0.65^* |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] SsType=16777246 SsKey=0 SsNode=1 SsParty=17715979 DevId=(0,0,0) BCC=6 OtherParty=17715981 NodeOtherParty=1 clearType = 0 CSS=a51c9b93-c567-5257-3e9d-b8de2f3129d0 CNumInfo = 0 CNameInfo = 0 ssDevType=1 ssOtherDevType=8 FDataType=0 opId=0 ssType=0 SsKey=0 invokeId=0 resultExp=F bpda=F ssCause = 102 ssUserState = 2 ssOtherUserState = 1 PL=5 PLDmn=0 isMultiForkingEnabled=F networkDomain= delayAPTimer=F geolocInfo={geolocPkid=, filterPkid=, geolocVal=, devType=4} cfwdTimerAction=0 matchInterceptPartition= matchInterceptPattern=


25198661.001 |14:16:04.774 |AppInfo |Recording::- (0005216) -handleSsDataIndRelease: ERROR-RecordingSetupFailed!


25198731.001 |14:16:04.782 |AppInfo |SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.108.0.65 on port 49966 index 3990
[4700950,NET]
BYE sip:9b0b0433-e70b-03c3-a41d-80b6cda13f76@10.108.0.65:49966;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.110.0.20:5060;branch=z9hG4bK729cb2c310e32
From: "Call Manager" <sip:10.110.0.20>;tag=1557946~dde0583b-a939-426d-9389-2f0dc1095506-17715975
To: <sip:9201@10.110.0.20>;tag=2c31246b3fed0df7078df267-13a1c4e5
Date: Mon, 14 Aug 2023 18:15:28 GMT
Call-ID: 8ab06580-1ef158d1-3ce95-14006e0a@10.110.0.20
User-Agent: Cisco-CUCM12.5
Max-Forwards: 70
CSeq: 103 BYE
Reason: Q.850;cause=102
Session-ID: 00000000000000000000000000000000;remote=1f35a22b00105000a0002c31246b3fed
Content-Length: 0


25198732.001 |14:16:04.782 |AppInfo |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 10.40.0.25:[5060]:
[4700951,NET]
BYE sip:3300@10.40.0.25:5060 SIP/2.0
Via: SIP/2.0/UDP 10.110.0.20:5060;branch=z9hG4bK729cc6b1a1884
From: "A user" <sip:X.X.X@10.110.0.20;x-nearend;x-refci=17715966;x-nearendclusterid=a companyCluster;x-nearenddevice=SEP2C31246B3FED;x-nearendaddr=9201;x-farendrefci=17715967;x-farendclusterid=a companyCluster;x-farenddevice=SIP_MAIN_ISR;x-farendaddr=14238950511;x-sessionid=3c09668200105000a0002c31246b3fed>;tag=1557947~dde0583b-a939-426d-9389-2f0dc1095506-17715977
To: <sip:3300@10.40.0.25>
Date: Mon, 14 Aug 2023 18:15:28 GMT
Call-ID: 8ab06580-1ef158d1-3ce96-14006e0a@10.110.0.20
User-Agent: Cisco-CUCM12.5
Max-Forwards: 70
P-Asserted-Identity: "Holly Newberry" <sip:4239263951@10.110.0.20>
CSeq: 102 BYE
Reason: Q.850;cause=102
Session-ID: 1f35a22b00105000a0002c31246b3fed;remote=8bda95359d28b3f90277899ab1557947
Content-Length: 0

0 Replies 0
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: