Recording: CUBE disconnects Cisco MediaSense right after recording begins
From DocWiki
(Difference between revisions)
m (1 revision) |
m (1 revision) |
||
| (One intermediate revision not shown) | |||
| Line 20: | Line 20: | ||
! '''Associated CDETS #''' | ! '''Associated CDETS #''' | ||
| CSCtz41118 | | CSCtz41118 | ||
| + | [[Category:Cisco_MediaSense,_Release_8.5]] | ||
| + | [[Category:Cisco_MediaSense,_Release_9.0]] | ||
|} | |} | ||
Latest revision as of 18:57, 14 August 2012
CUBE disconnects Cisco MediaSense right after recording begins
| Problem Summary | CUBE sends BYE to MediaSense while call is still active. Only the brief beginning of the call gets recorded. |
|---|---|
| Error Message | Call Control Service log contains BYE request from CUBE with “Reason: Q.850;cause=102” header |
| Possible Cause | See CSCtz41118. CUBE terminates the forked media because it inappropriately detects media inactivity from MediaSense. |
| Recommended Action | For now, disable RTP and RTCP media inactivity timers in IOS. Once CSCtz41118 is resolved in a version of IOS which is supported by MediaSense, upgrade your version of IOS and re-enable media inactivity timers if desired. |
| Release | Release 8.5(4), Release 9.0(1) |
| Associated CDETS # | CSCtz41118 |
